Controls you can show an inspector.
An air operator is judged on its records. Trailflow is built so that every release, approval and correction has a name and a time against it, and so that the people who check work are not the people who did it.
Write-only audit trail
Every state change on a flight, release, record, approval or amendment is logged with who and when. Application code can add to the log, never edit or delete it.
Two-person checks
The person who files a flight record can't also give it the commercial check. Once checked, the record locks; corrections go through a separate, logged route.
Permissions matrix
Tick what each role can see and do, including custom roles. Permissions are enforced on the server, not just hidden in the screen, and nobody can approve their own request.
Senior approvals
Internal and director allocations, prepaid overrides and purchases above a set value need a senior approver.
Registered crew devices
A crew link on its own opens nothing. Devices are registered once with a one-time PIN, can be removed instantly, and lose access the moment the crew member is taken off a flight.
Permanent references
Every Flight Release has a serial number that never changes, so paper copies and the system always point to the same document. Cancelled work is marked void, never deleted.
Hosting, backups and residency, agreed with you.
Every operator's needs are different. Some authorities and contract clients have rules on where flight and crew data may be kept. We agree hosting, backup schedule and data residency with each operator during onboarding, and put it in writing.
- Where the data is hosted, and in which country
- Backup frequency, retention and how a restore is tested
- Who at your operator can export or delete data
- What happens to your data if you leave
- Encrypted connections (HTTPS) for every user and device
Questions from your quality or IT team?
We're happy to walk them through the controls and the audit trail in detail.