Planning a small production team for recurring online briefings
You run an online briefing every fortnight with whoever is free, and the same few people keep carrying the load.
The short answer
A small team can run recurring briefings if each role has one named owner and one named backup. The roles are: host, producer who runs the platform, content owner who handles slides and speakers, and a chat and question handler. In a team of two or three, one person holds more than one role, but never the host and producer together.
What matters is that duties are written down, rehearsed once, and handed over the same way every time.
The four roles and how to combine them
| Role | Does | Can be combined with |
|---|---|---|
| Host | Opens, keeps time, reads questions, closes | Chat handler if the audience is small |
| Producer | Runs the platform, checks audio and slides, starts and stops recording | Chat handler, not host |
| Content owner | Confirms speakers, collects slides, signs off the final deck | Host in a short briefing |
| Chat and question handler | Welcomes arrivals, filters questions, handles joining problems | Producer |
Plan capacity against the briefing calendar
Count the hours each person needs before, during and after a briefing, and check the calendar for clashes with other duties. Two briefings in the same week can double the load on the content owner.
The recurring calendar capacity planner shows when one person is expected to cover two roles at once and when a backup is needed.
What to ask the platform supplier or internal IT
- Who can start the meeting if the producer cannot connect?
- What happens to the recording and who has access to it afterwards?
- Can a co-host take over controls if the host drops out?
- What is the support route during a briefing, and is it available at the time we run?
- Which of these settings are on by default and which need switching on? Ask the supplier to confirm in writing; do not assume.
A repeatable briefing day
- Producer joins well before the start to test sound, screen sharing and recording.
- Host and speaker run through the first two minutes.
- Chat handler welcomes arrivals and posts the joining link and the rules for questions.
- Host runs the briefing to the run sheet; producer signals time.
- After closing, the producer saves the recording and the content owner notes any promised follow-ups.
Worked example · Fictional example
A three-person team running a fortnightly briefing
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Pengurus Rantaian Bekalan ran a fortnightly thirty-minute update with a secretariat officer who acted as host, producer and chat handler at once. A technical fault during a speaker's slide went unnoticed because the officer was reading questions.
The secretariat added a second officer as producer and asked a committee member to act as host. They kept one backup for each role and shared a one-page run sheet. The content owner remained the original officer, and the rota showed who held each role for each date.
Use this yourself
Briefing run sheet and role rota
Copy this into a shared document. Fill the rota for the season and print the run sheet for each briefing.
- Date and time of briefing:
- Host (backup):
- Producer (backup):
- Content owner (backup):
- Chat and question handler (backup):
- Producer joins at:
- Speaker run-through at:
- Running order with minute marks:
- If audio fails: switch to backup speaker line or ask the speaker to reconnect:
- Recording saved by (name) to (location) by (time):
- Follow-ups promised during the briefing:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Briefings are short and the team of three or four already works well together.
- You use one familiar platform and one speaker at a time.
- Staff can swap roles without extra training.
Outside planning help earns its fee when
- Briefings are frequent and the same person is covering two roles.
- Speakers join from different organisations and need briefing each time.
- The team is volunteers with fluctuating availability.
Want the team and run sheet set up for your whole season?
A recurring programme manager can map your briefing calendar against the people you have, set up the role rota and run sheet, brief hosts and speakers, and manage the handover after each briefing. Technical production remains with your platform supplier or internal IT.
Questions organisers ask
Can one person host and run the platform?
It is risky because problems on screen go unseen while speaking. Separate the roles where you can; if not, ask a backup to watch the chat and the platform.
How many people do we need?
Two can run a short briefing if one hosts and the other produces. Add a content owner and chat handler as the briefing or audience grows.
What should be in writing?
The role rota, the run sheet, the fallback plan and the supplier support route. Confirm platform settings with the supplier rather than assuming.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.