Means of compliance
Means-of-compliance map evidence review for certification teams
A means-of-compliance map evidence review checks that the requirement-to-evidence logic actually closes: that every requirement given a means also has a real path to the evidence that means demands. It is run for a certification team before submittal, during a finding response, or ahead of a design change review, by or for the team that owns the compliance strategy. The work reads the map from each requirement through its assigned means to the test, analysis, or inspection that must produce the evidence, then flags where a means is declared but the evidence path dead-ends. You receive a gap list, an evidence map exposing each broken path, and a closure sequence compliance management can drive.
When this review is needed
- A requirement carries an assigned means on paper but no test, analysis, or inspection is scheduled to produce the evidence.
- A design change replaced a test article and the means that depended on it has not been reassigned.
- Several requirements were assigned the same analysis and no one confirmed it can support all of them.
- The team is planning the verification campaign and needs every means to resolve to a real evidence path first.
The problem
Assigning a means of compliance is a planning act, and plans outrun execution. A requirement gets marked for test, analysis, or inspection early, and the map records the intent, but the corresponding activity is never scheduled, the article it needed was cut, or the analysis method was chosen before anyone confirmed it could actually close the requirement. The map reads as fully assigned, yet a share of its paths lead nowhere, and that only shows up when the evidence is due and does not exist.
What gets reviewed
- Each requirement traced from its assigned means to the specific activity that produces the evidence
- Assigned means checked as appropriate to the requirement rather than chosen for convenience
- Test-based means reconciled to a planned test and an available or conformed article
- Analysis-based means checked so the method can actually close the requirement it is assigned to
- Requirements sharing one means checked so the single activity supports each of them
- Design-change effects traced to any means whose evidence path a change disturbed
What gets validated
- Every requirement with an assigned means has a scheduled activity that will produce its evidence
- Each assigned means suits the requirement, not merely the least costly option to declare
- A test-based means points to a planned test and an article that can be conformed for it
- An analysis-based means uses a method capable of closing the requirement it serves
- A means shared across requirements is confirmed to support every one it is assigned to
Evidence normally required
- The means-of-compliance map or matrix in its current state
- The requirement set and the certification basis behind it
- The verification plan and the test, analysis, and inspection schedule
- The article and test-asset availability for test-based means
- The design change history affecting assigned means
Common discrepancies
- A requirement with an assigned means but no scheduled activity to produce evidence
- A test-based means whose article was cut in a design change and never reassigned
- An analysis method assigned to a requirement it cannot actually close
- One analysis stretched across requirements it only partially supports
What is at stake
A means with no evidence path is a requirement that quietly has no plan to be met, and each one discovered late forces an unbudgeted test or analysis onto a schedule with no room for it. When several dead-end paths surface together near submittal, the verification campaign has to be replanned under pressure, and the compliance finding those requirements were meant to support cannot be made until the path is rebuilt.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Walk each path
Follow every requirement from its assigned means to the activity that must produce evidence.
Test the fit
Confirm each means suits its requirement and, for tests, points to a schedulable article.
Probe shared means
Check that any means assigned to several requirements can support each of them.
Sequence the rebuild
Order the reassignment and scheduling work against the submittal date.
What the buyer receives
- A gap list identifying each requirement whose assigned means has no evidence path
- An evidence map exposing where the requirement-to-evidence logic dead-ends
- A closure sequence ordering the reassignment and scheduling work against submittal
Who uses the output
- Compliance managers confirming every means resolves to producible evidence before submittal
- Certification leads deciding which broken paths must be replanned first
- Engineering owners reassigning a means whose test article or method fell through
How the work fits into the transaction or program
The means-of-compliance map is where the certification plan's strategy becomes an executable verification campaign, so a dead-end path here is a requirement that will fail to close downstream. Reviewing it before the campaign is committed lets the team fix a broken assignment while options are still cheap, and the map it produces feeds directly into the requirements and verification traces that record the evidence once it exists.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
FAA and EASA accept overlapping but not identical sets of means, and a method acceptable to one authority for a given requirement may need a different or supplemented means under the other. Where a project is certified under both, the review notes where an assigned means holds for one authority but leaves a gap for the other.
Regulatory limits
The review confirms the requirement-to-evidence logic is complete and executable. It does not accept a means of compliance on the authority's behalf, perform the assigned tests or analyses, or determine that a requirement is met.
What this review does not cover
- Performing the tests, analyses, or inspections the means require
- Deciding on the authority's behalf whether a means is acceptable
- Any determination that a requirement is complied with
Specific to this review
- Assigning a means is a plan, not evidence, so a fully assigned map can still hide requirements with no real path to being met.
- The costliest dead-end paths are test-based, because rebuilding one late means finding an article, conforming it, and scheduling a test with no slack left.
- An analysis assigned to a requirement it cannot close is a subtle failure, because the map looks complete until someone checks whether the method actually reaches the requirement.
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
How is this different from checking the compliance matrix?
The compliance matrix records whether evidence exists and supports a claim. The means-of-compliance map is upstream of that: it checks whether each requirement even has a viable path to producing evidence in the first place, which is where a verification campaign either holds together or quietly fails.
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.