Service 04
EASA and ATO documentation written to be used, not just approved.
Operations manuals, training manuals, ATO documentation and EASA regulatory submissions — structured so a crew member finds the answer quickly and an inspector finds the traceability immediately.
What this is
Two readers, one document.
An operations manual has two audiences with opposite needs. A crew member wants the answer in under a minute. An inspector wants to trace a requirement to the text that satisfies it. Documents written for only one of them fail the other — approved manuals nobody opens, or usable manuals that cannot demonstrate compliance.
The approach is to write for the operator and structure for the auditor. Plain language, short sections and a findable hierarchy for the first reader; a compliance matrix mapping every applicable requirement to where it is addressed, for the second. Neither audience is served by longer text.
This covers new approvals and existing documentation that has accumulated a decade of amendments. The second is more common, and usually needs restructuring rather than rewriting.
Scope
What the work covers.
Operations manuals
Parts A to D structured so the answer is findable, with change control that survives amendments.
Training manuals
Training and procedures manuals for ATOs and DTOs, aligned to the training actually delivered.
ATO and DTO documentation
The full documentation set for an approval application or a scope extension.
Compliance matrices
Requirement-by-requirement mapping to the text that satisfies it. The document that shortens an audit.
Approval submissions
Preparing submission packs and working through the authority’s questions.
Document architecture
Deciding what belongs in a manual, what belongs in a checklist, and what should not be written down twice.
Amendment and change control
Revision processes that keep traceability intact as documents evolve.
Documentation review
An honest read of an existing set against the requirements, with findings ranked by real risk.
Typical engagement
How the work runs.
Sized to the organisation. A four-week review and a six-month implementation follow the same shape.
Scope
Which documents, which requirements, and what the authority expects to see.
Structure
Architecture agreed before drafting. Restructuring after the fact is where documentation projects overrun.
Draft and review
Written in passes, reviewed by the people who will have to work to it.
Submission
Compliance matrix, submission pack, and support through the authority’s questions.
Questions
What clients ask first.
Straight answers, including where the answer is that we are not the right people for it.
Approval is the authority’s decision, and nobody can promise it. What is within our control is submitting something that is complete, traceable and answers the predictable questions before they are asked — which is what shortens the process. Beware anyone who guarantees an approval outcome.
Restructure first, almost always. Ten years of amendments usually means the content is broadly right but the architecture has collapsed — requirements addressed in three places, contradictions between sections, and no way to find anything. Rewriting discards accumulated operational knowledge for problems that were structural.
Both. Documentation is usually produced in English as the working language of aviation, but Dutch is available where the organisation or the authority prefers it.
Change control that is lighter than the drift. If amending a manual properly takes three weeks, people will stop doing it and the document will fall out of date. A workable revision process, a named owner per part, and a scheduled review cycle do more than any amount of policy.
Elsewhere on the site
Tell us what needs to happen.
Describe the operation, the standard you are working to, and the deadline. We reply within one working day.