How to Request a Single Case Agreement Before PHP Admission

When a prospective client’s plan has no in-network partial hospitalization option within a reasonable distance, a single case agreement is often the only path to reimbursement. Knowing how to request a single case agreement before PHP admission is what separates programs that get paid at a workable rate from programs that admit on good faith and then fight for payment for months. This guide walks operators through the sequence: benefits confirmation, network-gap evidence, clinical justification, and the contract terms worth negotiating, so admissions and billing work from one repeatable process instead of improvising each time.

What a Single Case Agreement Actually Covers

A single case agreement (SCA) is a one-time contract between a payer and an out-of-network provider for one identified member, for a defined level of care, over a defined period. It is not network participation. It does not carry forward to the next admission, and it usually does not cover services outside the scope written into it.

For behavioral health operators, that distinction matters. An SCA negotiated for PHP does not automatically follow the client down to IOP or up to residential. Each step change typically requires its own amendment or a new agreement, and assuming otherwise is a reliable way to generate unpaid days.

The leverage behind most SCAs is network adequacy. When a plan cannot point to an in-network program offering the required level of care within a reasonable travel distance and a clinically appropriate timeframe, the plan has a business reason to negotiate rather than deny. Your job is to document that gap before you ask.

Confirm Benefits Before You Make the Pitch

Every SCA conversation should start with a completed benefits check, not a cold call to a case manager. You need to know whether the plan is fully insured or self-funded, whether behavioral health is carved out to a separate managed care vendor, whether out-of-network benefits exist at all, and how the out-of-network deductible and out-of-pocket structure work for that member. A thorough verification of benefits for behavioral health providers also tells you who actually holds authorization authority, which is frequently not the entity printed on the card.

That last point derails more SCA requests than anything else. An admissions coordinator calls the medical plan, gets routed, leaves a message, and loses two days before learning that a behavioral health vendor owns the decision. Confirm the correct department and the correct submission channel first.

How to Request a Single Case Agreement Before PHP Admission

Understanding how to request a single case agreement before PHP admission comes down to running a tight, evidence-backed sequence rather than a persuasive phone call.

1. Complete the benefits check and identify the decision-maker. Get a name, a direct line or portal path, and a reference number for the inquiry.
2. Document the network gap. Search the plan’s own provider directory for in-network PHP options in the member’s area. Record which programs you contacted, who you spoke with, and the outcome: no availability, waitlist, wrong population, no age match, no co-occurring capability. Directory listings that turn out to be inactive are meaningful evidence.
3. Assemble the clinical justification. A current assessment, presenting symptoms, prior treatment history, risk factors, and a clear statement of why PHP is the appropriate level of care and why a lower level would not be sufficient.
4. Submit the request in writing. Include the proposed start date, expected length of stay, the requested rate, and the codes you intend to bill. Verbal requests leave you nothing to escalate with.
5. Set a follow-up cadence. Assign one owner and a callback schedule. Log every contact with name, reference number, date, and what was committed.

What to Have Ready Before You Call

A single case agreement request stalls more often on missing data than on clinical disagreement. Ask for it by name, and ask for a network gap exception as well — several payers file the same request under that label and will not recognise the first term.

The Four Grounds Payers Actually Accept

Payers rarely approve an SCA on clinical preference alone. The argument has to land on network inadequacy or continuity. Pick the one your facts support and document it.

When the payer gives you a list of in-network alternatives, call every one and record who is not accepting patients or does not actually provide that level of care. That call log is the evidence of network inadequacy, and it is usually what turns a denial around.

Terms Worth Negotiating Before Anyone Signs

Rate is the obvious term, but it is not the only one that determines whether the agreement is profitable. Before signing, get clarity in writing on each of the following.

• Covered services and codes. Which revenue and procedure codes are included, and whether ancillary services such as laboratory work or medication management sit inside or outside the rate.
• Authorized units and dates. The exact date span and number of days or sessions authorized, plus the process for requesting more.
• Concurrent review requirements. Who reviews, how often, and in what format.
• Member cost-share handling. Whether the member is held to in-network cost sharing, and what you are permitted to bill.
• Claims routing. The payer ID, the submission address, and any authorization number required on the claim. SCA claims are often denied simply because they landed in the wrong queue without the reference number attached.
• Term and renewal. What happens at expiration and how an extension is requested.

Ambiguity here becomes a denial later. Ask for the executed agreement in writing and store it somewhere your billing team can actually find it.

When the Request Stalls or Comes Back Denied

Not every SCA request succeeds, and some are simply ignored. If you get no response, escalate to a supervisor and reference your documented outreach log. If the plan declines on the basis that in-network options exist, respond with your specific findings: the programs you contacted and why each was not a viable placement.

If a client is already admitted and the agreement never materialized, the case shifts into utilization review support and, where warranted, formal appeals and audits work. Plans maintain their own internal review levels, and depending on the plan type an external review option may also be available. Because those rights and timeframes vary by plan and by state, check the member’s plan documents and the applicable state regulator’s guidance rather than assuming one standard applies everywhere.

Make It a Standard Operating Procedure

Programs that consistently land workable agreements treat the request as a defined workflow, not a favor. That means a template request letter, a network-gap search checklist, a named owner for follow-up, a shared contact log, and a handoff to billing that includes the executed terms. It also means tracking outcomes: request-to-approval rate, days to decision, and realized rate versus requested rate, so you can see which payers are worth pursuing and which are not.

If your admissions and billing teams are handling these one at a time with no repeatable process, we can help you build one. Call 877-715-7919 or contact us to talk through your current out-of-network workflow.