Digital file quality
Digital indexing quality review for the lease-transition records file
Digital records only help a lease transition if a stranger can find, read, and trust them, and this review measures the digital records index against that standard. It samples index entries across the lease-transition file and verifies that each one resolves to a legible scan, that the scan matches the source record it claims to represent, and that metadata ties the file to the right aircraft, date, and document type. Search behavior is tested with the queries an incoming records team would actually run. Exceptions come back keyed to index entries so the digitization team can correct them at the source.
When this review is needed
- A scanning project just finished and nobody has tested whether its output is searchable by anyone who did not build it.
- Counterparty access to the digital room opens soon and the first failed searches will shape their view of the whole file.
- The records of several aircraft were digitized in one batch and cross-attribution between tails is a live risk.
- The index claims full coverage but the physical folder inventory has never been reconciled against it.
The problem
Scanning projects optimize for volume. A repository of ten thousand PDFs with generic filenames is technically digitized and practically unusable, and the failure modes are quiet ones: text layers that failed without warning, multi-page certificates split across files, one aircraft's records attached to another's index after a batch job. None of this is visible to the team that built the index, because they navigate by memory. The counterparty navigates by search, and search is where the defects live.
What gets reviewed
- Index entries sampled across record types and lease periods, each resolved to its scan
- Scan legibility, completeness, and page order compared against source documents
- Metadata accuracy for aircraft identity, document type, dates, and revision
- Search retrieval tested with the queries a receiving records team runs first
- Duplicate, orphaned, and misattributed files inside the repository
- Index coverage reconciled against the transition folder inventory
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 index entry opens a scan of the document it names, at the revision it names
- Text-layer quality supports retrieval of key identifiers such as serial numbers and AD references
- Metadata assigns each file to the correct aircraft with no cross-contamination from other tails
- Multi-page documents are complete and in order, with no truncated task cards or split certificates
- Records present in the working folders appear in the index, and index entries without any source are flagged
Evidence normally required
- The digital records index and access to the underlying repository
- The transition folder inventory or physical file listing for the coverage comparison
- A sample of source documents for scan-fidelity checks
- The naming and metadata conventions the digitization effort claimed to follow
Common discrepancies
- Scans that exist but cannot be found by any reasonable search because the text layer failed silently
- Metadata pointing at the wrong serial number after a batch scan spanning several aircraft
- Certificates split across files, or task cards truncated at the page carrying the signature
- Coverage gaps where whole folder sections were never scanned while the index implies completeness
What is at stake
An index that fails in use pushes the counterparty back to the paper or into a manual page-turn, erasing the digitization investment at the moment it was supposed to pay off. Misattributed scans do worse than missing ones, because they actively mislead the reader. During acceptance, failed searches are recorded as missing records even when the documents exist, and disproving that later takes more effort than the original scan did.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Draw the sample
Select index entries across record types, periods, and scanning batches.
Resolve and compare
Open each sampled entry and check the scan against the source for fidelity and completeness.
Test retrieval
Run the searches a receiving team would run and record what surfaces and what hides.
Report by fix type
Group exceptions so rescans, re-indexing, and metadata corrections can be batched efficiently.
What the buyer receives
- An exception list keyed to index entries and sorted by fix type
- A coverage report comparing the index against the folder inventory
- A sampling summary the transition lead can present as quality evidence
Who uses the output
- Digitization teams correcting entries while the source documents are still at hand
- Transition leads standing behind the digital file during acceptance
- Incoming records teams planning how they will ingest the data
How the work fits into the transaction or program
This review sits at the end of the digitization workstream and ahead of counterparty access. It is deliberately distinct from the content reviews on this file: those test what the records say, this one tests whether the digital medium delivers the records at all. Exceptions route to the scanning team for correction, and the coverage report informs whether physical files still need to travel with the aircraft.
Jurisdiction-specific considerations
FAA guidance in AC 120-78 addresses acceptance of electronic records and signatures, and AC 43-9C describes what maintenance entries must contain, while EASA's framework under Regulation (EU) No 1321/2014 accepts electronic recordkeeping where integrity and accessibility are preserved. Under either system the digital copy is expected to reproduce the source faithfully, which makes scan fidelity a compliance matter rather than a convenience.
Regulatory limits
The review evaluates retrieval, fidelity, and attribution of digital copies. It does not validate the maintenance content inside the documents, makes no finding that the records satisfy retention duties under 14 CFR 91.417 or EASA requirements, and reaches no airworthiness conclusion.
What this review does not cover
- Scanning, rescanning, or performing metadata remediation
- Reviewing the maintenance content inside the documents
- Selecting or configuring records-management software
Specific to this review
- Text-layer failure is invisible to a visual quality pass, which is why an index that looks perfect can still fail its first serial-number search.
- Batch scanning of several aircraft in one project is the classic source of cross-attributed records, and finding one such error justifies widening the sample immediately.
- Page-order and truncation defects cluster in the documents that matter most, because certificates and task cards are the pages handled and stapled most often.
- A sampling summary produced before handover changes the tone of acceptance: search failures become known, owned exceptions instead of discoveries.
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
What sample size makes this review meaningful?
Systematic defects such as a failed text layer or batch misattribution reveal themselves quickly, within a modest sample spread across batches. Isolated misfiles need heavier sampling, which is why the effort concentrates on high-consequence sections such as release certificates and LLP trace, where a single lost document carries real value.
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.