Delivery and redelivery binder review inside a scanned records archive

When this review is needed

• A paper delivery or redelivery binder has been scanned and the originals are about to move to deep storage or be released.
• A lease return is approaching and the redelivery evidence will be presented from the archive rather than from the shelf.
• An archive migration is consolidating binders scanned by different vendors, in different years, to different standards.
• Spot checks have turned up binder pages that open blank, sit under the wrong tab, or belong to another aircraft.

The problem

A delivery or redelivery binder is assembled once, under transaction pressure, and then trusted for years. Scanning flattens it: tab structure becomes vendor batch folders, stamped certificates become images of uncertain resolution, and the index that made the binder navigable is retyped or exported by people who never saw the closing. The records team ends up presenting a binder it has never actually read in its digital form.

What gets reviewed

• The delivery and redelivery binder index against the file inventory of the scanned archive
• Tab-level structure: whether each indexed section resolves to the right file range
• Image legibility on sampled pages, including stamps, signatures, and dates
• Aircraft attribution: registration, serial number, and binder date on sampled documents
• OCR and metadata quality for the fields the binder index relies on
• Duplicate and orphan files sitting in the binder folders without an index entry

What gets validated

• Every sampled index entry opens a file, and the file content matches the entry's description
• Sampled certificate pages, including FAA Form 8130-3 and EASA Form 1 copies, are legible down to the release signature
• Sampled documents carry the correct registration or serial number for the aircraft the binder claims
• Page counts for multi-page documents agree between the index, the metadata export, and the image set
• Scan dates and batch identifiers reconcile with the binder's chain of custody

Evidence normally required

• The delivery or redelivery binder index in its current digital form
• The full image set for the binder folders, with file paths preserved
• OCR output and metadata exports from the scanning vendor
• Scanning batch logs or transmittal sheets, where they exist
• Access to sampled paper originals if they are still on hand

Common discrepancies

• Index entries that resolve to a placeholder page, a separator sheet, or nothing at all
• Certificates scanned at a resolution that loses the stamp or the signature block
• Files from two aircraft interleaved because their binders went through the same vendor batch
• A binder index copied forward from delivery that no longer matches what redelivery actually added

What is at stake

The first serious test of a scanned binder tends to be a lease event, when a counterparty asks for a specific certificate and the archive produces the wrong page, an illegible stamp, or nothing. By then the paper may be in deep storage or destroyed, and a document that existed at delivery is functionally lost at the moment it carries the most value.

How the work runs

What the buyer receives

• An exception list keyed to binder index entries, each with the failure mode observed
• A sampled legibility and attribution report for the binder's certificate pages
• A corrected index draft or markup the records team can load back into the archive

Who uses the output

• Records control leads deciding whether paper originals can be retired
• Digital records managers scoping rescan and reindex work with the vendor
• Redelivery teams who will present the binder from the archive at lease return

How the work fits into the transaction or program

The binder review is one slice of a wider scanned-archive quality program: the digital indexing review proves the archive can be searched, while this review proves the highest-stakes content, the delivery and redelivery evidence, survived digitization intact. Its exceptions feed the same rescan and reindex queue, and its cleared entries become the binder the next transaction is presented from.

Jurisdiction-specific considerations

14 CFR 91.417 and 91.419 require the records behind a transfer to be kept and to move with the aircraft, and digital copies inherit those duties in full. EASA-managed aircraft carry parallel obligations under Regulation (EU) 1321/2014, where the redelivery file feeds the receiving CAMO's baseline. Neither system relaxes legibility or completeness because a document is now an image, which is precisely what the review tests.

Regulatory limits

The review reports what the scanned binder can and cannot support. It does not issue an airworthiness determination, does not approve the archive or the scanning process, and does not decide whether an authority or counterparty will accept a digital copy in place of paper.

What this review does not cover

• Scanning or rescanning work itself
• Review of records outside the delivery and redelivery binder sections
• Negotiation with a lessor or lessee over redelivery document standards

Specific to this review

• Redelivery binders fail scanning differently from routine records: the highest-value pages are stamped, signed, and often on colored or embossed stock that OCR handles worst.
• A binder index built at delivery is frequently reused at redelivery with additions appended, so index drift concentrates at the end of each tab.
• The safe window to verify a scan is before the paper leaves the building; retrieval from deep storage can take weeks against a redelivery clock.
• Vendor batch naming often becomes the de facto file structure, and it turns meaningless once the vendor relationship ends.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits