A parts researcher can know the equipment family and still need one character from the identification label. A video of the whole unit does not solve that problem. Neither does a close photo of a serial number when nobody can tell which of three neighboring units it belongs to.
I treat identification as a small documentation task with its own finish line. The person doing the research should be able to connect the readable label to the right installed unit, distinguish the model from the serial number, and see which information remains uncertain. That is a different purpose from showing a customer the part that failed, where the main job is explaining a visible condition.
A live inspection use case with a narrow question
Before going live, I ask what identification the remote person needs and what I am authorized and qualified to observe. I want a short request such as "the full model, serial, and revision if shown," not a vague instruction to film the equipment until somebody recognizes it. I do not open restricted areas or approach moving or energized components to make an identification video.
The first view establishes the building, room or roof area, and the unit's site label if there is one. Then I show the unit as a whole and the position of its manufacturer label. That sequence creates a visible connection between location and identification. If two units look alike, I document them separately rather than trusting their order in a camera roll.
The live inspection use cases guide asks whether someone elsewhere needs to see a specific thing to move work forward. Parts research can fit that test when the person on site can safely show information that is missing from the job file. It does not require a full tour of everything in the room.
Capture the label, not just the number you expect
I first capture the entire accessible label, then a closer still if the text can be recorded clearly. The whole label preserves field headings, punctuation, suffixes, and the relationship between several identifiers. A tight image containing only a row of digits invites someone to call it the model number when it is actually the serial.
I read the headings aloud before the values. I pause between groups and say letters and numbers distinctly, but spoken identification is still a transcription that can be wrong. I compare my written note with the image before leaving. When a character is unclear, I mark it as unclear rather than letting familiarity with a common model fill it in.
Glare, wear, an angled view, and small print can all leave an otherwise useful image unreadable. I check the still at a readable size, not just as a thumbnail. If a better view is available from the same suitable position, I take it. If not, I preserve what is visible and state the missing part. A guessed suffix can waste more time than a clearly stated gap.
Separate equipment identity from component identity
An installed unit may have a site asset tag, a manufacturer label, and labels on individual components. I record which is which. The building's "Unit 4" identifies it for the property team; it does not replace a manufacturer's model designation. A label on a component does not automatically identify the complete assembly around it.
If accessible component markings are part of the request, I connect their location to the whole unit in a separate sequence. I avoid calling the component original or calling its visible marking the correct replacement reference without supporting information. Previous work may have changed what is installed. The point of the record is to support research, not quietly settle it.
I give the researcher the captured identifiers in text as well as the relevant images through the company's established job process. I label the text as my transcription and retain the image it came from. The text makes searching easier; the image gives the researcher a way to check my reading. InspectStream does not need to extract the label automatically for that workflow to be useful.
Use the live view, then check the handoff
I send the invited researcher an InspectStream browser viewing link. They do not need an app or account to watch. The viewer side is watch-only, so I agree on the needed views beforehand and handle any detailed back-and-forth separately after the inspection. The how it works page explains the viewing flow.
Live video can provide orientation while a still carries the fine print. Connection quality and camera focus affect what the person watching can read, so I do not treat their presence on the link as proof that every character was legible. Afterward I check that the saved material includes the unit context and the identifier detail before telling the researcher the packet is complete.
My closeout is a short list: which unit, which identifiers were captured, which characters remain unresolved, and who will confirm the parts reference. Manufacturer documentation or an appropriate supplier still needs to establish the correct component for the application. A clear record gets that work started with fewer missing facts; it does not turn an image into a parts-compatibility decision.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.