Rule, AMC or guidance? Label your EASA review notes clearly
Keep regulations, acceptable means of compliance, guidance and company procedures distinguishable in a source-to-document review.
About this article: This information illustrates the potential benefits of Aviation.Bot’s upcoming regulatory library and desktop/web document-review features. It is not compliance guidance, legal advice or a basis for a regulatory, certification or operational decision. Examples demonstrate the workflow; verify applicable official sources and use qualified professional judgement for actual work.
An aviation document review often brings several kinds of text into one workspace: a regulation, an AMC paragraph, explanatory guidance, an authority publication and an internal procedure. If they all appear as “requirements” in the final table, the reviewer loses an important part of the source trail.
The practical fix is small. Preserve the source type beside every observation, and make the reviewer’s inference a separate field. That helps readers see which text was found and which conclusion still needs judgement.
Workflow at a glance
Original workflow illustration. Candidate findings remain subject to qualified human review; the diagram does not establish an approval or compliance decision.
Why the labels matter
EASA describes AMC as non-binding standards illustrating means of establishing compliance. Its explanation also discusses the presumption of compliance associated with its AMC and the role of alternative means. “Non-binding” should not be shortened to “can be ignored”; consult the applicable process and authority context for a real case. EASA’s explanation of AMC and AltMoC
This article is about making notes readable. It does not decide whether an alternative means is acceptable, interpret an approval condition or tell an organisation how to demonstrate compliance.
Separate evidence from inference
Consider two ways to write a review row. The weak version says: “EASA requires our company to rewrite this procedure.” It does not identify the kind of source, the exact text or the reasoning connecting it to the procedure.
A stronger version says: “Selected AMC paragraph describes an approach relevant to this procedure. The reviewer should inspect whether the organisation’s recorded means and evidence address the point.” The exact source link and internal paragraph sit alongside that note. The wording makes the next decision visible without inventing an obligation.
A fictional source-label example
The following entries demonstrate a note format. They do not reproduce particular regulatory clauses:
| Material | Source label | Note to preserve |
|---|---|---|
| Identified regulation passage | Regulation | Exact provision, version and applicability question |
| Associated AMC passage | AMC | Approach described and relevance for reviewer confirmation |
| Explanatory material | Guidance | Explanation considered; do not silently rewrite as a new obligation |
| Authority publication | Authority guidance | Issuer, scope and edition; check whether it addresses this approval |
| Company procedure | Internal controlled document | Revision, section and organisation-specific commitment |
| AI summary | Generated interpretation | Unverified until checked against the cited originals |
Add a final column for the reviewer’s decision. A source label is useful evidence about a passage; it is not a completed applicability assessment.
Keep internal commitments visible
A company procedure may make a commitment more specific than a public source summary. If the reviewer finds a difference, record both passages rather than letting the AI blend them into a compromise sentence.
For example, an internal procedure might name a responsible role and a particular form. A generated summary may remove those details because they are absent from the public source. The loss can make the procedure less useful even when the summary sounds polished. Inspect the actual controlled text and the reason for its details before proposing any change.
Ask for a source map before a rewrite
Whether working manually or with an AI assistant, begin with a map of the material. Identify passages by source type and record their location. Then ask what connection, if any, exists between the official material and the selected internal document.
A useful prompt for a future document workspace would be:
List the passages relevant to this review question. Keep regulation, AMC, guidance and company procedure text separate. Cite each source and version. Put your interpretation in a distinct column and flag anything you cannot establish from the supplied files.
This is a suggested working prompt, not evidence that a tool retrieves every relevant passage. Review the original pages, surrounding text and any referenced material before accepting the map.
Handle uncertainty explicitly
If a source type or version is unclear, write “needs confirmation” rather than guessing. If the note relies on a source excerpt, say that the surrounding context has not yet been inspected. If the organisation’s chosen approach is not documented in the available files, request the relevant record instead of assuming a default.
These small labels help a second reviewer distinguish a missing document from a contradictory statement and an open question from a proposed action. They also make it easier to update the review when a source changes.
Where Aviation.Bot fits
Aviation.Bot’s upcoming regulatory library and desktop/web features are designed to support source classification like this. The starting libraries cover EASA, FAA, UK CAA, CAAC and Dutch IL&T across multiple document categories. The workflow lets a reviewer keep rule text, guidance and internal commitments separate, and return a source map with a distinct interpretation column. Desktop users work with selected local folders and files; browser users upload selected documents to their workspace. Available sources and editions remain visible parts of the review rather than an assumed complete collection. AMC/GM labels here remain tied to the EASA source context.
The practical difference from a typical ChatGPT upload session is the aviation-specific source collection and repeatable document-review workflow: selected regulatory material sits alongside the organisation’s manuals, procedures and evidence, with references the reviewer can reopen. ChatGPT also supports file analysis; Aviation.Bot’s differentiation is how the source set and review task are organised, rather than a claim that general assistants cannot read documents.
Complex tables and forms deserve the same inspection as prose. The workflow is being developed to retain table relationships, headings, footnotes and form context, and to let the reviewer check the original page when extraction is uncertain. Reliable review depends on seeing that structure—not merely receiving a confident summary. Better accuracy, complete table fidelity and time savings require task-specific validation; they are not established by having a curated database.
Read the AMC and CS reference hub for related source-navigation work and the MOE review article for the broader document context. Sign up on Aviation.Bot to stay up to date about upcoming releases.
Prepared with AI assistance and editorial checks against linked official sources. Illustrative examples do not represent authority or independent expert approval.