Functional completion and energisation readiness are frequently treated as equivalent milestones. They're not, and conflating them is one of the more consistent patterns in projects that proceed to energisation before verification is complete.
Functional completion is a construction milestone. Equipment installed, cables terminated, panels mounted, busbars bolted. Everything physically in place. It answers one question: is the installation present?
Energisation readiness addresses a different question: has the installation been tested, documented, and found acceptable before voltage is applied? Physical presence is the starting condition for verification — not a substitute for it.
What energisation readiness requires
The verification scope before energisation typically includes: isolation and earthing confirmed to a documented state, temporary earths removed, isolation points verified open. Test evidence for every circuit in the load path — insulation resistance, earth fault loop impedance, conductor continuity, polarity, and high-potential tests where the installation classification requires them. Each test record traceable to the specific circuit, signed by the person who conducted it, pass/fail confirmed against the applicable specification.
Protection settings should be programmed and cross-referenced against design documentation. Where relay tests were conducted, records should show pickup value and operating time — not just that the device operated. Where equipment was substituted during construction, settings need to reflect the installed devices, not the original specification.
On an anonymised data centre pre-energisation review, a contractor's functional completion declaration was followed by a project schedule that indicated energisation the following week. The test pack at that point was approximately 70% complete, with open NCRs on two sections of the primary load path and protection settings not yet verified against the as-installed relay configuration.
Functional completion was accurate as stated. Energisation readiness was not reached until three weeks later, after testing was completed, NCRs were closed, and protection settings were confirmed. The two milestones were distinct by three weeks of work — which is the verification period, not delay.
Documentation completeness at the point of decision
A test pack at 80% completion with the remaining 20% expected "by end of week" does not support an energisation decision. Circuits appearing on the installation schedule but absent from test records haven't been tested — the gap isn't administrative, it's a real absence of verification evidence. The documentation status at the point the energisation decision is made is what matters, not anticipated future completeness.
The test record is the only durable evidence that a circuit was in an acceptable condition at a specific point in time. Verbal confirmation from the commissioning team, however credible, isn't auditable, doesn't transfer to subsequent teams, and doesn't support retrospective queries about what was actually verified. Where records don't exist, the verification claim can't be substantiated.
Open NCRs on the load path
Equipment can reach functional completion while carrying open non-conformance reports indicating failed tests or components outside specification. Functional completion is a statement about installation — it doesn't address whether that installation is correct. An open NCR on a load path item means the item's conformance status is unresolved. That's a different condition from verified-and-found-acceptable.
The consequences of that gap tend to surface under load, not during commissioning. And the remediation options available to a live system are considerably more constrained than those available to a de-energised one.