Aviation Compliance Monitoring Software: Buyer’s Guide
01What compliance monitoring means in aviation
In the EASA system, compliance monitoring is not a product category. It is a named function of the management system. For air operators, ORO.GEN.200 lists what the management system must include, and point (a)(6) is a function to monitor the operator's compliance with the relevant requirements. The same point adds that compliance monitoring shall include a feedback system of findings to the accountable manager, to ensure corrective actions are implemented effectively. Point (b) says the management system shall correspond to the size of the operator and the nature and complexity of its activities.
Maintenance and continuing airworthiness organizations carry the same function in their own rules: 145.A.200 for Part-145 organizations and CAMO.A.200 for continuing airworthiness management organizations, again at point (a)(6). The guidance that accompanies these rules treats independent audit and the feedback system as the two essential elements of the function: audits are carried out by people who are not responsible for the activity being audited, and what they find reaches the accountable manager.
The FAA does not use the term. The nearest equivalent sits in safety assurance under 14 CFR Part 5, where section 5.71 requires, among other things, auditing of operational processes and systems, evaluations of the SMS and of operational processes and systems, and investigations of reports regarding potential non-compliance with regulatory standards. FAA Advisory Circular 120-59B describes the internal evaluation programme many air carriers use for this work.
IOSA, the IATA Operational Safety Audit, adds an industry layer on top. Its requirement statements, the IOSA Standards and Recommended Practices, cover flight operations, dispatch, maintenance, cabin operations, ground operations, cargo, security and organization, and auditors test conformity against documented evidence. Our guide to IOSA compliance software covers that programme on its own.
Three regimes, one shape. Each asks an organization to know what it is held to, check itself against it on a plan, record what it finds, fix it, and prove the fix. That shape is what the software has to carry.
02The six jobs the software must do
Strip away the feature lists and compliance monitoring software has six jobs. Use them to score any product, including ours.
- A requirement register. Every requirement you are held to, from the regulation, the standard and your own manuals, each with an owner and a status. Requirements you do not operate under are declared not applicable, on the record, not deleted.
- An audit programme. A plan that covers the whole register over the planning period, with audits scoped to departments, stations and suppliers, and a checklist built from the requirements in scope.
- Findings. Each one raised against the requirement it breaches, with a level and the evidence the auditor saw. A finding that is free text in a report cannot be counted, trended or traced.
- Corrective actions. An owner, a deadline, a verification by a named person, and a check that the fix worked. This is the feedback loop the EASA rules ask for, and it is where most programmes leak.
- Evidence. The proof behind each requirement: the approved procedure, the training record, the calibration certificate. Each with a review, an expiry date and a link to what it proves.
- Regulatory change. When a rule or an edition changes, a list of what changed for you, an impact assessment, and actions that close the gap.
The jobs matter less one by one than joined. A finding should hold its requirement's status down until it closes. An expired certificate should show as a gap on the requirement it backed. A revised manual section should flag the requirements that pointed at it. When those links are missing, a person carries them in their head, and the auditor's sample trace finds the place where they forgot.
03One register, several departments
The search that brings most buyers here is some version of “compliance monitoring for an operator with several departments”. The problem is real. Flight operations keeps its audit findings in one spreadsheet, maintenance in another, ground operations in email, and the compliance monitoring manager rebuilds the picture by hand before every management review.
Centralized does not have to mean one team does all the work. It means three things are shared. First, the register: one list of requirements, with each owner named, so every department answers for its own lines and nobody answers for a line twice. Second, the action queue: a corrective action raised from a hangar audit, a station audit or a safety report sits in the same queue, with the same stages, and overdue means the same thing everywhere. Third, the evidence: a training record filed once backs every requirement it proves, in every audit that samples it.
The same logic extends past your own staff. Contracted maintenance, ground handling and training are still your compliance problem, so supplier audits and their findings belong on the same register as your internal ones.
Centralizing also exposes a habit worth breaking. In a spreadsheet, “closed” is a cell someone edits. In a system built for the job, closure is something the record has to earn, which is the subject of our piece on enforced closure gates.
04A buyer checklist for the demo
Slides hide the difference between products. A demo on your own questions does not. Take the table below into the call and ask the vendor to do each one live, not describe it.
| Area | Ask in the demo | What a good answer looks like |
|---|---|---|
| Requirement register | Show me one requirement. Who set its status, and when? | The status is derived from the owner’s declaration and from the findings still open against it. Nobody typed it. |
| Standards | Which rule sets ship, and how do I add mine? | A named list of what ships, and a plain way to register your own manual or another authority’s rules. No vague "all regulations supported". |
| Audit programme | Plan next year’s audits for three departments. | A programme planned against coverage, with internal, authority and supplier audits scoped to the same register. |
| On site | Run this checklist with the network switched off. | The checklist works with no signal and sends the assessments when the device is back online. |
| Findings | Raise a finding. Now try to close the audit. | The finding names the requirement, its level and its evidence, and the audit refuses to close over a finding your policy treats as blocking. |
| Corrective actions | Close this action without verifying it. | It refuses. The record names who owned, verified and approved the action, and whether the fix was reviewed for effectiveness. |
| Evidence | Which requirements have no live proof today? | One view of coverage by requirement, with expired and soon-to-expire evidence listed, and a versioned package for the auditor. |
| Regulatory change | A new edition lands. What changed for us? | One change set: changed, added and withdrawn requirements, each assessed and closed on evidence. |
| Workflow fit | What can I configure, and what is fixed? | A straight answer on both. Policies you can set (blocking levels, review gates) and stages you cannot remove. |
| Audit trail | Pick a closed finding from last year and trace it. | Requirement, finding, action, verifier, evidence and dates, followed in one place without opening a second tool. |
Two of those rows deserve a second look. “Customizable workflows” is on every vendor's page, and it can mean anything from renaming a field to deleting the verification step. You want the first kind and not the second: enough configuration to match your manual, and no switch that lets a finding close with nothing behind it. Ask which is which.
“Mobile” needs the same care. An auditor on a ramp or in a hangar often has no signal, so a checklist that only works in a browser tab with a connection is a desktop tool with a small screen. Ask to see it offline, on the phone or tablet your auditors actually carry, before you take anyone's word for it.
05Where eAviora fits, and where it does not
eAviora covers the six jobs as modules on one connected operation, next to the safety management modules, so a finding, a hazard and an occurrence can raise actions into the same queue. On the compliance register, a requirement's status is derived from what its owner declared and from the findings and corrective actions still open against it. Audits and findings cover internal, regulatory and supplier audits, with checklists that run in the eAviora app with or without signal.
The limits are worth stating as plainly. The catalogues that ship are the IOSA Standards Manual, editions 18 and 19 with the crosswalk between them, Transport Canada's Canadian Aviation Regulations and Standards, EASA Air Operations, EASA Part-145 and Part-CAMO, FAA 14 CFR Parts 5, 119 and 121, and UK CAA Air Operations, each as the regulator's own text. A rule that is not on that list, or your own manual, is registered as a standard of your own. eAviora does not watch the regulators for you either. You bring a new edition in, and the product compares it with the requirements you hold.
On workflows, what you configure is policy: which finding levels block an audit from closing, and whether a verified action needs an effectiveness review before it closes (on by default). It is not a free-form workflow designer, and if your procedure needs stages we do not have, raise it in a demo before you buy. On mobile, the audit checklist and the document library are in the eAviora app on the phone; test it on the tablet you plan to use.
One last caution, and it applies to every product on your list. A clean compliance matrix tells you the organization does what the rules say. It does not tell you the operation is safe, which is the argument of why compliance alone cannot prevent incidents. Buy the tool that makes compliance cheap to prove, so the people running it have time left for the risks no rule names.
Questions
Compliance monitoring is the function inside an aviation organization that checks, independently and on a plan, whether the organization still meets the requirements it is held to, and that reports what it finds to the accountable manager so corrective action is taken. Under the EASA rules it is point (a)(6) of the management system requirement for air operators (ORO.GEN.200), maintenance organizations (145.A.200) and continuing airworthiness management organizations (CAMO.A.200). In practice it is a requirement register, an audit programme, findings, corrective actions and the evidence behind each of them.
Six jobs. Hold a register of every requirement with an owner. Plan and run the audit programme. Record each finding against the requirement it breaches, with its level and its evidence. Drive each finding to a corrective action that is verified before it closes. Keep the evidence, with its expiry, mapped to the requirements it proves. And handle a change in the rules as a change set, not a re-typed spreadsheet. A tool that does four of the six leaves the other two in email.
No, and the EASA rules list them as separate points of one management system. Safety risk management looks for hazards and asks whether the risk is acceptable. Compliance monitoring asks whether the organization does what the rules and its own manuals say. They share findings, corrective actions and the accountable manager, which is why running them in two unconnected tools costs so much: the same weakness gets recorded twice and fixed once, or not at all.
Not under that name. The nearest FAA equivalent sits in safety assurance under 14 CFR Part 5: section 5.71 requires auditing of operational processes and systems, evaluations of the SMS and of operational processes and systems, and investigations of reports regarding potential non-compliance with regulatory standards. Software that serves an EASA compliance monitoring function serves that work too, because the records are the same: an audit, a finding, a corrective action and its evidence.
It should, because the compliance monitoring function audits all of them. Ask to see three things in a demo: an owner named on each requirement, so flight operations, maintenance and ground operations each answer for their own; an audit scoped to one department that still reads the shared register; and one corrective action queue across every source, so an action raised by a maintenance audit and one raised by a safety report are tracked the same way.