Airports Editing and Proofreading Services

Fog closes the destination airport and thirty-one flights divert to an airport that was expecting four. There are no plans printed anywhere that say what happens next in specific terms: which gate agents get pulled from other duties, how many buses go where, whether the hotel contracts negotiated last year actually cover a night like this, and who tells four thousand unexpected arrivals anything at all before they work it out for themselves from the departure boards.

We edit what airports produce for irregular and disrupted operations — mass diversion and irregular operations plans, contingency and business continuity documentation, passenger communication scripts for major disruption, coordination briefings between airport, airline and ground handling teams, after-action reports following a disruption event, stakeholder notifications to local authorities and emergency services, and the annual exercise scenarios used to test all of it. Our editors work on plans that are read for the first time during the event they were written for.

The specific trigger and response is what makes a diversion plan usable at 2am rather than merely filed, and its failure is a plan that describes principles instead of actions. An airport should aim to manage disruption effectively describes an intention, not a plan. We work through these so each trigger is stated as a number — a diversion count, a passenger volume, a duration — with the specific response that number activates, since "significant disruption" means something different to everyone reading it and a number does not; so who does what is named by role rather than by department, given that "ground operations will coordinate" tells nobody which desk to call at 2am when the duty manager is dealing with three other things; so existing contracts and capacity are checked against the plan's assumptions rather than assumed to still hold, because a hotel block negotiated for forty rooms does not cover four thousand passengers and a plan that assumes it does fails exactly when it is tested; so passenger communication is scripted in advance for the most likely scenarios, as writing an announcement during the event itself is where the clearest information gets lost; so the plan states who has authority to activate it, given that a good plan sitting unopened because nobody was sure they were allowed to trigger it protects nobody; and so an after-action report distinguishes what the plan got right from what had to be improvised, since a report that only records what happened tells the next writer nothing about what to fix. Plans written this way get used instead of referenced afterward as evidence nobody followed them.

Everything you send is treated in confidence, including operational data, contracts and incident information. We are editors rather than airport operators, emergency planners or aviation safety specialists, and we offer no view on operational decisions or capacity. What we can do is make the plan specific enough to be followed under pressure.