Trade-show loops and rep leave-behinds for devices
Booth video is promotional material and earns the same review as a journal ad. A silent-readable loop spec plus a rep library derived from one approved master.
The booth loop is usually the last asset built and the only one that never went through review. Events commissions it three weeks out, the agency cuts it from launch footage, it plays on four monitors for three days in front of several thousand clinicians, and nobody in regulatory ever saw it.
That is a category error. A video playing on your booth is promotional material you are distributing about a regulated product. In the device world it generally falls under labelling and advertising rules, which means its claims have to be consistent with the cleared or approved indications for use — the same test a journal ad has to pass. Your regulatory function owns that call, not the exhibit house.
Accepting the review makes the production problem easier rather than harder, because it forces the structure that makes everything downstream reusable: one approved master, a defined swap layer, and a derived library that inherits approval instead of re-earning it.
The loop is a claim document
Before anyone opens an editor, write the loop as a claim list rather than a shot list: each row a statement the video makes, and the substantiation behind it. The statements that get missed are the ones that are not sentences.
- A juxtaposition. A competitor's device, then yours, then an outcome graphic, is a comparative claim assembled from three shots that each looked fine alone.
- A rendered mechanism. An animation showing how the device works is a claim about how it works. Show it operating in tissue outside the indication and that is an off-label claim in cartoon form.
- A number without an anchor. A large figure with a small unit under it gets read as the figure. If population, endpoint and timeframe do not fit legibly on the same card, the number does not go in a silent loop.
- A setting. Footage shot in an operating theatre implies a use environment. If the clearance is ambulatory, the room is a claim.
- An implied population. Casting reads as indication. A paediatric-looking patient in a video for an adult indication is a claim you did not write down.
Give the finished loop an approval identifier and an expiry date the way a journal ad gets one, and put both in the file name. Field teams keep assets for years, and a date somebody has to look at is the only reliable brake on an expired claim.
The silent-readable spec
Booth video plays muted. Halls are loud, most exhibitor manuals cap sound so it does not carry past your booth line, and the attendee is walking. A loop whose claims live in a voiceover is a loop whose claims are never delivered.
| Property | Spec | Why |
|---|---|---|
| Runtime | 45–75 seconds | Long enough to carry a full argument, short enough that a passer-by catches a whole cycle |
| Audio | Optional garnish only | Assume it is muted; nothing load-bearing in the track |
| Claims delivery | Burned-in text | Sidecar captions do not exist on a booth player |
| Type size | Roughly one inch of cap height per ten feet of viewing distance | Standard signage rule of thumb; measure from the aisle, not from the monitor |
| Text hold | Long enough to read the line aloud twice | Regulatory text especially — a two-second hold on an indication statement is not a disclosure |
| Contrast | High-key, heavy contrast | Hall lighting is bright and monitors are rarely calibrated |
| Safe area | Keep text well inside the frame | Booth monitors overscan and totem bezels crop |
| Loop point | Cut back to the opening frame, no fade to black | A loop that goes black reads as a broken screen |
| Frame rate | 25 fps, matched to the playback device | Mixed rates stutter on cheap players |
| Delivery | Local file on the player, no network | Show wifi will fail on day two |
Two additions specific to regulated devices. Hold the indication statement and any required legends as a full card, not as a strap under motion — a legend competing with a moving background is a legend nobody read. And nothing required may depend on the attendee choosing to engage: no QR code as the sole path to safety information, no "scan for full indications." The card goes in the loop.
Timed text overlays is where the claim cards get built, and burned-in captions covers the parts of the script that do carry voice. If you have a horizontal master and a totem, derive the vertical with aspect ratio change and then re-measure type size — reframing shrinks effective cap height relative to viewing distance and quietly breaks the legibility spec you just signed off.
One master, a derived library
The payoff for running the loop through full review is that everything else in the show kit gets cut from it.
| Asset | Derived how | May change | May not change |
|---|---|---|---|
| 60s booth loop | The approved master | Nothing | Everything |
| 30s pre-show teaser | Trim, no new material | Runtime, tail card | Claim set, indication card |
| 20s follow-up embed | Trim + new tail | Tail card, CTA | Claim set, indication card |
| 15s silent social reel | Trim + reframe | Aspect, tail card | Claim set, indication card |
| Rep leave-behind | Master + swap layer | Rep name, title, contact, meeting date | Everything else |
The governing rule is one sentence: a derivative inherits the master's approval only if the claim set is unchanged. Which sounds permissive until you notice how easy it is to change a claim set by subtraction. Cutting for time and losing the limitation card creates a claim by omission. Trimming a comparative sequence so the qualifier falls off the end creates a stronger claim than the one approved. Re-ordering two shots creates a juxtaposition that was not in the packet.
So the practical control is that trims are permitted at defined cut points marked in the master, and nowhere else. A derivative cut at a marked point is administrative; one cut anywhere else goes back to review.
Ship the master as a locked reusable draft with the swap slots named and everything else fixed. Saving a video edit as a reusable draft is what makes "rep opens it, changes three fields, exports" a real workflow rather than a wish, and promoting a winning video into a reusable workflow covers the general pattern.
The swap layer that keeps reps out of trouble
Field teams will personalise assets. The only choice is whether they do it inside a structure you built or in whatever editor is on their laptop. Expose exactly these fields:
- Rep name, title and territory
- Direct contact details
- Meeting date and account name, on the tail card only
- One free-text line, character-capped, with a house rule that it is a logistics line and not a claim line
Everything else is locked: the picture, the claim cards, the indication statement, the legends, the version stamp and the expiry date. The version stamp especially should be un-editable and visible, because the failure you are guarding against is a rep sending a two-year-old cut after the indication changed. Keep one thing out of the swap layer entirely — anything showing a named clinician or a specific institution's data. Those carry their own permissions, and a rep who can swap a logo will eventually swap in a hospital that never agreed to it.
For the wider show kit, trade show booth loops and follow-up covers the non-regulated version of this workflow and signage and trade show graphics from generated images handles the static surfaces around the monitor. The broader content programme for manufacturers reuses the same master for channel and distributor assets.
What to generate and what to film
Generated material has a real place in this kit, and a narrow one.
Film: the device, the packaging, the interface, the setup sequence — anything a clinician will recognise as right or wrong. Device audiences spot an incorrect port, a wrong-generation console or a sterile field that would fail. One wrong detail costs you the room.
Generate: backgrounds behind claim cards, venue-specific opening frames, transitions, ambient texture between procedural beats. Narration too, where the script is informational rather than testimonial.
Never generate: a clinician endorsing anything, a patient outcome, a mechanism-of-action animation not reviewed against the clearance, or a rendering of the device itself. That last one catches teams out — a generated near-miss of your own product is a labelling problem, because the thing depicted is not the thing cleared.
Run the kit through a QC pass before the crates ship. Quality control for generated marketing assets is the general checklist; add three device rows — indication card legible at aisle distance, version stamp and expiry visible, no unapproved cut points used.
FAQ
Does a booth loop really get the same review as a journal ad?
The safe operating assumption is yes, and the decision belongs to your regulatory function rather than to marketing or events. The underlying test is not in dispute: promotional claims about a regulated device have to be consistent with the cleared or approved indications for use, whether the claim arrives in a journal, on a monitor or in a fifteen-second reel. Route it early — a rejection two weeks out means the monitors play a corporate sizzle.
Can reps cut their own short versions for LinkedIn?
Only at the cut points marked in the master, and only using the swap fields. The most common compliance incident in field enablement is not a rep inventing a claim — it is a rep trimming for length and removing the qualifier that made the claim accurate. Marking legal cut points at build time turns that from a judgement call into a mechanical one.
We show at eight events a year. Do we need a new loop each time?
No. One master per product per approval cycle, then vary the opening frame, tail card and aspect ratio per show. Anything tied to a date, a booth number or a session schedule belongs in overlay text rather than in the picture, which is what makes that a swap job rather than a production.