How to Prepare a System Turnover Package
Hand a system from construction to operations with the evidence intact.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
A system turnover package (STP) is the compiled documentation that transfers a system from the construction/commissioning team to the owner/operations, demonstrating it was installed and commissioned as designed. A complete STP is what lets qualification leverage commissioning evidence instead of repeating it.
- 1
Define the turnover scope and contents
Define what the package must contain before construction finishes, so the evidence is generated rather than reconstructed. A typical package carries as-built drawings, material and weld certification, instrument calibration certificates, supplier documentation, completed commissioning records, the punch list with its classifications, and the maintenance and spare-part information operations will need. Defining it late guarantees that some of it was never collected.
- 2
Verify completeness against the design
Verify the package against the design rather than against the index. Completeness of a list is not completeness of evidence: the question is whether every system, component and instrument the design specifies is represented, and whether the as-built documentation reflects what was actually installed. Discrepancies between drawing and plant found here are far cheaper than the same discrepancies found at walkdown.
- 3
Confirm quality-critical evidence is present
Confirm that the quality-critical evidence is present and adequate, since this is the material qualification will rely on: calibration certificates traceable to standards, material certificates for product-contact surfaces, and commissioning records of a documentation standard that can be leveraged. Evidence that is merely present but not of leverageable quality means the testing will be repeated, which is a cost decision better discovered now.
- 4
Formally hand over and accept
Hand over formally, with acceptance recorded by the receiving party and any conditions attached to that acceptance stated. An informal handover leaves the system in an ambiguous state where neither party is maintaining it and neither is accountable for its condition — and systems sitting in that gap are where preservation, cleanliness and calibration status quietly lapse before qualification begins.
- 5
Feed into qualification
Feed the package into qualification deliberately: confirm which commissioning evidence is being leveraged and why, and confirm the system is in its intended state with no open critical punch items. Qualification beginning on a system that is still being worked on produces results that describe an intermediate condition, and that is not a defect of the protocol but of the sequence.
- !Incomplete packages that force qualification to re-generate evidence.
- !Open punch-list items handed over untracked.
- !Documentation of the design intent rather than the as-built system.
- !No formal acceptance, leaving the construction/operations boundary ambiguous.
How to Prepare a System Turnover Package: frequently asked questions
Common questions on prepare a system turnover package.
What is a system turnover package?
The compiled documentation that transfers a system from the construction/commissioning team to operations, evidencing that it was installed and commissioned as designed (drawings, specs, commissioning/FAT/SAT records, calibration, certifications, manuals). It marks the handover boundary.
How does it relate to qualification?
A complete, quality-reviewed turnover package lets qualification (IQ/OQ) leverage commissioning evidence under a risk-based approach (ASTM E2500) rather than repeating it — so the same evidence is generated once and reused.
What makes a turnover package inadequate?
Documenting the design intent instead of the as-built system, missing commissioning evidence, untracked open punch-list items, or no formal acceptance. Each forces rework or leaves responsibility for the system ambiguous.