Updated on
Distributing a manual means giving the people concerned the current version and making sure they have taken note of the changes. For operators, ORO.MLR.100 requires the operations manual to be kept up to date and all personnel to be made aware of the changes relevant to their duties. For ATOs, ORA.ATO.130 requires a training manual and an operations manual to be established and maintained, with their content made available to staff. Neither text prescribes the form: a named, dated read-and-sign record is one way to keep evidence of it.
The right revision, sent to the right people, and read.
Scheduled, targeted publication
Set the publication date and the recipients by role, group or base. Each person sees the documents they need to read.
Changes made visible
Comparing two revisions highlights what has changed. Readers keep their bookmarks and notes and resume where they left off.
A time-stamped acknowledgement
Acknowledgement unlocks once the document has been read through. The record captures date, time, IP address and device, and joins a signed append-only log.
Follow-up until acknowledgement
Track reading by document and by person, schedule reminders for overdue readers and export acknowledgements as XLSX or PDF.
From approved revision to the last acknowledgement.
Approve the revision
The Author → Reviewer → Approver workflow validates the new version, with each step signed.
Schedule distribution
Choose the publication date and the target groups.
Read and acknowledge
Each recipient reads the revision on the web or on mobile, then acknowledges it.
Follow up and export
Spot overdue readers, send reminders, then export the acknowledgements for audit.
These EASA references are provided to make verification easier. This page does not replace applicable rules or guidance from your competent authority.
