My phone was forty minutes off for most of a summer and I never noticed. It came back from a dead battery on a roof in Bixby, picked up whatever it picked up, and every photo I took for the next several weeks carried a time that was simply wrong. Nobody caught it. Nobody had any reason to. But every one of those files claimed to know when it was made, and none of them did. That is the problem with treating photo metadata as an inspection timestamp record: the clock belongs to the person taking the picture.
This sounds like a technicality until the first time somebody asks you what time you were on their roof.
Why photo metadata is a weak inspection timestamp record
Metadata is real data. It is just data that came from a device the photographer holds, and that changes what it is worth to somebody who was not there.
Phone clocks drift when they lose signal, which happens in attics, crawlspaces, and half the rural routes I run. They reset after a dead battery. They shift when a phone crosses a time zone or when carrier time and network time disagree. And they can be changed by hand in about four taps by anybody who wants to.
I am not suggesting contractors are out there faking timestamps. Most are not. But the value of a record has nothing to do with whether you personally would cheat. It has to do with whether a reasonable stranger can check it without taking your word first. Metadata fails that test, because the answer to "how do we know this time is right" is "because his phone said so."
Then there is what happens to the file afterward. Metadata rides inside the image. It survives some transfers and gets stripped by others. Text it, and depending on the path it may arrive with the timestamp gone. Drop it into a shared folder and the file's modified date becomes the date somebody copied it. I have watched a whole morning's photos end up dated to the afternoon they were uploaded.
What a server-side timestamp actually changes
When a session runs through a server, the time written down is the server's, not the phone's. The inspector cannot set it, cannot drift it, and cannot fix it later if it turns out inconvenient.
That is the entire trick. It is not fancy technology. It is just moving the clock out of the hands of the person with something to gain.
The same thing applies to the sequence around it. An append-only event log records when the session opened, when the stream connected, when signal dropped, when a viewer joined, when it ended. Each entry carries a server time and none of them can be rewritten afterward, which means the inspection timestamp record is not one number but a chain of them that would all have to agree in order to be tampered with successfully.
The recordings themselves sit in private storage, reachable only through short-lived signed links rather than a permanent public URL. That matters for time too. A file that cannot be quietly replaced at the same address is a file whose timestamp still means something a year out.
Time zones, offsets, and other ways to look sloppy
Almost every time problem I have seen in the field was not fraud. It was a mismatch nobody thought about, and mismatches make an honest record look careless.
The daylight saving jump is the classic one. Two inspections in the same week, one before the change and one after, and the times look inconsistent to anybody skimming.
Crews near a state line hit the time zone version. Your phone attaches to a tower thirty miles east and every photo shifts an hour. This is common enough along certain corridors that I know guys who set their phones to a fixed zone permanently.
Then the reporting version, where the software stores time in UTC and the report renders it in whatever the reader's browser thinks local means. Now the homeowner sees 8:14 p.m. for an inspection that happened at 2:14 in the afternoon. Nothing is wrong with the data. Everything is wrong with what the reader concludes.
Practical fixes, and none of them require software:
- Say the date and rough time out loud at the start of every session, in the recording. A spoken date is a nice cross-check against a written one.
- Name the property address out loud too, before you point the camera anywhere.
- Pick one display convention for your reports, with the zone spelled out, and never change it.
The audio version costs you four seconds and it independently corroborates the written record. I put that habit in the same bucket as the rest of the routine in my notes on structuring roof inspection documentation.
What a timestamp does not tell anybody
This is where I have to be careful, and where I would rather undersell.
A timestamp establishes when a recording was made. That is all it establishes. It does not establish when damage occurred, how long a condition had been developing, or whether anything happened before or after the visit. A record from the fourteenth showing lifted shingles says the shingles were lifted on the fourteenth. It says nothing about the eleventh.
I also cannot tell you what any of this means legally. I do not know what a court would make of a server timestamp versus a phone timestamp, and anybody who tells you they do without a bar license is guessing at your expense. Nothing here is legal advice, and if a dispute is headed toward litigation, an attorney is the right first call. Ask them what your situation requires before you go rebuilding your process around a blog post.
Same line on insurance, permanently. I record what I observed. I do not advise on claims, policy language, or whether to file, because I am a contractor and not a licensed public adjuster. Time of observation is a fact about my visit. What it is worth to an insurer is somebody else's job entirely.
The rest of what belongs in a defensible file, and how the pieces fit together, is laid out in the overview of what a field inspection audit trail is.
The version I actually use
Start the session before I get on the ladder. Say the address and the date out loud. Run the same route. Let the server keep time.
That is the whole discipline. It added nothing to my day, and it means I have never again had to answer a question about when I was somewhere with the phrase "let me check my photos."
If you want the specifics of what gets written down and when, the recordkeeping page walks through it without the marketing gloss.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.