A supplier demonstration can reveal more than the presenter intends. Project names, contact details, pricing or account notifications may appear briefly on a screen and remain visible in the recording. Before filming a demonstration at a construction forum, decide which environment and data can be shown publicly.
The useful outcome is a clear demonstration, not a last-minute blur over an uncontrolled screen capture. Ask the supplier to prepare an approved demonstration dataset and to rehearse the exact route through it.
Decide what proves the point
List the actions viewers must see to understand the claimed workflow. Remove unrelated screens and records from the planned route. The presenter should know which steps are essential and which questions must be answered verbally or deferred because they would expose unapproved material.
If a simulated project is used, label it appropriately. A demonstration dataset can be useful, but it should not be presented as evidence of an actual client outcome. Keep any performance or adoption claim separate from the screen walkthrough unless supporting evidence has been approved.
Test the whole display environment
Ask the supplier to check desktop notifications, recent-file lists, browser tabs and autofill suggestions. Production can help inspect what the output shows, but the data owner must determine what is sensitive. A technical operator should not be expected to recognise every confidential project abbreviation.
Include the start and finish of the demonstration in rehearsal. Private information often appears while switching applications or returning to a desktop, rather than during the prepared explanation itself. Agree the picture used while the presenter changes systems.
Give the moderator an interruption rule
An audience question may tempt the demonstrator to open a live client record. Establish a clear alternative: describe the principle, use another approved example or offer an authorised follow-up outside the broadcast. The host should support that boundary rather than encourage an improvised reveal.
If something unapproved appears, the live production response and replay response are separate decisions. Name who can call for a picture change and who assesses the recording before release. Do not assume a later edit reverses live disclosure.
Hypothetical project software demonstration
A presenter plans to show how a defect record moves between trades. The live workspace contains real resident details. The supplier instead prepares a labelled example project with fictional records and approved images. The demonstration still explains the workflow while avoiding the unnecessary exposure of people unrelated to the event.
Accept the rehearsal version
Retain the approved demonstration route and identify the person authorised to change it. If the supplier updates the software or dataset before the event, repeat the relevant checks. A controlled demonstration is easier to film, easier to understand and less likely to require an emergency editorial decision after the audience has already seen the material.
Discuss the proposed coverage
Contact Live Images with the event purpose, proposed deliverables and timing to ask whether the work is a suitable fit. Confirm the production scope and availability for the proposed brief.
Editorial and source note
This unpublished buyer resource offers original editorial production guidance, not a service guarantee. Any example identified as hypothetical is invented, not a Live Images project. Prepared with AI assistance for Live Images.