Five numbers show leadership how much recruiting work a small HR team handles.
Key takeaways
- Define each number once, in writing, and apply the definition every time.
- Pair each volume figure with a baseline or a trend.
- Measure scheduling hours over one or two representative weeks.
- Compare your busiest month with a typical month.
- Match each request to the numbers that support it.
Why numbers beat adjectives
Most small HR teams know they are busy. Recruiters answer email late into the evening, coordinators juggle interview calendars between other tasks, and the hiring manager who needs a role filled yesterday keeps asking why it isn't done. Leadership sees some of this, but it rarely sees the whole picture. When a team asks for another person or more recruiting time, the request often sounds like a complaint: "We're swamped." Leaders hear that a lot, and it's easy to set aside.
Numbers change the conversation. A figure tied to a specific activity gives leadership something concrete to evaluate. It shows the scale of the work, where the time goes, and what happens if nothing changes. It also makes the team look organized rather than overwhelmed, because the numbers show that someone has been paying attention.
A useful example comes from the Saskatchewan Roughriders. Their HR function is run by a two-person team, and Kim Gallagher, who has been with the organization for 15 years, oversees everything from executive hiring to an annual internship program. The organization employs approximately 80 salaried, year-round staff and scales to roughly 100 additional hourly roles during the season, according to Workable's case study of the team. When Kim pulled the data for one period, it showed over 900 messages exchanged with applicants. That single figure communicated the volume and care behind the team's work in terms leadership could immediately appreciate.
You don't need a sophisticated analytics stack to do this. You need a handful of numbers, collected consistently, and a clear explanation of what they mean. This post covers five that work well for small teams, how to calculate them, and how to present them without turning a budget conversation into a spreadsheet review.
Number 1: Open requisitions for each recruiter
The first number is the simplest. Count the number of open requisitions that each person on the recruiting side is actively handling. Divide the total by the number of people doing the work.
Be precise about what counts as "active." A requisition that is on hold because a hiring manager is reorganizing their team is not the same as one with applicants in process. Decide on a definition and apply it every time. A reasonable approach is to count any requisition that has been approved and has not been filled or formally closed, then note separately how many are on hold.
Raw ratios can mislead, though. Two recruiters handling twelve requisitions each is not the same workload if one set consists of entry-level hourly roles and the other of senior specialist searches. Leadership will ask about this, so it helps to group requisitions by type. A team might report "twelve open requisitions for each recruiter, including four senior roles that typically take more sourcing time." That single sentence does more work than the ratio alone.
Keep the number honest. If your team has a seasonal spike, report it separately, which we'll cover in a later section. A smoothed annual average hides the moments when the team is truly stretched, and those moments are often when leadership most needs to understand the constraint.
Number 2: Applicant messages and touchpoints
The second number captures the communication load. Recruiting involves a surprising amount of writing: acknowledgments, scheduling notes, status updates, rejection messages, offer discussions, and follow-ups when applicants go quiet. Much of this work is invisible to people outside the team.
Start by counting outbound messages to applicants over a fixed period, using whatever your system provides. If you use an applicant tracking system, it may log emails and messages automatically. If not, a rough count from a sample of recent requisitions can serve as a starting point. Be clear about your method so the figure can be repeated.
The Roughriders example shows why this matters. It makes an abstract workload visible. It also captures the quality of the work.
To make this number more useful, pair it with a second figure: the average number of touchpoints for each hire, or for each applicant who reaches an interview. This tells leadership whether the volume reflects a large hiring need or an inefficient process. If a typical hire requires forty messages across six weeks, you have a case for better tools, examples, or self-service scheduling. If it requires eight messages, the volume is likely driven by the number of applicants, which points toward a different conversation about sourcing or job requirements.
Be careful not to overstate. A high message count isn't automatically a sign of inefficiency. Sometimes it reflects an applicant-rich market or a role that demands extensive engagement, such as executive search. Present the number as context, and let leadership draw conclusions with you.
Number 3: Hours lost to scheduling
Scheduling is one of the most underestimated tasks in recruiting. Finding times that work for an applicant, two or three interviewers, and a hiring manager, then rescheduling when someone cancels, can consume hours each week. For small teams, this time often comes directly out of sourcing and relationship work.
To measure it, ask the team to track how much time they spend on scheduling for one or two representative weeks. A simple log works: each time someone schedules, reschedules, or confirms an interview, they note the approximate time. Over a short period, the total usually surprises people.
Once you have the figure, you can show what a change would recover. The Beauty Tech Group, a company that built a more modern recruiting operation on Workable, reported that self-scheduling alone returned an estimated 20 hours per week to its recruiting function, according to Workable's customer story. That is a specific, testable claim, and it translates into a question leadership can answer: what would twenty hours a week of recruiter capacity be worth?
Your own organization will have different numbers, and you should not borrow someone else's result as if it were your own. The point is to build the case with your data. If your team spends six hours a week on scheduling, that is still meaningful. Multiply it across a year, and it represents a substantial block of time that could go toward sourcing, employer branding, or reducing time-to-fill.
This number also supports a request that many leaders find easy to approve. Calculate the cost comparison with your own figures rather than assuming it. Show the current hours, the expected reduction if you have a reliable estimate, and the cost of the change. Leadership can then judge the return.
Number 4: Peak-season load against baseline
Many small HR teams don't hire at a steady pace. They hire in waves: a seasonal business ramps up, a fiscal year begins, a product launches, or a large project is approved. Averages hide these peaks, and peaks are often where teams break down.
Compare two figures: the team's typical monthly workload and its busiest month. Use the same measures from the earlier numbers, such as open requisitions, applicant messages, or hours spent on scheduling. The gap between the baseline and the peak describes how much capacity the team needs to absorb a surge without sacrificing quality.
Consider how the Roughriders describe their own staffing pattern. The permanent workforce is one kind of load; the seasonal surge is another, and it has to be planned for separately. A two-person team handling both is a meaningful operational fact, and it should be stated plainly.
If your organization has seasonal or cyclical hiring, build a simple calendar that shows when demand rises and falls. Mark the weeks when interview volume peaks, when offers cluster, and when onboarding overlaps with new requisitions. Then ask a direct question: what would the team need to deliver the peak without compromising the rest of its responsibilities? That question moves the discussion from "we need more help" to "here is when we need it and why."
Be realistic about options. Temporary recruiters, contractors, or a short-term coordinator can cover a peak. You don't have to request permanent headcount to make the case. Showing leadership the range of options, along with the costs and trade-offs, makes your proposal more credible.
Number 5: Time from requisition to decision
The fifth number tracks how long the process takes from the moment a requisition is approved to the moment a hiring decision is made. Time from requisition to decision is useful because it isolates the portion of the process the recruiting team controls more directly, and it reveals where delays come from. For a way to record the decision itself, see Hiring Decision Debrief: Notes to a Recorded Decision.
Break the timeline into stages: intake and job definition, sourcing, screening, interviews, decision, and offer. Record how many days each stage typically takes. The stage with the longest duration is often where the workload pressure is most visible, and it may point to a specific cause.
One frequent cause is unclear requirements. Before a recruiter can screen effectively, the team needs to know what the job requires. Requirements that shift during the search lead to rework, and they extend the timeline. The EEOC's guidance on job applicants and disability notes that an applicant with a disability, like all other applicants, must be able to meet the employer's requirements for the job, such as education, training, employment experience, skills, or licenses, as described on its Job Applicants and the ADA page. That guidance is about legal obligations under the Americans with Disabilities Act, so it should not be read as a general hiring procedure. Still, it underscores a practical point: requirements need to be defined clearly and applied consistently. A team that spends time revising requirements mid-search is spending recruiter capacity that could have gone toward applicants.
This number helps you make a targeted request. If the bottleneck is in intake, the solution may be a structured intake meeting with hiring managers rather than more recruiters. If the bottleneck is in interview scheduling, the solution may be better tools. If the bottleneck is in sourcing volume, the solution may be additional recruiting capacity. Without the stage-level breakdown, all three problems look like "hiring takes too long," and leadership has no way to choose among them.
Present this number with the others. A long timeline combined with a high requisition count and heavy scheduling hours tells a coherent story. A long timeline alone could have many explanations.
How to present the five numbers
Collecting the numbers is only half the work. How you present them determines whether leadership acts on them.
Start with the decision you want. Are you asking for an additional role, a budget for software, permission to use contractors during a peak, or simply recognition that the team's workload has changed? Each request draws on different numbers. A headcount request should lead with requisitions for each recruiter and peak-season load. A software request should lead with scheduling hours and message volume. A process request should lead with the stage-level timeline.
Keep the presentation short. One slide or a single page is usually enough. Lead with a sentence that states the conclusion, then support it with two or three figures. Avoid dumping every metric you collected. Leadership needs to understand the problem and the proposed response, not audit your data.
Define every term. If you say "open requisitions," clarify whether that includes approved roles that haven't been posted. If you cite "applicant messages," explain whether automated notifications are included. Ambiguity invites skepticism, and skepticism delays decisions.
Show trends when you can. A single snapshot is less persuasive than a comparison. If you have data from the previous quarter or the same period last year, include it. Even three data points showing a steady rise tell a stronger story than one number on its own.
Acknowledge what the numbers don't show. Metrics can't capture the quality of an applicant's experience, the value of a difficult conversation with a hiring manager, or the institutional knowledge that a long-tenured recruiter brings. You don't need to list these exhaustively, but mentioning that the numbers are a partial view signals that you are being honest about the limits of your analysis.
Connect the numbers to outcomes leadership cares about. Hiring delays affect revenue, operations, and team morale. Turnover in the HR team itself is costly. If your data suggests that a team member is at risk of burnout, state it plainly and tie it to the cost of replacing that person. Leaders generally respond better to business consequences than to workload complaints.
Finally, make the request specific. "We need more support" is hard to evaluate. "We need a temporary coordinator for eight weeks each spring to handle scheduling for the seasonal cohort, which currently takes an estimated six hours a week for each recruiter during peaks" is something leadership can approve, adjust, or decline with clear reasoning.
Illustrative example: one team's numbers
In one sample week, scheduling takes 20 hours. The team sends 60 messages to applicants in a quiet month and 100 in its busiest month. Last year the ratio was 4. Together, those figures show a rising load and a seasonal peak, which is a stronger request than any one number alone.
Building the habit
These five numbers are most powerful when they are tracked consistently rather than gathered once in a panic. A small team can set up a monthly routine: update the open requisition count, log the scheduling hours for one sample week, record the message volume from the applicant tracking system, and note the timeline for any requisitions that closed that month. This takes less time than most people expect, especially once a simple spreadsheet is in place.
Keep the definitions in writing. A consistent interview scorecard shows how written criteria work in practice. When a new recruiter joins or a manager asks a question six months later, the team should be able to explain exactly what each number means and how it was calculated. Consistency is what makes trends credible.
Share the numbers with the team, too. Recruiters and coordinators often have a sense of their workload but no shared vocabulary for describing it. Reviewing the figures together can surface patterns the team hadn't noticed, such as a particular hiring manager whose intake process consistently adds a week, or a type of role that generates disproportionate scheduling work. These insights make the team more effective, and they strengthen the case for change.
A closing thought
Small HR teams often feel invisible. Their work happens in calendar invitations, inbox threads, and late-night applicant follow-ups that rarely reach the executive level. Numbers don't solve the underlying staffing problem on their own, but they make the problem legible. They turn "we're busy" into a description of what the team does, how much of it there is, and what would change if the team had more time or better tools.
Start today by counting approved requisitions that are not yet filled or closed. Then pick one or two of the five measures that fit your situation best. Collect a baseline, write down your definitions, and share a short summary with the people who make decisions about headcount and budget. Then keep going. A year of consistent data is far more persuasive than any single presentation, and the habit itself tells leadership that the team is managing its work with the same care it applies to its applicants.
Frequently asked questions
How many of the five numbers should I track?
Track two or three to start, then add the rest once your definitions hold steady.
Do I need special software?
No. A spreadsheet is enough, although an applicant tracking system can log messages automatically.
When should I share the numbers?
Share them with each request, and include a trend whenever you have one.