The reveal moment: what the technical brief needs to specify
The reveal is the technical centrepiece of a product launch. Whether it is a physical product emerging from a dramatic set piece, a video moment driving a major announcement, or a combination of both, the technical specification must serve the creative treatment precisely. A TD who does not understand the creative intent cannot brief the lighting designer, the sound designer, or the set fabricator effectively.
The brief for a reveal moment needs to specify: the exact sequence of events from the moment before to the moment after, the content that plays on each display surface at each step, the lighting states that support each stage of the sequence, the audio cue or live sound that accompanies it, and any automation or physical movement involved (LED panels opening, drapes dropping, product platform rotating). Every one of these elements has a technical dependency that needs to be resolved before load-in.
AV and visual systems for launch events
Product launches typically require a more ambitious visual specification than conferences. The display system is not just a backdrop for a presentation. It is part of the narrative architecture of the event. Wide LED canvases, multi-surface configurations, projection mapping, and custom aspect-ratio LED builds are all common in launch production at brand level. The display system specification should be driven by the creative treatment document, not by a generic conference spec.
In practical terms, this means the production company needs the creative treatment before they can specify the AV. A brief that says "we need a big LED backdrop" is not a brief. A brief that says "we need a 9-metre-wide, seamless LED surface that will display a full-width product reveal video, then transition to a presentation display with a 16:9 zone centred in the screen while the outer panels hold a brand graphic loop" is a brief that can be specified, costed, and delivered.
- ✓ Issue the creative treatment to the production company as soon as it is available, even in draft form.
- ✓ Confirm the display system specification before the content team begins production.
- ✓ Build content review sessions into the production schedule: content needs to be checked on the actual hardware before event day.
- ✓ Specify audio for the reveal moment separately: a product reveal with generic background music says less than one scored specifically for the moment.
The best product launches are the ones where the technical production was briefed from the creative, not where the creative was adapted to fit the production. The distinction is visible in the audience reaction. One feels inevitable. The other feels like a compromise.
Content production and the production company relationship
On a product launch, the content is rarely produced by the same company that delivers the technical production. The brand creative agency builds the video content. The production company delivers the system that plays it. The interface between these two parties is the technical specification: the content brief that tells the creative agency exactly what to produce, in what format, at what resolution, by what deadline.
This document should come from the production company and be approved by the brand team before it is issued. A production company that cannot produce a technical content specification document is not experienced with high-production launch work. A creative agency that begins producing content before the specification is confirmed will almost certainly produce something that requires rework once it is tested on the actual hardware.
On-the-day management
A product launch typically has more VIP presence and tighter schedule management than a standard corporate event. The production company's technical director needs to be in direct contact with the event director at all times, not filtering communication through an account manager. Any programme change that affects the technical cue sequence needs to reach the TD immediately and directly. An intermediary introduces latency that is manageable in a low-stakes event and critical in a high-stakes reveal.
The technical rehearsal needs to include the full reveal sequence at performance levels. This is not optional. A reveal moment that has not been run all the way through at the correct audio level, with the correct lighting states, in the correct sequence, carries a risk that cannot be managed by confidence alone. If the venue does not allow a full technical rehearsal at production levels before doors, that needs to be known before the venue is booked, not forty-eight hours before load-in.
Planning a product launch and want to talk through the technical brief?
We work with brand teams and creative agencies on product launches and major corporate reveals. Tell us about the event.
Frequently asked questions
How long before load-in does the content need to be finalised for a product launch?
A minimum of 72 hours before load-in for a standard launch. For events with complex content delivery across multiple surfaces, custom LED configurations, or content-dependent automation, five to seven days is more appropriate. Finalisation means signed off by the brand team, not still in review.
What happens if the product reveal does not work as planned on event day?
A production company with contingency planning will have a fallback for every critical sequence in the programme. Discuss contingencies explicitly in the pre-production phase. Know what the fallback is for the reveal, the main AV system, and the audio before load-in day, not on it.
Do we need a separate director for the content versus the technical production?
On larger launches, yes. A show director or content director who manages the narrative and timing of the event is distinct from the technical director who manages the systems that deliver it. For smaller launches, an experienced TD can manage both functions, but the scope needs to be agreed explicitly.