I watched a contractor lose a job by overstating what his own footage showed. He had good video. He had time on it. And he stood in a kitchen and said the recording proved the damage came from the April storm. It did not prove that. It could not. It showed a roof with lifted shingles on a Tuesday in May, which is a real and useful fact, and by the time the conversation was over nobody in the room trusted anything else he had said either. That is what the limits of inspection evidence cost when you ignore them. Not an argument lost. Credibility lost, across the board.
I keep this post as the one I would hand to a new guy first, ahead of anything about features.
The limits of inspection evidence, stated plainly
One thing. Condition, at a moment, from one vantage point, as captured by one lens under whatever light and weather existed.
Read that again, because every word is doing work.
At a moment. The record covers the minutes it ran. Not the week before. Not the night after. A session on the fourteenth says the fourteenth.
From one vantage point. A camera sees what it is pointed at. What is under the shingle, inside the decking, behind the wall, or on the slope I did not walk is not in the record. Absence of something in a video is not evidence that it was not there. It is evidence that I did not film it.
Through one lens. Wide angle distorts scale. Overcast flattens texture that direct light would show. Phone processing sharpens and denoises in ways that can exaggerate or erase the thing you are pointing at. None of that is dishonest. It is optics, and a viewer who does not know it will read the image as more literal than it is.
Those are the limits of inspection evidence. Everything else people want a record to do is inference layered on top.
The four claims a record does not support
These are the ones I hear contractors make, and each of them goes beyond what any footage can carry.
Causation. Video does not show why a condition exists. Lifted shingles are consistent with wind, with a bad nailing pattern, with age, with foot traffic, with a previous repair. The record shows the condition. What caused it is an opinion, and if it matters to somebody's dispute, it belongs to an engineer or another qualified expert, not to me and not to my camera.
Timing of an event. This is the one that gets stretched most. A server timestamp establishes when the recording was made. It says nothing about when the damage occurred. I can show you a roof on the fourteenth. I cannot show you the storm.
Intent or knowledge. A record cannot show what anybody meant, believed, or knew. Attendance data shows that a link was opened and a connection stayed open. It does not show that a person was watching, understood what was said, or agreed with it. I keep those claims separate on purpose, for the reasons laid out in the post on attendance records elsewhere in this series.
Responsibility. Fault is a conclusion drawn from facts, contracts, and law. Footage is one input among many.
Why overclaiming is worse than having no record
You would think the downside of exaggerating is getting corrected on that one point. It is not.
Credibility is not scored claim by claim. It is scored globally. The moment somebody catches you stretching one thing, they discount everything, including the parts that were solid. That is a rational response and you should expect it.
The reverse is also true, and it is the part that surprised me. Saying "I cannot tell you when this happened, only what it looked like when I was up there" makes people believe the rest of what you say more, not less. Homeowners are used to being sold. Somebody voluntarily marking the edge of their own knowledge reads as unusual, and unusual in a good way.
Restraint is a sales advantage. I did not build my process around that idea and I did not expect it, but it has been true on every job since.
How to talk while the camera is running
Concrete habits, because the limits of inspection evidence are managed in the narration more than anywhere else.
Describe, do not diagnose. "The granules are worn through across about a two foot section" instead of "this is hail damage." The first is what I see. The second is a conclusion.
Say what you did not look at. "I did not get on the back slope today because of the ice." That single sentence does more for the record's honesty than any feature I could build.
Name the conditions. Overcast, wet, late light. That tells a viewer how to read the image.
Flag the inferences as inferences. "Given the pattern, my guess is this has been going a while, but that is a guess and I would want somebody to open it up." Guesses are allowed. Unmarked guesses are not.
Point out what would change your read. If lifting one course would tell you more, say so on the record.
None of that requires software. It requires deciding in advance what kind of witness you intend to be, which is really what a repeatable routine like structured roof inspection documentation is for.
The two lines I do not cross, and what is left
I am not a lawyer, and this is not legal advice. I do not know what any court will do with a recording, what your state requires of you, or what standard applies to anything. I avoid those claims because I have watched people in my trade repeat something they read online with real confidence and be wrong in an expensive way. If a job is anywhere near litigation, a demand letter, or a filing deadline, talk to an attorney first and let them tell you what your record needs to be.
And I am a contractor, not a licensed public adjuster. I do not tell homeowners what damage is worth, whether to file, what a policy covers, or how to talk to an adjuster. In most states doing that without a license is a crime, not a gray area. I document condition. The homeowner deals with their insurer.
What is left, once you take all of that away, is a clear, timestamped, unedited record of what a trained person observed on a property, made in front of the owner, in ordinary language, with the gaps stated out loud.
That is a smaller claim than the marketing version. It is also one I can defend in any room I walk into, which the bigger one never was. The rest of the pieces and how they fit are in the field inspection audit trail overview.
If you want to know exactly what gets written down and what does not, the recordkeeping page is deliberately specific about the boundaries.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.