Pre-submittal finding closure
Closing requirements with no means of compliance assigned
This work closes a finding where requirements carry no clear means of compliance, no named evidence source, and no owner to close them. An engineer reads the compliance data, isolates each requirement that lacks an assigned method, and proposes the means of compliance, the evidence that will satisfy it, and the party responsible for producing it. It runs during a pre-submittal review. You get a closure brief on the requirements with no assigned method, an evidence request list for the compliance data now to be produced, and a disposition package assigning a means of compliance, an evidence source, and a closure owner to every requirement.
When this review is needed
- Requirements appear in the compliance data with the means-of-compliance field blank or undecided.
- A requirement has a stated method but no evidence source and no one assigned to produce it.
- A method was assigned that does not actually fit the requirement it is attached to.
- Ownership of a cluster of requirements was never settled between engineering and certification.
The problem
Every requirement needs a decision about how compliance will be shown and who will show it, and those decisions are the ones that stall. A means-of-compliance field gets left as undecided, a method is picked but nobody is put on the hook for the evidence, or a requirement lands between engineering and certification with each assuming the other owns it. The requirement then drifts toward submittal with no path to closure, and because it looks like a planning item rather than a technical one, it is easy to leave for later until later is submittal.
What gets reviewed
- Each requirement checked for an assigned means of compliance
- The proposed method confirmed to fit the nature of the requirement
- An evidence source identified for each method, whether test, analysis, inspection, or review
- A closure owner assigned to every requirement so none is left unowned
- Requirements sitting between engineering and certification surfaced and allocated
- A view assigning method, evidence source, and owner across the requirement set
What gets validated
- Every requirement carries an assigned means of compliance rather than an undecided field
- The assigned method fits the requirement it is attached to and can actually satisfy it
- Each method names an evidence source that will exist, whether test, analysis, inspection, or review
- Every requirement has a named closure owner responsible for producing the evidence
- No requirement falls between engineering and certification with neither team owning it
Evidence normally required
- The requirements set with any means-of-compliance and ownership fields
- The certification plan and its acceptable means of compliance
- The compliance matrix as it stands, for cross-check
- The team responsibility split between engineering and certification
- The finding text identifying the requirements with no assigned method
Common discrepancies
- A requirement with the means-of-compliance field left undecided all the way to review
- A method assigned to a requirement it cannot actually satisfy
- A requirement with a method but no named owner for the evidence
- A cluster of requirements that engineering and certification each assumed the other owned
What is at stake
A requirement with no means of compliance has no way to close, so it either surfaces as an open finding at review or, worse, ships as a claim with nothing behind it. Both stall the submittal. An unowned requirement is the most likely to be forgotten entirely, and a method assigned that does not fit the requirement produces evidence a reviewer will reject, sending the team back to redo work that could have been scoped correctly the first time.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Isolate the unassigned
Pull the requirements with no means of compliance, no evidence source, or no owner.
Fit a method
Propose a means of compliance that suits each requirement and name the evidence it will produce.
Assign ownership
Put a named closure owner on every requirement, resolving the ones between teams.
Package the disposition
Write the closure brief, list the evidence to produce, and deliver method, source, and owner per requirement.
What the buyer receives
- A closure brief listing requirements with no assigned method and the method proposed for each
- An evidence request list for the compliance data now to be produced
- A reviewer-ready disposition package assigning method, evidence source, and owner per requirement
Who uses the output
- Certification engineers closing the means-of-compliance gaps before submittal
- Program managers scoping and scheduling the evidence each newly assigned method needs
- Compliance leads allocating ownership across engineering and certification
How the work fits into the transaction or program
Means-of-compliance closure runs early in a pre-submittal review, because an unassigned method usually implies evidence that still has to be produced. It builds on the certification plan and the basis coverage check, and it underpins the compliance matrix and the verification trace, both of which assume every requirement already has a method and an owner. Closing it early keeps the downstream evidence work inside the schedule rather than surfacing as new scope at review.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Jurisdiction-specific considerations
FAA and EASA maintain different catalogs of acceptable means of compliance and different conventions for how a method is stated, so each requirement's assigned method is expressed against what the reviewing authority will accept rather than a single generic list.
Regulatory limits
This work assigns a means of compliance, an evidence source, and an owner to each requirement. It does not produce the compliance evidence, approve the means of compliance, or make the compliance finding, all of which remain with the applicant and the authority.
What this review does not cover
- Producing the test, analysis, inspection, or review evidence a method requires
- Approving the means of compliance as a regulatory act
- Making the compliance finding on any requirement
Specific to this review
- An unowned requirement is the one most likely to be forgotten, because no single person feels the pressure to close it.
- A method that does not fit its requirement is worse than a blank field, since it produces evidence a reviewer rejects and sends the work back to the start.
- Means-of-compliance gaps read as planning items, not technical ones, which is exactly why they get deferred until submittal is already close.
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
Do you produce the compliance evidence once the method is assigned?
No. We assign the means of compliance, name the evidence source, and put an owner on each requirement so there is a clear path to closure. Producing the test, analysis, inspection, or review evidence is the assigned owner's work, scheduled by the program once the gaps are visible.
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.