Photo Requirements for Every Work Order

An empty photo record is bad.

A worse one is 47 unlabeled pictures in a technician's phone, mixed with lunch photos, screenshots, and two other jobs. The work was real. The photos may even be useful. But when the customer says the scratch was new, the invoice needs support, the warranty question comes back, or the card processor asks for evidence, nobody can tell which photo proves what.

That is why photo requirements belong on the work order, not only in the crew's memory.

A good work order tells the crew what to photograph before work starts, what to photograph while parts are exposed, what to photograph before leaving, and what exceptions need a separate note. It turns photos from "nice to have" into a field record that supports the service report, daily report log, change order, completion sign-off, invoice, warranty file, and dispute packet.

This is not about taking photos of everything. It is about requiring the few photos that let the next person understand the job without guessing.

Put the photo requirement on the dispatch ticket

Do not wait until the crew is already packing up.

Add a photo block to the work order before dispatch:

For a one-truck service business, that block can be short:

Photos required: arrival sink base and floor, shutoff condition before work, replaced trap and supply lines before cabinet contents are returned, leak test, final cleanup, customer sign-off.

For a small construction visit, it may be more specific:

Photos required: pre-existing drywall cracks, floor protection, open wall before patch, moisture reading if taken, first coat area, added patch requested by owner, final cleanup, open item list.

The general service work order should carry those requirements into the field. The daily field handoff report should confirm whether the photos were actually captured, labeled, and attached to the job file before the crew leaves.

Before, during, and after is only the start

"Before and after photos" sounds clear until the job changes.

Before what? After what? From which angle? Did the photo show the whole room, the damaged area, the serial number, the hidden condition, or the cleaned surface? Did the crew photograph the part before it was removed or after it was thrown away? Did the final photo match the approved scope, or only the easiest angle?

Use purpose-based labels instead:

The photo is the backup for the sentence. If the sentence is weak, the photo does too much work.

Weak note:

Done, photos uploaded.

Useful note:

Completed approved vanity faucet replacement. Photos 01-03 show existing corrosion and shutoff condition before work. Photos 08-10 show new faucet, supply connections, drain assembly, and dry cabinet after leak test. Customer declined replacement of left supply stop; see Photo 11 and declined-work note.

That note can support the service report, invoice, warranty, and any later chargeback defense packet.

Use the same photo log fields every time

A photo log does not need to be fancy.

It needs enough structure that the office can find the right proof without calling the crew.

Use these fields:

The job number matters for business records. IRS Publication 583, Starting a Business and Keeping Records tells business owners to keep records that support income, expenses, and credits on tax returns. A job photo is not a tax return by itself, but it often explains why labor, material, equipment rental, warranty cost, or an invoice line belongs to a specific job.

The related document matters for electronic records. The federal ESIGN Act at 15 U.S.C. 7001 generally prevents a signature, contract, or record from being denied legal effect solely because it is electronic, while also addressing retention and reproducibility of electronic records. In plain shop terms: do not rely on a photo that can only be found by scrolling one person's phone. Attach it to the job record in a form the business can reproduce later.

Make the requirement trade-specific

The right photos depend on the job.

Do not give every crew the same vague instruction. "Take photos" is not a requirement. It is a hope.

Use trade-specific prompts:

For digging work, the photo requirement should start before the crew breaks ground. The utility locate photo log should capture the ticket, proposed work area, marks, positive response, and stop-work condition before the auger, trencher, saw, shovel, or mini-excavator starts.

For closeout-heavy jobs, the requirement should carry into the job cleanup checklist, punch list, and completion certificate. The photo should show not only that the task was performed, but that the site was handed back in the condition the customer is accepting.

For jobs that change in the field, the photos should feed the hidden condition and change order workflow. The crew should photograph the condition, stop long enough to describe it, and get price or schedule approval before doing extra work that was not already authorized.

Separate proof photos from marketing photos

Marketing photos are allowed to look polished.

Proof photos need to be boring.

Do not rely on a beautiful final image if the dispute will turn on access, condition, scope, or timing. A proof photo should show the real job file facts:

• the actual address, unit, equipment, or work area;
• the condition before work;
• the part or area that will later be hidden;
• the reading, label, model, serial, tag, or measurement;
• the difference between included and excluded work;
• the customer-supplied material or missing material;
• the final condition from an angle that matches the before photo;
• the exception that explains a return visit or invoice hold.

For example, a driveway pressure washing job may need one nice after photo for the customer. The job file needs more: before condition, excluded oil stain, runoff control, blocked area, final surface from the same angle, and manager sign-off. That is the same logic behind a commercial pressure washing bid: the proof should match the approved surfaces, limitations, wash-water plan, and closeout note.

The same applies to rental work. A landlord or property manager does not need only a pretty "after" photo. They need the reported issue, access condition, repair, possible tenant damage, open item, and final status tied to the rental inspection or maintenance report.

Photograph what will disappear

The most important photo is often the one nobody can take tomorrow.

Photograph before it is covered, thrown away, cleaned, painted, buried, patched, removed, or reset.

Examples:

• pipe routing before drywall patch;
• valve position before cabinet contents return;
• rotten threshold before cutback;
• cracked tile before demolition;
• water intrusion before drying;
• deck ledger condition before flashing;
• electrical label before cover plate;
• trench before backfill;
• utility marks before rain, traffic, mowing, or grading;
• lead-safe containment setup before cleanup;
• replaced part before disposal;
• serial number before equipment panel is reinstalled;
• stain before cleaning;
• customer-supplied part before modification.

For construction employers, OSHA 29 CFR 1926.20 requires accident-prevention programs and frequent and regular inspections of jobsites, materials, and equipment by competent persons. OSHA 29 CFR 1926.21 requires instruction in recognizing and avoiding unsafe conditions. A photo log does not replace those duties, but it can help document the job-specific condition that led to a safety note, stop-work decision, JHA, near miss report, or incident report.

For covered lead-based paint renovation work in target housing or child-occupied facilities, EPA's RRP rules include work-practice standards at 40 CFR 745.85 and recordkeeping requirements at 40 CFR 745.86. Photos do not replace required RRP records, training, notices, or checklists, but a disciplined photo requirement can help the job file show containment, warning signs, cleanup status, and exceptions around a regulated job.

If weather affects the work, write what happened on site. NOAA's Climate Data Online can help with historical weather context, but the crew's photo and note should still say what mattered: wet substrate, standing water, wind exposure, frozen ground, high heat, mud, humidity, blocked access, or drying delay.

Do not use photos as approval

A photo is proof of a condition.

It is not approval for extra work unless the customer actually approved the extra work.

Bad workflow:

1. Crew finds rotten sheathing.
2. Crew sends a photo.
3. Customer replies, "Wow."
4. Crew replaces more sheathing.
5. Invoice includes added labor and material.

That is not a clean approval trail.

Better workflow:

1. Crew photographs the rotten sheathing.
2. Crew writes a short finding in the service report or daily report.
3. Office prices the added work or time-and-material limit.
4. Customer signs or otherwise approves the change order.
5. Crew performs the extra work.
6. Final photos and invoice match the approved change.

The photo supports the finding. The change order supports the money.

This matters for small jobs because field extras often feel too small to document. A $175 material substitution, a second trip, an added patch, a fixture move, a clogged drain that needs camera inspection, or a pressure-washing add-on can become the whole dispute. The written quote, statement of work, and change order should decide scope and price. Photos should make the decision easier to trust.

Label customer damage, contractor damage, and unknown damage carefully

Do not overstate what the photo proves.

If a scratch, leak, crack, dent, stain, broken latch, or missing item was present on arrival, say so only when the crew can support it:

Photo 02: arrival condition, scratch visible on left side of refrigerator door before appliance was moved.

If the crew discovers a condition after work starts, write the discovery honestly:

Photo 09: subfloor rot visible after vanity removal. Condition was not visible during initial walkthrough.

If nobody knows when the damage happened, do not invent certainty:

Photo 14: chip observed on tile at final cleanup. Timing unknown. Crew lead notified office before customer walkthrough.

That kind of wording helps later. It separates facts from blame. It also keeps the photo record useful for the incident investigation workflow, warranty review, customer service call, or insurer conversation.

For customer-facing records, keep the tone clean. Avoid captions like "customer lied" or "owner caused this." Write condition, location, date, and action. Let the document trail do the work.

Protect privacy while keeping the proof

Photos can create their own risk.

Do not photograph more of the customer's home, business, tenant space, vehicle, document, screen, child, medical item, financial paperwork, or personal property than the job requires. Do not upload other customers' data by mistake. Do not use a job photo for marketing without separate permission and a separate review.

Use a simple privacy rule:

Show enough to prove the job, crop or avoid what is unrelated.

The Federal Trade Commission's Protecting Personal Information guide gives the same practical business habit in broader terms: know what personal information you have, keep only what you need, protect it, dispose of it securely, and plan for incidents. For job photos, that means fewer unrelated images, clearer access rules, and cleaner packets when evidence has to leave the shop.

Keep the original job photos in the internal file when they matter for warranty, insurance, payment disputes, or legal review. When you send evidence outside the shop, send a copy with unrelated personal information cropped or redacted, and keep a note of what was shared.

Examples:

For a chargeback defense packet, targeted evidence is better than a raw phone dump. The processor needs enough to match the job, transaction, and disputed service. It does not need unrelated photos, full card numbers, other customer records, or internal commentary that does not prove the work.

Use photos to close the office loop

The work order should send the crew out with requirements.

The daily field handoff report or service report should bring the proof back.

End each visit with five checks:

1. Required arrival photos captured?
2. Required progress or hidden-condition photos captured?
3. Required completion photos captured?
4. Exception photos labeled and tied to next action?
5. Photos attached to the job file before invoice, warranty, closeout, or return scheduling?

Then decide what the photos trigger:

The material takeoff reconciliation workflow is a good example. A photo of five installed fixtures, the remaining boxed fixture, and the delivery label may explain why the invoice changed, why a return is needed, or why a supplier credit is due.

The as-built and redline packet is another. If the photo proves a route, measurement, valve, hidden repair, access panel, or field change that the customer will need months later, promote it into closeout instead of leaving it buried in a daily note.

A one-page photo requirement you can reuse

Use this as the work-order block:

Photo requirements

Arrival:
- Wide photo of work area.
- Existing damage, access issue, blocked area, or customer-supplied material.
- Labels, model/serial, meter, fixture, or room ID when relevant.

During work:
- Hidden condition before covering or disposal.
- Readings, measurements, test results, parts, or labels.
- Any condition that changes scope, price, schedule, safety, warranty, or return trip.

Completion:
- Finished work from same angle as arrival photo when possible.
- Close-up of installed/repaired/cleaned item.
- Cleanup, restored access, final setting, key return, lockup, or customer handoff.

Exceptions:
- Incomplete item, excluded area, customer-declined work, missing material, unsafe condition, weather/access delay, or disputed condition.
- Caption each exception with next action: invoice, change order, return visit, warranty review, safety review, or customer approval.

Storage:
- Attach required photos to the job file, not only to a phone thread.
- Keep originals internally when the photo may support warranty, insurance, chargeback, or legal review.
- Share cropped or redacted copies outside the shop when unrelated private information appears.

Do not make the block longer than the job can support. A ten-minute filter visit should not carry the same photo burden as a three-day repair. The goal is consistent proof, not field paperwork theater.

For most small shops, the rule is enough:

Photograph what you found, what you changed, what you finished, and what still needs a decision.

Sources

• IRS Publication 583, Starting a Business and Keeping Records, for general business recordkeeping discipline around income, expenses, supporting documents, and transaction records.
• Electronic Signatures in Global and National Commerce Act, 15 U.S.C. 7001, for electronic signatures, contracts, records, retention, and reproducibility context.
• OSHA 29 CFR 1926.20, for construction accident-prevention responsibilities and competent-person inspection context.
• OSHA 29 CFR 1926.21, for safety training and unsafe-condition recognition context.
• EPA RRP work-practice standards, 40 CFR 745.85, for lead renovation, repair, and painting work-practice context.
• EPA RRP recordkeeping and reporting requirements, 40 CFR 745.86, for regulated renovation recordkeeping context.
• Federal Trade Commission, Protecting Personal Information: A Guide for Business, for practical data-minimization, retention, security, disposal, and incident-planning guidance.
• NOAA Climate Data Online, for historical weather-record context when weather affects site conditions, delays, substrate, or closeout.
• Visa Core Rules and Visa Product and Service Rules, 18 April 2026, for payment-dispute context around services not received and not-as-described claims.
• Mastercard Chargeback Guide, Merchant Edition, 13 May 2025, for chargeback documentation and second-presentment context.

---

Verify legal, safety, payment-dispute, lead-paint, privacy, insurance, and record-retention requirements with the applicable regulator, processor, attorney, CPA, insurer, and customer contract before acting. Requirements can vary by trade, state, job type, customer, and transaction.