Read the letter before it goes

One button drafts whatever hasn't been drafted and shows the exact letter — same sections, same three numbers per line — before anything is sent.

What it is

A modal that is not a summary of the email but the email itself: a section per problem, colour-keyed and ruled, with ordered / arrived / claimed on every line, the remedy, the evidence, and an optional closing note. The builder attaches photos here, adds what they know, and then decides.

Also called: preview the claim · see what the supplier gets · claim review

See it
Read the letter before it goes
Area
Operations
Group
Claims
System
Supplier Order Lifecycle
Solves
3 named problems
01Opening it drafts any missing shortage or damage claim first
02Each section derives 'arrived' from the claim itself, not from the item's live counts
03Photos already taken at the tailgate come in pre-attached; more can be added per claim
The review modal headed 'This is what Harwood will receive', with a red-ruled 'Damaged on arrival' section, an Ordered/Arrived/Damaged table, photo thumbnails and a note box. ClaimReviewModal.tsx. Sample data — no customer information appears here.
How it works
  1. 1Opening it drafts any missing shortage or damage claim first
  2. 2Each section derives 'arrived' from the claim itself, not from the item's live counts
  3. 3Photos already taken at the tailgate come in pre-attached; more can be added per claim
  4. 4A coarse pointer gets a 'Take a photo' button; a desktop gets 'Browse files' instead
  5. 5Escape closes it while nothing is in flight; 'Not yet' leaves the draft standing
Why we built it

'Reporting a bad delivery is a letter to a business relationship the builder depends on — they read it first, add what they know, attach the evidence, and then decide.' The self-consistency rule is a fixed bug: 'Reading the item's live received_qty made the letter contradict itself: receiving got re-saved as complete after the claim was raised, so a line read "ordered 14, arrived 14, missing 3"… A claim is a statement about one delivery, and its own numbers have to add up no matter what happens to the order afterwards.' The device wording note: 'It decides the WORDING, not the capability… on a desktop the same button would open the file picker and look broken.'

The problem
  • A button that fires an email nobody has read
  • A claim whose own arithmetic contradicts itself gets argued rather than paid
  • Evidence gathered at the wrong moment in the wrong place
Sound familiar?
What you get
What you approve is what arrives
The claim's numbers always add up
The right upload affordance per device

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →