What To Write Down and When

Why this matters

The difference between a shop that wins disputes and one that loses them is rarely who was right. It is who wrote it down, and when. A note made on site, the same day, while the details are fresh, is evidence. The same facts reconstructed from memory three months later are an argument. Most techs under-document because writing feels like time stolen from real work, and then they pay for it the one time a job goes sideways. The skill is knowing which moments demand a record and which do not, so you capture what matters without drowning every job in paperwork. This is that map.

The test: would this hurt to not have later?

You cannot write down everything, and you should not try. Apply one filter to decide: if this job came back on me in six months, would the absence of this note cost me? If yes, write it. The high-value records cluster around a few predictable moments:

  • Anything a customer approved or declined. Decisions are the first thing people misremember.
  • Anything that changed from the plan. Scope growth, a substitution, a delay, a surprise.
  • Anything unsafe, damaged, or pre-existing. Conditions you did not create but could be blamed for.
  • Anything you were told that you are relying on. "The landlord said go ahead," "it's been doing this for weeks."
  • Anything that felt off. A hostile customer, a sketchy request, a job your gut flagged.

If a moment hits one of those, it earns a line in the record.

The timing rule: contemporaneous beats accurate-from-memory

When you write matters as much as what you write. A record made at the time carries weight precisely because it could not have been shaped by hindsight.

  • On site or same day, always. Memory degrades fast and a note written a week later is easy to attack as reconstruction.
  • Before you leave, for anything contentious. A refusal, a dispute, a hazard, an approval of extra work. Do not drive off intending to "write it up tonight."
  • Time-stamp it. A record with a date and time is far stronger than a floating note. Most job systems stamp automatically; leave that on.
  • Do not backdate, ever. If you missed it, note it honestly as recalled later. A backdated record, once exposed, destroys the credibility of every record you keep.

What good notes actually look like

A note is evidence only if it states facts a stranger could trust. The failure mode is vague, the second failure mode is editorial.

  • Specific, not general. "Found water staining at the base of the wall, photographed, customer says pre-existing" beats "some water damage."
  • Factual, not emotional. "Customer declined recommended repair after risk explained" is a record. "Customer was rude and cheap" is a liability that makes you look like the problem.
  • Names and times. Who you spoke with, when, what was decided. "Spoke with Maria at 2:40, approved the added line."
  • What was said, not what you assume. Record the statement, not your interpretation of their motive.

Write every note as if it might be read aloud later by someone who was not there. Because it might.

A field key for the common moments

Moment Write down When
Arrival Starting condition, access, anything pre-damaged On arrival, with photos
Approval of extra work What, the price, who approved, the time Before doing the work
Customer declines a repair What you found, the risk explained, that they declined Before leaving
Substitution or change What changed and why, that it was approved At the time
Unsafe condition found The hazard, what you did, who you told On site
Something you were told The statement and who said it Same day
Completion Final state, test result, sign-off At completion, with photos

What you do not need to write down

Over-documenting buries the records that matter and wastes time. You do not need a narrative of routine, uneventful work that went exactly as scoped and was signed off. The signed scope and the completion photos already tell that story. Save the written detail for the exceptions: the decisions, the changes, the hazards, the things that deviated. A job record that is all signal and no noise is the one you can actually use when you need it.

Where it has to live

A note in a tech's head, or on a scrap in the truck, or in a personal app, is not a business record.

  • On the job record, tied to the customer and the date, retrievable by anyone in the office.
  • Durable past your liability window. Disputes and warranty claims surface late.
  • Backed up, not sitting only on one device that can be lost or wiped.

The judgment to bank

Document the decisions, the changes, the hazards, and the things you were told, and do it the same day with a name and a time on it. Skip the narration of routine work. The note that protects you is the one that already existed when the dispute started, written when you had nothing to gain by shaping it. That is what makes it believable, and believable is the whole game.

References

  • Trade-standard practice for contemporaneous job documentation
  • Your insurer's claims guidance on record-keeping and what they require to defend a claim
  • Your company's documentation and data-retention policy
  • See related: The Photo Evidence Habit; Protecting Yourself From He-Said-She-Said