Recruiter capacity planning physician recruiting: req load math + calculator

Last updated: August 31, 2026

Ben Argeband, Founder & CEO of Heartbeat.ai — a math-first approach to setting req loads that recruiters can actually sustain.

Physician recruiting capacity breaks down in two places: reach (gatekeepers, clinic hours, private practice owners, wrong numbers) and admin drag (ATS updates, scheduling, duplicate cleanup, contact refresh). If you plan headcount around “reqs per recruiter” as a flat number, you’ll overload the team the first time connect rates dip or admin work spikes.

This playbook walks through a staffing model built on your own numbers: outreach attempts per placement, connect rate, time per attempt, and admin hours. The output is a safe active req cap per recruiter and a staffing estimate you can defend in a planning meeting.

Who this is for

Recruiting leaders planning headcount and setting realistic req loads for physician roles — in-house, agency, or hybrid — who need a defensible answer to:

• How many active reqs can one recruiter carry without missing follow-ups?
• How many recruiters do we need for next month’s req load?
• Should we hire, automate, or fix contact data first?

Quick answer

Calculate weekly attempt capacity, divide by outreach attempts per placement, then cap active reqs by the required attempts per req per week to protect speed-to-submittal.

Heartbeat’s Q1 2026 planning ranges put outreach attempts per placement around 100–200, with connect rates near 10% (roughly 10 connected calls per 100 dials) — treat these as starting assumptions to replace with your own logged data, not fixed benchmarks.

Compliance and safety

This method is for legitimate recruiting outreach only. Respect candidate privacy, opt-out requests, and local data laws. This is not medical advice or legal counsel.

• Inputs: admin hours, time per attempt, connect rate, attempts per placement, attempts per active req per week.
• Outputs: placements per recruiter per week, and a safe cap for active reqs per recruiter.
• Fast diagnosis: if connect rate drops, req capacity drops even if recruiters work the same hours.
• Fix order: reachability and suppression first, then automation and ATS enrichment, then headcount.
• Start a free search and preview data to see how much wasted dialing you can remove before hiring.

The throughput model: inputs, throughput, staffing

Capacity planning in physician recruiting is a throughput problem with constraints, not a headcount guess. Work through three layers:

• Inputs: time, admin load, reachability, and conversion assumptions.
• Throughput: how many quality outreach attempts a recruiter can execute per week while keeping the ATS usable.
• Staffing: recruiters needed, or req load per recruiter, to hit submittal and placement targets.

Automation increases capacity. Better contact data increases the share of attempts that turn into real conversations. Neither replaces the other.

Step-by-step method

Step 1: Define an outreach attempt

An outreach attempt is one discrete outbound touch to a specific physician or decision-maker, through a single channel — call, email, or text — with a logged outcome: connected, voicemail, bounced, replied, wrong number, and so on. If it isn’t logged with an outcome, it doesn’t count for capacity planning.

Step 2: Define capacity in weekly attempt capacity, not req count

Capacity is the number of quality outreach attempts a recruiter can execute per week at an acceptable admin burden, while keeping pipeline hygiene intact — notes, stages, next steps.

Start with time budgeting:

• Total weekly hours (e.g., 40)
• Admin hours (intakes, scheduling, ATS updates, reporting)
• Net outreach hours = total weekly hours minus admin hours

Convert time to attempts:

• Time per attempt (minutes): dialing, voicemail, logging, and immediate follow-up if your process requires it.
• Weekly attempt capacity = (net outreach hours × 60) ÷ time per attempt

Be careful here: if you force time per attempt down without improving data quality or workflow, you inflate the attempt count while reducing meaningful conversations and submittals.

Step 3: Anchor on your own attempts-per-placement, then revisit monthly

You need one conversion anchor: outreach attempts per placement. Use your historical data if you have it. If you don’t, start with a planning range and tighten it after 30–60 days of clean logging. Define “placement” for your team and keep it consistent — accepted offer for perm roles, start date for locums, for example.

Segment this by specialty and setting. A hospital-employed role and a private practice owner role behave differently, and blending them muddies the number.

Step 4: Track connect rate

Two recruiters can dial the same volume and get different outcomes if one is calling better numbers at better times. Connect rate = connected calls ÷ total dials, reported as connected calls per 100 dials. Use it as your reachability signal for call-heavy workflows; when connect rate drops, effective capacity drops even though nothing else changed. For a deeper look at how contact data quality moves this number, see how to measure contact data ROI in recruiting ops.

Step 5: Convert attempt capacity into placement capacity

Weekly placements per recruiter = weekly attempt capacity ÷ outreach attempts per placement. This is the cleanest way to discuss capacity without arguing over req counts.

Step 6: Convert placement capacity into a safe active req cap

Req load should be based on active reqs — reqs that require weekly outbound activity — not on reqs a recruiter simply owns. Set a minimum activity standard per active req (attempts per active req per week), using intensity tiers to standardize without arguing over exact counts:

• Low intensity: maintenance mode, keeping warm outreach and follow-ups moving.
• Medium intensity: steady build, needing new candidates weekly with consistent follow-up windows.
• High intensity: urgent fill, tight SLAs, more same-week touches and scheduling coordination.

Safe active req cap per recruiter = weekly attempt capacity ÷ attempts per active req per week. This is the number most leaders actually need for staffing and req assignment.

Step 7: Build the workflow around call windows and gatekeepers

Physician outreach isn’t a standard 9-to-5 desk job. Skip planning around call windows and you’ll burn attempts on gatekeepers and voicemail loops.

• Call blocks: protect two outbound blocks aligned to clinic gaps, often early morning and late afternoon, kept meeting-free.
• Gatekeeper routing: log the best callback window and the best path — direct line, provider office, or email review.
• Disposition discipline: every attempt gets an outcome so attempts-per-placement reflects reality.

For a deeper design on this, see call block math for physician recruiting.

Diagnostic table

Use this in weekly ops review to decide whether you have a staffing problem, a reach problem, or an admin/workflow problem.

Weighted decision checklist

Goal: decide whether to add headcount, improve reachability, or automate. Score each item 0–2 (0 = no, 1 = partial, 2 = yes) and multiply by weight.

If reachability scores low, fix contact data and suppression before hiring. If admin load scores low, automate and add ATS enrichment before hiring. If everything scores high and targets still miss, add recruiter capacity or reduce req load.

Outreach templates

Short templates built for physician reality — clinic hours, gatekeepers, short attention windows. Keep them tight and log outcomes.

Standard dispositions

• Connected
• Left voicemail
• Gatekeeper (no transfer)
• Wrong number
• Do not contact (opt-out)
• Email bounced
• Replied (email/text)

Call opener (direct physician line)

Opener: “Dr. [Last], this is [Name]. I’m calling about a [specialty] role in [region]. Do you have 20 seconds for the headline?”
Headline: “It’s [setting], [schedule/call], comp range [range]. If I send a 3-bullet summary, what’s the best email?”
Close: “If it’s not you, who’s the right person in your group to talk to?”

Gatekeeper-friendly ask (clinic front desk)

“I’m trying to reach Dr. [Last] about a physician opportunity. What’s the best time to call when they’re between patients?” / “Is there a direct line for the provider office, or should I email a one-page summary for review?”

Email (first touch)

Subject: “[Specialty] role — [city] schedule + comp”
Body: “Dr. [Last] — recruiting for a [specialty] opening in [region]. 3 bullets: (1) [setting], (2) [schedule/call], (3) [comp range]. If you’re open, I’ll send details and a 10-minute time slot. If not, who should I speak with?”

Text (after permission or warm context)

“Dr. [Last], [Name] here. Sent a 3-bullet summary to [email]. Want me to hold a 10-min slot this week or should I close the loop?”

Common pitfalls

Planning off req count instead of attempt capacity

Starting with “each recruiter can handle X reqs” skips the real constraint: how many quality attempts they can execute while keeping follow-up tight.

Treating all attempts as equal

A dial to a verified mobile is not the same as a dial to a hospital main line. If you don’t separate attempts from effective attempts, your model overestimates capacity.

Ignoring admin time, then blaming recruiters

Credentialing coordination, scheduling, and ATS hygiene are real work. Skip budgeting admin hours and you’ll steal them from outbound time, and the pipeline stalls.

Using stale contact data without suppression

Static lists decay quickly. The safer standard pairs access with refresh, verification, and suppression. Without suppressing wrong numbers, bounced emails, and opt-outs, reachability drops and the capacity plan quietly fails.

Not separating active reqs from owned reqs

Recruiters can own 40 reqs while only 12 are truly active. Capacity planning should run on active reqs that require weekly outbound activity, not the full owned list.

Build the capacity calculator

Create a spreadsheet tab called Capacity. Use this layout so leaders can audit assumptions quickly.

Symbolic example: if admin hours (B3) increase, net outreach hours (B4) decrease, so weekly attempt capacity (B6) decreases. That lowers placements per recruiter (B8) and lowers the safe active req cap (B10). If leadership adds reqs anyway, follow-ups slip first.

B10 is your reqs-per-recruiter cap for active reqs. If leadership wants to add reqs, they need to either raise B6 (capacity) or lower B9 (required weekly activity) without hurting outcomes.

Sensitivity check: how reachability changes the plan

Measurement cadence

Run a weekly funnel review per recruiter and per specialty line: attempts, connects, qualified, submitted, placed.

• Connect Rate = connected calls ÷ total dials (per 100 dials)
• Outreach attempts per placement = total logged attempts ÷ placements, segmented by specialty
• Capacity utilization = logged attempts ÷ weekly attempt capacity, per recruiter per week

Operating rule: if connect rate drops for two consecutive weeks, treat it as a reachability or workflow issue — refresh, suppression, call windows — before treating it as a recruiter performance issue.

Increasing capacity without hiring

• ATS enrichment: auto-fill contact fields, specialty, and location, and suppress duplicates so recruiters aren’t doing data entry mid-flow.
• Automation: templated follow-ups, sequences, and standardized dispositions.
• Reachability: fewer wrong numbers and bounces means fewer wasted attempts and a better connect rate.

Legal and ethical use

Physician outreach carries real trust and scrutiny. Keep the process clean:

• Contact people only for legitimate recruiting purposes and document your process where required.
• Honor opt-out requests immediately and suppress future outreach.
• Don’t misrepresent the role, compensation, or urgency.
• Keep sensitive information out of free-text notes when it isn’t needed for recruiting decisions.

Evidence and trust notes

This playbook draws on operational recruiting workflows and patterns observed in real outreach systems. For how Heartbeat.ai evaluates data quality, refresh, and suppression, read the trust methodology.

For general context on the recruiting profession (not a benchmark for this model), see the U.S. Bureau of Labor Statistics: Human Resources Managers.

FAQs

How do I estimate outreach attempts per placement if my ATS data is messy?

Run a 2-week logging sprint: require every call, email, and text to be logged with an outcome. Then compute total attempts divided by placements, segmented by specialty, and replace planning assumptions with your observed typical.

What connect rate should I plan around for physician calls?

Plan around your own dial logs. Connect Rate = connected calls ÷ total dials (per 100 dials). Use the median week, not the best week.

How do I turn attempt capacity into a req cap?

Set a minimum attempts-per-active-req-per-week standard (B9 in the calculator). Then cap active reqs using weekly attempt capacity ÷ attempts per active req per week.

Should I hire more recruiters or invest in automation first?

If admin hours are eating outbound blocks, automation and ATS enrichment usually increase capacity faster than hiring. If reachability is poor — low connect rate, wrong numbers — fix contact data and suppression first, or you’ll just scale wasted attempts.

Where does Heartbeat.ai fit in this capacity planning workflow?

Heartbeat.ai supports reachability and admin reduction: contact discovery, suppression, and ATS enrichment so recruiters spend more time on real conversations and less on rework. For fast contact discovery against a target list, see bulk physician lookup for recruiting outreach.

Next steps

• Build the Capacity worksheet (cells B2–B10) and fill it with your current assumptions.
• Run the sensitivity table and decide what breaks first: reachability, admin time, or attempts per placement.
• Protect outbound blocks and standardize dispositions so your data stays clean.
• Start a free search and preview data and pressure-test how much wasted dialing you can remove before adding headcount.

About the Author

Ben Argeband is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two platforms used by sales and recruitment professionals. Ben’s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on LinkedIn.