If demand is above target
Prioritize or phase requisitions first. Then compare redistribution, sourcing support, process fixes and additional recruiter capacity.
Talent acquisition operations
Reconcile current workload, add approved incoming demand and compare the forecast with a capacity target your own role mix can defend. Then verify whether the real constraint is recruiter capacity, candidate volume or pipeline speed.
Count active requisitions and recruiters on the same operating scope. Add approved incoming work separately, then stress-test complexity and leave an operating buffer for sourcing spikes and admin.
2 · Forecast capacity
15.0
raw future reqs / recruiter
Current raw load
10.0
Weighted future demand
60.0
Effective target / recruiter
8.5
Forecast utilization
176%
Recruiters needed
8
Recruiter gap
+4
Weighted reqs above target
26.0
Weighted demand = forecast requisitions × complexity. This is a planning scenario, not a productivity score or hiring-speed prediction.
Enter your own operating averages; Jobiba does not infer interview volume from job status.
Interview events / week
120
Team coordination hours
40.0
Hours / recruiter
10.0
Workweek consumed
25%
Hours left before other work
30.0
Hours to recover / week
8.0
Minutes to remove / interview
4.0
Target minutes / interview
16.0
Equivalent support capacity
0.20 FTE
After the week closes, enter observed workload from the same recruiter scope. These are employer-entered actuals until verified ATS transition events can hydrate them automatically.
Req variance
-6.0
Interview variance
-28.0
Coordination-hour variance
-6.0
Actual coordination share
21.3%
Actual min / interview
22.2
Support equivalent above target
0.05 FTE
Positive variance means actual workload exceeded this plan. Do not mix periods, recruiter scopes or interview definitions; refresh the plan before using the gap for staffing decisions.
Turn the observed overload into an explicit operating plan. Enter requisitions you can pause/redistribute and coordination hours you can remove through scheduling support or process changes.
Modeled active reqs
46
Modeled req utilization
135%
Modeled coordination share
16.3%
Remaining weighted req gap
12.0
Remaining coordination gap hrs
0.0
Weighted req gap closed
8.0
Coordination gap closed hrs
2.0
This is a planning scenario, not a promise that pausing work or reducing coordination will improve hiring outcomes. Reconcile the next closed period against actuals before attributing impact.
Prioritize or phase requisitions first. Then compare redistribution, sourcing support, process fixes and additional recruiter capacity.
Raise complexity for specialist, executive or outbound-heavy work. Lower it only when repeatable operations genuinely support it.
Keep room for interview coordination, hiring-manager delays, leave and demand spikes.
4 · Verify the bottleneck
If req load is high, capacity may be constrained. If load is reasonable but hiring is slow, inspect conversion, source quality and stage delays before changing team size.
Divide active open requisitions by recruiters actually carrying those requisitions. Keep the numerator and denominator on the same scope.
There is no universal safe number. Role complexity, application volume, sourcing difficulty, support and service expectations change workload, so Jobiba asks for your own target.
Forecast utilization is current plus planned requisitions divided by the team capacity implied by recruiter count multiplied by your target concurrent requisitions per recruiter.
No. Capacity and speed can interact, but this workspace does not invent a causal time-to-fill forecast. Verify hiring speed and funnel evidence separately.