Twelve training screencasts for our internal program

We have rolled out a new program across the company, and the support desk now spends most of its day answering the same four or five questions: where a shift is opened, how a routine operation is carried out, why a report comes back empty. Written manuals exist, but almost nobody reads them — it is easier to call a colleague and be walked through the screen. We want to replace those calls with short videos that a person watches once before the first login and re-opens later, when a rare operation finally comes up.

The order is a series of twelve clips, three to five minutes each: the first launch and workplace setup, the everyday operations people repeat daily, the reporting section, and the mistakes that generate the most calls. Scripts are written from our own internal instructions — we hand them over at the start and approve every script before recording begins. From there we expect clean screen capture, zooming and highlighting on the spot that actually matters, a calm unhurried voice-over, one shared opening title and end card for the whole series, subtitles, and chapter markers so a viewer can jump straight to the step they need.

Two conditions are firm. Everything is recorded on a test environment with depersonalised data: real surnames, contract numbers and amounts must never appear in frame. Passwords and keys are covered before recording starts, and a take in which live data accidentally showed up is re-recorded from scratch rather than blurred in editing. The program will keep changing and the clips will age together with the interface, so the project sources are handed over to us along with the finished files.

What we expect to receive:
— twelve clips of three to five minutes in the agreed order;
— approved scripts and a voice-over text for each clip;
— a single opening title, end card and on-screen captions;
— subtitle files and chapter markers for every clip;
— editable editing, graphics and audio sources for future updates.