Problem
When a manual alert or library document is issued, operators can only prove that a user acknowledged it. The Acknowledgement report in the Alerts Register shows who acknowledged and when, but not whether the document was actually opened or how long the user spent reading it. Several operators have asked for this evidence for audits and regulatory compliance, especially for crew notices and manual amendments. At the moment, OSS can’t provide it.
Proposed solution
Extend the in-app PDF viewer to record a read audit trail each time a user opens a document linked to an alert or the Library:
User, document name, document revision and the linked alert
Date and time the document was opened and closed
Total time the document was open, ideally also the active viewing time
Pages viewed, or whether the user reached the last page
Device or platform (desktop or mobile/PWA)
Show this information:
As extra columns on the Alerts Acknowledgement report
In a per-document read history, available to users with the right access permissions
As an export (CSV/PDF) for audit evidence
Optional enhancements
A configurable minimum reading time or “must reach last page” rule before the Acknowledge button becomes available
A flag on acknowledgements where the document was never opened, or was open for less than a set time
Benefit
This gives operators verifiable evidence that safety-critical documents were read, not just acknowledged. That strengthens compliance during regulatory and internal audits, and reduces the need for separate read-and-sign processes outside OSS.