Post-Merger Standardization of Patient Access Across Two Campuses
Northline Health merged with a suburban hospital 10 months ago. Patient access at the 480-bed flagship campus is decentralized, runs 8-hour shifts, and embeds schedulers in clinics with no standard script. The 140-bed suburban campus runs 12-hour shifts, a central scheduling unit, and a documented scripting and quality assurance program. The combined department has 64 full-time equivalents, 11 vacancies, and two agency registrars billed at $68 per hour against a $27 per hour internal rate. Annual turnover is 41% at the flagship and 19% at the suburb. Flagship staff learned about consolidation from a memo and have had no further communication; the union representing flagship registrars, which does not represent the suburban staff, requires 60 days written notice for shift and schedule changes. Outpatient registration wait time averages 24 minutes at the flagship and 9 minutes at the suburb. A single scheduling platform goes live in 120 days. The COO wants one standard operating model, no budget increase, and agency staff eliminated by go-live.
1. How should the leader sequence the first 120 days, and how does the 60-day union notice requirement constrain the plan?
Read the worked answer
The notice requirement is not a formality; it is the plan's spine. Any shift or schedule change must be issued in writing 60 days before it takes effect, which means the operating model must be finalized by roughly day 60 of a 120-day runway if it is to take effect at go-live. Working backward from that is the only defensible sequencing.
Days 1-30, assess and listen. Walk both campuses, review wait-time and turnover data by team and shift, and interview a representative sample of staff including union stewards. Do not announce a model yet; the flagship has already been burned by a memo, and a second premature announcement will confirm staff suspicion.
Days 31-60, co-design and publish. Convene a joint design group with flagship and suburban staff plus a union representative to test the 12-hour shift and central scheduling model against flagship volume and clinic-embedding realities. Finalize the standard model by day 55, issue the 60-day notice by day 60, and hold town halls the same week so staff hear it from the leader, not from a notice.
Days 61-100, build and train. Scripting, quality assurance, and platform training, with the suburban campus serving as peer trainers rather than the flagship being lectured by the acquirer.
Days 101-120, pilot and hypercare. Pilot at one flagship site, then go live with visible leadership presence and daily huddles for two weeks.
2. The COO wants agency staff eliminated by go-live and no budget increase. What do you recommend for the 11 vacancies and the two agency registrars, and how do you justify it financially?
Read the worked answer
The cost case is straightforward. Two agency registrars at 40 hours per week for 52 weeks is 4,160 hours. The premium is $68 minus $27, or $41 per hour, which is about $170,560 a year above internal cost. That premium is the funding source for the COO's no-increase constraint.
Recommendation. Fill vacancies at the flagship first, because that campus carries both the 41% turnover and the 24-minute wait, and unfilled positions there are being covered by overtime and agency. Prioritize candidates who have demonstrated 12-hour shift endurance and central scheduling aptitude, since the model is changing and hiring to the old model wastes training. Convert one agency registrar to an internal position if a qualified hire can be made within the runway; retain the other through go-live as a bridge, with a hard end date written into the contract rather than a vague intention.
Do not promise elimination by go-live if the hiring pipeline cannot support it. Vacancy-driven agency use that gets cut too early produces 40-minute waits and drives more turnover, which costs more than the premium. Instead, commit to a measurable glide path: agency hours capped at a declining monthly number, reported to the COO, with full elimination within 60 days after go-live.
Where the savings go. Redirect roughly half the agency premium into shift differentials and a referral bonus at the flagship, which attacks the 41% turnover that created the vacancies in the first place. That is a budget-neutral move the COO can support because it converts a variable premium into retention.
3. Flagship staff are openly resistant and turnover is 41%. What specifically would you do and say to bring them along without breaching the union relationship?
Read the worked answer
Resistance at 41% turnover is not an attitude problem; it is a rational response to being told nothing for 10 months while a merger happened around them. The intervention has to be information, influence, and a visible stake.
What I would do. First, meet the union steward before any all-staff meeting, share the draft model and the data behind it, and ask what would make the change survivable for their members. Second, run the design group with real decision authority on scheduling, break structure, and training pace, so participation is not decorative. Third, send flagship staff to the suburban campus to observe central scheduling and scripting in operation, and later make them the trainers for the flagship rollout, which converts the acquirer-acquired dynamic into a peer dynamic. Fourth, publish the wait-time and turnover numbers openly, so the case for change is data staff can check rather than a leadership assertion.
What I would say. Acknowledge the memo directly: the communication was poor, and that is on leadership. State the problem in their terms, that a 24-minute wait at flagship against 9 minutes at the suburb means patients are waiting longer and staff are absorbing the pressure. State what is not changing, such as no layoffs from this model and existing seniority recognition. State what is changing, when, and what support exists, including training hours, scripting tools, and a named person to escalate to.
What I would avoid. Do not oversell the suburban model as superior; flagship staff will defend their practice, and the 12-hour shift may genuinely fit clinics poorly. Test it rather than declare it.