Your first holding statement is approved. Mobile data has failed around the affected site, so the team reaches for radio and satellite backups. The message owner expects immediate release. The radio custodian refuses because nobody has identified the licensed channel. Both are doing their jobs.

The delay comes from a false hand-off. Editorial approval answers what may be said, to whom and in which version. It does not answer whether this terminal, on this frequency, from this place, may transmit it. That decision belongs to the licensee, network provider or authorised operator under the law of the transmitting territory.

If you merge those decisions, one mandate usually disappears. Communications may broadcast an approved message unlawfully. Technical staff may hold a useful statement while they seek facts that editorial approval has already bounded. You need two clearances running against one release clock.

Pre-approve the release machinery. Preparation fails when a template contains assumed incident facts. The approval then looks complete until the first verified detail contradicts it. The argument starts again under pressure.

Approve structure, tone, blanks, roles, substitutes and publishing access. The UK NCSC recommends adaptable pre-approved templates for media requests, internal updates and customer notifications. Prepare an owned crisis page, low-bandwidth copy and private contact routes. Leave event time, effect, cause and affected population blank until verified.

Give the communications lead authority over the factual core and audience versions. Give a technical lead authority over each transmission path. Record deputies for both. An approval from one side cannot substitute for the other, even when the same person happens to hold both roles.

Build a two-gate release clock. Sequential clearance creates avoidable delay. The operator first sees the message after editorial work finishes, then discovers that the proposed bearer has an expired account, an unapproved terminal or the wrong jurisdiction.

Start both checks when the incident is verified. Editorial staff assemble the smallest useful fact set. Operators test the intended route and its alternate at the same time. NIST SP 800-53 Revision 5 puts alternate telecommunications agreements in CP-8 and testing in CP-8(5). A contract on file still needs a tested path.

The release record shows two decisions. Editorial clearance names the version, audience and information limits. Transmission clearance names the terminal, service, territory, authorisation and operator. If the primary path fails either test, move the same approved version to the next cleared path.

Release a bounded account. A first statement fails when it tries to explain the whole incident. Cause, responsibility and final impact are often the slowest facts. Waiting for them leaves affected people without useful action and lets copied reports become the working account.

State what occurred in neutral terms, when and where if confirmed, who may be affected, what action is required, what remains unknown and where the next update will appear. Give the release a version and time. The UK GCS STOP guide places verification and an immediate holding statement inside a first-hour workflow, followed by first-day and first-week work. That is a UK planning model, not a universal 60-minute rule.

The next-update route matters because the radio message may outlive the facts. Point every short broadcast to one owned source or contact route. If connectivity prevents that source from loading, the message still states when and through which cleared channel the next version is expected.

Sequence audiences by the decision they face. A single public release is attractive because it is fast to approve. It can expose personal information, surprise families or arrive too late for someone who must shelter, stop using a product or account for staff.

Send protective instructions to people in immediate danger. Use a private route for directly affected people and families. Give authorities the information their process requires. Then publish the account that employees, customers, media and the wider public can use. These streams can run in parallel when privacy and legal dependencies allow.

Some orders are jurisdiction-bound. In US transportation investigations, 49 USC 1136 requires NTSB family briefings before public briefings about accident cause. Under US FDA guidance applying 21 CFR 7.49, a recalling firm promptly notifies affected direct accounts and gives stop-use, downstream-notice and disposition instructions. Neither rule creates a universal audience order. Each shows why the release map must name the decision and governing instrument.

Authorise the actual transmission. Equipment labelled for emergencies encourages category thinking. The governing object is the transmission. A certified radio may still use an unauthorised frequency, exceed permitted power or sit outside its licensed area.

For every radio or satellite path, verify the terminal, frequency, power, place, service, antenna, mode, equipment approval, responsible licensee and operator permission. Add import, customs, registration and network-account evidence where they apply. Write the jurisdiction and actual licence, exemption or temporary authority beside the path. Urgency supplies no universal permission.

The ITU Radio Regulations, 2024 edition, incorporate WRC-23 decisions, but national administrations license local use. In the United States, 47 CFR Part 90 defines Public Safety Pool eligibility and reserves five 800 MHz mutual-aid channels numbered 1, 39, 77, 115 and 153. A corporate team cannot infer access from urgency or from a programmed partner radio. Under 47 CFR Part 25, a provider may instead hold blanket authority for covered satellite user transceivers.

In the United Kingdom, Ofcom Simple UK Light permits 19 frequencies across four Business Radio bands and caps effective radiated power at 5 W. Simple Site Light covers 1 km or less. A temporary base station, repeater or larger footprint can therefore require another product even when the hardware is unchanged.

Border movement changes the check again. A Canadian radio licence normally lasts one year and specifies apparatus, location or radius, frequencies and power. Australia has 17 class licences requiring no application or fee, while its land-mobile regime offers six options under the Radiocommunications Act 1992. A broad permission still carries technical conditions.

India’s 2026 Rule 62 requires an overseas-registered satellite terminal to be registered before operation. A stationary fixed terminal is bound to its premises within plus or minus 100 m. In the UAE, satellite phones require Type Approval and generally must connect to a UAE licensee unless an effective roaming arrangement applies. A satellite footprint settles none of those national controls.

Keep the operator inside the correction cycle. Communications teams often record what they issued while technical teams record whether a channel opened. Neither log can show which audience actually received which version.

Maintain one versioned owned source. Archive every superseded statement, correction reason, approval and publication time. The operator log links each channel, terminal, operator, authority, transmission time, coverage or recipient set, acknowledgement and failure to that version. CAP 1.2 provides five useful transaction states: Alert, Update, Cancel, Ack and Error. An Ack still proves message acceptance rather than audience understanding.

Channel-specific correction times must stay visible. The FCC’s 2018 Hawaii investigation recorded an authoritative social-media correction after 13 minutes and EAS and WEA corrections after 38 minutes. One corrected source did not mean every distribution path had carried the correction. Your record must preserve that gap.

Exercise the competing mandates together. A message exercise that ends at approval misses the seam. A radio test that sends filler text misses the privacy, audience and correction decisions that constrain a real release.

Run the release with incomplete facts, one affected family awaiting private contact and a primary network failure. Make the communications lead issue a bounded version while the operator rejects one unlawful path and clears another. CISA’s 2024 PACE guidance describes four levels current as of 2023: Primary, Alternate, Contingency and Emergency. Each level still needs its own authority and evidence.

The useful measure is whether both records agree after the exercise. The owned source should show what governed at each time. The technical log should show which channels carried it. When those records diverge, you have found the delay before an incident makes it consequential.