Every other post in this cluster documents one event. You arrive after the weather, you record what is there, and the record stands on its own.
This is the version where you have been here before.
Maybe eighteen months ago, maybe two springs back. The address is familiar, you may even remember the dog. Somewhere in your files there is a walkthrough of this exact roof, recorded before whatever happened last night happened.
That changes the job, and most companies handle it as if it did not. They run the same inspection they would run on a house they have never seen, and the most valuable thing they own about the property — a dated record of how it looked before — goes unused.
Storm damage documentation when you already have a record
The difference is that you are no longer describing a condition. You are describing a change, and a change needs two observations to exist.
Which means the second inspection has a job the first one did not: make the two comparable. Not roughly comparable, actually comparable, in a way that somebody who was not on either roof can follow.
Three things do most of that work.
Walk the same route. If the first walkthrough went north slope, west valley, chimney, south slope, do that again in that order. It sounds trivial. It is the single biggest determinant of whether two recordings can be read side by side, because a viewer who knows the order can find the same spot in both files in seconds instead of scrubbing.
Stand in the same places. Ridge line from the same end, valley from the same side. You will not match it exactly from memory and you do not need to. Close is enough for a person to line them up.
Say the date out loud, on camera, at the start. "This is the second inspection at this address. The first was in March of last year." The recording already carries a timestamp, but a spoken sentence survives being copied, exported and pasted into somebody else's file. It costs four seconds.
Review the old file before you climb, not after
I know how this goes on a busy morning after a storm, when there are nine addresses on the list. Nobody opens the archive first.
Open it anyway, for two minutes, in the truck.
You are not looking for detail. You are looking for the three or four things you flagged last time — the lifted tab on the west slope, the boot you said had a year left, the gutter seam. Those are the places where "this is new" and "this was already going" are about to be decided, and deciding them accurately while you are standing on the roof is enormously easier than deciding them afterwards from two videos.
Separating storm damage from ordinary wear is the general discipline. A prior record turns that judgement from an inference into a comparison, which is a much stronger position to be standing in — and a much easier thing to explain to a homeowner who is watching you from the driveway.
Say what has not changed, too
The temptation on a second visit is to narrate only the differences. Resist it.
A walkthrough that mentions six new things and says nothing about the rest reads, later, as if the rest was not examined. Somebody looking at that recording cannot tell whether the south slope was fine or whether you skipped it.
So state the unchanged parts as findings in their own right. "South slope looks the same as last time, no new granule loss that I can see, the boot I flagged in March is holding." That is three seconds of narration and it converts an absence into an observation. Documenting pre-existing wear makes the same argument for a first visit; on a second visit the stakes are higher, because you now have a prior record that will be read against this one.
The part that catches people out: the old file may be gone
Here is the practical constraint nobody thinks about until it bites.
Recordings are kept on a retention schedule tied to your plan — ninety days, one year, or three years. Storms do not arrive on that schedule. A property you inspected twenty months ago on a one-year window has no video left, and that is the system doing what it was configured to do rather than a failure.
The fix is to know your window before you need it, not during the phone call. If you work in a market where the same roofs come back around, the length of that window is a business decision rather than a storage detail, and it is worth making on purpose. How long to keep inspection photos works through how to choose one.
The job record — dates, address, scope, what was flagged — is small, cheap and worth outliving the media. Even when the video is gone, "we were here in March and flagged the west valley" is a real answer.
Why the homeowner should watch this one in particular
A second visit is the appointment where live video earns the most.
The homeowner has heard a description of this roof before. Now they are being told something changed, by the same company, about the same house. That is precisely the moment where a folder of photographs feels like an assertion and watching the roof over the inspector's shoulder feels like being shown.
Hand them the link and walk the same route you walked last time, out loud. You are not asking them to take your word for the comparison. You are letting them watch it happen.
What each plan retains, and for how long, is on pricing. Who inside the company can open an older recording, and how access is controlled, is on the security page.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.