The first room is nearly finished, and the crew is ready to repeat its details across the floor. An owner saw a photograph of the wall last week. The designer remembers a conversation about the trim. Neither record makes clear which parts of this room are meant to become the reference for the remaining rooms.
I would make a dedicated mockup record before repetition starts. It should identify the sample, show the details under discussion and say exactly what is still undecided. Within construction inspection video, this is the point where one visible example may influence a large amount of later work. A little ambiguity here can travel a long way.
Room mockup documentation starts with its purpose
I begin by saying what the mockup is intended to demonstrate. It might be the visible relationship between a wall finish, trim and adjacent casework. It might be the placement of fixtures in one room type. I name the room and the date, then state which features are outside this particular review.
"This view is for the trim transition; the temporary light and unfinished floor are not part of the sample" is much clearer than "here is the finished room." People tend to treat everything in a sample as deliberate unless someone tells them otherwise.
I use the project's actual detail references where available. I do not create a new standard by narrating what happens to be on the wall. If the physical sample differs from the current drawing, that difference is a question for the responsible people, not something the recording resolves on its own.
Film the relationship, then the detail
I start with the whole wall or room so a reviewer can see how the pieces relate. Next comes a steady middle-distance view of the transition under discussion, followed by a close view of the specific edge, joint or alignment. I keep the same order for each feature.
The close view should not lose its location. "At the left side of the door in room 106" remains useful when someone opens only that section of the recording. If an identifier or dimension must be read accurately, I capture a still and retain the underlying measured or written record separately.
I also say what the camera cannot settle. Screen color is not a dependable substitute for a physical finish sample. A perspective view can make spacing look different. A visible surface does not establish the hidden construction behind it. Those limits should travel with the useful views, rather than appear only after someone mistakes the recording for a complete evaluation.
Keep the decision separate from the video
An invited reviewer can watch the mockup through InspectStream while the person on site narrates it. The viewer opens a browser link without an app or account, and does not broadcast camera or audio. I plan any decision conversation through the project's normal channel after the look.
A viewer count shows that people connected. It does not show that they accepted the mockup, agreed with a dimension or authorized repetition. The how it works page describes the viewing and recording flow; the project's written decision process still carries the outcome.
I record that outcome with the mockup reference, the details it applies to, any exceptions and the person responsible for the next action. Capturing a decision made on a walkthrough covers the handoff between something shown and a decision recorded. Here the extra concern is repetition: the instruction must be clear enough that another crew can follow it without attending the original discussion.
Give the repeating crew a bounded reference
Before work spreads across the floor, I would review the relevant saved section with the crew lead and the current written instruction. I ask the lead to identify which features repeat and which depend on the room type. That question exposes a mismatch earlier than "did you see the video?"
A sample in an accessible room does not necessarily answer a corner-room condition. I list those variations in the project notes and arrange a separate reference where needed. The aim is not to turn one mockup into an answer to every situation the building contains.
I also keep the physical sample identifiable for as long as the project requires it. A recording can help an off-site person understand the reference, but the product does not make a physical comparison unnecessary. The use cases page offers other situations where a live look supports the people already responsible for the work.
Changes need a new reference, not a quiet replacement
If the trim or finish changes after review, I make a fresh dated record and clearly identify the earlier one as the previous condition in our project index. I do not leave two unlabeled videos circulating as competing versions of "the mockup."
Before distributing the reference, I check that the recording saved and that its key views are legible. A frame lost during a connection problem cannot guide the next room. I pair the usable record with the written disposition and unresolved exceptions, then tell the crew which version applies.
The useful result is narrow and practical: a person who was absent can see the intended example, understand its limits and find the actual instruction. That makes the mockup a shared reference instead of a room everyone remembers differently.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.