How to Start a PHP Program Without Costly First-Year Errors

A PHP program that opens licensed but unsigned with payers will run payroll against an empty census. That's the first-year error we see most. You still have rent, a medical director, and nursing coverage while claims can't go out.

Owners treat the certificate of occupancy as the start date. Payers do not. We wrote this as a how-to for investors and operators who want a real sequence, not a brochure, and who will see quickly where an experienced consultant compresses the calendar.

The underwriting conversation belongs before the lease. Capital should pressure-test license timing, contract lead time, and the staffing model that keeps you solvent through a slow census ramp.

What Capital Partners Should Underwrite Before You Open a PHP Program

Capital partners should underwrite the cash gap between opening day and clean reimbursement, because a php program at ASAM Level 2.5 can treat patients for months before commercial and government payers actually fund the work. Build-out is the easy line. Credentialing, medical necessity standards, and denial management are the ones that break a first-year model. You can see a lease. You can't see a stalled CAQH file.

State boards and health plans don't share your construction schedule. Licensure packets, a medical director agreement, and clinical policies have to match how ASAM defines partial hospitalization as a structured daytime level of care. Those artifacts come before enrollment. They also have to hold up if a plan audits you in month four. Owners who treat compliance as a binder learn that after the money is already out the door.

Underwrite coverage, not a day-one roster. PHP days run long. Turnover, PTO, and a census that climbs in uneven steps are capital problems. So is the person who will work denials when claims start bouncing. Payers won't fund a day because you opened. They fund documented medical necessity at that level of care, and if your notes can't defend why the patient still needs PHP rather than a lower intensity, you treat for free. If your pro forma assumes full census and clean cash in the first quarter, the pro forma is a story.

Referral flow is not a purchase order. Hospitals and outpatient clinicians send people to programs they already trust. Square footage doesn't create that trust.

Pacific Viking Consulting sits with investors and operators who want those underwriting questions asked before the lease is signed. You can launch without us. You shouldn't launch on untested assumptions about licensure, contracting, and cash conversion. We'd rather you find the holes on paper.

The License-to-Contract Sequence That Sets Your Open Date

Your open date is set by the last license, Medicare or Medicaid enrollment, or commercial contract you still need before you can legally treat and submit a clean claim, not by the day the contractor hands you the keys. A PHP program at ASAM Level 2.5 that opens on hope rather than on that sequence burns cash while chairs stay empty. The order isn't optional.

Licensure of the operating entity comes first. Most states won't survey a concept. They survey policies, a medical director, a physical plant, and a staffing plan that matches the intensity of care you advertised to investors. File early. Incomplete packets reset the clock.

Occupancy and life-safety approvals can run beside the license only when zoning already allows the use. If they don't, your architect isn't your bottleneck. Your land-use counsel is.

Payer work starts after you have a license number a contractor will accept. Medicaid and Medicare enrollment packets are slow even when they are complete. Commercial networks ask for the same artifacts plus a rate conversation. Treat contracting as compliance with a negotiation layer, not as a brochure drop.

Accreditation sits on the path only if a state or a target payer made it a condition of participation. If your model assumed ASAM alignment and a survey before first admit, that survey owns part of the open date. If accreditation is a year-two promise, keep it off the launch Gantt so you don't hold census for a plaque.

The first-year error we see is hiring, marketing a month, and drawing rent before anyone owns the sequence on a calendar. Capital already underwrote the build. It won't underwrite idle burn. We map that license-to-contract chain with you so the date you publish is a date you can keep. That is the work Pacific Viking Consulting does with owners who want a start-up that actually opens.

Facility, Staffing, and Clinical Design Choices Owners Get Wrong

Owners get facility, staffing, and clinical design wrong when they sequence those decisions after the lease is signed. A PHP program lives or dies on whether the space, the roster, and the daily clinical product were designed as one system. ASAM Level 2.5 expects 20 or more structured hours a week. Sign a lease first and you'll inherit room counts that cannot support the group sizes your license and payers will expect.

Facility errors start with hope-based census. You take more square footage than you can staff in year one, then carry rent while groups sit half empty. The inverse is worse. Undersized group rooms can't meet the structured hours a partial hospitalization level of care requires. Check local zoning and occupancy rules against the populations you will treat before you lock a site. Privacy, medication storage, and a quiet space for assessments aren't optional finishes.

Staffing errors follow the same optimism. Owners hire a charismatic therapist first and leave the medical director, nursing coverage, and utilization-review function as afterthoughts. Payers don't pay on charisma. They pay when a licensed team can document medical necessity every day. Build the minimum clinical complement that matches your intended census, then hire to that grid. Cross-coverage plans matter more than job titles on a slide.

Clinical design is where first-year revenue quietly leaks. A schedule that looks full on paper can still fail ASAM expectations for intensity if group hours, medical oversight, and documentation don't hold together as a single day of care, or it can fail your state's hour and documentation rules. Mixing populations without a written rationale creates both clinical risk and denial risk. Templates that don't force medical-necessity language will cost you in retrospective review.

You can map this yourself. Many owners shouldn't. We work with investors and operators who want the facility, the staffing grid, and the clinical day designed together before capital is sunk. That is the work of Pacific Viking Consulting. That's how you avoid paying twice for the same mistake.

Where First-Time Operators Lose Months and Why They Hire Us

First-time operators lose months when they treat a php program as a facility project instead of a sequenced operating system, then discover that licensing, Medicare and commercial contracting, and clinical workflow cannot be finished in parallel without rework. Owners and investors often assume the building, the staff roster, and the policy binder can move on separate tracks. They cannot. A delayed medical director file on CAQH, an incomplete utilization-review process, or a floor plan that fails surveyor circulation rules forces the rest of the calendar to stop. That is the pattern Pacific Viking Consulting sees when leadership tries to self-assemble a startup without an operator who has already run the sequence.

The stall is rarely one dramatic failure. It is a chain of small, expensive pauses. A lease amendment sits idle because parking or egress was never mapped to program hours. Job postings stall when the staffing model was written before the census target was honest. Then a policy revision lands because the clinical design assumed a level of care the state will not recognize in that zip code. Each pause looks reasonable in isolation. Together they consume the first year you planned to spend filling beds and proving unit economics to your board.

Investors feel this as burn without revenue through the first 90 days. Executive teams feel it as meetings that re-decide last month’s work. Families waiting for a program never see the delay, but they absorb the cost when opening slips and referral relationships cool. A php program that launches late does not simply start later. It starts with a thinner referral book and a staff that has already lived through one reset.

Pacific Viking Consulting exists for that exact gap. We do not replace your ownership. We compress the sequence so you do not learn the order of operations on your own dime. You still make the capital calls. We keep the calendar honest, flag the design choices that will fail survey or contracting, and keep clinical, facility, and staffing decisions on one track. If you are past the point of another internal work session, the next conversation is with Pacific Viking Consulting. Contact Us

Frequently Asked Questions About Starting a PHP Program

How long does it take to start a PHP program?

It takes longer than a build-out schedule because licensing, payer credentialing, and clinical hiring move on separate clocks. You can finish a space and still wait on a state license or a commercial contract. First-time operators treat those tracks as sequential when they are not. We sequence them so you are not paying rent on an empty census. State rules differ. Medicare and Medicaid enrollment can sit in a queue you cannot rush, and that lag is where pretty timelines die.

Do I need a consultant to start a PHP program?

You need one if you have never taken a PHP from concept through first paid claim. A consultant does not replace your CEO or your medical director. We keep you off the regulatory and contracting landmines that eat the first year. Investors who have built other businesses still miss how a licensed level of care actually enrolls. That gap is expensive. If you already know the path, you will not need us.

What standards apply to a PHP program?

Payers and surveyors expect your PHP program to operate as a defined level of care with documented medical necessity, typically aligned to ASAM criteria. Get the documentation wrong and claims bounce. Your utilization review process has to match what an auditor will later request. Pretty policies on a shelf do not count. We build the operating version, not the binder version.

How much capital does a PHP program need before the first claim?

Working capital has to cover payroll and overhead through credentialing lag, and that lag is where first-year operators run dry. We will not invent a number for you. Build-out, staffing ratios, and cash runway depend on your state, your census target, and whether you lease or buy. Underfunding the first 90 days of operations is a common way new programs miss payroll. Talk to us before you lock a pro forma.

What should an investor diligence before funding a PHP program?

Diligence the path from occupancy to first paid claim, not the renderings. Ask whether the operator has a written sequence for license, payer enrollment, and clinical staffing, and whether that sequence accounts for credentialing lag. Pretty decks hide empty pipelines. Boards that want a real launch, not a concept, pressure-test those gaps. We do that work with owners who would rather find the holes now.