Compliance claims
Certification compliance claims that the evidence does not support
This page is for avionics and airborne-equipment suppliers whose compliance claims are not backed by the evidence they cite. The trigger is a met status in the matrix, a conformity or compliance statement, or a closed-finding response that asserts compliance the underlying data does not actually demonstrate. We review the compliance matrix, the cited artifacts, the verification record, and the supporting statements to separate claims that hold from claims that do not. You receive a register of unsupported claims, the specific evidence each one is missing, and a recommendation to substantiate it or restate the claim to what the data shows.
When this review is needed
- A matrix carries requirements marked met where the cited document does not demonstrate the claim.
- A conformity or compliance statement asserts more than the assembled artifacts actually show.
- A finding was answered with a claim of compliance but the closure evidence was never attached.
- Verification status was rolled up to met before the underlying test or analysis was complete.
- Carried-over or reused credit was claimed without confirming it transfers to this article and configuration.
The problem
An unsupported claim reads exactly like a supported one. Both show met in the matrix and both cite a document. The difference is whether the cited document, opened and read against the requirement, actually demonstrates compliance. Claims drift toward met under schedule pressure: status is rolled up before evidence lands, a citation is added before the artifact is final, or credit is assumed to transfer. When a reviewer opens the cited document and it does not say what the claim asserts, the credibility of the rest of the package drops with it.
What gets reviewed
- Each met or compliant status in the matrix and whether its cited evidence demonstrates the claim
- Conformity and compliance statements measured against the artifacts behind them
- Closed-finding responses that assert compliance and the evidence attached to them
- Verification status roll-ups checked against the completeness of the underlying activity
- Compliance credit carried from another program and whether it transfers to this article and configuration
- The gap between what each claim asserts and what the cited data actually shows
What gets validated
- Every met status cites a document that, read against the requirement, demonstrates the claim
- Conformity and compliance statements are consistent with the artifacts they summarize
- Closed-finding responses have the closure evidence they claim attached and current
- A met status is backed by completed verification rather than planned activity
- Carried-over credit is shown to apply to this article, configuration, and assurance level
- Claim wording matches what the evidence supports, with no overstatement of scope
Evidence normally required
- The compliance matrix with its status and citation columns
- The cited artifacts or an index that resolves each citation to a document
- Conformity statements, compliance statements, and finding responses
- The verification record showing which activities are complete
- Any prior authority correspondence on disputed or unsubstantiated claims
Common discrepancies
- A met status whose cited document does not address the requirement it is attached to
- A compliance statement that asserts broader coverage than the artifacts support
- A finding response claiming closure with no closure evidence attached
- Verification rolled up to met while the underlying test or analysis is still open
- Carried-over credit claimed without confirming it transfers to the current configuration
- Claims that overstate scope, covering conditions the evidence never tested
- Citations pointing at a draft or planning document rather than a final artifact
What is at stake
A claim a reviewer cannot substantiate from the cited evidence becomes a finding, and a pattern of them invites deeper sampling of claims that were sound. The work to substantiate a claim after the fact is the verification that should have preceded it, now done under review pressure. Each unsupported claim that surfaces in review costs a cycle and erodes the weight the authority gives the rest of the submission.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Resolve the claims
List each met status, statement, and finding response, and resolve every citation to a specific artifact.
Read against the requirement
Open each cited document and check whether it demonstrates the exact claim it is attached to.
Separate and register
Sort claims that hold from claims that do not, recording the specific evidence each weak claim lacks.
Recommend the fix
For each unsupported claim, recommend substantiating it with named evidence or restating it to what the data shows.
What the buyer receives
- A register of unsupported claims with the specific evidence each one lacks
- A recommendation per claim to substantiate it or restate it to what the data shows
- A separation of claims that hold from claims that need work, ordered by review risk
- A short list of the verification or analysis needed to make weak claims sound
Who uses the output
- Certification leads deciding which claims to defend and which to restate
- Compliance teams attaching or generating the evidence a claim needs
- Engineering teams completing the verification behind rolled-up statuses
How the work fits into the transaction or program
The review tests the truth of the claims a matrix asserts, where a matrix review tests coverage and currency of citations. Substantiating claims before submittal keeps a reviewer from finding the gap first and sampling deeper. It supports the applicant's program and stops short of any compliance finding.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Regulatory limits
Endeavor Elements assesses whether the applicant's evidence supports the applicant's claims. It does not make compliance findings, accept claims on the authority's behalf, or guarantee that a substantiated claim will be accepted. Records consistency and traceability are distinct from regulatory acceptance and airworthiness approval.
What this review does not cover
- Making compliance findings or accepting claims on the authority's behalf
- Generating the missing test or analysis evidence itself
- Issuing any approval, authorization, or airworthiness determination
Specific to this review
- An unsupported claim and a supported one look identical in the matrix; the difference appears only when the cited document is opened and read against the requirement.
- Claims drift toward met under schedule pressure, when status is rolled up before evidence lands or a citation is added before the artifact is final.
- A single unsupported claim a reviewer catches invites deeper sampling of claims that were sound, so the cost is wider than the one entry.
- Reused compliance credit is a frequent source of unsupported claims, because credit is assumed to transfer without confirming the article, configuration, and assurance level match.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
RTCA. Design assurance objectives and lifecycle data for airborne electronic hardware (FPGA/ASIC/PLD).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Frequently asked questions
Is an unsupported claim the same as a missing document?
Not always. A document can be present and cited yet still fail to demonstrate the claim it sits against. The review reads each citation against its requirement, so it catches present-but-insufficient evidence as well as absent evidence.
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.
Walk through your situation with an engineer who has done this work.