Digital records quality
Digital records index quality review inside a modification-baseline source file
A digital indexing quality review asks whether the scanned records behind a modification baseline can actually function as evidence. Each indexed file is opened and tested: can it be searched, is it assigned to the right aircraft, does it match the paper source it claims to represent, and does the index carry one entry per record with no orphans or duplicates. Records specialists run it during baseline assembly or before a digital records set changes hands. The configuration manager receives an exception list identifying every scan that cannot carry evidential weight as it stands.
When this review is needed
- A scanning project finished and the team must decide whether the digital set can replace working reliance on paper.
- An inherited records platform arrived from a prior operator with an index nobody on the current team built.
- A baseline validation keeps stalling because reviewers cannot find documents the index says exist.
- A transaction counterparty will receive the records digitally and will judge the asset partly on how the set navigates.
The problem
Bulk scanning projects optimize for throughput, so quality drops exactly where it matters: a page skipped in a feeder, a batch tagged to the wrong tail during a fleet scan, OCR that never ran, filenames that describe the box rather than the record. The index then reports a set that looks complete while individual scans are unreadable, unsearchable, or attached to the wrong aircraft. Reviewers discover this one failed lookup at a time.
What gets reviewed
- Index completeness against the inventory of source records in the baseline package
- One-to-one mapping between index entries and files, surfacing orphans and duplicates
- Aircraft assignment on each scan checked against registration and serial-number markings in the document
- Legibility and text-search capability sampled across record types and scanning batches
- Metadata and naming conventions tested for consistency and retrievability
- Match between each sampled scan and the source record it claims to represent
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 scans opens, reads legibly, and returns text search hits on known content
- Sampled files carry the correct tail and serial-number assignment in both metadata and document content
- No index entry points to a missing file, and no file sits outside the index
- Multi-page source records are complete in their scans, with continuation pages and reverse sides captured
- Scan content agrees with the physical or original digital source for the sampled records
Evidence normally required
- The digital records index and access to the underlying file store
- The scanning project's batch logs or vendor handover documentation, where they exist
- An inventory of the source records feeding the modification baseline
- Access to physical records or originating systems for sample matching
Common discrepancies
- Scans tagged to a sister aircraft during a fleet-wide digitization run
- Image-only PDF files with no text layer, invisible to every search the team relies on
- Continuation sheets and document reverse sides missing from multi-page records
- Orphan files in the store that never received an index entry and surface only by accident
What is at stake
An unreliable index quietly converts a records problem into a schedule problem. Every downstream review runs slower because each retrieval has to be double-checked against paper, and a counterparty who hits a few bad lookups early will stop trusting the digital set entirely and demand the physical records, erasing the investment the scanning project was meant to protect.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory and stratify
Map the index against the source-record inventory and design a sample across record types and scanning batches.
Test the sample
Open, read, search, and trace each sampled scan to its source, logging every failure by defect class.
Resolve orphans and duplicates
Reconcile the file store against the index to expose unindexed files and multiple entries for one record.
Report by batch
Deliver pass rates, the exception list, and ranked corrective actions keyed to scanning batches.
What the buyer receives
- An exception list identifying each scan or index entry that fails a quality test
- A sampling report stating pass rates by record type and scanning batch
- Corrective recommendations ranked by evidential impact, from rescan to re-index
Who uses the output
- Configuration managers relying on the digital set to assemble the modification baseline
- Records leadership deciding whether paper originals can move to deep storage
- Transaction teams preparing a digital data room a counterparty will navigate unassisted
How the work fits into the transaction or program
Indexing quality sits underneath every other source-file review in the baseline package: SB records, STC files, and binder sections are only as usable as the index that retrieves them. Running this check early keeps later reviews from mistaking retrieval failures for missing records, and its batch-level results tell the team where a rescan pays for itself.
Jurisdiction-specific considerations
FAA guidance in AC 120-78 addresses electronic recordkeeping and signatures, and EASA accepts digital records under Regulation (EU) No 1321/2014 where authenticity and legibility are preserved. Neither regime rescues a scan that cannot be read or tied to the aircraft, so the practical bar is the same on both registries: the digital copy must do everything the paper original did.
Regulatory limits
An indexing review assesses whether digital records can carry evidential weight. It grants no approvals, makes no airworthiness determination, and does not certify the records platform or scanning process itself.
What this review does not cover
- Rescanning or re-indexing work, which is quoted separately once the exception list exists
- Evaluation of the records platform's software features or vendor selection
- Verification of the underlying maintenance content of the records themselves
Specific to this review
- Index defects cluster by scanning batch, so a modest stratified sample locates most of the damage without opening every file.
- A scan with no text layer passes every visual spot check and still fails the way records are actually used, through search.
- Wrong-tail assignment is the costliest defect class because it simultaneously creates a gap on one aircraft and false evidence on another.
- Fixing the index is often cheaper than fixing the scans: many failures are metadata errors on images that are otherwise sound.
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
Do you check every scan in the set?
No, and a full census is rarely worth its cost. Defects track the scanning process, so a stratified sample across batches and record types finds the failing populations. Batches that fail the sample get escalated for wider inspection or rescan; batches that pass are documented as tested.
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.