Shop induction & work scoping
MRO work-package acceptance review
An MRO work-package acceptance review checks the planned work package before a shop visit begins, so the scope inducted into the shop is correct from the outset. It is run by the operator, owner, or manager as the aircraft is inducted, before hands are on the asset. It covers the work order and its task references, the data sources the tasks cite, the incoming configuration the package assumes, and the deferred items meant to be addressed in the visit. You receive an acceptance read on the planned package, a scope-discrepancy list, and the corrections to make before work starts.
When this review is needed
- An aircraft is being inducted into a shop visit and the planned work package needs a check before work begins.
- A work order was built from a planning system and the task references have not been verified against current data.
- Items the operator deferred are meant to be cleared in the visit and need confirming in the package up front.
- A manager wants the incoming scope right before committing the slot, so rework and change orders are avoided later.
The problem
A work package is built ahead of induction from a planning system, and the plan can drift from reality before the aircraft arrives. Task references point at superseded revisions, the assumed incoming configuration does not match the actual asset, and deferred items the operator expected to clear are not in the package. Errors caught after induction turn into change orders, schedule slip, and disputed charges once the shop is already working.
What gets reviewed
- The work order and the task list it inducts into the shop
- Task data references checked against current applicable revisions
- The incoming configuration the package assumes versus the actual asset
- Deferred items intended to be cleared during the visit
- Open AD and modification work the package is meant to cover
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 planned task cites a current, applicable data reference rather than a superseded one
- The package's assumed incoming configuration matches the asset being inducted
- Deferred items meant to be cleared are present in the planned scope
- Open AD and modification work due in the window is included in the package
- The work order scope is internally consistent with the aircraft's due-list status
Evidence normally required
- The planned work order and task list for the visit
- The task data references the package cites
- The aircraft's current configuration and modification status
- The deferred item and open due-list at induction
- The AD and modification work due within the visit window
Common discrepancies
- Tasks built against a superseded data revision
- An assumed incoming configuration that does not match the actual asset
- Deferred items expected in scope but absent from the package
- AD or modification work due in the window left out of the planned order
- A work order that conflicts with the aircraft's own due-list
What is at stake
Accepting a flawed package at induction means paying to discover and correct scope while the slot clock runs. A task built against a superseded revision or a missing deferred item found mid-visit costs more in schedule and change orders than the same finding caught before the aircraft was inducted.
How the work runs
Read the planned order
Take the work order and task list the shop is being asked to induct and the due-list it should reflect.
Verify the references
Check each task's data reference against current applicable revisions and the assumed configuration against the asset.
Confirm carry-over
Confirm deferred items and due AD or modification work are present in the planned scope.
Issue corrections
List the scope discrepancies and the corrections to apply before the shop begins work.
What the buyer receives
- An acceptance read on the planned work package before induction
- A scope-discrepancy list mapped to the work order and due-list
- A correction set to apply before the shop begins work
Who uses the output
- Operators and managers committing the shop slot
- Maintenance planning correcting the package before induction
- Records teams confirming the package against the aircraft due-list
How the work fits into the transaction or program
The review runs before induction, while the package can still be corrected without a change order, so the shop starts on a verified scope. It feeds the planning correction and the operator's induction decision.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
A package planned for a shop under a different authority has to cite data and clear work in a form that authority's approval scope covers. A task acceptable in one authority's system can need a different data basis when the work is performed under another.
Regulatory limits
The review checks that the planned package is correct and complete before work begins. It does not approve the work order, authorize the shop to perform the work, or make an airworthiness determination on the planned scope.
What this review does not cover
- Building or re-planning the work package itself
- Negotiating the shop's commercial terms or slot
- Performing or signing off any of the planned work
Specific to this review
- Acceptance review happens before any hands are on the aircraft, so its leverage is to catch scope errors while they are still a planning fix rather than a change order.
- Task data references drift between planning and induction, so a task can be correctly planned and still point at a superseded revision by the time the aircraft arrives.
- The assumed incoming configuration is checked against the actual asset, because a package planned for the wrong baseline mis-scopes the entire visit.
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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
How is acceptance different from validating the work after the visit?
Acceptance checks the planned package before induction, so errors are corrected before any work is done. Validating after the visit checks what the shop actually delivered. They sit at opposite ends of the shop visit.
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.