Most remote walks fail on structure, not technology. The video works fine. What goes wrong is that twenty minutes turns into forty, one participant hijacks it with a question about door hardware, and the mechanical room you scheduled the whole thing for never gets shown.
A site walkthrough agenda fixes that, and it has to be an actual agenda with times, not a list of topics. Topics expand. Clocks do not.
Here is the one I use. It is built for twenty minutes because twenty minutes is what an owner will reliably give you every week, and because a walk that runs long once gets declined the next time.
The twenty-minute site walkthrough agenda
0:00 to 1:30 - Cold open. Camera on, no small talk. State the date, the job, who is on, what this walk covers, and what it does not. "August eleventh, Riverside Building B, owner and owner's rep on. Covering Level 3 rough-in and the roof curbs. Not covering the garage, the electrician is pulling wire and I cannot hear down there." Naming the exclusion up front prevents the question at minute fourteen.
1:30 to 3:00 - The delta. What changed since last walk, against what you said would change. Two sentences and one shot. "Last week I said block would top out east and curbs would be set. Both done, here they are." This is the highest-trust ninety seconds of the walk and it belongs at the front, not the end.
3:00 to 11:00 - The route. Two or three areas, three to four minutes each, in the same order every time. Say the location as you enter each one: level, column line, orientation. Hold each shot longer than feels natural, about five seconds, because the person watching on a phone needs time to understand what they are looking at before you move.
11:00 to 15:00 - Open items. Go through last walk's list in order. Each item gets sixty seconds and ends with a state: done, in progress with a date, or blocked with a name attached. Show the item on camera, do not describe it.
15:00 to 18:00 - Questions. Stand still. Do not walk while taking questions, the motion makes people hold back. Ask by name if there are more than two viewers. Silence for four seconds is fine and usually produces the real question.
18:00 to 20:00 - Read back. Decisions made, who owes what by when, and what you will show next walk. Say it into the microphone, on camera, before you end. That is the part of the recording anyone will ever go back to.
Adjusting it for other walk types
The structure holds. The proportions move.
Draw inspection, twelve minutes. Cut the delta and the questions to almost nothing. Replace the route with the schedule of values in line order. Line item, condition supporting the number, next line item. Read back the percentages at the end. The person watching has a form, and your site walkthrough agenda should follow their form, not your building.
Punch disposition, forty-five minutes. Skip the route entirely, go in item number order, ninety seconds per item, and park anything that is really a change. The published list is the agenda.
Single-issue walk, eight minutes. One condition. Two minutes of context, four minutes on the condition from at least three angles, two minutes to get a decision. Do not add a tour to it because you are already out there. That is how an eight-minute call becomes a thirty-minute one and how a decision gets lost.
First walk on a new project, thirty minutes. Add a five-minute orientation at the front: site boundaries, how the building is numbered, which elevation you call north. Everything afterward depends on the viewer having that model, and you only pay for it once.
The rules that keep it from drifting
Publish the agenda in the invite. Three lines is enough. People who know the shape of the meeting interrupt less. Send the join link separately the morning of, and make sure it opens without an install, because the viewer flow is where a tight agenda usually loses its first four minutes.
One person runs the camera and the clock. Not two. If you are on site with a second PM, one of you holds the phone and calls the time and the other stays quiet unless asked.
Park, do not chase. When a question lands outside the agenda, say "parking that, I will come back to it after" and physically keep walking. Then actually come back to it in the question block, or you will not get the benefit of the doubt next time.
End on time even when you are not finished. Say what did not get covered and schedule it. A walk that ends at nineteen minutes with two items unaddressed is a functioning process. A walk that runs to forty-two is a meeting nobody joins again.
Never end without the read back. If you are out of time, cut the questions, not the read back. The questions can be an email. The read back is the record.
Where the times came from
Nothing here is arbitrary. Ninety seconds of context is about the length of a viewer's patience before they need to see something. Four minutes per area is about how long a phone-watching participant can track an unfamiliar space before losing the thread. Three minutes of question time is enough for two real questions and not enough for a tangent to establish itself.
Adjust them for your job and your owner, but adjust them once and then keep them. The consistency does more work than the specific numbers. An owner who has watched the same site walkthrough agenda six weeks running knows when to ask their question and stops interrupting the route, which is worth more than any two minutes you could redistribute.
The mechanics behind the walk itself, signal, light, narration, and what to do about a stair tower with no bars, are in the remote construction walkthrough guide. This part is just the clock.
Take the twenty-minute version, put it on one job for a month, and cut whatever you never use. The plans and limits are here, and a trial is enough to run four walks and find out whether the structure survives contact with your owner.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.