Certification problem
Compliance-matrix entries that cite superseded or moved documents
This page is for avionics and equipment suppliers whose compliance matrix cites document revisions that no longer say what the matrix claims. It triggers when documents have been revised, renumbered, or relocated since the matrix was built and the citations were never refreshed. The review opens each citation and confirms the referenced revision still exists and still supports the entry pointing to it, checking revision numbers, document identifiers, and the specific section cited. You get a citation-by-citation status and the corrected reference each stale entry needs.
When this review is needed
- Documents have been reissued at higher revisions and the matrix still names the original ones.
- A reorganization renumbered or relocated reports and the matrix references no longer resolve.
- An authority comment flags a citation that opens to a document saying something different.
- The team wants every reference confirmed against the current configuration baseline before submittal.
The problem
The matrix is the index a reviewer reads against, and it is built early while the documents it names keep moving underneath it. Reports get reissued, sections get renumbered, files get relocated, and the citation column quietly goes out of date. When a reviewer follows a reference and lands on a revision that has been superseded or on a section that no longer contains the cited material, the entry is dead on arrival and the credibility of the surrounding entries drops with it.
What gets reviewed
- Every document citation in the compliance matrix
- Whether the cited revision still exists in the configuration baseline
- Whether the current revision still supports the entry that points to it
- Section, paragraph, or figure references that may have moved within a revised document
- Document identifiers that changed under a renumbering or reorganization
- Citations to drafts that were later superseded by a released revision
What gets validated
- Each cited document and revision resolves to a record in the current baseline
- The current revision still contains the material the matrix entry relies on
- Section and figure references land on the content they name after any reissue
- No entry cites a draft when a released revision exists
- Renumbered or relocated documents are reflected by an updated citation
- Where a revision changed the cited content, the entry is reassessed rather than carried forward
Evidence normally required
- The current compliance matrix with its citations
- The configuration baseline or document revision index
- The cited documents themselves, or a controlled index to them
- Any reorganization or renumbering history since the matrix was built
Common discrepancies
- An entry naming a revision that a later release has superseded
- A section reference that points to relocated or renumbered content
- A citation to a draft that was finalized at a different revision
- A document identifier the matrix still uses after a renumbering
- A current revision that no longer supports the claim the older one did
What is at stake
A citation that resolves to the wrong revision turns a confirmable claim into a question. The reviewer cannot accept what they cannot find, so the entry reopens, the program chases the current reference, and the review stretches across the entries that should have been the simplest to clear.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Resolve each citation
Open every cited document and revision and confirm it exists in the current baseline.
Confirm the content
Check that the current revision still contains the material the entry relies on.
Flag the drift
Mark superseded revisions, relocated sections, and content that changed under a reissue.
Correct the references
Supply the current reference for each stale entry and list reassessments for review.
What the buyer receives
- A citation-by-citation status marking each as current, superseded, or unresolved
- The corrected reference for every stale or broken citation
- A flag where a newer revision changed the cited content and the entry needs reassessment
- A closure list ordered by the citations most exposed to a reviewer
Who uses the output
- Configuration management leads correcting the references
- Certification engineers reassessing entries whose source content changed
- Compliance management confirming the matrix before submittal
How the work fits into the transaction or program
This pass isolates citation currency, separate from whether the requirement is covered or the evidence is sufficient. It complements a full matrix review that also checks coverage and the strength of the underlying records.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Regulatory limits
Endeavor Elements checks whether the applicant's citations resolve to current supporting documents. It does not issue approvals, make findings for the authority, or warrant that any cited document satisfies the requirement.
What this review does not cover
- Reissuing or controlling the cited documents
- Generating evidence to replace a citation that no longer supports its entry
- Making official compliance findings or issuing approvals
Specific to this review
- Stale citation is the most common matrix finding precisely because the matrix is authored once and the documents it names keep being revised.
- Currency and content are separate checks: a citation can resolve to a document that exists yet no longer carries the cited material after a reissue.
- Renumbering and file relocation break citations silently, without changing any technical content, so the gap is invisible until someone follows the reference.
- A citation to a draft is a latent defect once the released revision lands at a different number.
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).
Frequently asked questions
Why not just bump every citation to the latest revision?
Because a newer revision can change the cited content. A citation has to resolve to a revision that still supports the entry, so some updates need the entry reassessed rather than the number swapped.
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.