Skip to content
FRSign inBook a walkthrough
DMSDocumentsDocuments & Training

Aviation document control, from draft to signed acknowledgment.

In 50 words

Document control keeps manuals and procedures current, approved and in the hands of the people who must follow them. In eAviora a released revision cannot be edited, only superseded by the next one, each approval is signed in order, and every reader’s acknowledgment is tracked against its due date.

Case file | DOC-2026-0042Revision 6, in review
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
A document, in review
01Draft, done02In review, current03Approved, not reached04Published, not reached
Next step, waiting onThe reviewers
Linked toCMP | AUD | REG | Evidence Hub
Sample data | Northwind Air, a fictional airline
At a glance

The module, on one sheet.

Module sheet | DMS
SuiteDocuments & Training | Documents & Training
ICAO Annex 19Component 1, safety policy and objectives, which includes SMS documentation
RecordsDOC documents, and the sections inside them
Stages
01Draft02In review03Approved04Published
On the phoneThe library in the eAviora app, with what is still to acknowledge
  • The library, in the eAviora app, done
  • What is still to acknowledge, not yet
What it does

Four things, done on the record.

The revision readers have now
Revision5Released2026-11-01Effective2026-12-01Revision 4superseded, never edited
Section 4.2 changed | Sample data | Northwind Air, a fictional airline
01Revisions, supersededSections change only in a draft revision; a released revision is replaced by the next, never edited.
02A signed approval routeReviewers, then approvers, each signing their step before the next one can.
03Distribution and read-and-signEveryone, a role, a department or a named list, each with a due date; a signed acknowledgment carries a signature hash.
04Review dates watchedThe owner is reminded 90 days before a periodic review falls due, and told when a review stalls.
In the product

A document, in review.

Case file | DOC-2026-0042Revision 6, in review
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
The next stepThe next step and what it waits on.
  • S. Okafor, reviewer, signed 10 Nov, done
  • A. Laurent, reviewer, to sign, not yet
  • C. Wright, approver, after both reviewers, not yet
On the recordThe revision in flight, and the published version readers have now.
Revision 6Draft, in review2 sections changed | in flight
Revision 5Published 2026-11-01what readers have now
Revision 4Superseded 2026-11-01never edited
On the recordWho must acknowledge it, and who has.
Flight operations, 171 readers | due 1 Dec
Sample data | Northwind Air, a fictional airline
The rule it holds

A document is never published to nobody.

  • Publishing is refused until the document has a distribution, so every release reaches the people who must read it.DocumentsHolds
ApprovedSigned along the route
DistributionFlight operations, 171 readersset before release
PublishedTo the people who must read it
Questions buyers ask

Short answers.

No. You start a new revision, edit it as a draft and send it through review and approval. The published one stays as it was until the new one supersedes it.

Reading | SMS fundamentalsWeb Manuals Alternatives: Document Control on One Connected OperationReading | SMS fundamentalsHow to Structure an SMS Manual (and What Regulators Actually Check)Reading | SMS fundamentalsSMS Audit Evidence: What Auditors Actually Ask For
All of SMS fundamentals

See Documents on your own records.

A walkthrough with the people who build eAviora.