The Pre-Recording Checklist Every Solo Creator Should Use

Most bad takes aren't caused by bad delivery — they're caused by something in the setup that nobody checked before recording started. A script that scrolls off-screen mid-sentence, audio that picks up a fridge hum nobody noticed while writing, a phone at 8% battery three minutes into a ten-minute recording. None of that is a talent problem, and all of it is preventable with a 90-second checklist before you hit record.

Audio, checked with your ears closed to the screen

Do a five-second test clip and actually listen back with headphones, not just glance at a waveform. Room echo, HVAC hum, and background noise are far easier to hear in headphones than through a phone's own speaker while you're standing in the room — you've adapted to the ambient noise, so your ears filter it out live in a way a recording won't.

Script visible from your actual recording distance

Text that's readable when you're testing up close can be too small once you back up to your real recording distance. Check legibility from where you'll actually be standing or sitting, not from arm's length while setting up — and confirm the script is positioned at your camera's eye-line rather than floating elsewhere on the screen, since that's the detail that determines whether you look like you're talking to the camera or reading off of it.

Battery and storage, not just "probably fine"

A dead phone or a full storage warning mid-recording is one of the most avoidable ways to lose an otherwise-good take. Check both explicitly before a session that's going to run more than a few minutes — "it was fine yesterday" isn't the same as checking today, especially if you've been shooting photos or other videos since the last charge.

Frame yourself for the crop you'll actually need

If this recording is going to more than one platform, center yourself in frame rather than off to one side — an off-center subject survives a vertical recording fine but can get awkwardly cropped once you export to square or landscape for other platforms. This is a five-second framing check before you record, versus a re-shoot after you notice the crop looks wrong in editing.

Light check from the lens's perspective, not your eyes'

A room can look adequately lit to your eyes while looking underexposed or harshly shadowed to a camera sensor, which handles dynamic range very differently than human vision. Glance at the actual camera preview, not the room, before recording — and if the background is genuinely messy or distracting, a background-blur mode does more for the finished look than most lighting adjustments would.

Have a plan for the line you'll probably fumble

Every recording has at least one section — a product name, a stat, a tricky transition — that's more likely to trip you up than the rest. Know before you start whether you're going to stop and restart on a fumble or keep rolling and flag it for a later trim; deciding this mid-recording, in the moment of actually fumbling, is where a lot of unnecessary full restarts come from.

Why a checklist works better than trying to remember

The individual items above are things most creators already know matter — that's not the problem. The problem is that under the mild pressure of "I'm about to record," it's easy to skip straight to hitting record and rely on memory, and memory reliably fails to flag the one thing that's actually wrong that day. A checklist isn't there because these details are hard to know; it's there because they're easy to forget in the specific moment you're most likely to forget them.

Adjusting the checklist for where you're actually recording

A home setup with the same desk and lighting every time can shrink this checklist over time, since most of the variables stay constant session to session. Recording somewhere new — a hotel room, an outdoor location, someone else's office — is exactly when the full checklist matters most, because every item that's normally a known constant (the room's echo, the available light, the background) is suddenly a variable again. Treat a new location as a reason to run the complete list slowly, not skip it because you're in a hurry to get the shot.

What to do when something fails mid-checklist

Occasionally a check turns up a real problem with no quick fix — audio you can't clean up with repositioning, light that's genuinely too harsh at this hour. In that case, it's almost always better to reschedule than to record anyway and hope editing fixes it; audio problems especially are far harder to fix after the fact than to avoid before recording. A checklist that catches a real problem and gets ignored anyway isn't doing its job — the whole point is catching it while it's still cheap to fix.

Adjusting the checklist for different content types

A quick 20-second social clip doesn't need the same rigor as a 10-minute tutorial or a pitch video — but the checklist items that matter most shift by format, not just shrink uniformly. For short clips, framing and lighting matter most since there's no time to recover from a bad first impression. For longer tutorials, audio and battery/storage checks matter more, since a problem discovered five minutes in costs far more than one caught in the first ten seconds. For anything higher-stakes like a pitch video, run the full list every time regardless of length — the cost of a re-shoot is highest exactly when the content matters most.

Building a checklist that's actually yours

The list here is a solid default, but the most useful version of this checklist is the one you build from your own actual mistakes. If you've ever lost a take to a specific, avoidable problem — a notification sound, a door slamming, a lighting change from the sun moving — that's a strong candidate for a permanent line item on your personal list, even if it's not a universal concern for every creator. A checklist that reflects your specific recording environment and your specific past mistakes catches more real problems than a generic one ever will.

The whole checklist, in order

• Test clip, listened back on headphones
• Script legible and positioned at eye-line from actual recording distance
• Battery and storage explicitly checked, not assumed
• Framing centered for whatever crop/export you'll need later
• Camera-preview lighting check, not a room glance
• Fumble plan decided before you start, not during

Run through it once, out loud if it helps, before every session longer than a quick clip. It costs less time than a single avoidable re-shoot.

How long should this actually take?

Once it's a habit, the full checklist takes under a minute for a familiar setup — most of that minute is the headphone audio test, since everything else is a quick glance. It only feels slow the first several times, before the specific checks become automatic. If it's still taking several minutes after a few weeks of using it regularly, that's usually a sign one or two items need a faster method (a saved lighting position, a standard mic placement) rather than a reason to skip the checklist altogether.

Why skipping "just this once" rarely stays a one-time thing

The moments a checklist gets skipped are predictable: you're in a hurry, you've recorded successfully without it recently, or the content feels low-stakes enough that a problem seems unlikely. Those are also, unsurprisingly, the exact conditions under which problems actually happen — being rushed is when a battery check gets missed, and "it's just a quick clip" is exactly the kind of recording where a bad take is most annoying to redo because it feels like it shouldn't have taken long in the first place. Treating the checklist as unconditional, not situational, is what keeps it from quietly eroding over time.

Pairing the checklist with your actual recording tool

A checklist works best when it maps directly onto what your recording setup actually does, not a generic list disconnected from your real workflow. If your teleprompter app has an auto-contrast toggle, a lens switcher, or a framing guide, build the check around confirming those specific settings are right for this session rather than a vague "lighting looks okay" — the more the checklist reflects your actual tool's actual controls, the faster and more reliable it becomes to run through before every take.