The shape of a live day
Most guidance about live production describes equipment. Much less describes the day itself... what you do, in what order, and where the time actually goes.
This is the shape of a routine week for a small team. Not a perfect run; a normal one, with the parts that matter marked.
An hour before: verify, do not configure
The first thing to understand about setup is that most of it is checking, not building.
Your system worked last time. The question is whether anything has changed since... and things change without anyone changing them. A monitor was unplugged for a meeting. Someone borrowed a cable. Windows updated. A phone that used to be a camera has a new owner.
So the first twenty minutes is verification:
Does the machine start and connect? Power, network, the software running.
Are the cameras joining? Each phone on, connected, appearing where it should. This is the most common thing to need attention, and the reason to do it first: if a camera will not join, you want an hour to solve it, not five minutes.
Is the output going where you expect? Look at the projector or screen and confirm it shows what you intend. Not the settings... the actual screen. Settings can be correct while the result is wrong.
Is audio arriving? Speak into the microphone and watch the level move. This takes seconds and catches a category of problem that is otherwise invisible until it is live.
Is the recording configured and is there disk space? Both. A recording that fails for lack of space is a recording that did not happen.
Only after all that do you touch anything specific to today.
Forty minutes before: today's specifics
Now the parts that differ from last week:
Load the plan. Songs, passages, slides, whatever the order is. If someone prepared it earlier, this is where you find out whether it is complete.
Check the decks. Open anything a speaker sent. This is where you discover that a file is the wrong format, or has an aspect ratio that will letterbox awkwardly, or contains a video with sound you were not expecting.
Frame the cameras. With people in the room if possible... an empty room frames differently from a full one.
Set anything unusual for today. A guest speaker, a baptism, a special item. The unusual parts deserve the attention, because the routine parts are routine.
Twenty minutes before: the last honest check
This is the most valuable window in the day and the one most often lost to conversation.
Look at what is actually going out. Not the settings... the output. If there is a way to see the program feed, look at it now.
Start the recording and confirm it is running. Not "click record and assume." Confirm.
Check the stream is connected, if you are streaming, before there is anything to see.
Decide who is doing what. Even a two-person team benefits from ten seconds of "you are on cameras, I am on lyrics."
Then stop touching things. The temptation in the last ten minutes is to improve something. Resist it. Changes made in the final minutes are the ones that break, because there is no time left to notice.
During: less than you would think
A well-set-up live day is not busy in a dramatic sense. It is a sequence of small, timely actions: advance the line, cut to the other camera, hold the wide during the quiet part.
The things worth knowing:
Most problems are not worth solving live. If something degrades but the output is still going out, note it and continue. Mid-event fixes carry a real risk of turning a small problem into a visible one.
Watch the room, not just the screen. The screen tells you what you are sending. The room tells you what is happening... a speaker moving, someone about to come up, a song ending sooner than planned.
Stay slightly ahead of the plan. Know what is next before it arrives. The difference between a smooth operator and a stressed one is usually ten seconds of anticipation.
If something breaks visibly, do the simple thing. A holding slide, a wide shot, a return to the last known good state. Do not debug in front of the room.
Afterwards: five minutes that matter
The temptation is to shut down and leave. Five minutes here prevents most of the problems people write to us about.
Stop the recording properly and confirm the file exists. Open it. Play three seconds.
Copy it somewhere else if you can. The laptop is not a backup.
Note anything that went wrong while it is fresh. One line is enough.
Leave the system in a known state. This is the most underrated habit available to a rotating team. The next person (possibly you, possibly not) inherits whatever you leave behind. A system left in a strange configuration is next week's mystery.
The pattern underneath
If there is one thing to take from this, it is the first rule and the last:
Start by verifying, end by resetting.
Most live-day problems are not caused by something breaking during the event. They are caused by a state left over from before... a setting from a special event, an output changed for a rehearsal, a device someone borrowed. The event does not create these problems; it reveals them.
Which means the highest-value habits are at the edges. Twenty minutes of checking at the start, five minutes of tidying at the end. Neither is interesting. Between them they prevent most of what goes wrong.
The middle, the part that feels like the job, mostly takes care of itself once the edges are right.