Skip to content
FRSign inBook a walkthrough
How-toWith a checklist

Replacing Spreadsheets and Email With an SMS: What Actually Changes

Most safety systems are not broken. They are held together by people who remember where things are, which works until an auditor asks a question that spans two files. This is what moving off spreadsheets and shared mailboxes actually changes, what differs by certificate, and what a realistic first month looks like.
Mounir OuafiFounder and CEO of eAvioraPublished 11 min read

Your first-month checklist

Tick each step as you finish it. Your ticks stay on this device and are never sent to us.

Steps done0 of 9

Next: Book a walkthrough on your own data, not a demo tenant

Week 0 | Walkthrough0 of 3

In eAviora. Export every record and the audit log as JSON or CSV, and occurrences as E5X for ECCAIRS.

Week 1 | One module family0 of 3

In eAviora. The risk library ships ready: 85 bow-tie models, 682 named barriers, 183 scenarios and 516 indicator definitions.

Weeks 2 to 4 | Migrate0 of 3

In eAviora. Bring existing registers in by CSV import: map your columns, check the result, and roll the import back if it is wrong.

01The seven swaps

Every row below is something an operation is doing today. The right column is not a feature list; it is the same job with the relationship kept by the system rather than by a person.

What an SMS platform replaces, and what each becomes
Running by hand todayOn a connected system
Occurrence reports in a shared mailboxStructured intake, classified and linked when it arrives
A hazard register in a spreadsheetBow-tie models with named barriers whose condition is assessed
Indicators recalculated by hand each monthControl charts where a statistical rule trips on its own
Findings tracked in a second systemOne record type on the same graph as everything else
Actions closed on a checkboxClosure gated on verified effectiveness by a second person
A board pack assembled the week beforeAn agenda derived from what the safety data escalated
An audit folder assembled from scratchEvidence attached to the requirement when it is produced

The row that pays for the project is usually the fifth. An action closed unverified is the most common reason a barrier is still degraded when the next occurrence arrives, and it is invisible in a spreadsheet because the closure and the outcome live in different files. See the closure gate.

02What differs by certificate

The ICAO Annex 19 four components are common to all of them. What changes is which records dominate and which rule set the evidence is assembled against.

  • Air operators (EASA Part-ORO, FAA Part 121 and Part 135). Occurrences, indicators and governance dominate. IOSA preparation reads the same records if they are connected. See Part 135 requirements and the 2027 deadline.
  • Maintenance organizations (EASA Part-145). Findings, corrective actions and competency validity for certifying staff dominate, with document control proving the current revision reached the floor. See SMS software for MRO and Part-145.
  • Training organizations (EASA Part-ORA). Competency records with validity windows and the requirement matrix an inspector reads. See SMS software for flight schools.
  • Ground handling. Per-station registers and intake that works on a stand, because the person who sees the event is outside and holding a radio.

For the United States timeline specifically, the FAA SMS final rule extended a mandatory SMS well beyond Part 121; see the Part 5 final rule explained.

03A realistic first month

Week 0. A walkthrough on your own data rather than a demo tenant. Bring three recent occurrences. Anything that cannot be shown on your records in forty five minutes is unlikely to behave differently on a hundred thousand of them.

Week 1. One module family live, with your taxonomy and your people. Scope the risk library to your operation rather than accepting the whole catalogue, since a register nobody recognises is a register nobody maintains.

Weeks 2 to 4. Migration of historic records with references preserved, and one existing programme moved end to end. Expect the taxonomy conversation to take longer than the import.

What consistently derails a first month is trying to move everything at once. The counter-pattern is to pick the module family where your next audit will look and finish it. For a phased plan against the framework, see Annex 19 in 90 days.

04What happens to your history

Ask this before signing, not during implementation. Historic records should import with their original references intact, so a finding raised two years ago can still be followed. An audit trail that appears to begin on go-live day invites the obvious question about what else did not survive the move.

The matching question is how you get out. Full export on demand in open formats, covering records and their links rather than a flat table, is the difference between a system you chose and one you are stuck with. Safety data is operational memory, and an operator that cannot take it with them has handed over more than a subscription.

Questions

You can run the record keeping on spreadsheets, and many small operations do it lawfully for years. What spreadsheets cannot hold is the relationships: which occurrence belongs to which hazard, which barrier a finding degraded, whether the action that closed last quarter actually worked. Those links are what an audit samples and what turns reports into prevention. The practical limit is usually reached when the person who remembers the links goes on leave, or when an auditor asks a question that requires joining two files.

Mounir OuafiFounder and CEO of eAviora, the aviation safety intelligence platform.

Related reading

Bring three recent occurrences and see them on one graph.

Book a walkthrough on your own operation, or keep reading in all the insights.