A Checklist for Planning a Live Stream and Recording Before You Commit

Before any equipment is discussed, I ask the same thing in our practice sessions: who is going to watch this, and what should they be able to do afterwards? A stream for a product reveal aimed at press needs different decisions than a recording meant for a internal team. Write the audience down in a sentence. Then write what a viewer should remember when the stream ends.

This sentence becomes the filter for everything that follows. If the audience is remote customers, clear speech matters more than a second camera angle. If the recording will be cut into short clips, you need clean moments to cut from, which affects how presenters pause between segments.

In Module 5 we begin each exercise this way, because a stream without a defined viewer tends to collect features nobody asked for. It is a calm way to begin, and it costs nothing.

• Who watches live, and who watches later
• What should viewers know or do afterwards
• Is the stream public, private or invitation only

Most stream failures I have seen in these autumn weeks, when venues are busy and networks are shared, come from the upload connection rather than the cameras. Ask the venue for a wired connection and find out what upload speed it can actually sustain, not what the contract says. A stream needs steady upload, and a figure measured at a quiet hour may not hold during the event.

Decide in advance what happens if the connection drops. Some producers keep a second route ready, such as a separate line or a mobile bonded option, and others accept a short interruption and plan a holding slide. Neither is wrong, but it must be a decision made at the desk, not discovered mid-show.

In guided practice we measure the connection at the same time of day the event will run, then leave a margin so the stream never uses everything available.

• Wired connection preferred over venue wifi
• Upload speed tested at the event time of day
• A written plan for a dropped connection

Viewers forgive a soft picture far sooner than muffled or uneven sound. When you review a plan, look at the audio chain before the video chain: how many microphones, who wears them, who mixes them, and who listens on headphones throughout the event.

Ask whether a person is assigned to monitor the sound for the whole stream. Setting levels once at the start is not enough, because speakers lean in, move away, and change volume when the room fills. A designated listener catches this within seconds.

We also practice with backup microphones close at hand. A spare handheld on the table costs little and removes a great deal of worry when a battery fails or a clip comes loose during a reveal.

• Microphone count and who wears each one
• One person listening on headphones throughout
• Spare microphone and fresh batteries ready

It is surprisingly common to send a stream out and have no way of seeing what viewers see. Your checklist should include a separate screen showing the outgoing feed, ideally with a short delay accounted for, so the person at the desk can confirm that picture and sound match.

Think about who watches that screen and what they are allowed to do. If a problem appears, does the operator switch to a holding slide, call the presenter, or wait? Agree this beforehand, in plain words, so no one has to improvise under pressure.

In Module 5 learners take turns at the monitoring position while others present, which is the quickest way to feel how quiet the job looks and how closely it must be watched.

• A screen showing the outgoing feed
• Named person responsible for the decision to switch
• Holding slide prepared and tested

A recording is not simply a stream saved to disk. If the recording matters, ask whether it will be captured from the stream, from each camera separately, or both. Separate captures give more freedom in editing but need more storage and more careful labelling.

Think about file naming, where files are stored during the event, and who copies them afterwards. A recording left on a single drive with no second copy is a risk that takes only one dropped cable to turn into a problem.

We teach learners to label files by session and camera from the first minute, and to copy to a second drive before packing anything away. It is dull work, and it saves the afternoon after the event.

• Stream capture, camera capture, or both
• Two copies before equipment is packed
• Consistent file names by session and camera

Finally, settle what the client receives and in what form. Ask which formats are needed, whether a trimmed version is expected, and how the files will reach the client. The answers shape both the time needed after the event and the storage used on the day.

Be realistic about the time between the event ending and files being ready. Review, trimming and checking audio take longer than people expect, and rushing this step is how errors reach the final delivery.

If you can answer every item here with a clear sentence, you are ready to decide. If several answers are still vague, that is useful information too, and worth settling before any commitment is made.

• File formats and any trimmed version
• How and when files reach the client
• Time set aside for review before delivery