Broadcast production is a promise made at a specific time. Viewers and listeners should receive the intended programme, with appropriate editorial checks, rights, sound, accessibility and continuity. A perfect studio rehearsal is not enough if the wrong version goes to air or nobody can explain a transmission failure.
This guide follows a fictional local television programme threatened by an outdated caption track and a live technical disruption. It explains how rundown control, editorial clearance, signal coordination, playout, broadcasting rules, operational fallback and records connect into one service.
The adjacent Media guide addresses publishing accountability; Film Production covers making finished audiovisual work; and Streaming Services addresses on-demand playback. This article focuses on scheduled live and linear radio/television operations.
Find the part you need
Choose a chapter group or follow the full broadcast journey from content selection to the record of what actually aired.
Chapter index
Scope, governance and editorial · Chapters 1–6
- The programme must reach the audience that expects it
- Know whether the service is linear broadcast, radio or on-demand
- Assign accountability for every live handoff
- Build a running order that can withstand real change
- Make factual material ready before airtime
- Verify media assets, schedules and rights before transmission
Signals, sound and access · Chapters 7–10
Playout and resilience · Chapters 11–13
Measurement and accountability · Chapters 14–16
1. The programme must reach the audience that expects it
A fictional local television operation, Harbour Evening, plans a live community programme for 7 p.m. Its production rundown looks complete, the presenter is ready and a prerecorded guest segment has been approved. Seconds before transmission, master control discovers that the item scheduled in the automation system is an older cut without the corrected captions. During the programme, a weather-related infrastructure issue further threatens the live feed.
The gold standard of broadcast production is not a stylish set or a perfect rehearsal. It is a coherent, authorised programme carried through live and recorded workflows into dependable transmission, accessible presentation and accurate records when conditions change. Broadcasting is especially demanding because time and continuity matter: a viewer or listener cannot simply wait for the editor to find the right file. Harbour Evening is fictional, and its problems are an operations case rather than a report about any actual broadcaster.
Back to chapter index · Next chapter
2. Know whether the service is linear broadcast, radio or on-demand
A scheduled linear programme, a free-to-air radio station, a nationwide subscription television service and an on-demand video library are not automatically governed by identical licences or content rules. Broadcast producers need to know the actual provider, distribution medium and legal scope before deciding what may be transmitted.
Singapore IMDA’s TV and Radio framework explains the distinction between free-to-air, subscription and on-demand offerings. Its current code directory separates nationwide managed linear television content, radio services, OTT services, advertisements and broadcast technical standards. A programme cleared for one outlet should not be assumed authorised everywhere without evaluating the different requirements.
Back to chapter index · Next chapter
3. Assign accountability for every live handoff
Broadcast output draws from editorial teams, studio crews, field units, transmission engineers, caption providers, playout staff, commercial scheduling and management. The existence of many specialist roles makes it especially important to identify who owns the final transmission decision and how authority moves during an incident.
For the fictional live programme, editorial approval of a guest segment and master-control acceptance of a file are related but distinct. An approved edit should have an identifiable asset and version, while the operator needs clear permission to place it on air. The responsibility register should specify who may replace a clip, interrupt scheduled output, approve corrected information and escalate a serious technical or editorial fault. Ambiguous titles lead to ambiguous decisions when minutes matter.
Back to chapter index · Next chapter
4. Build a running order that can withstand real change
A rundown coordinates stories, presenters, recorded inserts, live guests, advertisements and technical cues. Each element needs meaningful duration and status information, but a document alone does not make it ready. A contributor may be unavailable, an edited package may change length, or a breaking event may require a different sequence.
Give programme teams a controlled version and a shared understanding of which changes must be communicated to studio and playout. Harbour Evening cannot rely on a producer’s personal notes when its caption provider and engineering crew use the prior running order. Test foreseeable substitutions and transitions. A good rundown is a live agreement among accountable functions rather than an optimistic list of segments that no longer reflects the broadcast.
Back to chapter index · Next chapter
5. Make factual material ready before airtime
Live and recorded news content needs appropriate sourcing, context and editorial review. A rapidly developing event can tempt a team to repeat unverified information because viewers are waiting for an update. A reliable organisation distinguishes verified findings from developing reports and prepares language for material uncertainty.
The SPJ Code of Ethics describes truth-seeking, independence, fairness and correction as professional principles. For Harbour Evening, the weather segment should use identified official or otherwise reliable sources and clearly explain what is known. Producers should not create a dramatic ‘evacuation order’ graphic from an unverified message. The appropriate official authority determines emergency instructions; a broadcaster’s duty is to communicate responsibly, not invent command authority.
Back to chapter index · Next chapter
6. Verify media assets, schedules and rights before transmission
An automation server can play an audio-video file reliably while that file contains old information or lacks relevant distribution rights. Content metadata needs to include approved identifier, duration, language, captions or alternate audio where applicable, authorised territories and version. People should be able to distinguish a master from a review export by more than a filename ending in ‘FINAL’.
Before airtime, production control should reconcile the rundown with the actual playout asset and its editorial and legal approval. The older guest clip in the fictional scenario should be visibly out of date or blocked once superseded. Copyright, performance, commercial sponsorship and archive use may carry different licence scopes. The existence of a usable file on the station’s server is not proof that it can lawfully be transmitted in every market.
Back to chapter index · Next chapter
7. Connect sound, picture and timing across the studio
Studio audio, cameras, graphics, live links and prerecorded segments need to work together. Even when each source is individually correct, a wrong routing decision, mismatched reference or unexpected delay can make the broadcast unusable. Technical producers need a shared plan for source identification, transitions and monitoring.
SMPTE ST 2110 defines a suite for transporting separately identified and synchronised professional audio, video and ancillary media streams over managed IP networks. It is one important modern architecture, not an obligatory design for every small broadcaster. Whether a facility uses IP or other supported technology, it should test timing, source routing and approved fallback procedures with qualified engineers rather than assume correct signals will assemble themselves.
Back to chapter index · Next chapter
8. Control loudness and dialogue intelligibility for the distribution chain
Broadcast audio may alternate among studio conversation, field reports, prerecorded music and advertisements. Abrupt loudness differences reduce comfort and comprehension. Peak metering alone cannot establish consistent perceived level, and mixing needs to account for speech clarity and the relevant channel.
EBU R 128 version 5 (November 2023) recommends a broadcast programme target of -23 LUFS with defined loudness and true-peak measures. ITU-R BS.1770-5 specifies algorithms used for relevant measurements. Particular broadcasters and platforms may set other delivery rules. Engineers should follow the actual station specification and test how changes between programme and commercials affect real listeners, not assume EBU’s numerical target is universal law in Singapore.
Back to chapter index · Next chapter
9. Keep captions, subtitles and audio access matched to the on-air version
Accessible television production may require captions, subtitles or other services depending on platform, content and obligations. These tracks must correspond to the actual transmitted cut, including late script changes and inserted items. A technically valid text file is not useful if its timing or words belong to yesterday’s edit.
The W3C guidance on accessible audio and video explains caption and audio-description considerations. Web guidance does not automatically replace specific broadcast licensing rules. Harbour Evening’s master control should verify that the corrected guest segment and caption version form one approved package. If a live event cannot be captioned to the intended standard, the organisation should follow its applicable procedures and be transparent about what is actually available.
Back to chapter index · Next chapter
10. Identify commercial and editorial content transparently
Advertising, sponsorship, branded features and ordinary editorial programmes can follow different approval arrangements. A station should not let a sponsor’s payment silently change the factual conclusions of a news segment or present a paid endorsement as an independent interview. The broadcaster needs a clear interface between sales traffic and editorial control.
IMDA’s Television and Radio Advertising and Sponsorship Code is listed separately from programme content and technical standards. Those local rules should be assessed for the licensed service and content category. Even where a particular creative format is permitted, the audience should be able to recognise material sponsorship and the organisation should know who approved the commercial claims.
Back to chapter index · Next chapter
11. Treat master control as a final operational decision point
Master control or playout automation needs a dependable relationship among content inventory, schedule, technical format, transmission path and alarms. A playlist entry can look correct while its asset link points to an outdated master or a file whose audio channel mapping has changed. Automated operation must be supported by meaningful preflight verification and trained human oversight.
Run operational acceptance checks appropriate to the service, including file availability, duration, content and technical identifiers, audio tracks, captions and transitions. Do not reduce the work to a green ‘file present’ status. When staff make a last-minute replacement, record the reason and authorised version so later investigation can reconstruct what the audience actually received. Dependable playout makes creative work visible instead of turning invisible technical errors into public confusion.
Back to chapter index · Next chapter
12. Build redundancy around consequential failures
Live networks, field connections, servers and transmission services can fail. A service should identify which interruptions matter most and establish feasible, tested fallback options under its operational constraints. Redundancy does not mean purchasing two of everything; it means avoiding unacceptable single points of failure where risk and obligations justify a backup.
Rehearse scenarios such as a missing programme master, field-link dropout, operator absence or network interruption. A backup path that has never been tested during a relevant configuration change may not be dependable. Engineering teams should know who can move traffic, how continuity will be checked and which safety or legal requirements remain in force. The broadcaster’s promise is to operate responsibly even when ordinary conditions break down.
Back to chapter index · Next chapter
13. Handle live incidents with authorised decisions and truthful information
During an incident, technical restoration and audience communication must not be confused. Restarting a playout service may restore picture without ensuring the correct programme version, subtitles or commercial schedule. An interrupted news item may need explicit clarification if viewers received incomplete information.
Maintain a time-stamped event log, accountable decisions and suitable post-transmission records. For Harbour Evening, the weather-related issue should trigger the engineering response plan while editorial staff verify any public safety information with the correct authority. Do not invent restoration times or claim that all viewers are unaffected because one monitor in the control room looks normal. Broadcast resilience includes honest status and qualified recovery.
Back to chapter index · Next chapter
14. Measure the signal and the audience’s actual experience
Technical metrics can describe signal continuity, timing, audio levels, caption delivery and programme availability. Audience ratings and viewing figures describe something different. A high audience number does not establish that content was accurate, and a technically uninterrupted channel can still broadcast the wrong segment.
Use operational monitoring and appropriately collected feedback to find failures that an aggregate uptime measure conceals. Record incidents by cause: content version, rights, playout, connectivity, caption mismatch or incorrect schedule. Protect viewer information, and avoid interpreting every channel change as dissatisfaction with content. The eduKate Data Analytics guide reinforces the importance of using measures to support actual decisions.
Back to chapter index · Next chapter
15. Prepare archives and legal records for what really aired
A broadcaster may later need to establish what was transmitted, when, under which editorial and commercial approvals, and whether it retained relevant records under licence or law. Source files, approved masters, captions, traffic schedules and actual transmission logs are different forms of evidence. Each needs appropriate identity and retention.
The EBU Broadcast Wave Format supports identifiable audio exchange and metadata in professional workflows, while broader audiovisual archives need suitable record and file management. A studio master may not by itself establish exactly what the public saw if last-minute substitutions occurred. The organisation should retain the right evidence through lawful, secure and recoverable procedures rather than rely on a single employee’s memory.
Back to chapter index · Next chapter
16. The gold standard is reliable, accountable time on air
Return to Harbour Evening. The approved guest version, correct captions, current schedule, sound and rights now match. Master control knows which source is on air, engineering has tested a fallback and the team has a clear method for correcting material misinformation or technical defects. The station can explain what happened during the original interrupted programme.
Broadcast production earns its gold standard when creative teams and technical systems coordinate around an authorised, accessible and dependable service. The true achievement is not the absence of every future failure. It is a system that knows what should be transmitted, can verify what actually went out and has the capacity to recover transparently when the two diverge.
Worked example: the right show, the wrong on-air version
This is a fictional broadcast incident. The examples describe organisational controls, not procedures for altering live transmission equipment.
| Stage | Apparent success | Missing evidence |
|---|---|---|
| Editorial | Guest segment approved | Correct version and source clearance |
| Captions | Text track generated | Timing matches on-air cut |
| Automation | Playlist entry exists | Approved media asset actually linked |
| Transmission | Technical service available | Correct signal reaches target distribution path |
| Incident recovery | Primary system restarts | Output, content, captions and messages verified |
| Archive | Final studio master saved | Actual as-aired record and approval history |
The broadcast readiness checklist
- Licence category and applicable content, advertising and technical codes are understood.
- Editorial rundown and authorised media versions share a reliable identifier.
- Factual and rights clearance are complete for the intended outlet.
- Audio, video and supplementary data are checked for timing and compatibility.
- Loudness and captions meet the actual platform’s requirements.
- Master control can recognise a wrong asset before transmission.
- Fallback and escalation plans are rehearsed, including communication duties.
- As-aired logs, correction records and audience-impact reviews are preserved.
Broadcast standards and connected eduKate reading
- Singapore IMDA — Current Codes for Radio and Linear Television
- Singapore IMDA — Free-to-Air Television Licence (2026)
- Singapore IMDA — Free-to-Air Radio Licence (2026)
- SMPTE — ST 2110 Professional Media over Managed IP
- EBU — R 128 Broadcast Loudness Normalisation
- EBU — Radio Production and Distribution Loudness Guidelines
- W3C — Accessible Audio and Video Media
- eduKate — Media
- eduKate — Film Production
- Gold Standard Sectors and Services Directory
Broadcast licensing, editorial content rules, advertising, accessibility, music use and technical transmission requirements differ by jurisdiction and service category. SMPTE and EBU standards guide technical practices but do not replace the actual broadcaster’s contract or regulatory duties. This is production-management education rather than an operational switching or emergency-transmission protocol.