Aviation document control, from draft to signed acknowledgment.
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.
- Overview
- Workflow
- Linked
- Discussion
- History
The module, on one sheet.
- The library, in the eAviora app, done
- What is still to acknowledge, not yet
Four things, done on the record.
An approach is stabilised when the aircraft is on the correct flight path by 1,000 ft above the aerodrome, with only small changes in heading and pitch needed to hold it.
If the approach is not stabilised at that height, the crew goes around.
A document, in review.
- Overview
- Workflow
- Linked
- Discussion
- History
- S. Okafor, reviewer, signed 10 Nov, done
- A. Laurent, reviewer, to sign, not yet
- C. Wright, approver, after both reviewers, not yet
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
What it links to.
- From
- CMP
- To
- DMS
- From
- AUD
- To
- DMS
- From
- REG
- To
- DMS
- From
- Evidence Hub
- To
- DMS
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.
Readers sign their acknowledgment with the name on their profile. Each one is tracked against its due date, and a signed acknowledgment carries a signature hash.
Yes. A published revision exports as a controlled PDF with its status, effective date, approver and distribution.
See Documents on your own records.
A walkthrough with the people who build eAviora.