Video production for e-learning providers

What this is about

Volume changes every rule. A course is a series of short units, each with its own script, its own screen recording and its own place in a learning path, and they are recorded in batches to keep a presenter in front of a camera for as long as their voice holds. Continuity therefore stretches across months: the same backdrop, lens, wardrobe and colour have to be reproducible for the pickup that a curriculum update will demand. Content ages faster than the footage — a changed regulation or a new software release invalidates single modules, not the whole course. Accessibility obligations add subtitles and transcripts, which the script has to feed rather than the edit invent.

Sector routine beats general experience: knowing the field's approval paths and constraints produces more realistic plans than more shoot days without that context.

What runs differently here

In planning terms, that means:

• Modules are recorded in batches, so the running order is driven by wardrobe, backdrop and presenter stamina rather than by the learning path
• A setup card — lens, height, backdrop, colour temperature, wardrobe — has to be documented on day one to make pickups match months later
• Screen recordings need the software in a frozen demo state with fake data, captured at a resolution that survives cropping into vertical cutdowns
• Single modules expire when a rule or a product version changes; the plan should keep each unit independently reshootable without touching its neighbours
• Teleprompter density decides the day: a script written for reading runs faster and needs fewer takes than one written for the page

What the plan has to deliver

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

• A module list with duration, screen-capture needs and dependency on other units, before anyone books a studio
• A documented setup card and a stored backdrop so reshoots match without guesswork
• Scripts written for the prompter, with the subtitle text derived from the same source

Common pitfalls

What most often goes wrong in practice:

• Shooting the pilot module beautifully and never writing down how it was lit
• Recording screen content from a live system with real user data in the sidebar
• Cutting modules that reference each other so tightly that one update forces a dozen reshoots

With TillyGen

TillyGen turns a curriculum into a module-by-module shot list and a batch schedule, so a studio day is filled to the minute and every unit keeps the setup note its pickup will need.

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.