The Job File: What Belongs In It

Why this matters

When a dispute, a chargeback, a warranty claim, or an insurance question lands, the difference between a thirty-second reply and a losing fight is whether everything about that job lives in one place. Most shops have the records, scattered across a phone's camera roll, a texting app, a paper invoice, and someone's memory. Scattered records lose, because the one that matters is the one you cannot find when you need it. A job file is simply the discipline of putting everything about a job in one record as you go. It is the single best protection a small shop has, and it costs almost nothing if you build it during the work instead of after.

What a job file is

A job file is the complete record of one job, kept together: who, what, when, what was agreed, what was found, what was done, and what was said. It is not extra busywork. It is the same information you already generate, captured in one place instead of five.

The test of a good job file: if a customer disputed this job a year from now, could you answer every claim from this one record without relying on memory? If yes, the file is doing its job.

The core contents

Every job file should carry these, built up as the job moves.

• The agreement. The estimate or work order with scope and price, and the customer's authorization to proceed.
• Customer and site details. Contact info, address, access notes.
• Pre-existing conditions. Photos and notes of anything already damaged near your work, captured before you started. See the related article.
• Before and after photos. The condition you were hired to fix, and the completed work.
• Change orders. Any added or removed scope with the price and the customer's written approval.
• Flagged conditions. Hazards or recommended repairs you found, what you advised, and whether they declined.
• Communication. The key text and email exchanges, especially approvals and declinations.
• Completion record. Sign-off, final invoice, and what was done.
• Payment record. How and when they paid, and the authorization behind it.

When each piece goes in

The file is strongest when it is built in order, as the job happens, because each piece is created at the moment it matters.

1. At booking and sale: customer details, the estimate, the authorization.
2. On arrival, before work: pre-existing damage photos and notes.
3. During the job: before photos, any change-order confirms, any flagged conditions.
4. At completion: after photos, the sign-off, the final invoice.
5. At payment: the payment and its authorization record.

A piece captured at the right moment is clean evidence. The same piece reconstructed weeks later is a guess, and it shows.

Why one place beats five

Records scattered across apps and devices fail in the exact moment you need them.

• You cannot find them fast. A dispute has a deadline. A photo lost in ten thousand camera-roll images might as well not exist.
• You cannot prove they belong together. A photo with no link to the job is just a photo. In the job file, it is evidence of this job, this customer, this date.
• You lose them when a device dies. A thread only on one phone is gone when that phone is gone.
• Someone else cannot pick it up. If the dispute lands while you are out, can your office answer it from the record? Only if it is all in one place.

The discipline that makes it work

A job file system only protects you if it is used every time, not just on the jobs that feel risky.

• Build it on every job, because you do not know in advance which one gets disputed. The habit has to be automatic.
• Capture in the moment, not at the end of the week. Same-day records carry weight; backfilled ones do not.
• Keep it consistent so anyone can find what they need without hunting.
• Retain it. Disputes, chargebacks, and warranty issues can surface long after the job. Hold the file as long as your exposure lasts; confirm record-retention norms for your trade and any insurer requirements.

The mental model

Think of the job file as the story of the job, told in documents, while it is still true. You are not predicting which job goes sideways; you are making sure that whichever one does, the answer already exists in one place. The shops that get burned are not careless about the work. They are careless about the record. Build the file as you go, keep it together, and most disputes end the moment you open it.

References

• Trade-standard practice for service job documentation and recordkeeping
• Your insurer's and payment processor's record-retention and evidence requirements (confirm specifics)
• See related: The Pre-Existing Damage You Need to Flag; The Record That Wins the Chargeback; The Text Thread as Your Paper Trail