16 November 2026
Content for multiple exhibitions: preparing versions for each screen
Exhibitions change between venues: screens are added, proportions shift and visitors take different routes. Reusing content becomes easier when the likely configurations are known in advance. Agencies need a screen map, a structured asset library and a clear process for producing each version.

Plan a family of configurations
Floor area suggests scale, but does not determine video resolution or proportions. The same nine square metres could accommodate a portrait display or a wide LED surface. Gather upcoming event plans and describe the screen system for each. Record unknown parameters as questions for the stand builder and technical contractor.
A hypothetical range can support discussion:
- 9 m²: a rear screen and one interactive station.
- 18 m²: a main screen, side surface and demonstration area.
- 27 m²: angled surfaces and a separate conversation area.
- 36 m²: a central screen installation and several interactive stations.
These are possible briefs, not a compatible equipment specification. Each needs checking against the actual system.
Obtain screen maps before production
For each surface, establish physical dimensions, working resolution, orientation, visible boundaries and signal mapping. If a screen wraps around a column or comprises separate parts, compare its layout with viewing positions. Identify seams, overlaps, margins and areas that cannot be seen together. Record file, frame-rate, playback and synchronisation requirements.
A controller distributes the signal within its capabilities. It does not turn every composition into a successful version for another geometry. Check input, output and processing limits with the supplier. Before producing the full series, test a grid, labels and a representative scene.
Separate shared content from variable layouts
A master project retains reusable materials: models, footage, backgrounds, graphics, audio and approved wording. Keep text and important objects on separate layers where possible. Prepare a composition for each agreed configuration and check where its key information appears. A single central safe area cannot accommodate every proportion and viewing angle.
The story can also comprise independent blocks: introduction, demonstration, product options and next steps. A short presentation selects fewer blocks; a detailed one adds explanations while preserving continuity. Our article on brand character across formats discusses the shared visual and audio approach.
Define what can be reused
A changed label may need only a data update and layout check. Moving from a conventional display to a wraparound surface may require a new composition; a different product may need another scene. Distinguish included versions, updates and separate production tasks in the estimate. Prepared source assets reduce repeated work without eliminating it.
For Pokolenie Museum, we developed curved-screen content and autonomous playback software, with playlists and materials updated over the local network.
Test each version as a deliverable
Files need clear names, version numbers and an assigned screen. Record language, duration, audio and playback order for every package. Check product specifications, logos and contact details before delivery. A dependency list should identify which versions need rebuilding when a shared scene changes.
Test readability at the intended distance, scene transitions, surface joins, looping and synchronisation. Check application startup, material selection and recovery after stopping. Testing on the agreed player exposes problems that an editing application may hide. Equipment changes after acceptance require another check of affected functions. Keep the approved package identifiable so operators can distinguish it from drafts.
Agree handover and the next event's budget
Delivery includes final versions, a file-to-screen map, update procedures and startup instructions. Discuss editable source files and their dependencies in advance if the client needs them. Assign someone to approve changes and the final build, so the next team can understand the package without reconstructing it from filenames.
Omelchak prepares content and software within an agreed scope for agencies or stand builders. Responsible contractors coordinate structures, equipment and installation with that work. Assess savings against the event schedule and actual adaptation, testing and support costs. A promise of one video lasting forever cannot replace that calculation.