Two ways to put an event online
Most organisers who ask us about streaming have already settled on the idea and are stuck on the method. There are really two routes. The first is to bring in a production crew who take responsibility for the whole outgoing feed: encoding, signal routing, and watching the stream while the event runs. The second is to ask someone already on your payroll, often a technically minded member of the events or comms team, to run it with a laptop, an encoder and a good deal of goodwill.
Both routes can work, and I have seen each of them go well and go badly. The difference rarely lies in the equipment, which is broadly similar either way. It lies in what happens at the moment something goes wrong, and in who has the spare attention to notice it first. This article sets the two options side by side and ends with a recommendation, because a comparison that refuses to choose is not much use to you.
What a dedicated crew actually does
When we run a streamed event end to end, the work divides into three jobs that happen at once. Someone looks after encoding, making sure the picture leaves the building at a bitrate your venue's connection can sustain. Someone looks after signal routing, so that cameras, slides, graphics and any remote guest reach the right place at the right time. And someone watches the outgoing feed as a viewer would, on a separate device, with headphones on.
That third job is the one people underestimate. A stream can look perfect on the monitor in the room and be silent, frozen or badly delayed for the audience. Because the monitoring person has nothing else to do, a fault is usually caught within seconds rather than when the first complaint arrives in the chat. You also get a fixed point of contact before the day, which is where much of the real reassurance comes from.
- Encoding set to suit the venue's upload speed
- Routing checked source by source before doors open
- A separate pair of eyes on the outgoing feed
What an in-house operator can do well
Do not dismiss the second option. A capable colleague who knows your organisation brings something a visiting crew cannot: they understand the people, the running order and the unwritten rules about who must never be cut off mid-sentence. For a regular, low-risk broadcast such as a weekly talk, an internal briefing or a small lecture, one trained person with a simple setup is often entirely sensible and much cheaper over a year.
The trouble starts when that one person is asked to do everything. They switch, they check audio, they field messages from the organiser and they glance at the stream when they can. Attention is the limited resource. Our operator training sessions exist partly for this case, teaching signal flow and live show discipline so that a small team handles routine events with confidence and knows when a job has grown past what they should attempt alone.
Where the two options part company
Set them against each other and four things decide the matter. The first is consequence: what happens if the stream fails for ten minutes? For a paid conference, a funeral service or a public ceremony, the cost is high and it lands on you. The second is complexity: more than two sources, a remote guest or a live graphic changes the job from operating one device to running a small gallery.
The third is repetition. Something you do every week builds skill and justifies owning the kit. A single large event does not. The fourth is cover. A crew arrives with spare cables, a backup encoder and the habit of testing a second route for the signal. A lone operator has whatever fits in the bag, and when the venue's network drops, there is nobody to fix it while someone else keeps the show alive.
- Consequence of a failed stream
- Number of sources and remote contributors
- How often the event repeats
- Spare equipment and a second pair of hands
Our recommendation
For a one-off or high-stakes event, book a dedicated crew. The cost is real, but it buys the one thing you cannot improvise on the day: someone whose only job is to keep the feed healthy while you attend to your guests and your programme. If the event matters to your reputation or your income, treat the outgoing stream as part of the event rather than an extra bolted on afterwards.
For regular, modest broadcasts, train your own operator and keep them. Give them a written checklist, a rehearsal before each show and a clear rule about when to phone for help. Many of our clients end up combining the two, using their own person for routine shows and calling us for the larger occasions. That pattern is sensible, and it is the one I would choose myself in your position.
Questions to settle before you decide
Before choosing either route, answer a few plain questions in writing. How many people will watch, and what do they expect to see? What is the upload speed at the venue, tested on the day of the week and hour you will be live? Who, specifically, is responsible if the picture drops? If no name comes to mind, that gap is your answer.
Then ask what a bad hour would cost you. If the answer is a shrug, run it in-house and learn from it. If the answer makes you wince, the crew is the cheaper choice. Either way, arrange a rehearsal with the real equipment in the real room, because almost every problem we meet on the day was findable the afternoon before.
- Expected audience size and what they will see
- Tested upload speed at the actual venue
- A named person responsible for the feed
The choice comes down to what a failure would cost and how often you broadcast. A crew suits the large, rare or high-stakes event; a trained colleague suits the regular, modest one, and many clients sensibly use both. Whichever you choose, rehearse in the room, name one person who owns the outgoing feed, and watch the stream as your audience will. If you want to talk it through, get in touch through the contact page.
