Expose the dependencies
Walk through the planned demonstration and note every point that requires a connection. These may include logins, embedded media, fonts and cloud files as well as obvious websites. A presentation saved locally can still retrieve content from the network when it opens, so saving the main file alone is not enough.
Test the complete sequence with networking disabled. Use the device that will be on the stand and restart it for the test. This exposes dependencies that may remain hidden in an already open session. Record the specific gaps rather than simply labelling the whole demonstration as unreliable.
Create an honest substitute
Prepared screenshots or a short video can help with functions that cannot run locally. Clearly identify them as recorded material. Explain which step normally happens live and what the substitute actually demonstrates. A recording should not create the impression that processing is taking place at that moment.
Use appropriate example data without unnecessary personal information. Put the material in a clearly named folder and check both sound and picture on the intended display. If the sequence remains understandable without audio, it will also be easier to use in a noisy exhibition hall.
Practise the change together
Agree when the team should move from the live version to the fallback. Repeated attempts to reconnect may consume more conversation time than a calm switch after a brief explanation. Everyone giving demonstrations should know how to start the substitute and reset it afterwards.
Record which functions still need to be tested under real conditions when visitors ask about them. Offer a suitable later appointment rather than minimising the distinction. Check both versions again after an update. If the interface or data structure changes, an old video could otherwise demonstrate a different version from the product you currently provide.
