Why Admissions Performance Is Usually a Composition Problem, Not a Process One
When admissions numbers are inconsistent, the first instinct is almost always to fix the process. Tighten the call flow. Rewrite the script. Run another training on speed-to-lead. Coach the coordinators harder.
Sometimes that's the right call. Process matters, and we've written before about the pieces of it that quietly cost you admits.
But in a lot of the organizations I walk into, the process isn't actually the constraint. The team is. Not the people on it, the way it's built. Roles that blur into each other. One coordinator quietly doing five different jobs. No coverage when leads actually come in. A stage in the pipeline that nobody truly owns. You can hand a team like that the best call flow in the industry and watch it change almost nothing, because the problem was never the script. It was the structure the script was running on.
This is a piece about that: how an admissions team is composed and structured, and why those two questions usually deserve more attention than they get.
Composition and Structure Are Two Different Questions
They get treated as one, and they aren't.
Composition is who's on the team. The roles, the skill sets, the seniority mix, the raw headcount, and the ratios between roles. It's the roster.
Structure is how those people are arranged. Who owns what. Who reports to whom. Whether the team specializes or everyone runs the full cycle. How the work is covered across the hours and days leads actually arrive.
Most centers never deliberately decided either one. The admissions team wasn't designed; it accreted. Someone got hired when census dipped. Someone else absorbed verification because they were good with insurers. A strong coordinator gradually took on the hardest referral relationships because they could handle them. None of it was a decision. It was a series of reasonable reactions that added up to an org chart no one would have drawn on purpose.
That's the thing worth auditing before you touch the process.
The Three Ways Admissions Teams Get Built
Almost every admissions team is some version of one of three shapes. None of them is correct in the abstract. Each fits a different volume, acuity, and referral reality, and the failure mode is usually running one shape long after you've outgrown it.
The Solo Owner. One coordinator takes a lead from first contact all the way through to admit, doing everything in between: the phone call, the clinical fit conversation, the insurance verification, the follow-up, the handoff to the clinical team. Small centers run this way, and at low volume it works beautifully. There are no handoffs to break, the family talks to one person the whole way, and accountability is total.
It also breaks in predictable ways. It doesn't scale, because one person can only hold so many active leads before follow-up slips. It has no bench, so when your best coordinator is out, or leaves, that pipeline goes dark. And it makes performance impossible to diagnose, because when one person owns everything, you can't see which part of the job is where you're losing people.
The Assembly Line. The opposite approach: split the cycle into specialized stages and give each one to a different person or team. First contact and qualification go to one role, clinical fit and assessment to another, verification and UR to another. Everyone gets good at their piece. It's efficient, it scales with volume, and it makes performance legible, because you can see exactly which stage is converting and which isn't.
The cost is the seams. Every handoff is a place a lead can stall or fall out, and in behavioral health the seams are exactly where leads go quiet, waiting on a warm transfer that never happens, sitting in a queue because the next person assumed someone else had it. Specialization without tight handoff discipline just relocates your drop-off from inside the process to between the roles.
The Pod. A middle path: a small, cross-functional group owns a defined slice of the pipeline, say, a set of referral sources or a program line, from inquiry through admit, together. You keep some specialization inside the pod, but the group carries the lead as a unit, so continuity survives and no single stage is orphaned. It's the structure that scales relationship-heavy admissions without turning every handoff into a cliff.
Pods need enough people to populate them and, critically, a single person accountable for each pod's outcomes. Done loosely, a pod is just a group chat where everyone assumes someone else is watching the lead.
The point isn't to pick the trendy one. It's to notice which one you're actually running, whether you chose it, and whether it still fits the volume and complexity you have now rather than the volume you had when the team quietly took its current shape.
Composition: Get the Mix Right, Not Just the Headcount
When census is soft, the reflex is to add a body. But headcount is the least interesting part of composition. The mix matters more.
Not every admissions seat is the same job. Being first to the phone with a family in crisis is a genuinely different skill than sitting across a hard clinical-fit conversation and being willing to say "we're not the right level of care for this." Which is different again from the precision and patience that verification and UR demand. When you write one generic "Admissions Coordinator" job description and expect every hire to do all three well, you're guaranteeing that each person is strong at one and underwater on the others. The work looks understaffed. It's actually miscast.
Seniority needs a spread. A team of all junior coordinators has no one to escalate the hard call to, and no one modeling what good sounds like. A team of all veterans is expensive and quietly bored handling routine inbound. A functioning team has a range, and a deliberate path for the strong junior person to grow into the harder conversations instead of hitting a ceiling and leaving.
Coverage is a composition decision, not a scheduling afterthought. Speed-to-lead is one of the most reliable predictors of conversion, and it's fundamentally a coverage question. If leads arrive on evenings, weekends, and over the lunch hour, but your team is composed and scheduled to cover a nine-to-five, no amount of urgency training closes that gap. The lead that hits at 7 p.m. on a Saturday and waits until Monday didn't fail on process. It failed on staffing structure.
Structure: Ownership and Span of Control
Two structural failures show up again and again, and both look like performance problems until you look closely.
Every stage and every handoff needs exactly one owner. This is the same principle that governs a healthy CRM, and it's not a coincidence. When two people "share" responsibility for first contact, neither owns it, and the lead that slips through belongs to no one. Shared ownership is a polite way of describing no ownership. If you can't name the single person accountable for each stage of your pipeline, that's not a small gap. It's the gap.
Span of control quietly caps your coaching. A frontline admissions manager can genuinely coach somewhere in the range of six to eight people, listen to their calls, review their pipelines, work the hard leads alongside them. Push past that and coaching quality falls off a cliff; the manager stops developing anyone and turns into a dashboard-watcher who reports numbers up and pressure down. If you've got a dozen coordinators reporting to one director with no team lead in between, you don't have a motivation problem. You have a structure that makes real coaching mathematically impossible, and it will read as a performance problem on every individual under it.
There's also the question of where admissions sits relative to BD and marketing. When those functions report into genuinely separate worlds, the marketing-to-admissions and BD-to-admissions handoffs stop being internal handoffs and become border crossings between departments that measure success differently. Structure determines whether those handoffs are a warm pass or a wall.
Why This Matters More in a CRM-Driven Organization
Here's where composition and structure stop being an HR conversation and become an operational one.
Your CRM encodes your org chart whether you meant it to or not. Pipeline stages are owned by roles. Routing rules assume a coverage model. Every dashboard assumes some human owns the number it's reporting. When the team structure underneath is ambiguous, the CRM faithfully inherits that ambiguity, and it shows up as records with no owner, stages that mean different things to different people, and leads sitting untouched because "someone" was supposed to grab them and the system had no cleaner instruction than that.
You can't automate your way around a bad org design. Lead routing has to route to somebody. If your roles are blurry, automation has nowhere clean to send the lead, so it either lands everywhere (and gets worked by no one) or nowhere. The automation isn't broken. It's pointing at a structure that was never defined.
And read the other direction, the CRM is one of the best org-design diagnostics you have. Records piling up without an owner tell you a role is missing or unassigned. Dwell time concentrated at one specific stage tells you a handoff there has no owner. If you know how to read it, the pipeline is quietly drawing you an accurate picture of where your team structure is broken, which is usually a more honest map than the org chart on the wall.
What a Well-Built Admissions Team Actually Looks Like
Strip away the specifics and it comes down to a handful of things being true at once:
- Distinct jobs are staffed by people suited to them, rather than one generic role expected to do everything
- A seniority mix that gives the team somewhere to escalate and somewhere to grow
- Coverage that matches the hours and days leads actually arrive, not the hours the office is open
- A single, named owner for every pipeline stage and every handoff
- Manager spans small enough that coaching is real, with a team-lead layer added before it isn't
- A structure clean enough that the CRM can mirror it without inheriting a mess
None of that is exotic. What makes it hard isn't complexity; it's that it requires stepping back from the daily scramble to admit the next patient and asking whether the team was ever built to do this at the volume you're now asking of it.
The Bottom Line
When admissions underperforms, coaching the people and tightening the process are the visible levers, so they're the ones that get pulled. Sometimes they're enough. But often the real constraint sits upstream of the process entirely: a team composed for a smaller, simpler operation than the one it's now running, arranged in a way that makes good execution difficult no matter how sharp the script is.
Fix the composition and the structure first, and the process improvements you make afterward finally have somewhere solid to stand. Skip that step, and you'll keep rewriting the script for a team that was never built to run it.
Orbital Behavioral Health Partners works with behavioral health operators to build the revenue systems, team structures, and operational clarity that drive consistent admissions performance. Our Revenue Systems Assessment maps where your current setup is breaking down, structure, workflow, CRM, or all three, and produces a clear roadmap to fix it.