KENYA · GUIDE 0678 · EDITION 4.2
Livestream production in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Assign responsibility for programme cues, audience permissions and platform access, and distinguish the live public feed from the separately retained recording deliverable.
The operating sequence for this offer is:
- Confirm the livestream platform, access rights, event schedule and permitted content before inspecting the venue connection, power and audio arrangements.
- Run a closed rehearsal and document tested signal paths and backup recording, assigning a specific person to monitor the live output.
- Deliver the agreed recording and event report, noting interruptions honestly and applying the client's permissions for retaining or publishing audience images.
Put acceptance into the job record
The agreed feed and recording are delivered within tested conditions; internet reliability is not guaranteed.
Run the complete event sequence privately, including presentation slides and remote speakers, while someone independently watches the audience-facing stream for sound and framing problems.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Assign responsibility for programme cues, audience permissions and platform access, and distinguish the live public feed from the separately retained recording deliverable. |
| During delivery | Run a closed rehearsal and document tested signal paths and backup recording, assigning a specific person to monitor the live output. |
| At acceptance | Run the complete event sequence privately, including presentation slides and remote speakers, while someone independently watches the audience-facing stream for sound and framing problems. |
| At the pilot review | Retain a cue sheet, tested signal paths, interruption timeline, fallback actions and recording handover details to distinguish preparation failures from external connection problems. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
The camera preview may look correct while the audience hears silence, sees a frozen slide or receives restricted content through an incorrectly configured public link.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Walk through the panel running order and obtain authorized access to the client's streaming destination. Confirm the room's camera positions, available sockets, sound feed and internet arrangement with the venue. List what appears during opening, panel discussion, slides and closing. | A production sheet names the person who can authorize a delay, switch to holding screen or stop the broadcast. |
| 2 | Build separate scenes for opening card, wide shot, close-up, slides and holding message. Use approved speaker names and logos, keeping private desktop notifications and unrelated browser tabs out of the capture path. | Preview every scene and transition in a recording before connecting to the public destination. |
| 3 | Route panel microphones into a monitored mix and test both camera inputs. Record an actual speaking exchange with slides; listen from a separate receiving device using headphones so monitoring does not create an acoustic loop. | The received test has understandable sound, correct framing and no doubled audio or exposed private information. |
| 4 | Run a private rehearsal using the actual venue connection and agreed output settings. Observe encoding and connection warnings and practice the holding-screen procedure. Confirm storage capacity for the planned local recording and any separately quoted backup path. | The team documents a viable response to connection failure rather than assuming the stream will recover invisibly. |
| 5 | Start local recording and the stream according to the agreed countdown; keep a log of incidents and programme changes. After closing, verify the saved recording before deleting temporary media, then hand over the authorized recording and incident note securely. | The organizer confirms the live ending, access permissions and which recording may be shared publicly. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Audience hears an echo | Check whether desktop audio and a second device are feeding the same programme sound. | Mute the duplicate path and monitor on headphones. |
| Video drops during slides | Check encoder warnings and the actual connection test. | Use the rehearsed holding scene and agreed lower-demand configuration if approved. |
| Recording cannot be found after closing | Check recording path and file status before shutting down. | Verify playback and create the agreed backup immediately; never claim a recording exists without opening it. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.