sitebraid.
All insights

MULTI-PHASE CAMPUS DEVELOPMENT / DEVELOPMENT USE CASE

The next phase starts inside someone else’s operating environment.

A campus can have land and funding for expansion but no acceptable way to build it around its first tenant. Protect the next phase before the first one opens.

The owner’s situation

Tenant A is approaching handover. Tenant B will occupy a later phase using shared access and utility infrastructure. Some of the next phase’s connections and construction routes cross the area Tenant A will operate. The build programme assumes those interfaces can be completed later, but the operator has not accepted the required access or interruption conditions. The owner needs an expansion route that can be built without making conflicting commitments to either tenant.

The development context

Uptime Institute’s discussion of modular and phased construction identifies the importance of planning for later commissioning in the original design. Its certification context is not a universal requirement for every campus. We apply the underlying planning concern to owner-side decisions about tenant boundaries, shared assets and expansion readiness.

Our view

The first tenant’s opening is not the end of campus development. It changes the conditions under which every later phase must be delivered. Construction access, system connections, testing and operating obligations need to be considered before the campus becomes occupied. A future plot on a drawing is not proof of an executable future phase.

What we need to establish

We would bring together the campus master plan, tenant demarcations, the relevant operating commitments, shared-system drawings and the proposed construction and commissioning sequence. The appointed technical and operating teams should identify which future works touch live assets or occupied routes. The review must include temporary works, access and test conditions, not just the permanent end-state. Existing tenant agreements and approval conditions need review by the appropriate commercial and legal teams.

The options we would test

Install the necessary enabling interfaces before occupation

Early works can preserve a feasible future connection and construction route.

Before committing Qualified design, the owner’s funding decision and a defined scope that does not create unfinished operating hazards.

Use a separately deliverable expansion route

The later phase can avoid an unacceptable dependency on occupied infrastructure.

Before committing Space, rights, provider arrangements and a comparison of added capital against operating constraints.

Agree a revised operating or phase sequence

The original sequence cannot satisfy both tenant commitments as written.

Before committing Explicit operator and owner acceptance of the revised conditions, with contractual changes where required.

What owners should do

Our proposed execution sequence for this assignment:

  1. Test the first handover against the next build

    Before the initial operating boundary is fixed, ask the appointed teams to demonstrate how the next phase would be constructed, connected and tested. Identify the interfaces that become more difficult or expensive after occupation. Do not assume that access granted during construction remains available afterward.

  2. Separate campus-wide decisions from work procedures

    The owner and tenants must agree the permitted operating conditions and commercial responsibilities. Designers and contractors then develop the detailed technical methods, safety arrangements and test procedures within those boundaries. Sitebraid coordinates closure of the development interfaces; it does not authorize live-system work through a website-level plan.

  3. Resolve the enabling scope while options remain

    Where early infrastructure or corridor protection is justified, define the relevant packages and funding owner. Where an alternative route is better, advance the required design and approvals. Where no route supports the commitments, bring the conflict back before the owner promises the next opening date.

  4. Carry the expansion through controlled acceptance

    Track the agreed access, approvals, readiness evidence and operator decisions alongside the new phase’s programme. Confirm that shared-system and tenant handovers close the assigned scope and identify ongoing responsibilities. Carry the resulting changes into the current campus record rather than leave the next team relying on an old plan.

How we protect the decision

The owner should have a clear list of changes requiring tenant or operator acceptance and a defined route for resolving conflicts. A missed construction milestone does not authorize a change to operating conditions. We would connect delayed external decisions to the campus schedule and commercial choices, while the responsible professionals retain technical and safety authority.

What completion looks like

The result is an agreed expansion route whose critical interfaces are resolved for the appointed stage. Before live works, that means the required permissions, responsibilities and qualified plans are in place. At handover, it means the contracted phase has passed the agreed acceptance process and the shared-campus obligations are updated. The owner should be able to explain how the next phase will work, not only what the current building has completed.

What we would track

  • Future-phase dependencies crossing occupied tenant or shared-system boundaries.
  • Enabling decisions resolved before the first operating handover.
  • Operator decisions and required approvals still controlling expansion readiness.
  • Accepted phase evidence and updated shared-asset responsibilities.

The right time to protect Phase 2 is before Phase 1 changes the rules of access.

Source record

Uptime Institute: modular and phased construction, published 2015

An industry planning reference, not a claim of Tier certification or a certification requirement for Sitebraid clients. The scenario and proposed campus intervention are illustrative.

Our view and proposed execution plan are Sitebraid opinions, not prescribed engineering or a promise of approval. Specialist design and regulated work belong to the appropriately qualified appointed teams. Public context was reviewed September 7, 2026.

Is this holding your campus back?

Tell us what needs to move. We can discuss the development work your team needs.

Email the Sitebraid team