What to Document the Moment a Job Goes Sideways

Why this matters

Once a job goes wrong, whatever gets written down in the next hour becomes the entire record anyone will rely on later, weeks from now when the customer disputes what was offered, months from now if it becomes a chargeback, or the next time this same account calls in upset about something else. This is narrower than general job documentation. It is specifically what to capture the moment something breaks, gets damaged, or triggers a complaint, so the recovery decision is defensible and the outcome is not a dispute about what was actually said and agreed.

Capture the failure itself, in observed facts

Write down what you actually saw or were told, not your interpretation of why it happened.

• What was observed, in plain terms. "Found active drip at the base fitting, floor beneath was wet" beats "there was some kind of leak."
• What the customer reported, in something close to their own words, especially if it is a symptom or timeline detail. "Customer says the noise started the morning after the visit" is more useful later than "customer complained about noise."
• What you have not yet determined. If cause is unknown at the time of writing, say so. "Cause not yet confirmed" protects you from a note that reads, in hindsight, like it assumed something you did not actually know then.

Capture exactly what was said to the customer, and when

This is the part most often skipped, and the one that causes the most disputes later, because the customer's memory of a tense conversation and the business's memory rarely match without a contemporaneous note.

• The apology or acknowledgment given, in substance. Did someone say "I'm sorry this happened," did anyone say anything closer to an admission of fault, note the actual words if they were significant.
• Any promise made, specifically, including a timeframe. "Told customer we would call back within 24 hours with a plan" is a commitment someone now owns and a deadline someone can be held to.
• What was NOT promised, if that was explicitly discussed. If a customer asked for a full refund and was told that was not yet decided, note that the request was heard but not yet answered, so it does not get remembered later as a denial or a yes.

Capture the decision on remedy, once made

When a comp, refund, redo, or discount is decided, the decision itself needs its own clean record, separate from the narrative of the failure.

• What was offered, specifically, and by whom.
• Whether the customer accepted it, and if they wanted something different, what.
• The reasoning, briefly. Noting "moderate confirmed error, proportional redo plus fee waiver offered per severity" gives the next person who looks at this file the logic, not just the outcome, which matters if the same customer has a future issue and someone needs to see the pattern.

Photograph before anyone touches anything, if there is anything physical to see

If the failure involves visible damage, a failed part, or a physical condition, photos taken before any cleanup or repair are worth more than any description written afterward.

• Photograph the condition as found, from more than one angle, with a timestamp if your tools support it.
• Photograph again after the fix, so there is a documented before-and-after rather than a claim of resolution with no visual record.

Timing: write it the same day, not after things calm down

A note written contemporaneously, while the details are fresh and before hindsight has a chance to reshape it, carries far more weight than an accurate-feeling reconstruction written a week later. This applies especially to service-recovery incidents, because the emotional intensity of the moment makes people want to wait until they have "cooled off" to write it up, which is exactly when the specific words used start to blur.

Where the failure-specific record differs from routine job notes

Most jobs do not need a play-by-play, a signed scope and completion photos already tell the story of routine work. A service-recovery incident is the exception that earns the fuller record described here, because the stakes of a later dispute are higher and the details, what was said, what was promised, what was decided, are exactly the facts a dispute turns on. See related: What to Write Down and When for the broader discipline this fits inside.

The judgment to bank

If a customer or a manager asked you next month "what exactly happened and what did we tell them," the record from this hour should answer both halves without anyone needing to remember. Capture the observed facts, the exact commitments made, and the remedy decision with its reasoning, the same day, and the recovery stays defensible no matter how the conversation is remembered later by anyone involved.

References

• Trade-standard practice for contemporaneous incident documentation in service recovery.
• Your insurer's claims guidance on record-keeping for customer-incident disputes.
• See related: What to Write Down and When; A Job Goes Wrong: What to Say in the First Five Minutes Decision Tree.