Plan a New Clinic Site’s Program Onboarding

A health system administrator calls you about a clinic opening in six weeks. They want the new site ready for your program on day one, and they expect you, as their key account manager, to make that happen. You cannot promise that. Staffing decisions, IT builds, credentialing, and internal sign offs all sit outside your control. What you can do is bring structure to a conversation that otherwise turns into vague reassurance from you and rising worry from them. A clear plan, even one with open items still to confirm, beats a confident guess every time.

Why This Conversation Goes Wrong

This conversation goes wrong when the administrator treats you like the person who owns their internal timeline. You do not. You supply education, program materials, and a coordination point, but the clinic's staffing, its IT setup, and its local approvals belong to people you may never meet. When you sense pressure to reassure someone who is clearly stretched thin, it is tempting to say yes, we will be ready, just to keep the moment calm.

That answer backfires later. If the site opens and staff have not finished training, or nobody was ever named as the local coordinator, the administrator remembers the promise you made, not the caveat you meant to add. The relationship takes the hit even though the missed piece was never yours to control in the first place.

The opposite mistake is just as common. A manager who lists every dependency and risk without offering a path forward leaves the administrator holding a wall of uncertainty and no next step. Neither extreme actually helps. What the administrator needs is an honest picture of what you can commit to now, what depends on decisions still pending on their side, and what happens next.

How to Prepare Before the Call

Before you get on the call, pull together what you already know about how this account handles new site onboarding. Check whether the health system has opened a location before, and what the standard package looked like for it, things like education modules, access process training, and materials for front desk and clinical staff.

Write down the questions you need answered before you can build a real plan. When does the site open. Who will coordinate locally, since almost nothing moves without a named person on the ground. Which existing program workflows from the parent health system need to carry over to the new location, and which ones are being rebuilt from scratch. What decisions, like staffing levels or clinical roles, are still open on their side.

This is the same discipline that matters when you sit down to discuss a pilot with a health system. In Map Governance Before Discussing a Pilot for a Health System, the advice is to identify who actually decides before you talk about scope. A new site launch has a smaller footprint than a pilot, but the rule holds. Find the coordinator, find the open decisions, and do not fill either gap with your own assumptions.

Bring a short list of dependencies you do not control into the call itself. Naming them upfront, calmly and without apology, sets the tone for an honest planning conversation instead of a negotiation over a promise you cannot keep.

What to Say

The administrator opens with the question you expected. Can you guarantee the site is ready for our program by opening day?

You answer directly, without hiding behind soft qualifiers. I cannot guarantee every piece will be complete by that date, since some of it depends on decisions your team still needs to make. What I can do is map out the approved education and the local owners we need, so we walk into opening day with a real plan instead of a hope. Who is going to coordinate this on your side, and what does the site need to learn first?

The administrator thinks for a moment and says they just brought on a new office manager who will run the location, and the immediate need is a short orientation for front desk and clinical staff on the access process.

You confirm that as the first piece of work. Good, that gives us a starting point. I will put together an orientation outline this week and send it to your new office manager directly. Once staffing is confirmed, we can schedule the actual session. What is the target date for staff to be in place?

The administrator gives you a date two weeks before opening. You now have a real milestone, a named contact, and a task you can start today, instead of a promise resting on things you cannot see.

Mistakes to Avoid

A few habits turn this conversation into a bigger problem later.

1. Naming a firm readiness date before you have named a local coordinator. Without an owner on the clinic side, a date means nothing.
2. Treating your standard onboarding package as automatically right for this site. Confirm which existing workflows the health system wants carried over rather than assuming.
3. Letting silence stand in for a plan. If you do not know an answer, say so and name when you will have it, instead of leaving the administrator to guess.
4. Skipping the follow up meeting because the first call felt productive. A plan with milestones needs a second checkpoint to confirm the dependencies actually closed.
5. Mixing up onboarding with a procurement conversation. If the administrator starts asking about contract terms or purchasing timelines for the new site, that is a different conversation, closer to the one described in Handle a Procurement Request Before an RFP Is Issued. Keep the onboarding plan focused on training and coordination, and route pricing questions to the right process instead of answering them on the fly.

Practice and Score the Conversation

Practice this scenario before you face it live. Set up a roleplay with a six week timeline and deliberately incomplete information about staff roles, then have the counterpart push for a hard commitment. Score yourself, or have a manager score you, on three things. Did you ask for a local coordinator by name. Did you separate what you can start now from what depends on the clinic's own decisions. Did you offer a specific next meeting instead of a vague promise to check back in.

DealSpeak's Pharmaceuticals practice conversations give you a place to run this exact scenario against an AI counterpart that pushes back the way a real administrator would, pressing for a date you cannot honestly give.

After the roleplay, look closely at the plan you produced. It should list milestones with names attached, not just dates floating on their own. It should separate confirmed work from open dependencies in plain language, without hedging every line. And it should give the administrator something to validate before you schedule the first training session, rather than a document they are simply asked to accept.

Keep the Plan Honest

A new site opening is stressful for the administrator, and your honesty about what you actually control is what makes the plan usable. Name the coordinator, separate the confirmed work from the open questions, and set the next checkpoint before you leave the call. That gives everyone a stronger foundation than a promise you might not be able to keep.

You can rehearse this exact conversation in the Pharmaceuticals practice conversations library before it happens for real. When you have this one down, read Map Governance Before Discussing a Pilot for a Health System next.