Batch recording means scripting several videos ahead of time and shooting them all in one session — one rig setup, one block of performance energy, and an edit pile instead of a weekly scramble. For a solo creator, three to eight videos in a sitting is a realistic range, and the difference between a productive batch day and an exhausting one is almost entirely preparation.
This is a working system for that day: how to prepare the scripts, the order to shoot them in, the loop that keeps takes moving, how to protect your energy through take six, and what to capture so the edit is sorting rather than archaeology.
Why batching works
Every recording session carries a fixed cost that has nothing to do with the video: lights positioned, camera framed, prompter mounted and mirrored, font size checked from your mark, sound tested. Do that weekly and you pay it weekly — often twenty minutes of setup for fifteen minutes of recording.
Batching pays the setup cost once and spends the rest of the session on the only part that actually needs you on camera: delivery. There's a second, quieter benefit — consistency. Five videos shot in one session share light, framing, hair, energy and room tone, which makes them easier to edit and makes a channel look deliberate.
The precondition is that the scripts exist before the day. A batch day that includes writing is two jobs pretending to be one, and the writing always eats the shooting.
Preparing the scripts: a library and an order
Write everything in advance, and give each script one read-aloud pass in the days before — out loud, changing every phrase you trip on. (The full method is in how to write a script you can actually say out loud.) By shoot day the scripts should be performable, not just finished.
Then stage them where the shoot needs them. TellyPrompter's script library holds each script with a tag, so a "This batch" tag turns shoot day into a queue: every script one tap away, nothing to paste mid-session, and last week's material filtered out of view. Loading the next script is a ten-second gap between videos rather than a hunt through documents.
The order matters more than it seems:
- Front-load the hard one. Whichever script you're dreading — longest, most technical, most personal — goes first, while your energy and patience are at their peak. Every script after it feels downhill.
- Warm up on a throwaway. Before the hard one, spend five minutes reading something that doesn't count. The first read of any session is the stiffest; spend it where it costs nothing.
- End on the easiest. A short, familiar format at the end means finishing on a good take rather than a tired compromise.
The shoot-day loop: take, retake, move on
The engine of a batch day is a tight loop per video, and the enemy of the loop is friction — anything that means walking to the rig, touching the phone, or re-settling into position.
A workable loop looks like this. Load the script. Read the first paragraph aloud once as a level and pace check. Take the take, all the way through, without stopping for small stumbles. If it needs another pass, retake immediately while the script is warm — saying "Telly, again" starts the retake from your mark, no walk to the rig. Two usable takes, then move on.
Two habits keep the loop honest:
Mark stumbles instead of stopping for them. A flub mid-take doesn't need a restart; it needs a note. Saying "Telly, marker" drops a marker at that moment and the take keeps rolling — the stumble report afterwards shows you exactly where the rough spots were, so "was that take clean?" gets an answer without scrubbing back through the footage between videos.
Cap the takes. Two, at most three, per script. The tenth take is rarely the best one, and on a batch day it also taxes every video after it. If a script isn't landing in three takes, the problem is usually the writing — park it, shoot the next one, and come back at the end with fresh eyes or a red pen.
TellyPrompter's batch mode is built around exactly this loop — the session moves from script to script without returning to setup between them, which sounds minor and saves its minutes on every single video.
Keeping energy through take six
Delivery energy is a budget, and batch days spend it fast. The audience for video five deserves the same person who showed up for video one; these things protect that:
- Real breaks, on a schedule. Five minutes off camera every two or three videos, before you feel you need them. Off camera means away from the rig — the pause between takes doesn't count.
- Water within reach, not in shot. Reading aloud for an hour dries you out audibly.
- Stand up between videos even if you shoot seated. Posture collapses gradually and reads on camera before you feel it.
- Watch for the tell. When you start fluffing lines you'd previously nailed, the session is over — new mistakes in old material is fatigue, not carelessness, and no take shot past that point survives the edit anyway. Better to finish a five-video day with four good ones than push through to five tired ones.
- Rehearsal mode for the nervy script. If one script has a section you keep worrying about, run it once in rehearsal — a pass that doesn't record — rather than burning performance takes on rehearsing.
Capture for the edit: sorting, not archaeology
The edit for a batch day starts days later, when you remember nothing. The goal on shoot day is to leave your future self a labelled pile rather than a mystery.
Most of that labelling can happen as a by-product of shooting. Markers dropped mid-take become a map of every rough moment. The stumble report per take answers "which of the two takes was cleaner" at a glance, and each take's timing is kept, so you also know which was tighter. Ending the take writes the file — in TellyPrompter, finishing a take, disarming the camera or leaving for the library all save the recording, so a perfect performance can't end with no file.
Captions are the other edit-day gift. Because the prompter follows your voice word by word, it can export SRT or VTT caption files built from the script and your actual timing — script-accurate, no transcription pass, no mis-heard words to fix. Export them on shoot day while the takes are named and fresh, and the edit inherits captions for free.
Beyond the app: keep filenames or a one-line note per video ("v3 — take 2 is the keeper"), and shoot ten seconds of room tone once for the whole session.
The one-page batch-day checklist
Before the day: scripts written and read aloud once each; tagged into a batch queue; order set (warm-up, hardest, easiest last); rig checked — mirror mode, font size from your mark, mic level.
Per video: load script → one-paragraph level check → take → mark stumbles, don't stop → "Telly, again" if it needs a second pass → check the stumble report → export captions → next script.
Per hour: break off camera; water; stand; posture check.
End of day: confirm every video has a take you'd ship; note the keepers; room tone; charge everything for next time.
The point of all this structure is a paradox worth keeping in view: the system exists so that the performance can be unsystematic. When the scripts are ready, the queue is loaded and the retakes are one spoken word away, the whole of your attention is free for the only thing a batch can't prepare in advance — sounding like yourself, six times in a row.