The twelve months before a hospital opens: a checklist

A hospital gets built by people who measure in cubic metres and kilowatts. The civil contractor has a bar chart. The biomedical planner has a bar chart. The NABH consultant has a gap list with dates against every line. Digital usually has one line in somebody’s capex deck and a meeting about nine weeks before opening where a project director asks, with visible irritation, why the website is not live.

I have sat in that meeting more than once. The honest answer is always the same: nobody sequenced it. Digital readiness for a new unit is not a task, it is roughly forty tasks, and a dozen of them depend on things marketing does not control — a licence number, a bank account in the unit’s name, a signed consultant contract, an empanelment letter from a payer. Start them in the wrong order and you spend the last month doing emergency work that should have been routine.

What follows is the sequence I use now, for a single new unit opening in twelve months in a micro-market where the group has no presence. Compress it if you must. Compress the back end, not the front.

What digital actually owns in a launch

Be precise about scope early, in writing, with the project director. Digital owns five things: the unit’s identity in search and maps, the unit’s pages on the group website, the doctor content, the enquiry-to-appointment path including the contact centre and CRM, and the launch communication itself. Digital does not own signage, does not own the opening event, and does not own whether the cath lab is commissioned on time.

That last distinction matters because launch dates move. In my experience a hospital opening date slips at least once, usually by four to eight weeks, and often the reason is a fire NOC or a lift inspection. Every digital asset you build must survive a date change without rework. That means no campaign creative with a date burned into it until the date is confirmed twice, and no countdown anywhere.

Month twelve to month nine: entity and listings groundwork

This is the least glamorous work and the only work that cannot be bought back later. A new unit has to exist as an entity in the places patients look, and those places verify slowly.

• Decide the naming convention for the unit and freeze it. Group name plus locality is usually right. Whatever you choose, it must match the board resolution, the clinical establishment registration, the GST registration, the signage and the bank account. Mismatches here cause verification failures nine months later that take weeks to unpick.
• Open the map listing as soon as you have a site and a board outside it. You cannot verify a listing that has no physical presence, but you can create it early, claim it, and let it age. Listings that have existed longer behave better.
• Get the phone number allocated now, not at month two. The contact centre number you publish on day one should be the number that has been in the listing for months.
• Register the unit with the aggregators and directories that matter in that city. In most Indian metros two or three doctor aggregators and one or two insurance-linked directories carry real volume. Each has its own onboarding queue.
• Start the regional language work. Transliteration of the unit name, the locality, and the specialty terms. Do it once, centrally, and make every downstream asset use the same strings.

The failure mode at this stage is thinking the listing is a five-minute job for an intern. It is not. It is the single asset that determines whether a person standing two kilometres away can find you in the first week.

Month nine to month six: the website and the unit pages

A new unit does not need a new website. It needs to be a first-class citizen of the existing one. If your group site treats units as an afterthought — a tab, a dropdown, a PDF of the address — fix that architecture before you add a unit to it, because you will add more.

What the unit needs by month six:

• A unit page with the address, the map embed, the directions from the two nearest landmarks, parking, visiting hours, emergency entrance, and the single contact number.
• Specialty pages scoped to that unit. Not the group’s generic cardiology page. A page that says what cardiology at this unit actually is: the cath lab, the ICU beds, the named consultants once you have them, the hours.
• An honest facilities list. If the MRI is phase two, the page does not say MRI. I have seen a unit lose a referring physician permanently over one line on a webpage that promised a service the hospital did not yet have.
• The enquiry form, wired to the CRM, tested end to end with a real phone picking up a real call.

Build these pages with the content half-empty and visible only internally. Month six is when you discover that nobody can tell you how many ICU beds the unit will have, and you want to discover that in month six rather than month one.

Month six to month four: doctor content before the doctors

Clinical recruitment almost never finishes when the plan says it will. The senior consultants sign late, sometimes in the final four weeks, and they arrive with a notice period and an existing practice they are winding down. Meanwhile doctor pages are the highest-intent content a hospital has. Patients search names.

So build the machinery before you have the people. Define the doctor page template and the collection process: photograph specification, qualification string, registration number, years of experience, areas of focus, languages spoken, OPD timings, and one short paragraph in the doctor’s own register. Decide who approves the clinical claims — in a group this should be a medical services person, not marketing. Build the intake form and the approval workflow.

Then, as each contract is signed, you have a two-day path from signature to a live page. Not a three-week path. The difference shows up directly in the first month’s OPD numbers, because a consultant whose page is live and whose listing is attached to the unit starts receiving enquiries before he has physically moved.

One thing I got wrong early: I let the photography wait. Do not. Book a photographer for a half-day every fortnight in the final quarter and shoot whoever has joined. Inconsistent doctor photographs across a group look exactly as cheap as they are, and retrofitting them is a year-long argument.

Month four to month two: CRM and contact centre readiness

This is the part that gets skipped and the part that determines whether the launch spend converts to footfall.

The new unit has to exist in the CRM as a routable destination before the first rupee of media goes out. That means the unit, its specialties, its consultants, its OPD slots, and its enquiry sources are all configured, and a lead tagged to that unit reaches a human who knows the unit exists.

• Train the contact centre on the new unit four weeks before opening, not on opening day. Agents need the address in the words a patient will use, the landmark, the autorickshaw instruction, the list of services that are live and the list that are not.
• Write the script for the question you will be asked most in the first month: “are you open?” and “do you have my insurance?” Get both answers agreed with the payer team in writing.
• Decide what happens to an enquiry for a service the unit does not yet offer. Transfer to the nearest sister unit is the obvious answer and it requires a pre-agreed handshake, otherwise agents will simply say no and you will never see the lead again.
• Test the whole path in the regional language. An agent handling a Telugu or Marathi caller with an English-only screen is a lost enquiry.

Run a soft dial-in week. Publish the number quietly, run a small paid campaign into a small catchment, and let real enquiries hit the live system while the stakes are low. You will find three or four breakages. You want to find them then.

Month two to month one: empanelment communication

Empanelment timelines are not in your control and they are the single most common source of launch embarrassment. Insurers, TPAs, CGHS, ECHS, state schemes and corporate panels each have their own cycle, and several will not process an application until the clinical establishment licence is issued — which may be weeks before opening.

What you can control is how you talk about it. Three rules. Publish a payer list only when each name on it has a signed letter. Give the contact centre a dated view of what is in process, so the answer is “cashless with that insurer is expected within this quarter, reimbursement works from day one” rather than a shrug. And brief the front office and insurance desk with the same list on the same day — the most damaging version of this problem is a patient who was told yes on the phone and no at the counter.

Corporate empanelment runs on a separate track and deserves its own sequence: HR contacts in the catchment’s large employers, a health check package, and an onsite camp calendar. Start that conversation at month three. It does not convert quickly, but it converts steadily, and it is the cheapest demand a new unit will ever get.

The last three weeks

Freeze. No new build. The last three weeks are for verification and rehearsal: map listing live and verified with correct hours, number ringing to a trained agent, unit page accurate against the actual commissioned services, doctor pages live for everyone who has joined, forms tested from a mobile phone on mobile data, and a single named person who can change a webpage within the hour on opening day.

Appoint that person explicitly. On opening day something will be wrong — the hours, a department that is not ready, a doctor who did not join — and the gap between noticing and fixing should be minutes.

What must be live on day one, and what can wait

Live on day one, without exception: the verified map listing with hours and photographs, the unit page with accurate services, the emergency number, doctor pages for every consultant who is physically present, the enquiry path end to end, and the reimbursement and cashless position as it actually stands.

Can wait, and should: the blog, the video library, the patient testimonial programme, the awards page, the detailed treatment cost pages, the health check e-commerce flow, the chatbot, and any app integration. I have watched teams burn the final fortnight on a chatbot while the map listing showed the wrong closing time. The chatbot can ship in month four. The closing time cannot.

The thing that looks like it can wait but cannot is review response. From day one you will get reviews, some of them from people who came on the first morning and found a queue. Somebody has to reply within twenty-four hours, in the reviewer’s language, with a name and a number. Set that up before you open.

If you’re starting this next quarter

1. Get the unit’s naming convention, registration name and phone number frozen and documented. One page, signed by the project director.
2. Create and claim the map listing this month, even with a hoarding as the only physical proof.
3. Audit whether your group website can carry a new unit properly. If it cannot, that is a platform project, not a launch task, and you need to start it now.
4. Build the doctor onboarding workflow and the approval chain before a single contract is signed.
5. Put the new unit into the CRM and run a soft dial-in week at least four weeks out.
6. Agree the empanelment communication rules in writing with the payer team and the front office together.
7. Name the person who can edit the website on opening day.

A launch does not fail because the campaign was weak. It fails because a patient who wanted to come could not find the gate, reach a human, or get a straight answer about her insurance.

Questions people ask