Testing Whether a Finished Project Phase Depends on Unfinished Shared Works
Test a project's apparently finished phase against unfinished power, access and control dependencies before treating visual completion as readiness.
How can a team establish whether a finished phase can operate independently of unfinished shared works?
Map the phase's intended functions to the shared infrastructure each requires, then obtain technical evidence that the dependencies are available or that an approved alternative supports the intended operation. Record constraints and unresolved tests. Visual completion, isolated component tests and an overall project percentage do not establish independent operation.
A new community hall looks complete, but its permanent power supply and shared access works are still under construction. The project report calls the hall finished while operations cannot explain how it would function normally. Finance needs a supported readiness assessment. A dependency matrix turns that disagreement into specific questions for the technical and operational owners.
Map functions to shared dependencies
Start with the phase's intended operating purpose and the functions needed to achieve it. Ask the technical owner to list dependencies such as power, water, drainage, access, communications and control systems. For each, record the supplying asset or work package, current status and evidence owner. Include shared dependencies outside the phase's physical boundary.
Distinguish a dependency required for intended operation from a convenience or future enhancement. The asset team should capture the technical conclusion and its basis, not make engineering judgements from a checklist. Ask what would fail or be restricted if the dependency were unavailable. This explanation is more useful than a colour-coded complete flag without context.
Test the basis for independent operation
Collect relevant commissioning results, interface tests and operational acceptance evidence for the dependency chain. Testing a component in isolation may not demonstrate that the connected system works. Record which configuration was tested and whether it matches the intended arrangement. If the final shared supply is unfinished, identify exactly what supports any claimed current operation.
Where a temporary arrangement is proposed, obtain its authorised technical basis, scope, limitations and expected duration. Do not assume temporary means unsuitable or that successful limited use establishes full readiness. Ask the responsible specialists whether the arrangement supports the intended function and what restrictions remain. Keep those conclusions separate from finance's accounting decision.
Resolve and track readiness constraints
Prepare a readiness note showing each unresolved dependency, its operational consequence, required evidence and responsible owner. Finance can evaluate the note under the applicable framework. For GRAP reporters, GRAP 17's availability-for-use assessment concerns intended operating capability; a visually finished phase can still need investigation when essential shared works remain incomplete.
When a dependency changes, update the affected readiness conclusion with new evidence and its date. Preserve the earlier assessment so the record explains why the position changed. Do not close an unresolved interface simply because the main contractor marks the phase complete. Handover should leave operations with a clear list of remaining constraints and who will remove them.
Practical Example
Illustrative example: a hall has finished interiors, but permanent power and the shared access road are incomplete. The dependency review establishes what lighting, equipment and normal access require. A temporary generator has supported one test event, which is recorded with its limits. Technical owners explain whether intended operation is supported, and finance assesses readiness from that evidence rather than the appearance of completion.
Action Checklist
- 1.Define the phase's intended functions with the operational owner.
- 2.Map each essential function to its shared infrastructure and evidence owner.
- 3.Check whether tests covered the connected configuration rather than isolated components.
- 4.Document the authorised basis and limitations of any temporary arrangement.
- 5.Track unresolved constraints and retain dated changes to the readiness conclusion.
Prepare dependency evidence that makes project readiness reviewable through Audit-Ready Asset Management.
