Uncrewed aircraft documentation sits on a boundary that most technology writing never approaches: it is read by regulators who can ground your fleet, by pilots making decisions in changing weather, and by landowners and members of the public who did not ask to be flown over. An operations manual is not marketing collateral with a safety section — in most jurisdictions it is the document your authorisation rests on, and it will be assessed by someone who has read hundreds and can spot a copied template immediately.

We edit what drone operators, manufacturers and service providers produce — operations manuals and standard operating procedures, risk assessments including SORA submissions, applications for operational authorisation and specific category approvals, flight and site survey checklists, emergency and contingency procedures, maintenance and airworthiness records, pilot training syllabuses and competency assessments, insurance submissions, privacy and data protection notices for aerial imagery, client proposals for survey and inspection work, incident and occurrence reports, and product manuals for aircraft and payloads. Our editors check that procedures are written as executable steps rather than intentions, and that terminology matches the regulator's own vocabulary rather than the industry's informal shorthand.

The emergency procedures section is where an operations manual is really assessed, and where most are weakest. Assessors have learned to look past the well-formatted normal operations chapter and read what happens when the link drops, the battery warning fires over a crowd, or the pilot loses sight of the aircraft in glare. Generic text — "the pilot will take appropriate action to ensure safety" — is the clearest possible signal that the procedure has never been rehearsed. We rewrite these sections so each contingency names its trigger condition, the immediate action in order, the decision point at which the flight is terminated, and who is contacted afterwards and within what time. We also make sure the emergency procedure is consistent with the site-specific risk assessment, because the mismatch between the two is the most common reason an application comes back with questions.

Everything you send is treated confidentially, including client site details, incident reports and applications still under preparation. We are editors rather than aviation consultants and cannot advise on regulatory compliance, but we can make your manual read as the document of an operator who has thought it through. Operators writing in English as an additional language are especially welcome.