From NPA or NPRM to a review worklist: track proposals without treating them as final rules
Separate proposed aviation changes from adopted material and build a traceable preparation worklist for engineering, operations and compliance teams.
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 regulatory proposal can matter before it becomes an adopted change. A manufacturer may need to understand the questions raised about a future certification approach. An operator may want to assess which manuals could be affected. A training team may want to prepare questions rather than discover the topic late.
The mistake is to move a proposal directly into a table labelled “current requirements.” The useful task is preparation: identify what is being consulted on, connect it to the organisation’s work and preserve the uncertainty until an authoritative outcome is available.
This article proposes a document-review method. It is not a determination that a proposal applies, will be adopted or requires a controlled change.
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.
Preserve the publication’s status
EASA describes its Notices of Proposed Amendment as draft regulatory material used to collect stakeholder views before Opinions and Decisions. It distinguishes public and focused consultations. That explains why the document’s consultation status belongs in the source record, rather than disappearing in an AI summary. EASA’s NPA collection
FAA’s rulemaking resources distinguish proposed and final material. When reviewing a US source, preserve the named document and its actual procedural stage; do not rename it an NPA to fit an EASA-oriented template. FAA rulemaking, recently published rulemaking documents
Use the same discipline for UK CAA consultations, CAAC material and national authority publications: establish the document type and status from the issuer. Similar subject matter is not proof that two proposals have equivalent effects or that one has been adopted elsewhere.
Start with a preparation question
“What must we change?” is often premature. Begin with “What does this proposal ask stakeholders to consider, and which parts of our work might need examination if the relevant approach is adopted?”
The second question gives engineers and manual owners useful work without pretending that the outcome is settled. It can produce a source map, questions for specialists and a list of information needed for a consultation response. It should not trigger an automatic rewrite or set a legal deadline that the source does not establish.
A fictional consultation worklist
The following example is entirely synthetic. It is not a summary of a particular NPA or NPRM:
| Field | Example working entry |
|---|---|
| Source | Identified proposal, issuer and official link |
| Status | Consultation material; adoption not established |
| Passage | Exact section inspected by reviewer |
| Internal connection | Fictional design-verification plan DV-04 |
| Preparation question | Would the described approach change the evidence we collect? |
| Information needed | Existing evidence method and rationale from engineering owner |
| Next action | Draft an internal question note; no approved plan change |
| Follow-up trigger | Official response, revised proposal or adopted material |
Add any consultation deadline only after checking the live issuer page and the document’s instructions. A historical search snippet should not decide whether comments are still open. Preserve the date checked with the status.
Connect disciplines without flattening their decisions
One passage might interest engineering, operations, safety and training for different reasons. Give each connection its own row and owner. The engineering question may concern test evidence; the operations question may concern a future procedure; the training question may concern what people would need to understand if a procedure changes.
Do not copy a single proposed action into all three rows. Ask each owner to explain the connection and the evidence supporting it. A missing document is an information request, not a regulatory finding. An apparently irrelevant proposal can be closed with a bounded rationale rather than ignored without explanation.
Follow the outcome, not just the document
A consultation record is useful only if it remains connected to what happens next. Preserve the original proposal and review questions, then record the official outcome when available. If wording changes, identify which observations depended on the old passage.
This avoids two common mistakes: leaving an old preparation note as if it describes adopted material, and deleting it so thoroughly that nobody can explain why a team investigated the topic. The historical note can remain valuable when its status and limitations are clear.
Where AI assistance could reduce repeated work
A useful assistant task is to find the selected proposal passages, locate references in chosen internal documents and draft a question register with precise citations. The reviewer should inspect those matches and confirm the publication status. Proposal analysis is not a licence for AI to invent the final text.
Aviation.Bot’s upcoming regulatory library and desktop/web features are designed to support regulatory change preparation like this. The starting libraries cover EASA, FAA, UK CAA, CAAC and Dutch IL&T across multiple document categories. The workflow lets a reviewer search proposals and adopted material beside manuals, engineering plans and evidence, then draft impact questions with the publication status preserved. 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.
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.
The potential saving is fewer repeated searches and less reconstruction of why a team examined a source. That benefit is a hypothesis to measure on an actual task, not a claimed percentage or proof of better regulatory judgement.
For the underlying method, read regulatory change-impact review. 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.