Document Before vs During vs After on a Disputed Job Decision Matrix

Why this matters

When a job is likely to be disputed, the technician who documented at the right moments wins the disagreement and the one who reconstructed it from memory afterward loses. Pre-existing damage, ambiguous scope, warranty questions, and unhappy customers all turn on a single question: what was the condition, and when? Documentation has three windows, before the work, during the work, and after the work, and each window captures evidence the others cannot. Knowing what to capture in each window, and recognizing when a job carries dispute risk so you raise the bar before you start, is a process skill that protects you and the customer alike. This applies to every trade equally.

The options

There are three documentation windows, and on a dispute-prone job you use all three deliberately rather than relying on one:

• Before: capture the as-found condition before you touch anything, pre-existing damage, prior work, the starting state, and the agreed scope.
• During: capture the work in progress, what you uncovered, the measurements that drove decisions, and anything you discovered that changed the scope.
• After: capture the completed state, the as-left condition, test results proving the fix, and the customer's acknowledgment.

The decision matrix is about which window carries the weight for a given dispute risk, and what specifically each window must capture.

When each wins

Before-documentation wins the dispute when: the argument is about pre-existing damage or condition ("you broke that" / "it was already cracked"), the scope itself is contested, or the customer may later claim the situation was different than it was. The before window is the only one that can prove a condition existed prior to your work. It is irreplaceable; you cannot capture it after you have started. On any job where pre-existing damage is plausible, before-documentation is mandatory.

During-documentation wins when: the dispute is about why you did what you did, what you found, or a scope change you made mid-job. Photos and readings taken as you uncover the problem prove discovery and justify added work. A hidden condition you photographed when you found it is far stronger than one you describe after the fact.

After-documentation wins when: the dispute is about whether the work was completed, whether it works, or the condition you left things in. As-left photos, test results, and a signed acknowledgment close the loop. The after window proves the deliverable; it cannot prove the starting condition, which is why it is never sufficient alone on a disputed job.

Field decision flow

1. Assess dispute risk before starting. Pre-existing damage, vague scope, an already-unhappy customer, warranty exposure, or high value all raise the bar. Recognize this before you touch anything.
2. If risk is real, document the before window first, no exceptions. As-found condition, pre-existing damage, scope agreement. This window closes the moment you start work, so it comes first.
3. Document during for any discovery or scope change. When you uncover a hidden condition or change the plan, capture it as it happens with photos and readings, not from memory later.
4. Document after to prove completion and as-left state. Test results, finished condition, and customer acknowledgment.
5. Match capture to the likely dispute. Pre-existing-damage disputes need the before window; scope-change disputes need the during window; completion disputes need the after window. On a genuinely disputed job, cover all three.
6. Use objective evidence, not adjectives. Timestamped photos and measured readings carry weight; "looked fine" does not.

The single rule that prevents most disputes from going badly: capture the before-state before you touch anything whenever dispute risk is real, because that is the one window that can never be reopened.

Common pitfalls

• Documenting only the finished work. A technician who photographs only the clean, completed result has proof of the deliverable and nothing about the starting condition. After-only documentation is the most common gap and the easiest dispute to lose, because the customer's damage claim has no counter-evidence.
• Reconstructing from memory. Notes written hours later, after a dispute has surfaced, carry far less weight than contemporaneous, timestamped capture. Memory is contestable; a timestamp on a photo taken at the moment is not.
• Vague language instead of objective evidence. "Looked worn" and "seemed fine" are opinions. A measurement, a model number, and a dated photo are facts. On a disputed job, capture facts.
• Underestimating dispute risk at the start. The before window closes the instant you begin, so a technician who realizes only mid-job that the situation is contested has already lost the chance to document the as-found state. Read dispute risk before touching anything.
• No customer acknowledgment of as-left state. A signed or recorded acknowledgment that the work is complete and the system functions closes the after window cleanly. Skipping it leaves "you never finished" arguments open.

A disciplined habit of before-during-after capture on every dispute-prone job costs minutes and prevents the worst outcome in service work, which is a he-said-she-said with no evidence and a customer who feels wronged.

References

• ISO 14224 on as-found and as-left condition recording and contemporaneous documentation of maintenance work.
• NARI documentation and consumer-protection guidance for home-improvement and service disputes.
• ACCA and PHCC service guidance on pre-existing-condition documentation and scope agreement.
• OSHA 29 CFR 1910 recordkeeping principles for contemporaneous, objective condition records (general recordkeeping guidance).