A supplement got questioned once because of a filename. Not the photo, the filename. The image had been texted to an office manager, saved to a desktop, dropped in a shared drive, renamed twice, and re-exported from a slide deck, and by the time it came back around it was a JPEG with a modified date three weeks after the inspection and no metadata left in it at all. The picture was accurate. The file was a mess. That is what people mean when they talk about chain of custody photos, and it is not a fancy idea. It is just knowing where a file has been.
Most contractors, me included for years, have no answer to that question beyond a shrug.
Where the line breaks
Every hop weakens a file, and the hops are so normal that nobody registers them as hops.
Texting. Depending on the path, a texted photo gets recompressed and can arrive stripped of its metadata. The image looks the same. Everything that described it is gone.
Re-saving. Open it, crop it, save it. Now the modified date is today and the original is wherever the original happened to be.
Renaming. IMG_4471 becomes north-slope-2.jpg becomes north-slope-2-FINAL.jpg. The rename is helpful for humans and destroys any link between the file in your hand and the file that came off the camera.
Shared drives. Three people with edit access and no history. Six months later nobody can tell you whether the version in the folder is the one that was uploaded.
Personal phones. This one is the quiet disaster. The photos live on a device you do not own, belonging to a guy who might not work for you in March, backed up to a personal cloud account you cannot reach.
None of that involves anybody doing anything wrong. It is just what happens to files. But the cumulative effect is that when somebody asks where an image has been, the honest answer is "several places, and I am not sure in what order."
Chain of custody photos, kept clean
The goal is boring: the file lands in one place directly from capture, and everything after that is a read, not a move.
For live sessions, that means the recording is written server-side rather than assembled from a phone later. The inspector's device never holds the file of record. There is nothing to upload, which means there is nothing to forget to upload, nothing sitting on a personal phone, and nothing that got recompressed on its way through a text thread.
It means server-side timestamps rather than device clocks, so the time attached to the file was never under the control of the person who made it.
It means an append-only event log around the session. Start, connect, drop, viewer join, end, recording written. Nobody edits it, including the company that runs it. If a file and a log disagree, you can see that they disagree, which is more than most systems offer.
And it means the recording lives in private storage that is reached only through short-lived signed links. There is no permanent public URL. Links expire. Access is a door somebody opens for a while, not an address that lives forever in a text history.
Put together, the chain of custody photos question becomes answerable in one sentence: it was captured here, written there, and has not moved since.
What you still have to do yourself
Software handles storage. It does not handle habits, and chain of custody photos are won or lost on habits.
Stop working from copies. If the record lives in the system, share access to it instead of exporting a JPEG into an email. Every export creates an orphan that will show up later with a wrong date attached.
Keep the original even when you annotate. Circles and arrows are useful. They are also a modification. Keep the clean version and make it obvious which is which.
Get inspection media off personal devices. Not because you distrust your crew. Because people leave, phones break, and accounts get closed, and none of that should be able to take a job's record with it.
Narrate location before you shoot. A file whose contents identify themselves survives a rename. If the audio says "north slope, above the garage, second course up," the record does not depend on the filename being intact. That habit and the rest of the routine are in my notes on roof inspection documentation.
Write down the exceptions. If a session dropped and you finished on stills, say that out loud in the record. A gap you explained is a gap. A gap you did not is a question.
The part where I stay in my lane
I am a roofer who got tired of being disbelieved in driveways. I am not a lawyer and I have no idea how any of this is treated in a legal setting, in your state or any other. Nothing here is legal advice, and I am deliberately not going to tell you what standard your records meet, because I have no idea and neither does anybody selling you software.
What I will say is the practical version. A file with a clear, short path from capture to storage is easier for somebody else to rely on than one with a long, murky path. That is a statement about credibility, not about law. If your situation involves litigation, a demand letter, a deadline, or a subpoena, talk to an attorney before you send anything to anyone. Ask them what they want your process to look like, and then build that.
And the insurance line, which does not move. I record condition. I describe what I saw while the camera was on it. I do not evaluate claims, interpret policies, advise on filing, or price a scope of loss, because I am a contractor and not a licensed public adjuster. The homeowner deals with their insurer directly.
Worth an afternoon
Pick a job from last year and try to trace one photo. Where was it captured, where did it land, how many copies exist, who can reach them today. Most people find something they do not like.
Custody is one of four pieces that make a record something a stranger can check rather than something you have to be believed about, and the others are laid out in the field inspection audit trail overview.
If you want the specifics on where recordings live, how signed links expire, and who inside a company can reach footage of a customer's property, the recordkeeping page covers it plainly.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.