Job Photos and Documentation: The Record That Settles a Dispute in 2026

TL;DR

Most service businesses treat job photos as a nice habit some technicians have. They are actually the evidentiary basis for three arguments you will have this year, and the difference between winning and losing those arguments is almost never who was right.

As of September 2026 the practical standard is not more photographs. It is fewer, taken at specific moments, timestamped, attached to a job record, and retrievable by customer and date in the time you have to answer a card dispute. This guide covers the three disputes documentation settles, what to capture and when, why an untagged photo is nearly worthless, how to get it done in under a minute, and the two other legs that hold the record up.

The three disputes documentation actually settles

Owners imagine documentation as general insurance. In practice it resolves three specific arguments, each needing different evidence at a different moment.

"That damage was already there." The scuff on the cabinet, the cracked tile by the unit, the dented panel. This one is unwinnable by argument, because the customer is not lying — they genuinely had not noticed it until a stranger worked in that spot. The only thing that settles it is a wide shot taken before anyone touched anything, and the moment for that has passed by the time the accusation arrives.

"The work was never done." Usually not fraud either. It is a landlord who was not present, a spouse who did not see it, or a fault that returned a fortnight later and got remembered as a fault that was never fixed. The answer is an after photograph from the same angle as the before, plus a completion note in plain language and, ideally, a signature.

The card chargeback. Different in kind: your counterparty is a card issuer working from a form, on a clock, deciding on documents. Being right is irrelevant if they take two weeks to assemble from four phones.

Read the right-hand column again, because it is the whole discipline. Every piece of evidence there has one moment when it can be captured, and no later.

What to photograph, and when

The list is short on purpose: a requirement of twenty photographs per job produces zero by the second week.

Before, wide. One shot of the work area from a step or two back, on arrival, before anything is moved. The highest-value image in the set and the one most often skipped, because on arrival the technician is thinking about the fault and not a conversation three weeks away.

The fault itself. A close-up of what is actually wrong, as found. It does two jobs: it supports the price you are about to quote, and it establishes the component's condition before you worked on it.

After, same angle. Matching the before shot's framing matters more than image quality. Two photographs from the same position are an argument; two from different positions are unrelated pictures.

The meter, serial or model plate. The reading at handover, the serial of what you installed, the model of what you worked on. Thirty seconds that pays for itself the first time a supplier asks for a serial you would otherwise drive back for.

Access and site conditions, when relevant. The locked gate, the car parked across the unit, the crawl space nobody mentioned. "Nobody was home" as a note is your word; a timestamped photo of a locked gate is not.

A photo with no timestamp and no job attached is nearly worthless

This is the part that gets missed, and it turns thousands of photographs into no evidence.

An image in a camera roll establishes that something looked a certain way at some point. A dispute is never about appearance in isolation. It is about sequence: was the tile cracked before the technician arrived or after. Answering that needs a reliable time, bound to a job that carries a customer, an address, a technician and an arrival record.

Three failure modes, and most businesses have at least one:

• Photos on personal phones. They exist until the technician changes handset, leaves, or fills the storage, and there is no search. When you need the March job on Oak Street, you are texting a former employee.
• Photos in a shared album with no job link. Searchable by date at best, and nobody remembers the date. The customer's name is the only thing you ever have when a dispute starts.
• Photos attached to a job but never syncing. Captured in a basement with no signal and quietly never uploaded — the cruel one, because the technician did everything right.

The fix is structural rather than behavioural. Capture inside the job itself, in a mobile tool that stamps the time, binds the image to the job and the customer, and queues the upload so a dead-signal basement does not lose it. That is what Tech Mode and the mobile app are for: a technician photographs a water heater and the system supplies the customer, address, technician, timestamp and job identifier without anyone typing. And because that record holds customer premises and personal details, it belongs somewhere with real access control and an audit trail rather than a consumer photo app — see security.

The other two legs: the signature and the completion note

Photographs are one leg of a three-legged record, and they are the leg that proves condition. They do not prove agreement or scope.

The signature. Captured on site at completion, against a line stating what was done and what was charged. Its value is not really legal — it is temporal. It establishes that when the technician left, someone at that address looked at the work and did not dispute it, which is difficult to argue with a month later.

The completion note. Two or three sentences on what was found, what was done, and what the customer was told, written on site rather than from memory at 8 p.m. The most valuable notes record the thing you recommended and the customer declined, because that is the exact sentence you will want when the declined item fails.

Both belong on the same job record as the photographs, alongside the invoice. When the invoicing record and the evidence live together, producing a complete history is one search rather than an archaeology project — a point the service business invoicing and payments guide develops on the payment side.

Getting it done in under a minute

Every documentation policy dies the same way: it survives the pilot and then meets a Friday afternoon with four jobs left.

What survives contact with a busy day has three properties.

Fewer than five photographs. Three on a standard job. A technician who has to decide what to capture captures nothing, so the categories must be fixed and obvious.

Inside the existing flow. If documentation is a separate app or something done later, it is done later, which means never. The camera has to sit inside the job the technician is already looking at.

Checked by the status change, not by a manager. The moment that enforces documentation is the transition to completed. If closing a job prompts for the after photo and the note, the prompt does the supervision — and chasing technicians for photographs is a task that gets abandoned in month two of every attempt.

Then measure the compliance rate rather than the count: the percentage of completed jobs carrying at least a before and an after is the only documentation metric worth reporting.

Chargebacks are decided on what you can produce in a week

A card dispute is not a debate about the work. It is a paperwork race with a deadline.

The issuer asks for evidence that the service was authorised, delivered, and delivered as described. The realistic list is the quote or authorisation, the before and after photographs, the completion note, the signature, the invoice, the payment receipt, and the arrival and completion timestamps showing a technician was at that address at that time.

Every item on that list is something you either had or did not have at the time of the job, and adding it afterwards is worse than not having it.

So the practical test is not whether the photographs exist. Pick a customer name and a rough month from six months ago and time how long it takes to produce the complete set. Minutes is good shape. If it involves asking two technicians to check their phones, you will lose disputes you should win — and the loss is the full amount plus the fee on a job you already paid a technician to complete.

Retrievability by customer and date is the requirement, not storage. This is one of the quieter reasons scheduling and job management belong in one system rather than three, a theme running through best field service management software.

What else the record earns

The dispute case gets owners started. Three other returns make it worth continuing.

Sometimes the photograph is the deliverable. On commercial and property-management work the ranking changes: a manager with forty units is not at any of them, so what they buy is confirmation — a dated record they can forward to an owner, a board or a tenant showing the unit before, the work done, and the unit after. Supply that reliably and you become hard to displace on price. The same holds for any account where somebody must justify the spend to someone else, which makes documentation a sales feature worth naming when you quote.

Callbacks get cheaper. A technician sent to a return visit with the original photographs, the completion note and the parts list arrives knowing what was found and done, which sometimes resolves the visit in the driveway. Without it a callback starts from zero and re-diagnoses a fault someone already diagnosed. Tracking those returns properly is a discipline of its own, covered in warranty and callback tracking.

Supplier claims stop failing. A failed part under manufacturer warranty typically needs the serial or batch number, the install date and evidence of the failure mode. A business that photographed the serial plate at install produces all three from one search and gets the part replaced. A business that did not is asking a distributor to take its word on an install date, and absorbing the cost when that fails.

Retention, privacy, and not photographing more than the job needs

Two boundaries worth setting explicitly, because neither is set by default.

Photograph the job, not the home. Frame tightly, keep people out of shot, and do not capture documents, screens, mail, medication or anything of obvious value. Say what you are photographing and why before starting — one sentence, delivered as routine, prevents nearly all discomfort. Customers are relaxed about a before and after of a furnace and entirely reasonably not relaxed about a wide-angle shot of their bedroom.

Set a retention window on purpose. Long enough to cover the warranty you offer plus a margin, because claims cluster at the end of the term. If you warrant labour for a year, two years of job media is sensible and fifteen is not. A defined window is also the answer when a commercial customer eventually asks how long you keep images of their site.

Neither boundary is compliance theatre. They are the difference between a habit customers experience as professional and one they experience as intrusive.

What this costs

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff. Documentation lives on Pro, because that is where Tech Mode, the mobile-first technician experience, Stripe payments and deposits, and the two-way SMS inbox arrive — and where the AI receptionist is included. Agency adds multi-location, the REST API and outbound webhooks, and an activity log with a full audit trail, which is the tier commercial accounts with reporting obligations tend to need.

Extra staff seats are $25/mo per seat on Starter and Pro, the SMS bundle is $19/mo, and annual billing gives you two months free. All plans include a 14-day free trial, there is a live demo with no signup required, and setup takes under five minutes. Full detail is on pricing. A trade-specific setup helps here too — the complete locksmith software guide works through the version where a before photograph of a door and frame does exactly the damage-claim job described above.

Where to start

Do not write a documentation policy. Pick one requirement and enforce it at the completion step for two weeks: no job closes without a before and an after photograph attached to it.

Then run the retrieval test on a customer from four months ago and time how long their full job record takes to produce. That number, not the photograph count, is what a chargeback will be decided on. Then add the completion note, then the on-site signature, in that order — and stop there, because a record with three solid legs beats a policy with twelve requirements nobody follows past the first busy Friday.