Index quality
Testing digital records index quality before the transaction relies on it
Before an acquisition team stakes a transaction on a digital records set, this review measures whether the index behind it actually works. It samples scans against source documents, tests metadata and OCR quality, and checks that every indexed file is searchable, attributed to the right aircraft, and matched to the record it claims to be. The review runs during transaction preparation, ahead of the sale, financing review, or lease event that will exercise the index under pressure. Deliverables are an exception list by record, a map of index entries to source evidence, and a fix plan scoped to the deal calendar.
When this review is needed
- A financing review will search the digital set directly, and unsearchable scans will read as missing records.
- The deal team plans to populate the data room straight from the digital index.
- Records for the target aircraft arrived as bulk scans with vendor-generated metadata nobody has audited.
- An upcoming lease return will be argued from the digital set rather than paper.
The problem
Digital record sets project confidence: thousands of files, tidy folders, a searchable interface. The trouble is that a scan is only evidence if it can be found, read, and tied to the aircraft, and bulk digitization routinely produces files that fail one of the three. The team discovers this when a counterparty's keyword search comes back empty for a document that is, in fact, in the set, filed under a scanner's default name.
What gets reviewed
- Scan quality sampled against source documents for completeness and legibility
- Metadata accuracy: aircraft attribution, dates, document types, and event linkage
- OCR coverage and whether text search actually retrieves the sampled records
- File-naming conventions and their consistency across the set
- The index's coverage of the record types a transaction review will demand first
- Duplicates, orphans, and files indexed to no identifiable record
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 record can be located three ways: by index browse, by metadata filter, and by text search
- Scans reproduce the full source document, including reverse sides, attachments, and stamps
- Metadata aircraft and date fields match what the document itself states
- Record types the deal will hit first, such as AD evidence and LLP releases, are indexed at document level rather than batch level
- No sampled index entry points to a file belonging to a different aircraft or event
Evidence normally required
- Access to the digital records set and its index or platform
- A sample of source documents, paper or trusted digital, for comparison
- The digitization vendor's specification and completion reports, if available
- The transaction's records requirements or the counterparty's review checklist
Common discrepancies
- Batch-level indexing that files an entire work package under one entry, defeating document search
- OCR absent or unusable on older records, leaving text search silently incomplete
- Vendor default file names carried into production, so retrieval depends on one person's memory
- Reverse sides and oversized pages missing from scans of certificates and disk sheets
What is at stake
In a transaction, an unfindable record and a nonexistent record price the same. Counterparties reviewing a weak index either extend the review, demand paper, or write exceptions for everything they cannot resolve, and each of those outcomes costs more than fixing the index would have.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Profile the set
Establish size, structure, record-type coverage, and the indexing approach actually used.
Sample with intent
Test retrieval, legibility, and attribution on the record types the transaction will examine first.
Grade against the deal
Score exceptions by how the counterparty's review would experience them.
Plan the remediation
Sequence fixes to the deal calendar and define what enters the data room meanwhile.
What the buyer receives
- A record-level exception list graded by transaction impact
- An index-to-source map for the record types the review will hit first
- A remediation plan sequenced against the deal calendar
Who uses the output
- The deal team deciding what enters the data room and in what form
- Technical due diligence staff anticipating the counterparty's search behavior
- Records staff executing re-indexing and re-scanning before the review window
How the work fits into the transaction or program
Index verification precedes data-room assembly in a well-sequenced transaction. A verified index feeds the data room clean, shortens the counterparty's review, and keeps the exception discussion on genuine records gaps rather than retrieval failures that only look like gaps.
Jurisdiction-specific considerations
FAA guidance on electronic recordkeeping, including AC 120-78 and the record-content expectations of AC 43-9C, accepts digital records that preserve integrity and availability, and EU 1321/2014 applies the same retention duties regardless of medium. A digital index that cannot reliably retrieve its contents risks failing the availability test under either framework.
Regulatory limits
The review assesses retrievability, legibility, and attribution in the digital set. It does not validate the technical content of the underlying records, issue any airworthiness finding, or approve the records platform against regulatory requirements.
What this review does not cover
- Executing re-scanning or re-indexing, which is scoped after the defect rate is known
- Diligence on the aircraft's technical status itself
- Selection or configuration of records software
Specific to this review
- Counterparties increasingly review by keyword before they review by folder, so OCR failures distort their first impression of the whole set.
- Batch-level indexing is the defect that costs the most review time per instance, because every retrieval becomes a manual page-through.
- Scan defects concentrate in exactly the documents transactions care about: stamped certificates, multi-part forms, and oversized engine paperwork.
- A fix plan started after the data room opens is already public; the same plan run two months earlier is invisible.
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 records platform reports 100 percent OCR coverage. Is that not enough?
Coverage means the OCR process ran, and no more than that. On faded thermal paper or handwritten logbook pages the output can be unusable while still counting as covered. Only retrieval testing, searching for what a reviewer would search for, shows whether the index performs.
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.