Certification evidence
Compliance matrix evidence review for avionics suppliers
A compliance matrix evidence review reads an avionics supplier's matrix as a reviewer will and tells you where it does not hold up. It is for a supplier about to submit, respond to a finding, or run a design change who needs the matrix to be more than a list. The review checks that every applicable requirement is covered, that each cited means of compliance is the right one, and that the evidence a line points to still says what the line claims. You get a gap list ordered by leverage, an evidence map behind the matrix, and a closure sequence that certification leadership can work through.
When this review is needed
- A submittal is imminent and the matrix has to survive a reviewer walking it line by line.
- A finding was raised and the response depends on matrix entries that have not been re-checked.
- A design change touched requirements and the matrix has not been reconciled to the new evidence.
- Ownership of the matrix passed between engineers and no one has confirmed it still hangs together.
The problem
A compliance matrix looks finished long before it is trustworthy. Requirements get a means of compliance assigned early, then the evidence they point to is revised, superseded, or never actually produced, and the matrix keeps asserting the old claim. A reviewer does not read the matrix as a summary, they treat each line as a promise and pull the evidence behind it, and a supplier who has not done the same walk is finding the broken lines in the room instead of before it.
What gets reviewed
- Every applicable requirement checked for a matrix line that addresses it
- The means of compliance on each line confirmed as appropriate to the requirement
- The evidence each line cites verified to still support the claim it carries
- Links from the matrix to the certification basis confirmed rather than assumed
- Superseded or revised evidence caught where a line still points at the old version
What gets validated
- No applicable requirement is left without a matrix line addressing it
- Each cited means of compliance suits the requirement rather than defaulting to inspection
- The evidence a line points to reads, on retrieval, as supporting the claim made
- Each matrix line traces to the certification basis it is answering
- A revised or superseded piece of evidence is caught before the line relying on it is submitted
Evidence normally required
- The compliance matrix in its current revision
- The certification basis and applicable requirements for the article
- The evidence artifacts the matrix lines cite
- The revision history for the evidence the matrix depends on
- Any open finding the review is responding to
Common discrepancies
- A matrix line citing evidence a later revision superseded
- A requirement with no line addressing it at all
- A means of compliance assigned that does not actually suit the requirement
- A line that traces to the wrong paragraph of the certification basis
What is at stake
A matrix line that cites evidence no longer supporting the claim turns into a finding, and a cluster of those turns a submittal into a series of round trips that each cost a review cycle. A requirement with no evidence path at all is worse, because it surfaces as a coverage gap the supplier has to close before the review can even continue, and by then the schedule pressure is highest.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Confirm coverage
Check every applicable requirement has a matrix line that addresses it.
Test the means
Confirm each cited means of compliance suits the requirement it answers.
Pull the evidence
Retrieve what each line points to and confirm it still supports the claim.
Sequence the fixes
Rank the broken lines by leverage and lay out the order to close them.
What the buyer receives
- A gap list ranking each matrix shortfall by its effect on the submittal
- An evidence map tying every line to the artifact behind it
- A closure sequence certification leadership can work through in order
Who uses the output
- Certification leads walking the matrix as a reviewer will before they submit
- Engineering leads deciding which lines need new evidence or a different means of compliance
- Reviewers on the supplier side confirming coverage is complete before a finding response goes out
How the work fits into the transaction or program
The compliance matrix is the index a reviewer navigates the whole submittal by, so a weak matrix undermines strong evidence sitting behind it. Reviewing it before the reviewer does lets the supplier fix broken lines on their own schedule, and the evidence map it produces becomes the working index for the certification plan and the requirements trace that sit alongside it.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
The matrix has to answer the certification basis the FAA and EASA set for the article, and the two authorities can accept different means of compliance for the same requirement. The review notes where a line that satisfies one authority would be questioned by the other, so a matrix built for one submittal is not assumed to carry the other unchanged.
Regulatory limits
The review checks the matrix for coverage, appropriate means of compliance, and evidence currency. It does not make a compliance finding, accept the matrix on an authority's behalf, or determine that the article is compliant or approvable.
What this review does not cover
- Producing the evidence a matrix line is missing
- Making the compliance finding on any line
- Any determination that the article meets its certification basis
Specific to this review
- A reviewer treats each matrix line as a claim to test, not a summary to skim, so the review walks the lines the same way rather than reading the totals.
- The most common failure is not a missing requirement but a line pointing at evidence a later revision quietly superseded.
- A means of compliance defaulted to inspection where analysis or test was needed is a finding waiting to happen, because it reads as covered until the reviewer asks what the inspection actually showed.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
Frequently asked questions
Is this the same as making the compliance findings?
No. The review checks that your matrix is complete, appropriately justified, and backed by current evidence, so it holds up when a reviewer walks it. Making the compliance finding on each line rests with the authority, and the review does not do that or predict that it will go your way.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.