Aviation document control
Control the distribution, not just the library.
Document control keeps the right revision approved and filed. It doesn’t prove that the people who work to that revision have read it. SkySign does that part, and is clear about the parts it leaves to your document control system.
See how SkySign distributes, tracks and proves operational briefings in 20 minutes.
Upload a PDF procedure
Choose a file to issue to staff
Straight answer
What SkySign does and doesn’t do for document control.
What SkySign does
- Issues the approved file to the departments, station groups or people who must read it.
- Fingerprints the file with SHA-256 when it is issued, and stores that fingerprint with every acknowledgement.
- Shows, for each document, who has and hasn’t acknowledged it.
- Lets you deactivate a superseded document so it stops asking for acknowledgement.
What it doesn’t do
- Keep revision history or compare revisions.
- Run review and approval workflows.
- Check documents in and out, or manage controlled copies.
- Replace your master document library.
Working together
Your library approves it. SkySign proves it was read.
- 1Step 1
Approve in your system
Review, approve and file the revision as you do today. - 2Step 2
Issue the approved PDF
Upload it with the revision in the title, such as “GOM 4.2 Pushback, Rev 14”, and choose read-and-comply wording. - 3Step 3
Collect acknowledgements
Staff in the chosen groups are emailed, and completion builds group by group. - 4Step 4
Retire the old revision
Deactivate the previous document. Its records stay available to administrators.
Proving the revision
How to show which revision someone acknowledged.
| Evidence | Where it comes from |
|---|---|
| Document title | Include the revision number when you issue, so it appears on every record and export. |
| SHA-256 fingerprint | Taken from the file at issue. Compute the fingerprint of your controlled PDF to show the two match. |
| Acknowledgement time | The server timestamp shows the revision was acknowledged while it was current. |
Worth knowing
- Revision numbers live in the document title; SkySign doesn’t track them separately.
- Editing an issued document doesn’t ask anyone to acknowledge again. Issue a changed procedure as a new document.
- Deactivated documents disappear from staff lists, including their history. Administrators keep the records.
Questions
Frequently asked questions
Does SkySign keep revision history?
No. Keep revisions in your document control system, and issue each approved revision in SkySign as a new document.
Can SkySign hold our controlled manuals?
It keeps every file you issue in private storage, but it isn’t designed as a controlled library: there are no folders, approval steps or check-out. Keep the master copy in your library.
How do we prove someone read the current revision?
Put the revision number in the title, keep the document’s fingerprint, and show that the acknowledgement time falls while that revision was in force.
What happens to acknowledgements when we deactivate the old revision?
They stay on record for administrators and in exports. Staff no longer see the document.
Keep your library. Add the proof.
We’ll show an approved revision issued from your process and acknowledged by the people who use it.
See how SkySign distributes, tracks and proves operational briefings in 20 minutes.