Compliance matrix evidence review for equipment suppliers

When this review is needed

• A compliance matrix is about to anchor a submittal and its coverage of the certification basis has not been independently checked.
• The certification basis changed and the matrix may not yet reflect every requirement it now has to address.
• A finding questions the means of compliance stated for a specific requirement.
• Evidence cited in the matrix was revised and the entries pointing to it have not been rechecked.

The problem

A compliance matrix is the one document that claims completeness, and that claim is the easiest to overstate. Every cell asserts that a requirement is met, by some means, with some evidence, but the matrix is filled in over months while the basis, the design, and the evidence all move. A requirement gets added to the basis and no row appears for it; evidence gets revised and the cell still cites the old revision. The matrix reads finished long before it actually reconciles.

What gets reviewed

• Every applicable requirement of the certification basis confirmed present as a matrix row
• The stated means of compliance checked as defensible for each requirement
• Cited evidence opened and confirmed to support the claim at its current revision
• Entries marked complete separated from those still open or partially supported
• Requirements added by a basis change confirmed to have rows and evidence
• Cross-references to underlying data checked so the matrix points where the evidence actually lives

What gets validated

• Each applicable requirement of the certification basis has a corresponding matrix entry
• The means of compliance stated for each requirement is defensible for that requirement
• Evidence cited by each entry supports the claim at the revision now released
• Entries marked complete resolve to opened evidence rather than a planned or in-work status
• Requirements introduced by a basis change appear in the matrix with supporting evidence

Evidence normally required

• The compliance matrix or compliance checklist as maintained
• The certification basis with any amendments the program is working to
• The evidence each matrix entry cites, at its current revision
• Change records for the basis and for cited evidence since the matrix was last reconciled
• The certification plan that established the means of compliance the matrix uses

Common discrepancies

• A requirement added by a basis amendment with no matrix row to address it
• A matrix entry citing an evidence revision that a later release superseded
• A means of compliance stated for a requirement that the requirement does not actually admit
• Entries marked complete that resolve to planned or in-work evidence rather than released records

What is at stake

An authority uses the matrix to plan its review, so a gap in the matrix becomes a gap in the plan, and a cell that overstates its evidence becomes a finding as soon as the reviewer opens the citation. Because the matrix drives how the whole package is examined, a weak matrix invites deeper scrutiny of everything, turning a documentation shortcut into a longer, more adversarial review than a reconciled matrix would have drawn.

How the work runs

What the buyer receives

• A gap list naming each missing row, weak means of compliance, or stale citation
• An evidence map behind every matrix entry, tying the claim to its current supporting record
• A closure sequence that puts basis-coverage gaps ahead of citation refreshes

Who uses the output

• Engineering leadership deciding whether the matrix is a sound basis for the submittal
• Certification staff who need the specific rows and citations to reconcile
• The team responding to a finding about coverage or means of compliance

How the work fits into the transaction or program

The compliance matrix is the index to the entire certification package, the document an authority reads first to plan its review. This review checks that index against the basis and the underlying evidence, so the matrix presents an accurate map rather than an optimistic one, and the deeper reviews it points to hold up when the authority follows the citations.

Jurisdiction-specific considerations

FAA and EASA build their reviews around the compliance matrix, but each frames the certification basis and acceptable means of compliance in its own terms. The review reconciles the matrix against whichever basis and means the program is working to, so the same matrix does not quietly leave a requirement uncovered under one authority's framing while appearing complete under the other's.

Regulatory limits

This review reports whether the matrix covers the basis and whether its citations hold. It does not accept the matrix, does not issue or accept a compliance finding, and does not make an airworthiness determination. Judging the sufficiency of a means of compliance remains with the authority or its delegate.

What this review does not cover

• Authoring the missing evidence a matrix gap calls for
• Setting the means of compliance an authority must accept
• Issuing or accepting a compliance finding

Specific to this review

• The matrix is the only certification document whose defect propagates into the authority's review plan, so an omission there quietly shrinks the scope the authority thinks it is examining.
• Basis amendments are the usual source of missing rows, because a new requirement has to be noticed and added by hand, and nothing in the matrix flags its own incompleteness.
• A stale citation is more dangerous than a missing one, because a missing cell looks unfinished while a stale cell looks done, and only opening the evidence reveals the difference.
• A weak means of compliance often survives internal review precisely because the cell is filled in; the claim is only tested when a reviewer asks why that method suffices for that requirement.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits