Finding closure
Certification findings left open with no closure evidence on file
This page is for avionics and airborne-equipment suppliers carrying open certification findings that no closure evidence has been filed against. The trigger is a finding register, issue-paper list, or audit action set that shows items still open with no evidence tying a response to the finding it answers. We review the finding register, the responses on record, the cited artifacts, and the traceability between them to map which findings have closure evidence, which have a response but no evidence, and which have neither. You receive a closure-status map per finding, the specific evidence each open finding still needs, and a sequence to close them.
When this review is needed
- A finding register shows items open with no closure evidence tied to them.
- Issue papers were raised during certification and the responses were never substantiated and filed.
- Stage-of-involvement or audit action items remain open and the closure record is incomplete.
- A program was paused and restarted, and nobody can say which findings actually closed.
- A change of certification team left findings whose closure history lives only in people's memory.
The problem
A finding stays open until evidence closes it, but the evidence and the finding often live apart. A finding is raised in one system, a response is written in another, and the artifact that should close it sits in a third with no link back. When a program slows or the team changes, the thread between a finding and its closure breaks, and a finding that was effectively answered still reads as open because nothing ties the answer to it. Reconstructing that link late, against memory rather than records, is slower than building it as the findings closed.
What gets reviewed
- The full finding register and the current status recorded against each item
- Issue papers, stage-of-involvement actions, and audit findings raised during the program
- The response on record for each finding and whether closure evidence is attached
- Traceability from each finding to the artifact that closes it
- Items answered in principle but never substantiated or filed
- Items whose closure history was lost to a pause or a team change
- Duplicate or superseded entries that distort the open count
What gets validated
- Every finding in the register has a recorded status that matches its evidence
- Each closed finding has closure evidence attached and traceable to the finding
- Each open finding has the specific evidence it needs identified
- Responses written in principle are backed by a substantiating artifact
- Issue-paper and audit actions are reconciled into one finding view
- Duplicate and superseded findings are identified so the open count is real
- The link between a finding and its closing artifact survives independent of who recorded it
Evidence normally required
- The finding register and any issue-paper or audit action lists
- The response written against each finding
- The artifacts cited as closing each finding, or an index to them
- Prior authority correspondence on the findings
- Any record of which findings closed before a pause or team change
Common discrepancies
- An item marked open with a written response but no closure evidence attached
- Findings effectively answered yet never substantiated, so they still read as open
- Closure artifacts that exist but are not linked back to the finding they close
- Issue-paper and audit actions tracked in separate systems with no reconciled view
- Duplicate entries inflating the open count beyond the real work
- Items whose closure history was lost to a program pause or a change of team
What is at stake
Open findings with no closure evidence hold a submission as surely as a technical gap does, because an authority will not close a program against unanswered findings. Findings that were actually resolved but never documented have to be reworked or re-substantiated, repeating effort the team already spent. Each unclosed finding is a held item on the path to authorization, and the longer it sits the harder its history is to recover.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Reconcile the register
Pull every finding from the register, issue papers, and audit actions into one view and remove duplicates and superseded items.
Match evidence to findings
For each finding, find the response and the closing artifact, and confirm the link between them holds.
Map the status
Separate closed findings from answered-but-unsubstantiated and from open, recording the evidence each open one needs.
Sequence the closure
Order the open findings by the evidence they require so the team can close them in a workable sequence.
What the buyer receives
- A closure-status map across all findings, separating closed, answered-but-unsubstantiated, and open
- The specific closure evidence each open finding still needs
- Traceability links from each finding to its closing artifact where it exists
- A sequence to close the open findings, ordered by the evidence each one requires
Who uses the output
- Certification leads driving the program to a closed finding state
- Quality teams reconstructing the closure record across systems
- Program management sequencing the work to close held findings
How the work fits into the transaction or program
The review reconciles findings against their evidence, which complements a claims review and a matrix review by closing the loop opened during the program rather than asserted in the package. It supports the applicant's own finding-closure work and leaves a traceable record the next reviewer can follow.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Regulatory limits
Endeavor Elements maps findings to closure evidence and identifies what is missing. It does not close findings on the authority's behalf, make compliance findings, or guarantee that the authority will accept a closure. The authority retains its role in determining whether a finding is closed.
What this review does not cover
- Closing findings or accepting closures on the authority's behalf
- Generating the closure evidence a finding requires itself
- Issuing any approval, authorization, or airworthiness determination
Specific to this review
- A finding, its response, and its closing artifact frequently live in three separate systems with no link between them, which is why an answered finding can still read as open.
- Findings that were actually resolved but never documented are common after a program pause or a team change, and they have to be re-substantiated rather than simply marked closed.
- Superseded and duplicate entries inflate the open count, so the real closure workload is often smaller than the register first suggests.
- Reconstructing a finding-to-evidence link late, from memory rather than records, is slower than building it as each finding closed.
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.
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
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).
Frequently asked questions
What if a finding was answered but the evidence was never filed?
That is the most common case. The review flags it as answered-but-unsubstantiated, identifies the artifact needed to make the response stand on its own, and links it back to the finding so it reads as closed against the record rather than against memory.
Can you close the findings for us?
No. We map findings to the evidence they need and sequence the work. The applicant assembles or generates the closure evidence, and the authority retains its role in determining whether a finding is closed.
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.