Power date slipping in multi-phase campuses
Recognize the early warning signs before the campus commitments collide.
OUR APPROACH
Make the campus work as one system.
Connect the evidence. Resolve the tradeoff. Carry the chosen route through.
Begin with commitments, not an activity list
We would establish the tenant requirements, phase dates, reserved infrastructure and assumptions behind the campus plan. Distinguish what is physically available from what is contractually committed or still contingent. The first question is which conflict controls the next viable outcome, not which report should be written next.
Build one record of the dependencies
Connect provider correspondence, land rights, design requirements, approval conditions and delivery packages to the relevant tenant and phase. Identify the source, responsible party and condition for each material claim. A proposed allocation is not confirmed capacity; a planned route is not an acquired right. That distinction should survive every revision.
Give the owner a decision with consequences
Compare viable alternatives against capacity, timing, upfront spend, future flexibility and operating exposure. For example, advancing shared infrastructure may protect an opening date but bring expenditure forward before the next tenant is committed. Rephasing may protect capital but require a revised commercial commitment. State the consequence rather than bury it in a risk register.
Translate the choice into work
After the owner selects a route, assign the actions, authority, specialist support and evidence required to close each dependency. Connect the sequence to procurement releases and phase gates. The campus recovery capability shows how we apply this when the original plan no longer holds together.
Protect occupied phases
When work touches a live campus, the responsible operating and technical teams must establish permitted access, isolation, testing and change windows. We connect those requirements to the development sequence; we do not authorize technical procedures on their behalf. The live-campus expansion use case explains why that interface should be designed before mobilization.
Close the result and update the campus
At handback, reconcile what was delivered with the accepted capacity, access rights, operating boundaries and remaining obligations. Update the next phase’s baseline. An early intervention should make later decisions easier, not leave another set of assumptions for the owner to reconcile. See campus readiness for the handover focus.