Evidence HubShared by every suite
One evidence register, and what each proof discharges.
In 50 words
Evidence management keeps the proof an operation holds, from an approved procedure to a training certificate, and shows what each piece proves. In eAviora every piece of evidence is reviewed and accepted by a person, carries its expiry date, is mapped to the requirements it backs, and can be bundled into a versioned package for an auditor.
- Overview
- Workflow
- Linked
- Discussion
- History
A piece of evidence, verified
01, done02, done03, current04, not reached
Linked toCMP | CAP | AUD | GOV
At a glance
The module, on one sheet.
Module sheet
SuiteShared by every suite | Shared Workspaces
RecordsEVD evidence and EVP evidence packages
Stages
01Draft02Submitted03Verified04Accepted
Attaches toRecords, actions, documents, audits, investigations, training completions, requirements and governance reviews
RecordsActionsDocumentsAuditsInvestigationsTraining completionsRequirementsGovernance reviews
CoverageEvery requirement, with the live proof behind it and the gaps with none
Organization96%Flight operations91%Operational control94%Maintenance88%Ground handling74%
What it does
Four things, done on the record.
Crosswind training records, Q3 2026
EvidenceEVD-2026-0298BacksREQ-2026-0118Expires2027-09-30Verified
EvidenceEVD-2026-0310EventSEMS-EVT-2026-0014Submitted
Gaps first
GRH 3.1Ground handling recordsNo live proof | last evidence expired 2 Nov
GRH 4.2Load controlNo evidence attached
MNT 1.6.2Parts traceabilityExpires in 12 days
01Reviewed and acceptedEvidence moves from submitted to verified to accepted; a reviewer can rate its adequacy and set its validity and expiry.
02Coverage by requirementFor every requirement, how much live proof backs it, and a list of the requirements that have none.
03Expiry watched every nightEvidence tied to a requirement that has expired, or will within 30 days, is caught by a nightly check.
04Packages for an auditorBundle evidence for an audit, a regulator submission or a compliance argument; regenerating makes a new version.
In the product
A piece of evidence, verified.
- Overview
- Workflow
- Linked
- Discussion
- History
On the recordIts status and type, and who verified and accepted it.
2 NovSubmittedA. Laurent
4 NovVerifiedM. Tremblay
NextAcceptedwaits for C. Wright
On the recordWhat it proves, and the requirement it backs.
BacksREQ-2026-0118
Every flight crew member completed the session in Q3.On the recordThe file, its adequacy rating and the date it expires.
Pages12Size1.4 MBAdequacyAdequateExpires2027-09-30
The rule it holds
Replaced, lapsed or refused evidence is never deleted.
- Superseded, expired and rejected evidence stays as the trail, and evidence held in a package cannot be deleted until it is removed.Evidence HubHolds
SupersededKept as the trail
ExpiredKept as the trail
RejectedKept as the trail
In a packageCannot be deleted until it is removed
On the graph
What it links to.
CMP | Linked recordComplianceEach proof, and the requirement it discharges.
- From
- CMP
- To
- Evidence Hub
- From
- CAP
- To
- Evidence Hub
- From
- AUD
- To
- Evidence Hub
- From
- GOV
- To
- Evidence Hub
Questions buyers ask
Short answers.
A reviewer verifies it, can rate its adequacy and set the date it expires, and it is then accepted. Rejected evidence goes back to its owner to rework.
Yes. Assemble an evidence package for the audit. Regenerating it makes a new version and keeps the earlier one.
eAvy can suggest an evidence type with its confidence. Nothing changes until a person accepts it.
Reading | FAA Part 5SMS Audit Evidence: What Auditors Actually Ask ForReading | FAA Part 5The Part 5 Declaration of Compliance: An Evidence ChecklistReading | FAA Part 5IOSA Compliance Software: How Airlines Can Link ISARPs, Evidence, Findings and Corrective Actions
All of FAA Part 5See Evidence Hub on your own records.
A walkthrough with the people who build eAviora.