Conference recording

What this is about

Count first: rooms times slots times days. A conference recording is sized by that multiplication, and every planning decision follows from it — how many static camera kits, how audio comes off each room's PA, how slides are captured as a clean signal instead of filmed off the screen. The product is an archive and a content library: talks published individually, searchable, credited. That makes it the sober sibling of the aftermovie, which chases emotion for marketing. The critical system is unglamorous: naming and logging, so that after three days and dozens of sessions, every file finds its talk, speaker and consent form.

The format determines scope, crew and timeline — before the first location has been scouted.

What runs differently here

In planning terms, that means:

• Scale is multiplication, not addition: each parallel room needs its own kit and operator or a tested remote setup — the plan states which rooms get which tier
• Slide capture runs as a signal split from the presentation output, synchronized with camera and audio, because filmed screens age terribly
• Speaker consent is collected per talk with the session log, including publication scope — one missing form blocks one published video
• Turnover between slots is the tightest constraint: card changes, file naming and level checks happen in minutes while the next speaker plugs in

What the plan has to deliver

A production plan is useful to this role when it provides the following:

• A room-and-slot matrix assigning kits, operators and audio sources per stage
• A naming and logging convention applied from the first card: event, room, slot, speaker
• A consent workflow tied to the session log, with publication scope per speaker
• A slot-change checklist that fits inside the conference's shortest break

Common pitfalls

What most often goes wrong in practice:

• Filming the projection screen instead of splitting the slide signal
• Relying on one operator to cover two parallel rooms with overlapping slots
• Sorting three days of unlabeled files after the event instead of naming them during it

With TillyGen

TillyGen builds the room-and-slot matrix from the conference program and attaches kits, operators and consent status per session — the archive is organized before it is recorded.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.