Who Is Managing Everything Between the Lease and the Move?

Architects, contractors, brokers, technology teams, furniture vendors and movers may all have defined scopes. The owner still needs someone watching how those scopes come together.

Originally published November 2011. Updated September 2026 to reflect current owner-side project leadership and coordination.

An office relocation can have an excellent architect, contractor, broker, furniture dealer, technology team and mover.

Every one of them can perform exactly as expected.

And the project can still have gaps.

That’s because each party is primarily responsible for its own scope.

The architect designs the space. The contractor builds it. The furniture dealer provides furniture. The technology team handles technology. The mover gets people and equipment from one location to another.

But an owner doesn’t experience those scopes separately.

The owner experiences one project.

Which raises a question I would want answered very early:

“Who is responsible for making sure all of this works together?”

Someone Has to See the Whole Project

An office relocation isn’t just a construction project.

It may begin with business requirements, site selection and lease negotiations. Then come programming, design, budgeting, approvals, procurement, construction, technology, furniture, security, move planning, occupancy and closeout.

Each decision can affect several others.

A furniture layout affects power and data.

Technology requirements affect electrical loads, cooling and pathways.

Security can affect doors, hardware and access controls.

Equipment can affect structure, power and space planning.

The move date depends on much more than whether construction is substantially complete.

Someone needs to see those relationships before they become problems.

Defined Scopes Still Leave Gaps

A common assumption is that if every consultant and vendor has a clearly defined scope, everything must be covered.

Not necessarily.

Clear scopes establish responsibility within each contract.

They don’t automatically establish responsibility between contracts.

Who confirms that the furniture vendor’s information reaches the electrical engineer in time?
Who makes sure the technology team has reviewed the architectural drawings?
Who coordinates equipment that is owner-purchased but contractor-installed?
Who confirms that security requirements are reflected in the door hardware?
Who tracks decisions that affect multiple vendors?

Those responsibilities can be assigned.

The danger is assuming somebody else has them.

Coordination Is More Than Holding Meetings

A project can have plenty of coordination meetings and still be poorly coordinated.

The question isn’t whether everyone attends.

It’s whether information gets to the right party early enough to affect the work.

If a decision is made in a furniture meeting, who determines whether it affects electrical drawings?

If IT changes an equipment requirement, who checks the mechanical implications?

If construction discovers a condition that changes the layout, who tells the mover or furniture vendor?

Coordination means understanding who needs to know what, by when, and what happens next.

The Owner Has Decisions That Nobody Else Can Make

Not every issue can be coordinated away.

Projects eventually reach decisions that belong to the owner.

Is the additional cost justified?
Can the business tolerate a schedule change?
Should the project accept a compromise?
Which operational requirement takes priority?
Is a proposed solution consistent with the original business objective?

Consultants can explain the options.

They shouldn’t quietly make those decisions on the owner’s behalf.

Part of owner-side project leadership is making sure those decisions reach the right person with enough information—and enough time—to make them.

The Budget Needs One View Too

Individual vendors naturally manage their own costs.

The contractor has a construction budget.
The furniture vendor has a furniture number.
Technology may have another budget.
The mover has another.

There may also be security, signage, audiovisual, equipment, consultants, permits, landlord costs and internal expenses.

The owner needs to know the total project exposure, not simply whether each individual contract is behaving.

That means maintaining a consolidated view of commitments, forecasts, allowances, contingencies and pending decisions.

Otherwise, every individual workstream can appear to be under control while the overall project isn’t.

The Schedule Has the Same Problem

A contractor’s schedule is critical.

It is not necessarily the entire project schedule.

Furniture needs to be selected, ordered and delivered.
Technology infrastructure needs to be installed and tested.
Security needs to be commissioned.
Equipment may need relocation or installation.
Employees need communications and move instructions.

The existing location may have lease obligations and restoration requirements.

A certificate of occupancy doesn’t necessarily mean the business is ready to operate.

The owner needs a schedule that connects construction completion to operational readiness.

The Move Is an Operational Event

The physical move may happen over a weekend.

The planning shouldn’t.

Long before move day, the team should know what is moving, what isn’t, where equipment belongs, what needs power or data, which employees are going where, what vendors need access and what has to function before people arrive.

Then there is the old space.
What must be removed?
What belongs to the landlord?
What restoration is required?
When do services terminate?
What equipment is leased?
What records or assets need special handling?

The project isn’t finished simply because everyone made it into the new office.

Closeout Is Part of the Project

The same integration issue continues after occupancy.

Warranties need to reach the people who will use them.
Operations needs training.
Open punch-list items need ownership.
Final documentation needs to be collected.
Maintenance requirements need to be understood.
Outstanding financial commitments need to be closed.

The project team may be preparing to leave just as the operating organization is taking responsibility.

Someone needs to manage that handoff.

Decide Who Owns the Integration

On some projects, the owner has an experienced internal capital-project team that can perform this role.

On others, an owner’s representative or project manager provides it.

The title matters less than the accountability.

What matters is that someone is explicitly responsible for maintaining the owner’s view across the project—not merely managing one professional discipline or contract.

That person should understand the business objective, know where decisions are being made, identify gaps between scopes and keep the owner informed when something requires direction.

Without that role, the owner often becomes the default integrator.

Usually while trying to run the business at the same time.

Ask the Question Early

Before the project becomes complicated, put all the major workstreams on the table.

Design.
Construction.
Furniture.
Technology.
Security.
Equipment.
Move.
Operations.
Closeout.

Then ask:

“Who is responsible for coordinating across these lines?”

If the answer changes depending on which line you’re discussing, that’s worth examining.

The project doesn’t need another layer of management simply for the sake of management.

It needs clear accountability for the places where one party’s responsibility ends and another’s begins.

Leadership takeaway: A collection of well-managed scopes does not automatically create a well-managed project. Assign someone to maintain the owner’s view across design, construction, technology, furniture, move and operations—and make the gaps between those scopes somebody’s responsibility.