Compliance planning
Means-of-compliance map evidence review for qualification test teams
A means-of-compliance map review checks that every certification requirement in a test program has a declared method and an evidence artifact that actually satisfies it. It is run for a qualification test team ahead of a data submittal, a finding response, or a design change that reopens the map. The reviewer walks each row from the requirement to its assigned means and then to the evidence that closes it, flagging requirements that carry a means on paper but no path to a deliverable. You receive a gap list, a reconciled evidence map, and a closure order that test leadership can work against.
When this review is needed
- The compliance data is about to go to the authority and the map has never had an outside read.
- An authority finding questioned the method chosen for a set of requirements and the map has to answer it.
- A design change altered which requirements apply and the assigned means no longer line up.
- A new certification basis was agreed and the map was updated in a hurry to match it.
The problem
The map is where a program tells itself the compliance story is complete, and that is exactly why it hides trouble. A requirement can show a tidy method in the column, test or analysis or inspection, while the artifact that method points to was never produced or points back at the wrong requirement. The team reads the column, sees a means, and moves on. The authority reads the evidence and finds nothing behind it.
What gets reviewed
- Each requirement in the certification basis traced to a declared means of compliance
- The declared method checked against the artifact type it is supposed to yield
- Requirements carrying a means with no evidence artifact identified and listed
- Method choices reconciled against the guidance the basis actually allows
- Shared evidence checked so one artifact is not credited to requirements it does not cover
- The closure order set by which gaps block the most downstream work
What gets validated
- Every row links a specific requirement to a specific means and a named artifact
- The declared method is one the certification basis accepts for that requirement class
- No requirement is marked complete against evidence that does not yet exist
- An artifact credited to several requirements genuinely satisfies each of them
- Requirements added or changed by the latest design change appear on the map
Evidence normally required
- The current means-of-compliance map or compliance checklist
- The agreed certification basis and applicable special conditions
- The requirement set the map is built against
- The list of evidence artifacts already produced or planned
- Any authority correspondence that constrains a method choice
Common discrepancies
- A requirement with a declared means but no artifact assigned to close it
- A method that the basis does not accept for that requirement class
- One test report credited to requirements it never exercised
- Requirements introduced by a design change that never reached the map
What is at stake
A map that declares a means without an artifact behind it turns into a finding the moment a reviewer pulls the thread. Late-stage discovery forces the team to generate evidence under schedule pressure, or to change the method and rerun work that was thought closed. Either path pushes the submittal date and burns credibility with the authority that will read the next package more skeptically.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Pull the map against the basis
Lay the means-of-compliance map beside the agreed certification basis and confirm every applicable requirement appears.
Walk means to artifact
For each row, follow the declared method to the named evidence artifact and confirm it exists and fits.
Test the shared evidence
Check that artifacts cited against multiple requirements actually satisfy each one they are credited to.
Order the gaps
Rank open rows by the downstream work they block so leadership closes the most costly first.
What the buyer receives
- A gap list of requirements whose means has no supporting evidence path
- A reconciled evidence map tying each requirement to its artifact
- A closure order ranking gaps by the downstream work they block
Who uses the output
- Test leadership deciding which gaps to close before the data ships
- Certification leadership answering an authority on how a method was chosen
- Engineering leads generating the artifacts the map still lacks
How the work fits into the transaction or program
The map is the index the rest of the compliance package hangs from, so this review runs before the individual evidence reviews rather than after them. Once the map holds, the trace, verification, and lifecycle data reviews each check that the artifact behind a row is real. The gap list here tells those later passes where to look first.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
The FAA and EASA accept overlapping but not identical methods for a given requirement, so a map built for one authority can carry method choices the other will question. The review notes where a declared means holds under one system and needs a different justification under the other, which matters most on a program pursuing validation on both sides.
Regulatory limits
The review checks that the map is internally coherent and that every declared means has an artifact behind it. It does not make a compliance finding, approve a method of compliance, or determine that any requirement is satisfied. Those determinations rest with the authority and its designees.
What this review does not cover
- Producing the missing evidence artifacts
- Selecting or approving the method of compliance for a requirement
- Any airworthiness or compliance determination on the design
Specific to this review
- The map is the one document a reviewer can use to audit the whole program at once, so a soft row here is more exposed than a soft row buried in a report.
- A method declared correctly but pointing at an artifact that was never built is the most common defect, because the column looks complete either way.
- Shared evidence is where credit gets overstated: one report gets cited across requirements it only partly exercises.
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 running the compliance checklist ourselves?
It is an independent pass over the same map. The value is that the reviewer has no stake in a row reading closed, so a means that points at nothing is caught here rather than by the authority. The output is a gap list your team works, not a rewrite of your checklist.
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.