Clearing findings marked closed without real closure evidence

When this review is needed

• The register shows a wall of closed findings, but spot checks turn up closures with no attached artifact.
• Findings were marked resolved in a review meeting and the follow-up evidence was never filed.
• A previous submittal reopened items the team believed were long closed, and confidence in the register has dropped.
• Program management wants the closure history verified before it becomes part of the record the authority reads.

The problem

A finding register is only as honest as its closure column. Under review pressure an item gets marked closed when someone agrees to fix it, when a discussion feels settled, or when an owner leaves and their open items are tidied away. The status reads closed, the artifact that would prove it never landed, and the register grows a comfortable green that nobody has tested. By submittal the team has stopped remembering which closures were real.

What gets reviewed

• Every finding marked closed tested against the specific issue it was raised to address
• Closures that rest on a meeting note, a verbal agreement, or an action item with no artifact identified
• The attached evidence checked for whether it resolves the finding or merely acknowledges it
• Reopened items dispositioned with the closure evidence they actually need
• Residual actions assigned to a named owner where closure cannot happen before submittal
• The register reconciled so its status column reflects what the evidence supports

What gets validated

• Each closed finding links to an artifact, not to a note that closure was intended
• The linked evidence answers the finding as written, covering the same scope the finding raised
• Closures inherited from a departed owner are re-tested rather than accepted on the prior status
• Findings touching several disciplines show closure evidence from every affected area, not one alone
• Reopened items carry a disposition and an owner so their status is honest going into submittal

Evidence normally required

• The current finding register with its status and closure references
• Closure artifacts, dispositions, and review-meeting minutes cited against the findings
• The certification plan and the review records that generated the findings
• The compliance evidence the findings were meant to protect
• Any prior authority correspondence that reopened or questioned closed items

Common discrepancies

• Findings marked closed against a meeting agreement with no follow-up artifact ever attached
• Closure evidence that acknowledges the issue but does not resolve the specific concern raised
• Items tidied to closed when their owner rolled off, with no one having verified the fix
• Multi-discipline findings closed on evidence from one area while another affected area was never addressed

What is at stake

A reviewer who reopens one green finding treats the closure column as unreliable and re-examines items the team counted as done. That reverses weeks of apparent progress and pushes the schedule right as the program feels finished. Findings that reopen at the authority arrive as formal actions, each one a new cycle, and a register that cannot be trusted invites broader scrutiny than the original findings ever warranted.

How the work runs

What the buyer receives

• A closure brief separating findings with real evidence from those closed on nothing
• An evidence request list naming the artifact each reopened finding needs
• A reviewer-ready disposition package the authority can follow finding by finding
• A reconciled register whose closure column reflects verified status

Who uses the output

• Certification engineers who will answer to the authority for each closed line
• Program managers judging whether the closure history is defensible enough to submit
• Register owners re-establishing that closed means closed before the authority reads it

How the work fits into the transaction or program

The register is where design reviews, internal audits, and authority questions all land as findings. This pass makes sure the closure column earns the trust the rest of the submittal depends on. Verified closures feed the disposition record the authority works from, and anything reopened flows into the same evidence retrieval effort that supports the rest of the package.

Jurisdiction-specific considerations

The FAA and EASA both weight a clean closure history heavily, because a register they can trust lets them sample rather than re-audit. When findings reopen, both authorities read it as a signal to look harder. Testing closures before submittal keeps the register credible under either regime and against the certification basis agreed for the program.

Regulatory limits

This work tests whether closures are supported and organizes reopened items for disposition. It does not make findings of compliance, close findings on the authority's behalf, or determine airworthiness. Accepting a closure as satisfied remains the authority's decision.

What this review does not cover

• Producing the corrective evidence a reopened finding needs
• Making or accepting compliance findings on the authority's behalf
• Re-running the design reviews that originally generated the findings

Specific to this review

• A finding closed on a meeting agreement is the register's most common lie, because the discussion felt conclusive and no one went back to check the artifact ever arrived.
• Closures inherited from a departed engineer deserve the most suspicion, since tidying an open list to closed at handover is easier than proving each item was fixed.
• One reopened green finding costs more than the finding itself, because it converts the whole closure column from evidence into a claim the reviewer now has to test.
• Evidence that acknowledges a finding is not evidence that closes it, and the gap between the two is where most false closures hide.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits