A general contractor emails you a backcharge on a Tuesday. Your crew cracked the roof membrane setting the new curb, they say, and they're docking it off your next draw. You know that's wrong, because your guys taped off the area and laid down plywood like they always do. The only proof is on a phone that's out in Spring right now, running a maintenance route.
So you call the tech. He remembers the job and thinks he got pictures. Forty minutes of scrolling later, somewhere between a hundred shots of other rooftops and his kid's ball game, he finds two that might be the right curb. No readable date, no address, nothing that ties them to that roof on that morning. You're going to eat the charge.
Photos win these fights, but only when you can find them and prove when they were taken. The shooting part your crew mostly does already. The filing part is where it all falls apart, because nobody files anything on a 101-degree afternoon with three trucks down. The job, then, is to make each photo land in the right place on its own, the moment the tech hits send.
Why a camera roll is a liability, not a record
A phone's camera roll is a pile, not a filing system. Ten thousand photos in one stream, sorted by nothing but the order they were taken, spread across four or five phones that each belong to a different guy. When you need the one shot that proves a condenser was already dented when you showed up, you're not searching, you're digging.
That pile also walks out the door. When a tech quits, his photos leave with him, and you've got no copy of the work your company actually did. Phones get dropped off roofs, dunked in condensate pans, and factory-reset at the counter when they act up. Every one of those takes your evidence with it.
There's a timing problem too. Every photo carries metadata, the hidden date and location tag a phone stamps on each shot, but screenshots strip it, texts can compress it out, and most folks can't pull it up anyway. If you can't show a GC or a judge when and where a photo was taken, it's just a picture of a roof, and the other side has pictures too.
What to shoot, and when
Good photo habits are a checklist, not an art project. The goal is to document the condition you found, the work you did, and anything that could come back on you. Keep it to shots that would mean something to a stranger six months from now.
Have the crew grab these on every job of any size:
- The nameplate. Model and serial on the unit, clear enough to read. That one shot registers warranties, orders parts, and settles which unit you even touched.
- Before, wide and close. The whole unit and the specific problem. A rusted contactor, a flooded pan, a disconnect left open by the last company.
- Pre-existing damage. Anything already dinged, cracked, or wrong before you laid a hand on it. This is the shot that kills a backcharge.
- After. The repair done, the new part in, the area left clean. Same angles as the before shots so the pair tells the story.
- Readings and labels. Gauges, the meter, the breaker you tagged, the curb you protected. Proof you did the step, not just claimed it.
Timing is simple: before shots before you touch anything, after shots before you pack up and leave. Once the truck rolls, nobody's driving back across Houston to reshoot an attic. Teach it as the first and last thing you do on site, same as setting the brake.
Make the filing happen on its own
This is the part that decides whether any of it works. Ask a tired crew to upload photos to the right folder at the end of a long day and it won't happen, not reliably, not in July. So you take the filing out of their hands. The tech does one thing he already knows how to do, and the photo files itself.
A few setups that work for a small shop:
- Text to a job number. The tech texts photos to one number with the job or ticket number in the message, and a simple automation drops them in that job's folder. Texting is the one thing every tech will actually do.
- A per-job upload link. Your dispatch or field software makes a link or a QR code for each ticket. The tech taps it, shoots, done, and the photos attach straight to the job.
- A shared album per job. If you live in a shared drive, one folder per job named by ticket number and address, with the crew dropping photos in from their phones.
Whatever you pick, the rule is the same: one tech, one tap, no deciding where it goes. Every choice you ask for at 5 PM on a Friday is a choice that gets skipped. The software or the automation does the filing, because software doesn't get tired or quit.
Tag it so you can pull it back fast
Filed isn't the same as findable. A folder of two hundred photos named IMG_4471 is barely better than the camera roll. What turns photos into evidence is being able to type in a job number, an address, or a date and have the right shots come up in ten seconds while the GC is still on the phone.
Each job's photos should carry four things: the job or ticket number, the service address, the date, and which tech shot them. Most field software tags these automatically once a photo attaches to a ticket, which is the whole reason to attach it to a ticket instead of a loose folder. If you're on a shared drive, bake the job number and date into the folder name and let the phone's timestamp handle the rest.
How this holds the bill and backs a claim
Here's where the habit pays for itself. When that backcharge lands, you pull the dated before-shot of the membrane you protected and the GC's story falls apart in one email. No forty-minute phone hunt, no eating a charge that was never yours.
Same thing on a customer dispute. A homeowner says you never replaced the capacitor, and you send the before shot of the bulged old one and the after shot of the new one on the unit, both stamped the day you were there. Most disputes end right there, before anyone says the word chargeback.
Warranty claims run on this too. A manufacturer wants the nameplate, the failed part, and proof of install date before they'll credit you for a compressor. If that's already filed under the job, the claim goes out the day the part fails instead of waiting on a tech to go find pictures that may not exist.
Worth doing this week
You don't need new software to start. You need one channel the crew uses and a habit that sticks.
- Set up a single number or link where photos go, and tie it to a job number. Even a dedicated texting number and one folder beats four camera rolls.
- Write the shot list on a card for the trucks: nameplate, before, pre-existing damage, after, readings. Five shots, every job.
- Run it on this week's jobs and check Friday. If photos landed in the right place without anyone babysitting, it works. If not, make the step simpler, not longer.
- Pull one closed job from last month and try to find its photos in under a minute. That's the test. If you can't, that's the hole you're closing.
Get this running before the next heat wave buries the crew, and the next time a GC or a customer comes at your bill, the answer's already in the file. If you want a hand wiring the text-to-file part into your dispatch software, that's the kind of plumbing we set up for Houston shops.