The CSU Readiness Checklist: From Construction to Commissioning Without Losing Data

The construction-to-commissioning handoff is where progress data goes to die: the construction tracker says 98%, the commissioning team starts its own workbook at 0%, and readiness becomes a matter of opinion for a month. The fix is a checklist that treats data handover as part of mechanical completion, not an afterthought.

Gate 1 — Mechanical completion, by system

• Punch lists categorized (A/B/C) and loaded as tasks, not PDFs.
• System and subsystem boundaries agreed and reflected in the tracker's structure.
• Every walkdown finding has an owner and a target date.

Gate 2 — Pre-commissioning

• Reinstatement, flushing, and drying tracked at task level with real percents — not “in progress”.
• Blocked items carry the blocker (parts, permits, vendors) so the morning meeting works the right list.
• Weights reviewed: loop checks are not the same size as a solo run.

Gate 3 — Commissioning

• Energization and function-test sequences ordered by system readiness, driven from the rollup, not a whiteboard.
• Field updates land the day they happen — from the plant, not from memory at a desk.
• Every claim of “complete” traceable to who recorded it and when.

Gate 4 — Ready for startup

• The RFSU review reads directly off the tracker: phase rollup, open blocked items, outstanding B-punches.
• Operations sign-off recorded against the same structure the work was tracked in.
• The final export is archived as the handover record — same numbers the team worked to, board-clean.

The thread through all four gates

One structure, carried from construction punch to startup: milestones, activities, and tasks with weighted rollups, statuses that distinguish “not started” from “blocked”, and an audit trail under every number. Whether you run that in Fieldcurve or elsewhere, the checklist only works if the data survives each gate intact.