Government schemes: the volume, the margin and the front door

A unit head in a Tier 2 city once put it to me plainly in a P&L review. “The scheme fills my beds and empties my margin. Tell me which one you want.” He was not being difficult. He had a hospital at modest occupancy, a state scheme and the national scheme sending him patients at package rates that did not cover his cost in half the procedures, and a group leadership that wanted both the occupancy number and the margin number to go up. Nobody had told him how.

Government scheme patients are the third demand pool most private hospital groups run on, after cash and insurance, and the one least discussed in growth meetings. Partly that is because the economics are uncomfortable. Partly it is because the growth function assumes it has nothing to do with this pool: the patients arrive by referral, the rates are fixed, the marketing budget was never meant for them. Both assumptions are wrong, and the second one is expensive.

The scheme patient uses the same front door as everyone else. The same phone number, the same site, the same chatbot, the same reception. If that front door was designed for a cash patient in a metro, it fails the scheme patient in ways that cost admissions the unit wanted and create experiences the brand cannot afford. This is about serving both from one front door, and about being honest with finance about what that volume is worth.

Why a group takes scheme volume at all

Start with the commercial logic, because everything else depends on it. A hospital with empty beds has a marginal cost per admission that is far below its average cost. In a unit at moderate occupancy, a scheme admission at a package rate below average cost can still be contribution-positive, because the building, the equipment and most of the staff are already paid for. The same admission at a unit running near full occupancy displaces a cash or insured patient and is a straightforward loss.

That is the whole argument, and it means scheme volume is a unit-by-unit and speciality-by-speciality decision, not a group policy. It also means the decision changes as the unit fills. A unit that needed scheme volume in its second year needs to manage it down in its fifth, and the growth function should be the one watching for that turn, because it sees the demand data first.

There are non-financial reasons too, and they are real. Licence to operate in a state, relationships with the health department, the reputation of the group in a district where the scheme is how most people access care, and the volumes that let a new speciality build its case mix quickly. I have seen groups underweight these and pay for it later. I have also seen groups use them to justify scheme volume at units where the economics had stopped working. Both are governance failures, and both are avoidable if the numbers are on the table.

How scheme patients actually find a hospital

Almost nothing in the standard digital playbook describes this pool. The scheme patient does not search for a speciality on a search engine and compare doctor profiles. They are referred by a government hospital that cannot do the procedure, sent by a scheme helpline, told by a community health worker, or forwarded a hospital name on a messaging app by a relative whose neighbour was treated there. They often arrive with a scheme card and a referral slip and very little else.

When they do go online, the query is in the regional language, on a phone with limited data, and it is usually the scheme’s name plus the city plus the word for hospital. Some go to the scheme’s own hospital locator, which lists empanelled hospitals by district and speciality, and which, like insurer network lists, is often wrong about your unit. Many call, and the number they call is whatever the referral slip or the messaging forward had on it, which may be a ward extension or a number that stopped working two years ago.

The practical consequences are simple. Your unit’s entry in the scheme locator has to be right. Your map listing needs to work in the regional language and to say, in that language, that the unit is empanelled. And the phone number in circulation in the district needs to reach a person who can answer, in that language, the only two questions the caller has: is my card accepted here, and is my procedure covered. Get those three things right and you have done more for scheme demand than any campaign could.

The contact-centre script for a scheme call

Listen to recordings of scheme calls at a contact centre built for cash and insured patients and you will hear the problem inside a minute. The agent asks which doctor the caller wants. The caller does not know; they were told to come to the hospital. The agent asks about a speciality. The caller describes a symptom in a language the agent speaks imperfectly. The agent offers an appointment slot. The caller asks whether the scheme is accepted, and the agent says they will have to check at the hospital. The caller says thank you and does not come.

The scheme script is different from the cash script and should be written separately. It leads with eligibility: which scheme, which card, which state. It confirms empanelment at the unit the caller can reach, from the same register the website uses. It explains what to bring, in the caller’s language, and it sends that list by message. It does not try to book a specific doctor, because the scheme patient will be seen by whoever the unit’s scheme desk assigns. It captures a callback number that belongs to the patient or a family member and not to the referring clinic.

Language capacity is the constraint here, and it is the item most often cut from the contact-centre budget. A centralised contact centre serving units across four states needs agents in at least four languages beyond English and Hindi, at the hours scheme patients call, which are earlier and later than the office-hours peak. Voice automation helps at the front of the call for the eligibility questions, and I have found it useful for exactly that and not much more; the moment the call needs judgement, a scheme patient needs a person, and a person who speaks their language.

Capacity allocation and who decides it

The scheme patient competes for the same beds, operating-theatre slots and diagnostic capacity as everyone else, and at most units nobody has written down how that competition is decided. In practice it is decided by whoever is loudest that week: a surgeon who wants the scheme cases for volume, a unit head who wants the cash cases for margin, a scheme desk that has a queue and a relationship with the district office to protect.

The growth function should push for the allocation to be explicit. Not a rule that never bends, but a stated share of capacity by unit and speciality that scheme volume is expected to occupy, reviewed quarterly against occupancy, realisation and the cash and insured pipeline. When the cash pipeline is thin, the share goes up. When the unit is filling, it comes down. The scheme desk and the contact centre then know what they can promise, and the surgeon who wants the volume has a number to argue with rather than a person to argue at.

I would not have been able to make this argument without the funnel data by payer. The moment the executive committee could see enquiries, appointments and admissions split across cash, insured and scheme for every unit, alongside realisation, the allocation conversation became a numbers conversation. Before that it was a conversation about fairness and philosophy, and those never end.

One brand across very different economics

The most dangerous thing a hospital can do with scheme volume is let it become visible as a lower tier of care. A separate entrance, a separate waiting area with worse chairs, a scheme ward that staff refer to differently, a desk where scheme patients queue while others are attended. Patients see it. Staff absorb it. Reviews describe it, and cash patients read those reviews and draw their own conclusions about what the hospital is really like.

The group’s brand is a single promise about how people are treated there. It cannot carry an asterisk for payer. That does not mean the same room category or the same amenities; it means the same courtesy, the same clarity of information and the same clinical seriousness. The scheme patient who is told plainly what is covered and what is not, given a date, and treated with respect at the desk will tell their district about it. So will the one who is not.

There is a subtler risk in the other direction. A unit that becomes known locally as “the scheme hospital” finds that cash and insured patients begin to route around it, on the assumption that it is crowded or that its doctors are second-choice. I have watched a unit’s cash enquiries decline over eighteen months for no reason the campaigns could explain, and the reason was reputation drift as scheme volume grew. Watching the payer mix of enquiries, not just admissions, is how you catch that early.

The dashboard the CFO should see

Scheme volume gets discussed badly in finance reviews because it arrives as a single line: scheme revenue, scheme receivables, scheme days outstanding. That line is almost always uncomfortable, because scheme payments are slow and the deductions are opaque, and the conversation ends with someone proposing to cap scheme admissions everywhere.

The growth function can improve that conversation by bringing the same view it brings for every other demand pool: enquiries, conversion and admissions by unit and speciality, with contribution rather than revenue, and with occupancy shown alongside. At a unit with beds to fill, scheme contribution is positive and the case for keeping the front door open to it is clear. At a unit that is full, the same view shows what each scheme admission is displacing. That is the level at which the decision should be taken, and growth is the function that can present it that way.

What I would do differently

I under-invested in language for too long. The business case for regional-language contact-centre capacity looked weak when measured against cash conversion, which is what the contact centre was budgeted on. Measured against scheme admissions at Tier 2 units that needed occupancy, it was obviously worth it, and I did not make that case until a unit head made it for me.

I also let the scheme locator listings sit unaudited because they were “government” and felt outside my remit. They are listings. They are wrong in the same ways every other listing is wrong, and correcting them is the same tedious, valuable work.

If you’re starting this next quarter

• Weeks one to two: get the payer split of enquiries, appointments and admissions by unit, with scheme separated from insurance. Add occupancy and contribution per admission by payer, from finance, even if rough.
• Weeks two to four: audit every unit’s entry in the scheme hospital locators and the regional-language map listings. Fix them. Find out which phone number is actually circulating in the district and make sure it works.
• Weeks four to eight: write the scheme call script, separately from the cash script. Staff the languages the units need at the hours the calls come. Tag scheme on every CRM record.
• Weeks eight to twelve: take the payer view by unit to the executive committee and get a capacity share for scheme volume agreed per unit, with a quarterly review.
• Ongoing: watch the payer mix of enquiries, not only admissions, at any unit where scheme share is rising. That is where reputation drift shows first.

The scheme patient will come whether you plan for them or not. Planning is the only part you get to choose.

Questions people ask