Draft
Your job photos are on an ex-employee's phone. Now what
The proof of a July dispute lives in a guy who quit in March. Here are the recovery moves that sometimes work, and the policy that ends the problem.
The guy quit in March. It was not ugly, he just took a job across town, and you shook hands and wished him well. Now it is July, a customer is disputing a finished job, and the only photos that prove you did the work right are on his personal phone. Before-and-afters, the shot of the framing before it got covered, the readings, all of it went into his camera roll and left the building with him.
This is one of the quiet ways a small shop pays for having no place to keep its own record. The photos existed. Someone took them. They were good photos. They are just sitting in a device you do not own, controlled by a person who no longer works for you and has no reason to dig through nine months of pictures for your sake. This guide covers the moves that sometimes get them back, with the real odds on each, and then the policy that makes sure you are never here again. If you want the wider picture on why proof wins these fights, the proof and getting paid hub is the place to start.
The recovery moves, and their real odds
You have a few plays. None is a sure thing. Run them in order, because the good outcome from an early one saves you the pain of the later ones.
Ask him nicely. Text him, keep it warm, be specific: “the Reyes bathroom on Maple, back in February, I need the before shots and the shot of the valve. Can you AirDrop or text me what you have from that job?” A former employee who left on good terms will often help, especially if you make it easy and ask for a narrow set of photos rather than a data dump. This is your best shot and it costs you nothing but a little pride. The odds drop fast if the parting was sour, if he has changed phones since, or if he simply deleted old pictures to free up space, which people do without thinking.
Check the cloud. If he ever backed his phone up to a shared company account, a shared photo album, or synced to a drive you control, the pictures may still be sitting there even though the phone is gone. This is worth ten minutes of looking. The catch is that most crews never set this up, so the photos were only ever in one place. If they were, this is a dead end.
Mine the old threads. Go back through your group text, your email, any place where he might have sent a photo during the job. Guys post pictures to the crew thread all the time. A shot he texted you in February is still in your phone in July, buried but yours. The problem is that a group text scatters photos with no job attached, so you are scrolling a wall of images trying to remember which one belongs to Maple Street. It is slow, and the coverage is spotty: you will find the photos he happened to send, not the full set. But sometimes the one shot you need is in there.
Reconstruct without him. If the photos are truly gone, you are not out of the fight. Pull the invoice, the material receipts, the inspection sign-off, the permit. A passed inspection on a date is hard evidence the work met code. This will not win a cosmetic he-said-she-said, but it holds the line on the big questions. For how a photo trail wins the argument a paper trail cannot, see he said, she said.
Run all four and you might get most of what you need. You might also get half of it, on a job where half is not enough.
What the gap actually costs
Put a number on it so the abstract “we lost the photos” turns into something you can feel.
Say the dispute is a customer claiming your crew cracked a tile that was already cracked when you got there. If you had the pre-existing damage photo, this is a two-minute conversation and the customer eats it. Without it, you are choosing between two bad options. You eat the repair to keep the peace: a half day of labor and materials, two men, call it six labor-hours plus the tile, north of four hundred dollars for damage you did not cause. Or you fight it, the customer posts a one-star review, and you spend the next month watching a bad rating cost you calls that would have closed. Either way the number is real, and it is a number you would not be looking at if the photo you already took were still yours.
The sting is the same as always: the proof existed. Your guy did his job and documented the work. The company just had no place of its own to keep the record, so the record walked out the door in a back pocket. Prevention here is not about taking more photos. Your crew already takes them. It is about where they land.
The policy that ends round two
The whole failure has one root: the photo lived on a personal phone instead of on the job. Fix that and the phone walking off site stops mattering at all.
The rule is simple to say. A photo that proves work belongs to the company from the moment it is taken, not whenever someone remembers to forward it. That means the photo has to land somewhere the company owns on the day of the job: attached to the specific job it proves, in a record you control, not in a camera roll and not in a thread that scatters it. When a guy shoots the before-and-after, the covered rough-in, the pre-existing crack, that image should be on the job the instant he takes it, tied to the address and the date, sitting in a place that is still yours whether he stays five years or quits next Tuesday.
Two habits make this stick. First, decide which shots are proof shots and get the crew shooting them every time. The list is shorter than you think: the six photos that end most callback arguments is a good starting set. Second, and this is the part that saves you, make sure those shots go into a company record on the spot. A photo you have to remember to collect later is a photo you will be chasing across an ex-employee’s phone in July.
The place this bites hardest is condition photos, the ones that prove a problem was there before you were. Those are the shots most likely to matter in a dispute and most likely to be missing when you need them. Document existing damage before you start work walks through which ones to take and when. All of it assumes the same thing: the photo has to end up somewhere the company keeps, not somewhere an individual keeps.
Where the record should live
This is exactly the gap Crewmigo is built to close. Every job is its own thread, and the proof photos land on the task inside that thread, tied to the address and the date, the day the work happens. The record belongs to the company, not the person holding the phone, and it can be exported whenever you need it. When someone leaves, their access leaves with them, but the photos they took on your jobs stay put, because they were the company’s from the moment they were taken. We are new, and the ask is a small one: put your next job on it, and let the proof land where it belongs from day one.
Crewmigo runs every job in a thread your crew already knows how to use, with the photo that proves it and a sign-off that closes it. One plan, one price a head. Subs ride free.
Start a job