Run these tests on every platform.Including us.
Ten tests an honest evaluator should run on any aviation safety platform — what to ask, and what a real pass looks like. For each one, eAviora shows its own shipped answer. Written for Safety, Quality and Compliance leaders, and the accountable manager and IT reviewer who sign with them.
One picture, or separate silos
THE TEST
Ask the vendor to take one occurrence and follow it through to a quality finding, the corrective action that fixed it, and the training record that closed the loop. A real pass shows it on one screen, on one record. If the demo copies and pastes between modules, you have a four-tool stack dressed up as one tool.
WHAT eAviora SHIPS
- One record table. Occurrences, hazards, findings, corrective actions, barriers and bulletins are the same records, joined by links between records — not separate databases.
- A finding raised against a requirement degrades that requirement straight away, and threads to its corrective action — no manual cross-referencing.
- A corrective action’s effectiveness feeds barrier health, which feeds the risk profile, automatically. It computes; it does not just store.
Closing a finding for real
THE TEST
A corrective action is not closed when the work is done. It is closed when a named verifier confirms, with evidence, that it actually reduced the risk. EASA Part-ORO and FAA Part 5 both make this effectiveness check mandatory. In the demo tenant, try to close one without it. A real pass blocks you. If the system lets you through “just for the demo,” it does not enforce the rule it claims to support.
WHAT eAviora SHIPS
- A degraded barrier requires a linked corrective action. The record cannot close until that action passes a scheduled effectiveness check.
- An action judged ineffective reopens governance — it escalates to the Safety Action Group instead of dying in a closed ticket.
- When leadership accepts residual risk, the waiver is two-person co-signed and audit-logged. The gate is proven by a 13-of-13 live scenario suite.
A risk model in the box
THE TEST
ICAO-aligned should mean the platform ships the real taxonomies — occurrence categories, a configurable risk matrix, named barriers, a starter set of safety indicators — not a badge with no traceability into the data model. Ask which standards it cites, in which edition, and how it handles amendments. A real pass hands you a working model; a weak one hands you an empty canvas to fill yourself.
WHAT eAviora SHIPS
eAviora ships a pre-built, version-pinned aviation risk knowledge base on day one. Every occurrence maps to a bow-tie family with named preventive and recovery barriers, so “what failed and what should have stopped it” is answered structurally, not in free text.
Where the isolation lives
THE TEST
Your safety reporting is your most sensitive operational data. Three questions, three yes-or-no answers: are your records isolated from every other operator, enforced at the database itself? Is your data ever used to train an AI model, for you or anyone? Can you export everything in 24 hours, on request, with no friction? “We have controls in place” is not the same as “enforced at the database.” A real pass names the mechanism.
WHAT eAviora SHIPS
- Isolation is enforced at the database with row-level security forced on, against an app role that cannot bypass it — a missing org context fails the query, not exposes a neighbour.
- Five layers, not one: procedure checks, per-query org filters, request-bound context, deny-by-default policies, and the database itself refusing a cross-tenant read underneath.
- Data residency is named — Canadian region, encrypted at rest — with a published trust page and a named sub-processor register, not a marketing line.
AI that proposes, never decides
THE TEST
Two things to check. First, consistency: re-run the AI classification on the same occurrence and see whether the output holds — a regulator can reopen that decision years later. Second, and harder: can the AI, or an integration, move a record’s workflow or governance state on its own? A real pass keeps a human between the AI and the record of truth, and can show you the trail of every accept, edit and reject.
WHAT eAviora SHIPS
- The AI proposes; a person decides. Every change the copilot wants surfaces as a one-click approval card — accept, edit or reject — and that decision is logged for audit.
- Workflow and governance state are non-settable by the AI or the API. Low-confidence or out-of-catalogue output is queued for a human, never written silently.
- ICAO Annex 19 confidentiality holds through the AI — a confidential report stays invisible to an analyst without clearance, even via the copilot.
The board-level answer
THE TEST
A safety platform should do more than count reports. The question an accountable manager and a board actually ask is whether risk is trending up or down — and they need the reasoning, not a coloured bar. Ask the vendor to produce a single risk read per theme that fuses base risk, trend, barrier health and open corrective actions, and to show the components behind it. A real pass shows the maths; a weak one shows a gauge with no source.
WHAT eAviora SHIPS
- A computed Safety Risk Profile fuses base risk, trend, barrier health, open-action exposure, active signals and surveillance coverage into one ICAO four-level score per theme.
- Indicators run real statistical process control — Western Electric breach and shift detection per ICAO Doc 9859 — rendered as a flight-deck weather chart, not a coloured trend line.
- Every score drills into its contributing indicators, linked barriers and open actions, so the board sees why the number moved.
Getting your data out and in
THE TEST
For a commitment of three years or more, ask how the data flows both ways. Is there a documented API, or only an export-to-spreadsheet ritual? Can you connect your own systems and, increasingly, an AI assistant? And get the exit clause in writing before you sign — format, timeline, cost. A real pass is a published, modern surface; a weak one is “we’ll work it out.”
WHAT eAviora SHIPS
- A public REST API, version 1, with an OpenAPI 3.1 contract generated from the runtime so it cannot drift — generate a typed client in any language.
- An MCP server and an OAuth 2.1 connector let an AI assistant query your live safety operation in plain language — tenant-isolated and audited, with governance state still locked.
- Full-tenant exports run async to JSON, CSV or Parquet with a signed download link. Your exit answer is a real endpoint, not a promise.
Onboarding you can measure
THE TEST
A twelve-month implementation is a twelve-month chance to lose the budget and the sponsor. Ask for a written plan with weekly milestones and named deliverables. If it starts at “kickoff workshop” and ends at “go live” with three boxes between, push back — that is usually their data-model design happening on your time. A real pass shows go-live gated by a named sign-off, not a calendar.
WHAT eAviora SHIPS
- Onboarding is a self-driving checklist — each step completes the moment the underlying data exists, so progress is real state, not a tick someone forgot.
- Go-live requires a two-person, e-signed sign-off — Safety Manager and Accountable Manager both confirm — producing an immutable, regulator-grade paper trail before the org activates.
- Trial governance is enforced, not hoped for: scheduled reminders, then a clean read-only suspension if the sign-off is not made.
Buy only what you need
THE TEST
Scrutinise three patterns. Per-occurrence pricing puts a price tag on every report a crew member files — the opposite of Just Culture. Record types sold as separate licences mean you pay twice for one operational picture. Long pre-paid implementation fees cover the vendor’s risk, not yours. A real pass is a clear unit, unlimited reports, and access enforced consistently — no half-gated module a user can hack into by URL.
WHAT eAviora SHIPS
- Reporting is never metered — the lifeblood of a safety system is open, unpriced reporting, so there is no price tag on a crew member’s report.
- Buy only the modules you need. Access is enforced at the menu, the page and the API at once — so there is no module a user can reach by guessing a URL.
- Billing is seat-based and clear. There is no mandatory six-month implementation toll standing between you and value.
The shortlist test
THE TEST
Run each shortlisted vendor through these four, side by side:
- The same real occurrence. File it, classify it, link it to a finding, open a corrective action, prove effectiveness, close. End to end. Count how many tools you touched.
- The same regulator. Load your authority’s mandatory reporting rules. See whose system encodes them as structured rules, not just documents.
- The same Friday edge case. A pilot files at 16:55 on Friday; the safety manager is away. Does the clock start, does it escalate, does the accountable manager get pulled in?
- The same export. Request your tenant data back within 24 hours. See who delivers cleanly and who stalls.
WHAT eAviora SHIPS
- One occurrence threads through classification, barriers, the risk profile, governance review and a de-identified bulletin — in one connected operation, one audit trail, no integration project.
- Mandatory reporting and regulator deadlines are structured rules with reminders and escalation, not a folder of PDFs.
- Run the four scenarios on your own data shape with us in 30 minutes, and judge eAviora against the same tests it just set.