Pre-submittal finding closure
Refreshing stale citations in a compliance matrix before submittal
This work repairs a compliance matrix whose entries point at evidence that has moved on: a superseded report revision, a renumbered document, an analysis that changed conclusions after the citation was written. An engineer reads the matrix, checks each citation against the current evidence, and confirms the cited document still says what the compliance claim depends on. It runs during a pre-submittal review before the matrix goes to the authority. You receive a closure brief on the stale and inconsistent citations, an evidence request list for documents that need to be located or reissued, and a disposition package with a matrix a reviewer can follow to live evidence.
When this review is needed
- The compliance matrix cites report revisions that have since been superseded and never updated in the matrix.
- Documents were renumbered or reissued and the matrix still references the old identifiers.
- An analysis was revised after the citation was entered and its updated conclusion no longer matches the claim.
- The same requirement is supported by two matrix entries that cite conflicting evidence.
The problem
A compliance matrix ages faster than the team maintaining it. Reports get revised, documents get renumbered, an analysis changes its answer, and each event breaks a citation somewhere in the matrix that nobody circles back to update. The matrix still looks authoritative, but a reviewer who opens a cited document and finds a superseded revision, or a conclusion that no longer supports the claim, has to wonder how many other citations are stale. Checking them all by hand is tedious and easy to defer until submittal is already looming.
What gets reviewed
- Each matrix citation checked against the current controlled revision of the document it names
- Renumbered or reissued documents reconciled to the identifiers the matrix uses
- Cited analyses confirmed to still support the compliance claim after any revision
- Duplicate matrix entries for one requirement resolved to a consistent citation
- Citations pointing at documents no longer in the data set flagged for retrieval
- A corrected matrix in which every citation resolves to live evidence supporting the claim
What gets validated
- Every citation resolves to the current controlled revision, not a superseded one
- Document identifiers in the matrix match the current numbering of the evidence they cite
- A cited analysis or report still states the conclusion the compliance claim relies on
- No requirement carries two matrix entries that cite conflicting evidence
- Any citation to a document absent from the data set is flagged rather than left in place
Evidence normally required
- The compliance matrix or checklist with its current citations
- The controlled document register showing current revisions and identifiers
- The cited reports, analyses, and test records themselves
- The change history for evidence that has been revised or reissued
- The finding text identifying the stale or inconsistent citations
Common discrepancies
- A matrix entry citing a report revision two levels behind the current issue
- A document renumbered in a reorganization that the matrix still cites by its old identifier
- A revised analysis whose new conclusion no longer supports the compliance claim above it
- Two matrix rows for the same requirement citing different and inconsistent evidence
What is at stake
Stale citations turn a strong compliance argument into an untrustworthy one. A reviewer who catches a citation pointing at superseded evidence stops taking the rest on faith and starts pulling documents, which slows the review and can convert a clean submittal into an iterative one. If a cited analysis actually reversed its conclusion, the underlying compliance claim may no longer hold, which is a far larger problem than a bad reference.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Resolve each citation
Open the document behind every matrix entry and confirm it is the current controlled revision.
Test the claim
Check that a cited analysis or report still states what the compliance claim depends on.
Reconcile duplicates
Collapse conflicting entries for one requirement onto a single consistent citation.
Package the disposition
Write the closure brief, list documents to retrieve, and deliver a matrix that resolves to live evidence.
What the buyer receives
- A closure brief cataloguing the stale and inconsistent citations and their corrections
- An evidence request list for documents that must be located or reissued
- A reviewer-ready disposition package with a matrix whose citations point at live evidence
Who uses the output
- Certification engineers refreshing the matrix ahead of submittal
- Program managers judging whether a reversed analysis reopens a compliance claim
- Document control staff reconciling matrix identifiers to the current register
How the work fits into the transaction or program
Citation refresh runs at the pre-submittal stage, once the compliance matrix is assembled and about to become the reviewer's roadmap through the evidence. It depends on a settled document register and complements the verification-evidence check, since a citation is only as good as the artifact behind it. A clean matrix keeps the review moving through the argument instead of stalling on broken references.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Jurisdiction-specific considerations
FAA and EASA structure their compliance checklists differently and expect citations in their own conventions, so the refreshed matrix uses the identifiers and format the reviewing authority reads rather than a single internal scheme.
Regulatory limits
This work verifies that citations point at current evidence that supports the claim. It does not revise the underlying reports, re-perform any analysis, approve the matrix, or make the compliance finding, which stay with the applicant and the authority.
What this review does not cover
- Revising or reissuing the cited reports and analyses
- Re-running an analysis whose conclusion has changed
- Making the compliance finding on any matrix line
Specific to this review
- A citation to a revised analysis is the dangerous case, because the reference can be corrected while the compliance claim it supports may have quietly become false.
- Document renumbering during a reorganization breaks citations silently, since the old identifier still looks like a valid reference until someone tries to open it.
- Two conflicting entries for one requirement read to a reviewer as a matrix nobody controls, which erodes trust faster than a single stale reference.
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
What if a revised analysis no longer supports the claim it is cited against?
That is more than a citation problem, so we flag it as a substantive gap, not a reference fix. The compliance claim then needs the applicant's engineering judgment, possibly new work, before it can be relied on. We surface it clearly rather than papering over it with an updated reference.
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.