Broadcast Infrastructure Editing and Proofreading Services

A broadcaster schedules a transmitter changeover for a Sunday overnight window and circulates a method of procedure describing the steps. The document says to switch to the auxiliary antenna and reduce power, but never states the order, the power level to reduce to, or what to verify before proceeding. The engineer on site, working alone at 3 a.m., performs the steps in the sequence that seemed logical, and the station goes dark for forty minutes across a market of two million people during a window the licence treats as reportable.

We edit what broadcast infrastructure teams produce — methods of procedure and switching scripts for transmitter work, emergency alert system test and compliance records, tower crew work orders and rigging plans, transmitter and antenna acceptance test reports, STL and microwave path documentation, licence renewal and technical filings, outage and incident reports to regulators, translator and repeater coordination documents, and facility maintenance and inspection logs. Our editors work on the procedure an engineer follows alone at three in the morning.

The method of procedure for live transmitter work is executed by one person under time pressure with the station on air, and its failure is a step written as an instruction to a reader who already knows the answer. We work through these so each step states its actual order, the specific value to set, and the condition to verify before moving on, rather than naming an action and leaving its sequence and target to the operator's judgement at three in the morning; so any step that puts the station off air is marked as such with the expected duration, given that an engineer needs to know which action starts the clock on a reportable outage before performing it rather than after; so the abort criteria and the rollback path are stated as their own steps, since an engineer discovering a problem mid-procedure is the least equipped moment to be improvising a way back to the prior state; so terminology matches the labels physically on the equipment — the switch position, the panel marking, the actual designator painted on the cabinet — because a procedure calling a control by its schematic name when the rack says something different is one that gets performed on the wrong device; and so the specific readings expected at each checkpoint are given as values with tolerances, not as "verify normal operation," since normal is exactly what an engineer alone at night has no independent way to confirm. Procedures written this way survive being followed by one tired person with no one to ask.

Everything you send is treated in confidence, including facility documentation, technical data and operational procedures. We are editors rather than broadcast engineers, RF technicians or regulatory specialists, and we offer no view on technical procedures, equipment settings or compliance determinations. What we can do is make sure a step means the same thing at 3 a.m. as it did at the desk where it was written.