The Project-to-Operations Handover: A Missed-Engineering Checklist

Key takeaways

See our guide to the system that should be live before this handover.

• The capital project commissions on schedule, the project team disbands, and within six months the operations team is fighting issues that the project team understood but never documented. The pattern is so consistent that the project-to-operations handover deserves its own discipline.
• The eight items most often missed at handover are not the obvious ones (drawings, manuals, spares). They are the soft items: who was the OEM engineer who knew this asset, what was the unwritten installation tolerance, which third-party integrator owns the custom code, what tweaks were made on-site that never made it to the design documents.
• The fix is a structured handover checklist applied during the project's last 30 days, before the project team leaves, not after they have moved on. The checklist is short, the discipline of running it is everything.
• The single biggest gain from a working handover is faster first-quarter MTBF. Plants that run a clean handover see materially fewer first-quarter post-commissioning failures than plants that skip it, because the operations team is operating the asset the way the project team intended rather than the way the manual literally describes.

Why the handover gets skipped

The project team's incentive ends at commissioning. The contract was to deliver the asset operational; once it is producing, the project is done. The team rotates to the next project. Documentation that exists in the project files but not in the operations team's hands gets lost in the transition. Knowledge that lived in the project engineer's head leaves the building.

The operations team inherits an asset that works on day one and accumulates issues over the next quarter. Some of those issues are documented in the project files nobody handed over; some are in the head of the OEM engineer nobody met; some are in the third-party integration code nobody knows how to modify. The first major failure forces a reverse-engineering exercise that should have been a 30-minute conversation.

The fix is procedural. A handover checklist that runs in the project's last 30 days catches most of the gaps before they become operational debt. The article on the work order management system covers the data structures the handover output feeds into.

The eight items most often missed

1. The OEM engineer's name and direct line

Not the sales contact, not the support email, the actual engineer who knows this specific asset. When something goes wrong in month four, the operations team needs to reach someone who has worked on this asset, not a generic support queue. The handover should capture this contact and the engineer should be told to expect the call.

2. Unwritten installation tolerances

Every installation has tolerances that were applied in the field but never made it back to the design documents. The asset was levelled to a specific shim configuration; the alignment was set to a tolerance tighter than the standard; the cooling water flow was tuned to a value the manual does not mention.

These tweaks are often the difference between the asset running well and running poorly. The piece on root cause analysis covers how these undocumented tolerances surface in early failures.

3. Third-party integrator ownership

Custom code, configurations, integration scripts, usually written by a third party during commissioning. The operations team needs to know who owns this code, who can modify it, and what the support arrangement looks like. Without this, the first integration issue six months later turns into a multi-week investigation to find out who can even change the code.

4. The list of on-site modifications

What was changed during commissioning that was not in the original design. Wiring changes, pipe routing, control logic adjustments. These almost always exist; they almost never make it back to the as-built drawings unless the handover process explicitly captures them.

5. The startup sequence

Not the documented startup sequence, the actual one the commissioning team used. Most assets have a startup ritual the OEM does not document: which valve gets opened first, how long to wait before energising, what the first reading should be. This ritual is often the difference between a clean startup and a damaged one.

6. The known quirks list

Every asset has quirks the commissioning team knows about. "The third gauge reads 5% high; we calibrated against the master." "The PLC takes 30 seconds longer than the manual says to boot after a power cycle." "The motor draws more than expected on cold start; this is normal." These quirks save the operations team weeks of investigation when they encounter them.

7. The PM schedule the OEM actually recommends vs the one in the manual

Manuals describe generic PM cadences; OEM engineers often recommend tighter or looser cadences for the specific install, the duty cycle, the local conditions. The handover captures the recommendation the OEM engineer made, not just the manual default. The piece on the preventive maintenance schedule covers how this informs the long-term PM design.

8. The first-90-days expected issues

What the commissioning team would not be surprised to see in the first 90 days, even on a successful install. New seals seat in, certain bolts need a re-torque after thermal cycling, sensor drift in the first month is normal. Without this list, every minor issue looks like an installation defect.

The 30-day handover checklist

The structure that catches the eight items:

• Day -30 (30 days before commissioning): Project team and operations team identify the handover lead on each side. The handover lead is the person responsible for the checklist completion, not a committee.
• Day -21: The eight items above (or the plant's version of the list) are assigned to specific project team members for capture.
• Day -14: First draft of the handover pack circulated. Operations team identifies gaps.
• Day -7: Final pack ready. Joint floor walk with project and operations teams covering each item in person.
• Day 0 (commissioning): Handover pack signed off. The project team's incentive to be reachable for follow-up questions is contractualised as a 90-day post-commissioning support period.

The piece on manufacturing KPIs covers the post-commissioning metrics that show whether the handover was successful.

How to measure handover quality

The honest measure is first-quarter MTBF compared to the project's pitched MTBF. A clean handover produces a first-quarter number close to the pitched one. A skipped handover produces a first-quarter number well below pitched, with the gap closing over 6-12 months as the operations team rediscovers what the project team already knew.

Plants that track this metric over multiple capital projects build a feedback loop: project teams that handover well get repeat business; project teams that don't get held to the gap. The discipline propagates over time.

How Fabrico fits

The handover checklist works in any plant with a CMMS.

Where a unified OEE + CMMS platform helps is in two places: the eight handover items become standing fields against the asset (not buried in a project folder), and the first-90-days expected-issues list ties into the OEE event stream so the operations team can distinguish "expected pattern" from "real problem" without having to remember.

Fabrico is built for that workflow. To see what a handover-ready asset record looks like, book a demo .

Frequently asked questions

Who should own the handover process?

The plant's capital projects function, with operations as the receiving party. If the plant does not have a dedicated capital projects function, the plant engineer or the operations director takes the role. Without a single owner, the checklist degrades into "everyone's responsibility."

What if the project is delivered by an EPC contractor?

The handover checklist becomes a contractual deliverable. The contractor should be paid against successful handover, not just commissioning. EPC contracts that pay on commissioning alone consistently produce the worst handover outcomes.

How long should the post-commissioning support period be?

90 days at minimum. The first 90 days reveal most of the issues the handover missed; the project team's availability during that window is what fills the residual gaps.

What if the project team has already left?

That is the unhappy path. The operations team has to reconstruct the eight items themselves, usually through trial and error over the first 6-12 months. The checklist exists to prevent this scenario; once it has happened, the only fix is documenting what they discover so the next handover is better.

What is the most common implementation mistake?

Running the checklist as paperwork rather than as a conversation. The eight items above are best captured in a joint walk-through with project and operations teams together, not as a form the project team fills in alone. The conversation surfaces the quirks; the form captures the checkboxes.