The Certificate of Occupancy lands on the wall and the phones go quiet. The GC demobilizes within a week. The OPM closes out the project file. Vendor invoices get paid, and the names in your group chat start disappearing one by one.
Somewhere in that quiet week, the building changes hands — from the team that built it to the team that has to run patients through it — and almost nobody sees the handoff happen.
That seam is where the first 90 days gets hard. Your clinical director is running her first real patient flow through a space she's only walked through three times. There's an HVAC quirk nobody flagged. The supply room is laid out for a workflow that changed two months ago. Warranty contacts live in a SharePoint folder she can't access.
And when a light switch stops working in week two, nobody's sure whether to call the GC, the electrician, the landlord, or the facilities vendor you haven't hired yet.
The first 90 days after CO isn't a victory lap. It's a stabilization phase — a period where the building is still learning how to behave like a clinic, and somebody still has to be driving.
Handoff Is the Most Fragile Moment in the Project
The project team and the clinical team are optimizing for different finish lines.
The project team's finish line is closeout: punch list signed off, lien waivers collected, final pay application processed, warranties delivered. From their side, the job is done and done well.
The clinical team's finish line is months away. It's the first week where patient flow runs end-to-end without someone having to improvise. It's the month where your MA stops asking where things are because she knows. It's the point at which the building stops being a project and starts being infrastructure.
Nobody owns the gap between those two finish lines. That gap is your 90 days.
What Breaks in the First 30 Days
The most expensive version of this gap is the warranty question, and it's the one founders and operating teams ask me about for years after a project ends.
The question sounds simple: when does the warranty end and tenant responsibility begin?
The honest answer is that it depends on which system, which contract, and who registered what — and if you don't have that documented in one place by Day 30, you're going to sort it out under pressure when something fails.
Here's the pattern. Founders assume the one-year GC warranty starts at CO. It often starts earlier, at substantial completion, which can be weeks before CO. That's a small window, but it matters when a failure shows up in month 11.
Then there are sub-warranties. The electrician's work may carry a different completion date than the GC's base warranty, and the same goes for mechanical, plumbing, roofing, and specialty trades. Each trade can have its own start date, its own duration, and its own registration requirements.
The roof warranty sits with the manufacturer. HVAC equipment carries separate manufacturer coverage tied to commissioning. Medical gas systems have their own certification trail. Landlord base-building responsibilities blur against tenant improvements, and if the lease language is imprecise, you'll spend weeks arguing about which side owns a failed rooftop unit.
Clarify all of this with your OPM before they disengage. If they can't produce one document with every warranty, every sub-warranty, and every registration, you don't have a closeout — you have a pile of invoices.
The warranty gap is the headline failure, but it's not alone.
HVAC balancing that's "complete" on paper dumps cold air on the check-in desk. Access control gets programmed for the GC's schedule, not clinical shift patterns. Medical gas certifications are signed off but nobody ties them to the licensing inspection calendar.
O&M binders arrive as PDFs nobody opens. Punch items closed by the GC get reopened by staff in week two because a touch-up paint job didn't hold, or a door sweep was reinstalled wrong after a final cleaning.
Each of these is a dependency the project team considered done and the clinical team considered unstarted. Warranty is just the most expensive version of the same disease.
Project-Team Done vs. Operator Done
Project-Team Done
CO issued. Punch list closed. Final lien waivers collected. Warranties delivered as documents. Final pay application approved.
Operator Done
Full patient flow runs without friction. Staff know who to call when a system fails. Building systems behave predictably under clinical load. Warranty claims can be filed without confusion. The team stops talking about the building and starts talking about the patients.
The gap between these two definitions is the 90 days nobody budgets for.
The project team's definition is contractual. The operator's is operational. One is measurable in documents, the other is measurable in how the clinic feels at 9 AM on a Tuesday in week six.
The Stabilization System: Three Workstreams That Stay Live Through Day 90
The first clinic teaches you that stabilization doesn't happen by default. If nobody owns it, the building runs the clinic instead of the other way around.
The founders who stabilize well treat the first 90 days as three parallel workstreams, each with a named owner, a documented artifact, and a cadence that doesn't drift.
1. Warranty and Building Systems Orchestration
Somebody has to own the building after the GC leaves. Not "facilities" in the abstract — a named owner with the warranty matrix, vendor contacts, and escalation authority.
The artifact is a single document: every system, its warranty start date, its end date, the vendor contact, the required registrations, and the escalation path when something fails. Delivered in week one, not month six. Reviewed weekly through Day 30, monthly through Day 90.
If you're staffing this in-house, it sits with your facilities lead. If you don't have one yet — most first clinics don't — this is where a fractional real estate advisor continues the work the OPM started.
2. Workflow Friction Mapping
Your clinical director owns this. The project PM translates between what she sees and what the building can adjust.
The artifact is a running Friction Map captured at Day 15, Day 30, Day 60, and Day 90, with each item tagged as a building fix, a workflow fix, or a training fix — because those three categories get solved by three different people, and mixing them is why nothing gets resolved.
A $200 power drop, a rehung door, a relocated workstation: these cost hundreds now and save thousands in throughput drag and staff frustration over the year.
Staff frustration compounds faster than any other variable in a new clinic. If your team doesn't feel heard in the first 30 days, you will feel it in retention by month six.
3. Continuous Improvement and Feedback to Site #2
This one is yours, as the founder. Nobody else has the incentive to capture it.
Every lesson about what worked and what didn't — in site selection, design, GC selection, inspector management, vendor coordination — is data you need when you plan the next location. If you reconstruct it from memory six months later, you'll lose half of it and romanticize the rest.
This is the workstream I've run on every project I've been involved in. As a fractional VP of real estate, I generally stay with my clients for 90 to 180 days past go-live to sort through exactly this — the warranty matrix, the friction map, the lessons document — or I'm already working with them on the next site and we fold the learnings directly into Site #2's planning.
The founders who do this well don't build a clinic. They build a system that builds clinics.
Keep the Project Team Reachable Through Day 90
The instinct after CO is to demobilize quickly. It feels like capital discipline. It isn't.
A rushed disengagement costs more than a deliberate 90-day wind-down, because the failures that surface in weeks two through twelve are the ones only the project team can answer quickly. Who installed that valve. Why that circuit is on that panel. What the original spec said before the value-engineering call in month four.
Budget for a 90-day stabilization phase the same way you budget for construction. Separate line item. Named owner. Weekly cadence. Exit criteria that are operational, not contractual.
This is the same principle I wrote about in Collaboration Isn't Comfort — intentional overlap is the accelerator, not the bug.
The Bottom Line
The question at Day 90 isn't whether you opened. You opened. The question is whether the building is behaving the way you designed it to, under real clinical load, with the staff you hired, and the patients you're actually seeing.
If the answer is yes, you haven't finished a project. You've started a platform. Every decision you made about handoff on Site #1 — the warranty matrix, the friction map, the lessons document, the named owners — becomes the template for how Site #2 stabilizes faster.
That compounding is how first clinics turn into second clinics without breaking the model.
Activation is ongoing system, not a moment. Your job, 90 days in, is to still be driving.
Planning Your First Clinic — or Stabilizing One That Just Opened?
The first 90 days after CO determine how fast your second clinic gets built. If you want a partner who stays through stabilization — not one who disappears at closeout — let's talk.
We'll walk through:
- Your warranty matrix and handoff documentation
- Friction mapping across the clinical team
- Lessons capture for Site #2 planning
- A 90-day stabilization cadence with named owners
