A finished building and a building you are allowed to operate are two different things — certified by two different authorities, on two different clocks. In regulated real estate you can hold a certificate of occupancy, walk through a complete, code-compliant building, and still sit months away from the approval that lets you move a single resident through the door. The construction schedule says you are done. The regulator has not agreed yet. And the distance between those two facts — not the site, but the gap between the approvals — is where openings are actually won or lost.
Almost every opening team has the same roster: the architect, the general contractor, the consultant, the lender, the operator. And almost every one of them, after the fact, says some version of the same thing — we had everyone we needed, and we still lost months, because no one owned the interface between construction and operations.
It happens because the seam is structurally orphaned. The GC's scope ends at substantial completion. The operator's clock is assumed to start at opening. Everything in between — commissioning into live operations, regulatory licensing, staffing ramp, vendor mobilization, policy and program stand-up, life-safety and systems sign-offs — belongs to everyone and therefore to no one. It isn't anyone's deliverable, so it runs on goodwill and reminders until something slips.
The cost is the same in every asset class
The shape of the failure doesn't care what you're opening. Every month the doors stay closed is a month of carrying cost — financing carry on the build, pre-opening payroll already committed, and revenue you cannot earn yet. The build is complete, but it isn't earning yet — and the carry doesn't pause while the operation waits on its approvals.
In a retirement-home opening it shows up as a licence inspection that won't schedule until specific items are complete. In a multifamily or build-to-rent lease-up it's the sign-off that pushes first occupancy and compresses year-one NOI. In a hotel it's the pre-opening ramp that starts late. Different regulators, same physics: the building exists, but the operation was never governed into existence on a schedule.
What the handoff actually contains
Take the most demanding version — a regulated seniors residence. The critical path runs months before the doors open and spans tracks that rarely sit in one place:
- Regulatory: licence application dependencies, life-safety and technical-systems sign-offs, infection-prevention and food-service programs that must exist before occupancy, not after.
- Operational: staffing recruited and trained to a ramp curve, policies and programs stood up, day-one service readiness across every department.
- Vendor: dozens of contracts mobilized, with the right ones live on day one and none of them quietly auto-renewing at the wrong rate before you've even opened.
- Construction interface: the commissioning items that have to clear in sequence before any of the above can be signed off.
That's well over a thousand discrete tasks, with hard gates between them — points where you simply cannot move people in until a specific thing is true. Miss the sequencing and the opening date moves — the build is done, the carry keeps running, and everyone points at the interface.
Why spreadsheets lose here specifically
The handoff fails because it's scattered across a dozen tools that don't talk to each other: the GC's schedule, the consultant's checklist, the operator's spreadsheets, the lender's conditions, the regulator's requirements. None of them assigns single-owner accountability with a date and a dependency. None of them stops the opening when a gate isn't met. The interface fails precisely because it is nobody's system — and informal coordination is no match for a sequence this dense with consequences.
Govern the handoff as a system
The fix isn't more meetings or a thicker binder. It's treating the handoff as the governed object it always was:
- One critical path that starts at the first decision gate — not at T-6 months, when it's already too late — and runs through to a stabilized operation.
- Every task with a single owner, a due date, and its real dependencies, across construction, regulatory, operational, and vendor tracks at once.
- Kill points that physically stop the opening until the gate clears — so readiness is proven, not assumed.
- One view that shows whether the operation is actually being governed into existence, so the interface stops being the place months quietly disappear.
The building was never the hard part. The hard part is everything that has to be true the day before it opens — and making sure someone owns each of those things, on a date, behind a gate. That is the critical path. It runs straight through the handoff nobody owns, and it is the same path whether you're opening a residence, a tower, or a portfolio.
Solving the critical path.