Shop archive integrity
Repair-approval record reconciliation for MRO teams after an archive migration
When an MRO migrates its work-order archive or re-indexes historical records, repair dispositions can silently detach from the engineering approvals that justify them. This reconciliation verifies that each repair record in the new archive still connects to its damage report, approved data, and certifying sign-off, and that the repair map references resolve after the move. A records specialist runs it once the new index is in use, before customer substantiation requests or a quality audit test it. The MRO receives an integrity report on the migrated repair records, an orphan register, and re-linking corrections for the archive team.
When this review is needed
- The shop moved to a new records or ERP system and historical work orders came across through a bulk load.
- A scanning project converted the paper archive and the linkage between work orders, dispositions, and engineering approvals was rebuilt by index.
- Legacy records from an acquired facility were folded into the shop's archive under a different numbering scheme.
- Customer requests for repair substantiation are taking longer to answer since the migration, hinting that links are broken.
The problem
A repair record is really a chain: damage found, disposition decided, data approved, work performed, release signed. Archive migrations treat these as separate documents and rebuild the connections by work-order number, so anything filed under a task card, a suffixed order, or a nonconformance reference falls out of the chain. The shop still holds every page, yet can no longer produce a complete substantiation package on demand, and discovers this one awkward customer request at a time.
What gets reviewed
- Sampled repair chains traced end to end in the new archive: damage report through disposition, approved data, and release
- Work orders with suffixes, splits, or nonconformance references tested specifically, since numbering-based loads drop them first
- Engineering approvals held outside the work-order series, such as DER packages, checked for surviving linkage
- Repair map and customer-deliverable references resolved against the new index
- Legacy numbering from any absorbed facility mapped and probed for collisions with the shop's own scheme
- Retention-period coverage confirmed so no era of the archive was left behind in the migration
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- A sampled repair's full chain can be assembled from the new archive without resorting to the legacy system
- Documents indexed by work-order number include those under suffixed and split orders, verified by sampling known cases
- Engineering approval references inside dispositions resolve to the actual approval document, at the correct revision
- No two legacy numbering schemes collide in the new index such that a lookup returns another job's records
- Customer-package copies retained by the shop match the archive's assembled chain for the same repair
Evidence normally required
- Access to the new archive and its index, plus the legacy system or its final export
- The migration or scanning project's mapping documentation
- A listing of historical repairs, dispositions, and engineering approvals for sampling
- Numbering schemes used in any absorbed facility's records
- Recent customer substantiation requests and how they were answered
Common discrepancies
- Nonconformance dispositions separated from the engineering approvals they cite, each surviving but no longer linked
- Suffixed work orders dropped by a load that treated order numbers as plain integers
- Approved-data references resolving to a superseded revision because the migration kept only the latest document version
- Jobs from an acquired shop's old numbering scheme colliding with native work-order numbers and returning the wrong records
What is at stake
An MRO that cannot promptly substantiate past repairs pays for it in audit findings, strained customer relationships, and hours of manual archive spelunking per request. Quality-system auditors treat broken record linkage as a process failure regardless of whether documents exist somewhere, and a customer facing a transaction deadline will escalate a slow substantiation response to shop leadership immediately.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Design the sample
Select repair chains weighted toward suffixed orders, nonconformance routes, absorbed-facility jobs, and old retention eras.
Reassemble each chain
Attempt full substantiation packages from the new archive alone, recording every link that fails.
Diagnose the failures
Trace each broken link to its cause in the load, the indexing, or the numbering mapping.
Re-link and report
Deliver the orphan register, corrections, and an integrity report suitable for auditors and customers.
What the buyer receives
- An archive integrity report stating, from sampled evidence, how reliably repair chains reassemble in the new system
- An orphan register of dispositions, approvals, and reports that lost their connections
- A re-linking correction set and guidance for answering substantiation requests until corrections land
Who uses the output
- Quality leadership answering auditors on records-system integrity
- Records control staff executing the re-linking corrections
- Program managers who commit substantiation response times to customers
How the work fits into the transaction or program
For a shop, repair records are a product deliverable as much as a compliance artifact: customers buy the work and the ability to prove it later. This reconciliation closes the archive migration with evidence that the proof still functions, and its orphan register becomes the punch list that restores response times on substantiation requests.
Jurisdiction-specific considerations
Repair stations under 14 CFR Part 145 and organizations approved under EASA Part-145 both face record-keeping requirements that an archive migration does not suspend, and both regimes' auditors probe whether historical work remains retrievable. Shops holding dual approvals should expect either authority's audit to sample the migrated archive, so the reconciliation samples across both customer populations.
Regulatory limits
The reconciliation examines record linkage and retrievability only. It renders no judgment on the technical adequacy of past repairs, confers no approval on any data or work, and leaves the repair station's regulatory record-keeping obligations exactly where they were.
What this review does not cover
- Re-performing or re-certifying any historical repair work
- Producing new engineering approvals for chains where the approval never existed
- Migration tooling fixes or re-execution of the data load
Specific to this review
- Substantiation requests arrive years after the work, typically triggered by the customer's own transaction, so archive defects stay latent until the least convenient moment.
- Suffixed and split work orders are the canary population: if a migration handled them correctly, the plain-numbered majority almost certainly came through as well.
- Keeping only the latest revision of engineering data corrupts history, because a repair must be read against the revision in force when it was accomplished.
- Auditors distinguish between missing documents and broken linkage, but both produce findings; existence without retrievability fails the test all the same.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
We can still find everything in the old system. Is reconciliation still worth it?
The old system is a fallback with a shelf life: licenses lapse, the hardware ages out, and the people who knew its quirks move on. While it remains available, reconciliation is cheap because failed links can be diagnosed against a living reference. Waiting until the legacy system is gone converts every broken link into a manual archive search with no answer key.
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.