Scan and index quality
Digital records index quality review for an import and export records package
A digital records index quality review asks three questions of every entry in a transition data room: can the document be found through the index, can it be read, and does it demonstrably belong to this aircraft. It runs against the digital index of an import and export records package, cross-checked with export applications, registry files, and the status summaries the scans are supposed to support. Teams commission it before an importing authority or counterparty gets data-room access. The finding set is an exception list of unsearchable, illegible, orphaned, or mismatched entries, ready for the authority-response evidence file.
When this review is needed
- A data room is about to open for an importing authority, buyer, or receiving registry.
- Records were bulk-scanned by a third party and the index was generated rather than verified.
- Two archives were merged during the transition and duplicate or orphaned entries are likely.
- Earlier reviewers reported documents they could not locate even though the index said they existed.
The problem
Bulk scanning produces volume, and volume hides defects. An index generated from file names looks complete while pointing at skewed scans, cut-off stamps, multi-aircraft batch files, and pages whose serial numbers never made it into the metadata. The team only learns which entries fail when an authority reviewer asks for one specific document at a specific moment, and the search that should take seconds takes days.
What gets reviewed
- Index completeness: every source document has an entry and every entry has a document
- Legibility sampling across scan batches, with attention to stamps, signatures, and handwritten fields
- Aircraft linkage: serial number, registration, or part identity verifiable on the scan itself
- Search behavior tested with the queries an authority reviewer would actually run
- Duplicate and orphan detection across merged archives
- Metadata fields checked against the document content they describe
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 stratified sample of index entries resolves to the correct, complete, readable document
- Documents known to exist in the source package are findable through the index by realistic search terms
- Scans carrying compliance significance show legible dates, signatures, and certificate numbers
- No index entry resolves to a batch file where the target aircraft's pages cannot be isolated
- Metadata aircraft identifiers agree with the identifiers visible on the scanned pages
Evidence normally required
- The digital records index and access to the underlying repository
- The source package the index claims to cover, including status summaries and registry files
- Scanning history: who scanned what, when, and under what quality standard
- Any prior reviewer complaints or search failures already logged
Common discrepancies
- Entries whose metadata names one aircraft while the scan shows another
- Release certificates scanned at a resolution where the certifying signature cannot be confirmed
- Documents present in the repository but absent from the index, invisible to any search
- One index entry covering a hundred-page batch scan with no way to isolate the relevant pages
What is at stake
A data room that cannot produce documents on demand converts every authority question into a delay, and repeated misses push reviewers from sampling toward exhaustive checking. In the worst case a document that exists but cannot be located gets treated as missing, and the team pays for a reconstruction it never needed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Profile the repository
Map index structure, scan batches, and metadata conventions before sampling begins.
Sample and search
Test stratified samples for legibility and linkage, and run realistic reviewer queries against the index.
Chase the orphans
Reconcile repository contents against index entries in both directions to expose orphans and duplicates.
Order the fixes
Deliver the exception list and a rescan worklist ranked by compliance significance.
What the buyer receives
- An exception list by index entry: unfindable, unreadable, orphaned, or misattributed
- A scan-batch quality profile showing where defects cluster
- A rescan and re-index worklist ordered by compliance significance
Who uses the output
- The transition lead deciding whether the data room is ready to open
- The scanning or records function assigning rescan work
- Reviewing counterparties and authorities, indirectly, through a data room that answers on demand
How the work fits into the transaction or program
This review runs after scanning and indexing settle but before external access begins. It complements the content-focused source reviews in the import and export workflow: they establish whether the evidence is right, this one establishes whether the evidence can be produced, and both feed the authority-response file.
Jurisdiction-specific considerations
FAA guidance in AC 120-78 addresses electronic recordkeeping and signatures, and reviewers on the EASA side expect continuing-airworthiness records to remain producible under Regulation 1321/2014 regardless of medium. Neither system excuses an operator whose records exist but cannot be retrieved, which is precisely the failure mode this review targets.
Regulatory limits
The review measures findability, legibility, and linkage. It does not validate the technical content of the records, does not rule on whether an electronic recordkeeping system meets any authority's approval requirements, and does not make airworthiness determinations from the scanned material.
What this review does not cover
- Performing the scanning or rescanning work itself
- Substantive review of maintenance content within the documents
- Certifying an electronic records system for regulatory acceptance
Specific to this review
- Index defects cluster by scanning batch, so a modest stratified sample locates most problem areas without opening every file.
- A document that cannot be found in time behaves exactly like a missing document during authority review.
- Batch scans that combine several aircraft are a recurring artifact of fleet exits, and they defeat single-aircraft data rooms.
- Search testing with realistic reviewer queries finds different failures than metadata inspection does; both are needed.
- Legibility problems concentrate in the oldest and most compliance-critical records, because those passed through the most photocopy generations before scanning.
Sources
Federal Aviation Administration. FAA acceptance criteria for electronic recordkeeping systems and electronic signatures.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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.
Frequently asked questions
The scans were done professionally. Why would the index still fail?
Scan quality and index quality are separate risks. A vendor can produce clean images while the index inherits wrong metadata from file names, folder structures, or a prior operator's conventions, and those errors only show up when someone searches.
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.