Acceptance evidence gap
Missing acceptance evidence for delivered work and assets
Missing acceptance evidence means the records do not show that delivered work, a component, or an aircraft was formally accepted, so the handover rests on assumption rather than a documented sign-off. It is a problem for lessors, airlines, and MROs at work-package handback, delivery, or transaction close. The check reads the acceptance documents each handover should carry against the work and assets delivered. You receive a list of handovers with no acceptance evidence and the path to recover each.
When this review is needed
- A work package is handed back and the records must show the operator formally accepted it.
- An aircraft or component was delivered and the acceptance document that should close the handover is absent.
- A transaction is closing and the chain of acceptances behind prior deliveries needs confirming.
The problem
The moment a handover becomes the receiving party's responsibility is supposed to leave an acceptance record. In practice the work-package completion or the delivery can be filed while the sign-off that closes it is never raised or never retained. The handover then has no documented point of transfer, and a later dispute has no record to rest on.
What gets reviewed
- Each work-package handback, delivery, and asset acceptance
- The acceptance or handback document that should close each handover
- Conformity and inspection sign-offs supporting acceptance
- The party that accepted and the basis they accepted on
- The chain of acceptances across prior deliveries where a transaction depends on it
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
- Each handover carries an acceptance or handback document closing it
- The acceptance identifies the work or asset accepted and the accepting party
- Conformity and inspection sign-offs supporting acceptance are present
- The acceptance is dated and consistent with the completion it closes
- The chain of acceptances is continuous where a transaction relies on it
Evidence normally required
- Work-package completion and handback records
- Delivery and asset acceptance certificates
- Conformity and inspection sign-offs
- Transaction documents referencing prior acceptances
Common discrepancies
- A completed work package with no acceptance record closing the handback
- A delivery with no acceptance document identifying who accepted it
- An acceptance dated inconsistently with the completion it is meant to close
- A broken chain of acceptances across successive prior deliveries
What is at stake
A handover with no acceptance evidence leaves the transfer of responsibility unsupported, which can reopen who owned a defect or a cost. Reconstructing acceptance after the fact is harder once the parties have moved on, and at a transaction a missing acceptance record weakens the chain the buyer is relying on.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
List the handovers
Identify each work-package handback, delivery, and asset acceptance in the period under review.
Find the closing record
Locate the acceptance or handback document that should close each handover and name the accepting party.
Test consistency
Confirm the acceptance is dated consistently with the completion it closes and is supported by the conformity sign-offs.
Map recovery
For each unsupported handover, set the path to locate the acceptance or substantiate the transfer of responsibility.
What the buyer receives
- A register of handovers with missing or incomplete acceptance evidence
- The supporting evidence held for each unsupported handover
- A recovery path per handover, whether locating the acceptance or substantiating the transfer
Who uses the output
- Quality assurance establishing where responsibility for a handover transferred
- Asset and transaction teams confirming the chain of acceptances behind a deal
- Records teams recovering the acceptance closing each handback
How the work fits into the transaction or program
The review isolates acceptance as the closing record of a handover, so a handback with full completion evidence but no acceptance sign-off is caught distinctly from one missing the work itself. It feeds the handback validation and the discrepancy register.
Jurisdiction-specific considerations
What acceptance must document can differ by authority and contract. Where a handover crosses registries, acceptance evidence is read for whether the receiving authority and party accept the form and basis it was recorded on.
Regulatory limits
The review confirms whether acceptance evidence is present and consistent with the handover it closes. It does not accept work on a party's behalf, issue a certificate, or make an airworthiness determination.
What this review does not cover
- Accepting work or an asset on a party's behalf
- Issuing any certificate of completion or conformity
- Making an airworthiness determination on the handover
Specific to this review
- Acceptance is the documented point where responsibility transfers, so a handover with no acceptance record has no clear owner if a defect later surfaces.
- Completion evidence and acceptance evidence are checked separately, since work can be fully documented as done yet never formally accepted.
- Reconstructing acceptance is hardest after the parties disperse, which makes the handover itself the practical window to capture it.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Is a completed work package the same as an accepted one?
No. Completion shows the work was done. Acceptance shows the receiving party took responsibility for it. A package can be fully documented as complete while the acceptance that closes the handover was never raised, which leaves the transfer unsupported.
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.
Walk through your situation with an engineer who has done this work.