Building an Audit-Ready AD Evidence Chain for Your Next Authority Audit

When an authority audits your continuing-airworthiness organisation, the question is rarely "are you compliant?" in the abstract. It's "show me." Show me that you knew about this directive, that you determined whether it applied to this aircraft, that the work was done and signed off, and that you can produce the evidence — with dates, with names, with the reasoning. A green status on a dashboard is a claim. An evidence chain is proof.

This article covers what auditors actually look for in AD compliance, what a defensible evidence chain contains, and how to build one that stays current between audits rather than being reconstructed under pressure the week before.

What auditors actually want: the evidence, not just the final state

Audit expectations have shifted. It's no longer enough to present a spreadsheet asserting that every AD is closed. Auditors increasingly want to see the decision trail behind each state — because the final state is easy to type into a cell, and the trail is not. For each directive, they may ask:

• How and when did you become aware of it?
• How did you determine whether it applied to this aircraft, given its serial number, modification state, and engine variant?
• If you determined it did not apply, on what basis?
• If it applied, what action was taken, by whom, and when — and where is the record?
• Is the aircraft still compliant now, including any recurring requirement?

Notice that most of these questions are about process and evidence, not about the headline number. That's the shift: the burden is to demonstrate a documented determination, not merely to assert a result.

The chain: AD → applicability decision → work order → sign-off

A defensible AD evidence chain links four things, per aircraft, per directive:

1. The directive. The source AD itself, from the issuing authority, at the correct revision — with its cross-references to any equivalent directive from another authority.
2. The applicability decision. The determination of whether it applies to this specific aircraft, and the basis for that decision (type, serial range, mod state, engine variant, effectivity read). Crucially, this includes the "does not apply" decisions — a documented, reasoned not-applicable is evidence; a silent omission is a gap.
3. The action. Where the AD applies, the work order or corrective action that addresses it, linked directly to the source directive so the connection is explicit rather than inferred.
4. The sign-off. The confirmation and release by qualified personnel, with identity and date — the point at which engineering judgement is recorded, not assumed.

Each link should reference the next, so an auditor can start at any directive and walk the chain to the sign-off, or start at an aircraft and walk back to every directive that touched it.

Timestamps, provenance, and who decided what

Two attributes turn a record into evidence:

• Timestamps. When the directive was ingested, when applicability was determined, when the action was completed, when it was signed off. A chain without dates can't demonstrate that you acted in time.
• Provenance and identity. Which source the directive came from and at what revision; which person made the applicability call and the sign-off. Evidence answers "who decided this, on what, and when" — anonymous state does not.

The goal is that any single determination can be reconstructed months later exactly as it was made, without relying on someone's memory.

Independent verification: a second source

A growing expectation is that an operator's internal AD log isn't the only record — that there's a second, independent source confirming it. The value is simple: a self-maintained list is easy to drift, and an auditor knows it. Being able to reconcile your internal position against an independently computed applicability set — and to show they agree — is a much stronger posture than "trust our spreadsheet." Where they disagree, catching it before the auditor does is exactly the point.

Common findings — and how to avoid them

A few recurring audit findings, and their antidotes:

• Undocumented not-applicable decisions. An AD isn't on the aircraft's list, but there's nothing showing you decided it didn't apply. Antidote: record not-applicable determinations with their basis, as first-class results.
• A recurring AD marked closed. A recurring inspection was complied with once and then treated as done. Antidote: track recurring requirements as continuing, with the next due point computed, not closed.
• A superseded AD still open — or the superseding one missing. Antidote: maintain supersedure links so the active list reflects the current directive without losing the history.
• A missed cross-jurisdiction AD. Present on one authority's feed, absent from your single-source list. Antidote: reconcile both authorities into one deduplicated list.
• State without evidence. A "complied" status with no linked record. Antidote: every status references its evidence.

Build it once, keep it current

The reason evidence chains get reconstructed in a panic before an audit is that they were never maintained as chains — they were a status list, with the evidence scattered across emails, PDFs, and someone's folder. The durable approach is to capture the chain at the moment each determination is made: ingest the directive, record the applicability decision and its basis, link the action, capture the sign-off — so that "audit-ready" is the steady state, not a project.

How Aviagent helps

Aviagent builds this chain as a by-product of doing the work. It links every EASA, FAA, TCCA, and ANAC directive to your registered fleet, records the applicability determination with its reasoning and provenance, ties actions to the source directive, and timestamps each step — with engineers confirming and signing off every determination. Because it computes applicability independently from your internal log, it also gives you that second source: reconcile the two, resolve any disagreement on your terms, and walk into the audit able to say "show me" and mean it. The evidence is documented, traceable, and ready to defend — and engineering judgement stays where it belongs, with your team.

FAQ

What does "audit-ready" actually mean for AD compliance? That for every directive and aircraft you can produce the full chain — source directive, applicability decision and its basis, the corrective action, and the sign-off — with dates and identities, without reconstructing it from memory.

Do I need to document ADs that don't apply? Yes. A reasoned, recorded not-applicable determination is evidence. A directive that's simply absent from the list, with nothing explaining why, reads as a gap to an auditor.

Why do auditors want an independent second source? Because a self-maintained log is easy to drift. An independently computed applicability set that agrees with your internal record is far stronger evidence than the record alone — and where they disagree, you want to find it first.

How do I keep the chain current between audits? Capture each link at the moment the determination is made, rather than assembling evidence before an audit. That way audit-readiness is the steady state.

See which ADs apply to your fleet — free, in about 30 seconds. Try the free AD lookup, or book a 20-minute walkthrough.

Related reading: Which airworthiness directives apply to your aircraft (the pillar) · Superseded and recurring ADs · AD deadlines: hours, cycles and calendar limits.

About the author — Satya Neerupudi is Founder & CEO/CTO of Aviagent and an aeronautical engineer with 25 years in continuing airworthiness at SAS, GE Aviation, Pratt & Whitney, and HAL.