The Schedule Says January 31. That Is Not Your Opening Date.
A construction schedule is the general contractor's document. It sequences the GC's trades, tracks the GC's scope, and reports the GC's progress. Inspections and utility milestones are usually on it, but as the GC's plan for them, not as commitments from the inspector or the utility. And unless your GC understands your operations and is working in lockstep with you, nothing on it describes your side: load-in, licensing readiness, staff in the building. On a first PACE center, the distance between that document and your actual go-live is the difference between July and January.
Last week I overheard a PACE leader talking through her center's construction timeline. The plan: Certificate of Occupancy at the end of January, load-in the first two weeks of February, State Readiness Review after that, July go-live. She had the schedule in front of her. Rough-in, hydro test, life safety, punch, substantial completion. Line after line of construction terms, and none of them answered the most important question her organization has: will we be enrolling participants in July.
She was asking the right question of the wrong document. The GC's schedule cannot tell you when you will open, because most of what determines your opening date is not on it.
What does the construction schedule show you?
The contractor's scope, sequenced. Demolition, framing, rough-in, inspections, finishes, punch, with the milestone the contract cares about near the bottom: substantial completion, or CofO. Inspections are on it. Permanent power is probably on it. That is what makes the document convincing. It looks complete.
Look at whose dates those are. The inspection bar is when the GC intends to call for inspection, not how the last three inspections went. The power bar is when the GC needs SCE to energize, not a date SCE committed to. And your scope, load-in, licensing prep, staff training in the space, shows up only if your GC understands your operation and is building the schedule in lockstep with you. That is rare, and it is not a knock on the GC. It is not their job.
The document can be accurate and still give you the information you need. Which lines can slip without moving your opening, and which cannot. Which bars depend on someone the GC does not control, and what that party actually committed to. What has to happen after the last bar ends and before you can operate. The schedule, as delivered, answers none of that.
What does the schedule hide?
Three things, and they compound.
The critical path. Out of forty or sixty line items, a handful set the end date. Everything else has float and can slip without moving anything downstream. The GC knows which lines are critical. A standard schedule export rarely marks them, so a two-week slip on signage and a two-week slip on the electrical service look identical on the page. One is nothing. The other moves your opening.
The dependencies nobody on the schedule owns. Utility energization. Fire marshal scheduling. The building inspector's corrections. The licensing agency's calendar. These show up as bars because the GC needs them to happen, dated to when the GC needs them. They are not commitments from the party that controls them. "Permanent power, Jan 12" is the GC's need, not SCE's promise.
Everything after the last bar. CofO means the building is done. It does not mean the building is a PACE center. IT and low-voltage, furniture, medical equipment, AV, kitchen equipment, signage, supplies, and staff learning the layout all still have to happen. None of it is the GC's scope. None of it is on the schedule. All of it stands between the milestone and your first participant.
The schedule is one of three timelines
Construction (the GC's), external agencies and utilities (their calendars), and tenant-responsible work (yours). Your opening date is set by the slowest of the three and by how well they overlap. A schedule that shows only the first will always read as more finished than the project is.
Why is two weeks between CofO and SRR really zero weeks?
The plan in the room
CofO January 31. Load-in February 1 through 14. Then SRR. Then July.
The problem is the DHCS sequence. In my experience on first PACE centers, DHCS requires a copy of the final CofO and a full virtual walkthrough of the center before they will book flights for the onsite SRR. The virtual walkthrough is effectively a virtual SRR. They look at everything. So the state's clock does not start until the CofO is issued and the building is furnished, equipped, and ready to be walked on camera. Then DHCS schedules the onsite on their calendar, not yours.
Read that against the plan. If CofO lands January 31 and load-in starts February 1, the earliest the virtual walkthrough can happen is mid-February, in a building that just got its furniture. Then you wait for DHCS to schedule. A February SRR was never two weeks away. It was two weeks of load-in, a virtual review, DHCS's scheduling lag, and an onsite, all stacked behind a CofO date that SCE and the inspector still have to cooperate with.
And the consequence of missing is not a few weeks. If the SRR slips past the window for a July go-live, the next available go-live is January 1, 2028. Six months of a built, leased, staffed center with no participants and no revenue. The only way your GC knows the impact is if they've done PACE before or it's drilled into them from the time you send out an RFP.
Load in before CofO. As early as you and your GC can stand it.
Even if you trust your contractor's dates, plan your load-in before CofO, overlapping the punch list, in areas the GC has turned over. It is hectic. Your vendors are wheeling in furniture while the GC is finishing paint. It is also the single biggest lever you have, for four reasons.
If CofO comes late, your building is already effectively done and you are waiting only on final corrections and the document. Your contractor is still onsite, so when the exam room diagnostic equipment needs a laborer to help mount it, you are not chasing someone to send one back. Your team gets weeks in the actual layout instead of days. And you can run SRR dry-runs in the real space before DHCS is on the call.
Two stories from my time working in PACE.
Downtown Los Angeles: the red button
The inaugural center had a schedule that kept pushing. The elevator kept getting delayed. Inspectors kept coming back with minor corrections on finals. Every push moved our load-in. We had planned a sequenced load-in, IT, then furniture, then equipment, then AV, then supplies, over three weeks. We ran out of room to push and hit our red button schedule: all of it, concurrently, in seven days, so the SRR could be scheduled before we would have been forced to move it. It was pandemonium. We got it done. I do not recommend planning around this approach.
Compton: the inspector wanted the furniture
The second center had the opposite problem, and it taught me something. We hit final inspections in November for a July go-live. The building inspector told us he would not sign off on the CofO until all the furniture was installed. He wanted to assess ADA clearances with the furniture in place and check anything we planned to hard-wire rather than plug in. We had planned a December install, so we had time. If we had planned furniture for after CofO, the CofO would have been waiting on the furniture. This varies by jurisdiction. Most inspectors will let you install furniture and equipment before CofO. Some will not sign off without it.
Know everything CofO requires before you get there
Business license. Landlord sign-off, if you're leasing. Furniture in place, if your inspector wants it. Every one of these is a document or a signature that can sit on someone's desk for a week while your DHCS clock waits to start.
What should you ask on the weekly OAC call?
Whoever is managing construction on the partner side, ask them to add you to the weekly Owner, Architect, Contractor call. Most of it is listening. But when you have a question, ask it, and do not accept a wishy-washy answer. I've been doing this for ten years and I still have no shame about asking the GC to explain something to me like I'm five.
The questions I ask to understand project risk:
What are the major risks right now, and how are they tracking against the schedule? Then dig in on what they are doing to mitigate each one. If the answer is a garbled paragraph, ask again.
What is the percent likelihood you hit the CofO date on the schedule? What are the known risks to that date? What are the likely risks that come up as the project progresses, and what are you doing about them now?
How have the recent periodic inspections gone? Full approvals, partial approvals, or rejections and rework? This tells you how well the GC manages inspections and whether you should expect a difficult inspector at final.
Which bars depend on someone you do not control, and what date did that party commit to? Utility, fire marshal, health department, long-lead equipment. Ask for the committed date, not the scheduled date, and the name of the person who committed to it.
When can I start bringing in IT, furniture, and equipment, and in which rooms? This is the question that overlaps your timeline with theirs. If the answer is "after CofO," you have just added weeks to your opening and taken away your best hedge.
Whose job is it to connect the three timelines?
On the project I was listening to, nobody's. The partner organization runs construction and forwards the GC's schedule. The PACE organization runs licensing and staffing and waits for the schedule to tell them when. SCE talks to whoever calls, and nobody is calling weekly. Each party is doing its own work competently. The gaps between them belong to no one.
I've watched this on projects run by very good people. The failure is not effort. It is three parties each holding one timeline and assuming someone else is holding the overlaps.
What leadership was receiving
- A forwarded GC schedule, updated monthly
- Percent complete by line item
- A CofO date
- No flag on which lines are critical
- No status on PG&E, inspections, DHCS, or load-in
What leadership should receive, weekly
- The critical path, named: the five to eight lines that set the CofO date
- Every external dependency with the outside party's committed date and a contact name
- Utility status: application, design, crew scheduled, energization date
- Inspection results from the last two weeks: approved, partial, rejected
- DHCS status: CofO submitted, virtual walkthrough scheduled, passed, onsite booked
- Load-in plan by week, with the GC turnover dates required to start it
- Best-estimate go-live date, and what moved it since last week
The second list is not more information. It is the information. Someone has to own producing it, and they have to sit on the owner's side of the table.
How do you know when a green schedule is lying?
A schedule can be all green and the project can be behind. What I look for:
Percent complete moves, but finish dates don't. A line that went from 40% to 85% over two months with the same finish date is being updated, not re-forecast. The number moved because the month ended, not because someone re-planned the work.
External dependencies have dates but no names. No SCE work order, no engineer, no last-call date. That date came from the GC's need.
Float is disappearing without anyone saying so. When the schedule is reissued and the non-critical lines have lost their slack but the end date hasn't moved, the project has absorbed slippage silently. The next slip goes straight to CofO.
The milestone at the bottom has never moved. Real projects move. A CofO date that has held for eight months while lines shift underneath it is a date the GC is protecting contractually, not forecasting.
Control the controllables
Utilities and inspectors are two things you cannot fully control. Read: impossible. What you can control is whether your building is loaded, your team is trained, and your DHCS paperwork is staged the day the CofO is signed, so the state's clock starts the same week and not a month later.
What lives on the GC's schedule is not going to change unless you force the issue. You need to weave your operations milestones within construction critical path. External dependencies with committed dates and names. Tenant-responsible work backed into from the go-live date, with the turnover dates you need from the GC to start it.
On the project I was listening to, that page would show a January 31 CofO with two uncontrollables in front of it, a load-in planned to start the day after, a DHCS clock that can't start until both are done, and a July go-live that becomes January 2028 if any of it slips. Read that way, January 31 stops looking like the end of the project and starts looking like the beginning of the part nobody planned.
Whoever holds that page is running your opening. If no one holds it, no one is.
Key takeaways
- The GC's schedule tracks the GC's scope. Your go-live depends on two other timelines it does not contain.
- For a first PACE center, DHCS requires the final CofO and a virtual walkthrough before scheduling the onsite SRR. Two weeks between CofO and SRR is no time.
- Missing the SRR window for a July go-live means January 1, 2028. Six months of a built center with no participants.
- Load in before CofO, overlapping punch, in turned-over areas. It is your biggest hedge against inspector and utility slippage.
- Get on the weekly OAC call. Ask for the critical path, the CofO likelihood, recent inspection results, and committed dates from every outside party.
- Someone on the owner's side has to hold all three timelines weekly. If that role is unassigned, it is unfilled.
Frequently asked questions
Why can't I rely on the GC's schedule to plan my opening?
Because it covers only the contractor's scope. Utility energization, inspections, licensing reviews, and your own IT, furniture, equipment, and staff onboarding sit outside it. Retained CRE ensures regulatory and operational timelines are included so the final goal is not construction complete, it's a site that can see patients.
What does DHCS require before scheduling a PACE State Readiness Review onsite?
In my experience on first PACE centers, DHCS asks for a copy of the final Certificate of Occupancy and conducts a full virtual walkthrough of the center before booking the onsite visit. The virtual walkthrough functions as a virtual SRR. Plan for the building to be furnished, equipped, and staffed before it happens.
Should I load in furniture and equipment before the Certificate of Occupancy?
In most jurisdictions, yes, and as early as you and your contractor are comfortable. Some inspectors will not sign the CofO until furniture is installed so they can check ADA clearances and hard-wired items. Loading in early also puts your team in the space for training and SRR dry-runs while the GC is still onsite to help with equipment installs. You must work with your contractor to communicate with the AHJ to understand their expectations, and plan accordingly.
What should I ask on the weekly OAC call?
The current major risks and how each is being mitigated, the percent likelihood of hitting the CofO date, results of recent periodic inspections, and the committed date and contact for every dependency the GC does not control. Retained CRE sits in on these calls for operators as a fractional real estate lead and translates the answers into a weekly go-live view for leadership.
Getting a schedule and not information?
That is the gap I fill: one weekly view across construction, agencies, and your own load-in, with a go-live date you can defend.
Schedule a Conversation