Multi-party walkthroughs covers how to run one well: who speaks, what order you walk, how to stop it turning into a meeting.
This post is about the step before that, which is where these actually die. Not the video. The calendar.
You need the owner, the architect and your superintendent looking at the same fifteen minutes. One of them is in a car, one is on another site, and one replies to email twice a day. Three days later the walkthrough has not happened, the crew has moved on, and the decision it was meant to produce gets made by someone guessing.
Scheduling a remote construction walkthrough people actually attend
Four rules. They are unglamorous and they work.
Name a window, not a time. "Thursday between ten and ten-thirty" gets more people than "Thursday at ten." Field work does not land on the minute and everybody involved knows it. A window you hit is better than a time you miss by nine minutes, because the person who showed up at ten and saw nothing will not show up next time.
Put the duration in the invitation and mean it. Fifteen minutes. People will give you fifteen minutes from a car park. They will not give you an open-ended commitment to a site visit by video, because they have all been trapped in one.
Say what the walkthrough is for in one sentence. "Confirming the soffit detail before we close it up." A person who knows the question can decide in three seconds whether they need to be there — and half the time the answer is no, which is a good outcome that saves everybody the slot.
Send the link on the day, not with the invitation. The link is live for the inspection and expires when it ends, or after twelve hours. A link sent on Monday for a Thursday walk is a support call waiting to happen. Send the calendar hold early; send the link that morning.
Accept that somebody will not make it
Plan for it rather than rescheduling around it.
The walkthrough is recorded from the start, and the recording stays with the company. So the person who could not get free watches it that evening and is only a few hours behind rather than a week. That changes the shape of the whole exercise: you are no longer trying to get everybody simultaneous, only the people whose input changes what happens next.
Usually that is one or two people, not four. The rest are being kept informed, and informed is a job the recording does better than attendance.
Worth knowing on the numbers: five people can watch the same inspection at once on the standard plans. That is comfortably more than any walkthrough should have live — three watchers is usually one too many already — but it is a real ceiling and it is worth knowing before you forward a link to a distribution list. Anyone beyond that is a recording recipient, not a live viewer.
Make the fifteen minutes actually fifteen minutes
The single biggest cause of overrun is starting the walk before everyone is on.
You can see who has arrived — the staging screen shows when an invited viewer has opened the link, and the live view carries a count of who is watching. Use it. Wait for the count you expect, give it two minutes past the window, then start regardless and say out loud who is missing.
Then walk the route you said you would walk, in the order you said, and stop. The temptation to add "while we're here, let me show you the other thing" is what turns a fifteen-minute walkthrough into a forty-minute one and teaches everybody to decline the next invitation.
Remember also that nobody watching can interrupt you. The viewer side is receive-only — no microphone, no camera, no chat — which is what makes this a walkthrough rather than a video meeting, and it is genuinely why people accept the invitation. Nobody is going to be put on the spot. If the question button is switched on, a watcher can flag the frame they are looking at and it saves for review afterwards; discussion happens on the phone once you are down.
Write the outcome down before you leave site
The walkthrough exists to produce a decision. If the decision is not captured, the fifteen minutes bought you a shared feeling rather than a result.
Say it out loud on camera at the end — "so we are going with the wider fascia, confirmed by the owner just now" — and then put it in writing the same day. Capturing a decision made on a walkthrough is the full method, and the reason the spoken version matters is that it lands inside the recording, at a timestamp, in the voice of the person who agreed to it.
When nobody turns up at all
It happens, and it is not always a scheduling failure.
Sometimes the walkthrough was not needed and people quietly voted with their calendars. Sometimes the link went to an address nobody reads. Sometimes the owner meant to and simply forgot. When nobody taps the link goes through the causes and what to do about each.
The thing not to do is cancel the walk. Do it anyway, narrate it as if somebody were watching, and send the recording. You lose the live back-and-forth and you keep the record, which was always the more durable half.
How an inspection is created, shared and retained, end to end, is on how it works.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.