You do not win a job site dispute by proving your work was good. You win it by producing a dated, boring, complete record of what happened, in an order that somebody who was not there can follow.
That distinction is the whole game. A UK adjudication practice put it in one line worth taping to a truck dashboard: ask a contractor what the dispute was about and they will tell you about the work, ask the adjudicator and they will tell you about the paperwork.
Most guides on this topic tell you to take before and after photos and get change orders in writing. Correct, and not enough. Photos and change orders are what you build in advance. This article is about the other half, the part almost nobody writes down: what you do in the hours and days after somebody accuses you of something, and how to build a record that survives the specific place the fight ends up.
A dispute is a timeline problem, not a photo problem
Nearly every contractor already takes photos. The photos are rarely the problem. The problem is that they sit in a camera roll with 600 others from four other jobs, with no note, no location and no order, and reconstructing a story you already lived takes an hour you do not have.
Contractor Magazine described the exact failure in July 2026: a camera roll strips out the two things that turn a photo into evidence, where it was taken and why it mattered. A picture of a clean solder joint proves nothing on its own. The same picture tied to a unit, a spot in the house, a date and a one line note is a record you can stand behind.
So the unit of documentation is not the photo. It is the entry: a date, a location, a plain language observation, and whatever attachment supports it. Entries stack into a timeline. Timelines are what people who were not there can actually read.
By the numbers
The four things that decide most construction disputes, per adjudication practice: was there a signed contract, was the variation instructed in writing, are there dated photographs, and does the correspondence exist. Three of the four are writing, not pictures.
The three records, and only one of them usually wins
There are three kinds of record on any job, and they carry very different weight.
The contemporaneous record is what you made while the work was happening, before anybody was arguing. Photos from the pre-work walk, the daily entry, the delivery ticket. This is the strongest thing you own precisely because you made it when you had no reason to lie.
The shared record is the part of that record you sent to the customer at the time. The same-day photo email, the confirmation text, the invoice with the extras listed. This is usually what actually ends the dispute, because it is dated by a third party, it proves they had the information, and their silence at the time becomes part of the story.
The dispute record is everything you write after the accusation. It has a place, but it is the weakest of the three and everybody reading it knows why. A record assembled after a dispute has started invites the question of whether it is what it claims to be.
Most contractors have a decent contemporaneous record, almost no shared record, and end up trying to win on the dispute record. That is backwards, and it is the single cheapest thing to fix.
Rule 1: Open the file the day the tone changes
You will feel a dispute before you can name it. The emails get shorter. Somebody starts copying a spouse. A client begins querying items they previously asked for. A payment that has always cleared in three days sits for two weeks.
That is the moment to open a dispute file on the job, not the day a demand letter arrives. From that point on:
- Every phone call gets a two line entry afterwards: date, who, what was said.
- Every site visit gets a photo set even if nothing is happening.
- Every verbal request gets confirmed in writing before the tools come out.
- Nothing important happens by phone alone any more.
None of this is aggressive and none of it needs to be announced. It is just a switch from documenting the work to documenting the relationship, and it costs about four minutes a day.
Rule 2: Write down what they said before you answer
When a customer accuses you of something, the instinct is to respond immediately, because you know you did not do it. Resist it for ninety seconds.
Open the job, and write the claim down in their words with the time you received it. "9:12am, homeowner texted, says the crack in the neighbour's slab was caused by our saw cutting on Tuesday."
Two reasons. First, the first version of an accusation is the most specific one you will ever get, and specific claims are the easiest to disprove. Once people start defending a claim it becomes vaguer and harder to pin down. Second, you now have a fixed starting point, so if the story shifts later, the shift itself is documented.
Then check what you already hold before replying. In a widely shared r/Contractor thread from March 2024, a contractor woke up to a message that a neighbour was claiming his crew had cracked their slab during a concrete removal. He had one photograph from before work began showing the crack already there. That single photo was the entire case.
The comments underneath were a catalogue of the same story from both directions. One contractor photographs all the concrete around any property where he rents a lift, after a church tried to make him replace its sidewalks; he showed the before pictures and the claim evaporated. A custom cabinet installer had no before photo when a client accused his crew of scratching a $4,000 fridge, and paid for new doors. An inspector who requires pre-construction photos wrote that he cannot count the times residents and their neighbours have emailed photos claiming damage that was clearly there the week before at the pre-job walk.
Rule 3: Record who instructed it, and whether they could
This is the gap almost nothing on the topic covers, and it is where good documentation still loses.
A demo crew posted on r/Construction in early 2026 about a flood job. The foreman asked the homeowner, standing in her own basement, whether she wanted the drinks bar gone. She said yes. He tore it out. The insurer had hired the general contractor, was paying the bill, and had never approved removing the bar, which was not on the scope of work.
The instruction was real, it was witnessed, and it was worthless, because it came from someone with no authority to authorise that spend on that job.
So your instruction entries need three fields, not one:
| Field | What to capture | Why it matters |
|---|---|---|
| What | The scope in one plain sentence | Vague scope is where the argument restarts |
| Who | Name and role of the person instructing | Occupant, owner, tenant, GC, adjuster and property manager are different authorities |
| Authority | Whether that person can approve the cost | The payer and the person in the room are often not the same |
On insurance work, property management work, tenanted units, HOA work and anything with a general contractor above you, assume the person standing in front of you cannot approve money until you have it in writing from the person who can. It takes one sentence in a text to establish: "Confirming you are approving this and it goes on your invoice, not the insurer's scope."
Rule 4: Send it to them the same day
This is the highest leverage habit in this article and it takes under two minutes.
A photo sitting in your job file is dated by you. The same photo attached to an email you sent the customer at 4:40pm on the day of the work is dated by a mail server, proves they received the information, and starts a clock on their objection. Silence in response to a clear statement is a fact you can point at later.
The pattern is a short end of day message, three to six photos, plain language, and one closing line: "If anything here does not match your understanding, let me know by Friday and I will correct it."
That closing line is doing most of the work. It converts a one way notification into an invitation to object, and an unanswered invitation to object is remarkably persuasive to anyone reviewing the file later.
A practical caution on channel. Messaging apps handle image metadata differently. WhatsApp strips most EXIF data, including GPS coordinates, from photos sent in normal photo mode, though it keeps them when a photo is sent as a document. iMessage does not strip EXIF by default. If the underlying metadata matters to you, keep the original file in the job record and treat what you texted as the notification. There is more on choosing the right channel in our guide to sending job photos to customers.
Most disputes are lost in retrieval, not in the field. If your photos live on four phones and your approvals live in three text threads, we build a custom CRM that keeps every photo, note, approval and message attached to the job, so assembling a dispute file takes ten minutes instead of a weekend.
Rule 5: Record readings, not verdicts
Everything you write becomes evidence, and it becomes evidence for both sides. The note that reads "homeowner is being unreasonable again, third time this week" does not help you and will be read out loud to you at the worst possible moment.
Write observations that a stranger could verify: measurements, readings, times, positions, what was said. Skip characterisations, skip diagnoses you cannot support, and skip anything you would not want the customer to read. This is a discipline worth applying to every job note, not just disputed ones, and we cover the mechanics of it in keeping job notes anyone on the crew can find.
The same rule applies to the ugly parts. If your crew did make a mistake, record it factually and record what you did about it. A documented mistake with a documented remedy is a far better position than a gap in the record that somebody else gets to fill in.
Rule 6: Match the evidence to the forum
Here is the part that costs contractors real money: they build one pile of evidence and assume it works everywhere. It does not. Each forum has its own rules about what counts, and its own clock.
| Forum | What actually decides it | The clock |
|---|---|---|
| The conversation at the kitchen table | Dated before and after photos, sent same day | Hours. Answer while they are still asking |
| A card chargeback | Authorisation, delivery, and the terms the cardholder agreed to. Photos of the work often carry little weight | Typically 20 to 45 days by network, often less from your processor |
| A public review | A calm, specific, dated public reply and nothing else | Days. It is read by future customers, not by a judge |
| Small claims | Contract, written approvals, invoices, correspondence and a clean timeline | Weeks to months |
| An insurance or liability claim | Pre-existing condition photos and the pre-job walk | Report immediately, do not admit liability |
| A licensing or board complaint | Permits, scope, code compliance and your written responses | Fixed statutory response deadlines |
The chargeback row is where trades get ambushed, because the evidence that feels most convincing to you is often not the evidence the network scores. An auto glass shop posted on r/smallbusiness after losing a chargeback on a windshield over $2,200. He had a copy of the customer's ID matching the card, multiple signed receipts, the VIN, and security video of the man standing in his shop. He lost, because the payment had been taken over a link and the network would not accept the shop video for a card not present transaction.
Another operator submitted a signed authorisation form, images of the card and ID, a police report and CCTV of the customer loading materials, and received a one line answer: reversal rejection, chargeback cannot be remedied. A third lost a $750 dispute despite having a signed agreement on file, because of a single address verification mismatch on the original charge. In his words, everything else in the file was beside the point.
That is the lesson in three stories. Great evidence in the wrong category loses. If a dispute reaches a card network, the shape of the transaction matters as much as the truth of it, and the deadlines are brutally short. Our guide on handling a chargeback from a customer covers those mechanics in detail.
Rule 7: Never repair the record backwards
Once a dispute is live, you will find gaps. There will be an approval you never got in writing, a day with no photos, a call nobody logged. The temptation is to quietly fill them in.
Do not. Adding an entry today describing what you remember is legitimate, provided it carries today's date and says that is what it is. Editing an entry from three weeks ago, or setting a file date backwards, or recreating a change order and treating it as original, converts a documentation problem into a credibility problem. You can survive a thin record. You cannot survive being caught fixing one.
The same applies to the parts of the record you do not like. If your file shows three variations carried out with no recorded instruction, that is uncomfortable to read, and it is also information you need before you decide whether to fight or settle.
What to do when you already have nothing
Sometimes you get to the accusation and there is genuinely no record. It happens most often on the small side jobs and the favours.
An r/Construction post that drew over 300 comments described exactly this: a worker agreed with a customer to handle some obstructions outside the main contract, cash, nothing signed. Three thirteen hour days and about $3,500 of his own money in materials later, the customer decided it should have been included in the original job and stopped responding. His supervisor's answer was that nothing could be done, because nothing was signed first.
If that is you, four things still help:
- Reconstruct honestly and date it today. Bank records, supplier receipts, fuel and toll records, phone logs, location history and truck GPS all carry independent dates you did not create.
- Ask for the account in writing. A calm message asking the customer to confirm their version often produces a written admission of the parts that are not in dispute.
- Move while you still have leverage. Anything unfinished, any material you still hold and any warranty you have not yet issued is worth more before the job is closed than after.
- Price the fight honestly. Some disputes are cheaper to settle than to win, and the record you build now is mostly about not being in this position on the next job.
The dispute file: what to assemble
When it goes past a conversation, somebody will ask you for everything. Hand over one organised bundle, not a folder dump. It should contain:
- The signed agreement and any attached scope or specification
- Every approved change, with the date, the requester and the amount
- The complete photo set in date order, with locations noted
- Daily entries covering the disputed period
- Every invoice and payment record, including deposits and credits
- The full correspondence, exported rather than screenshotted where you can
- A one page timeline in plain language, written last
That last page is the one people actually read. Ten to twenty dated lines, no adjectives, no argument. If your timeline is clean and complete, most of the time the dispute stops there, because the other side can see what a full record looks like and can also see they do not have one.
The bottom line
Documentation only feels like overhead until the week it is worth the entire job. The habits that decide it are unglamorous: an entry rather than a photo, a same-day message rather than a private file, a name and an authority beside every instruction, observations rather than opinions, and a record that runs forwards only.
Build that and most disputes end in the driveway, which is where you want them, because the ones that get past the driveway are decided by people who were never there and can only read what you wrote down.