Plan a search around the reviewers and decision-makers who must move it forward. More sourcing can increase the waiting list when the team has no capacity to review profiles, conduct interviews, or decide. Estimate each of those workloads before opening additional roles.
This is an internal planning exercise, not a benchmark for how many candidates a startup should interview. Use your team's available time and observed process.
Map the work that consumes capacity
Start with a normal hiring week. Include preparation, written feedback, candidate questions, and debriefs as well as meetings. A calendar with interview slots can still lack decision capacity.
| Activity | Accountable owner | Capacity question |
|---|---|---|
| Profile review | Hiring manager or delegated reviewer | How much protected review time exists? |
| Initial assessment | Assigned interviewer | Are preparation and feedback included? |
| Specialist assessment | Qualified technical or functional evaluator | Is one person shared across several searches? |
| Candidate questions | Hiring manager | Can material questions be answered promptly? |
| Debrief and decision | Decision owner | When can the evidence be considered together? |
| Offer approval | Authorized approver | Which approvals can be prepared in advance? |
Do not count the same person's available hours separately for every open role. Keep one capacity view across searches.
Estimate throughput with your own assumptions
For each stage, divide the time available for that work by the estimated time required per candidate. Treat the result as a planning estimate, then compare it with what happens in practice.
Allow for variability and interruptions. A schedule that assumes every minute will be used perfectly leaves no room for a complex candidate question or an urgent product issue.
The stage with the least usable capacity deserves attention first. Increasing activity upstream does not solve a blocked technical review or an absent final approver.
Decide which constraint to change
Fictional example: A startup can hold initial conversations promptly, but the same engineer reviews work samples for several roles. Completed exercises accumulate. Asking recruiters for more introductions would expand the queue. The team instead reserves review time, trains another qualified reviewer, and sequences the less urgent search.
Possible responses include narrowing active priorities, delegating a well-defined review, reducing duplicated assessments, or moving a decision meeting. Each changes a different part of the process. Identify the actual constraint before choosing.
Avoid skipping necessary evidence simply to clear the calendar. Use the interview evidence map to identify work that can be removed without leaving an important requirement unassessed.
Control the queue visibly
Track which stage each candidate is waiting for, who owns the next step, and how long the item has been waiting. Keep only the information needed by the people doing the work.
When capacity changes, update sourcing partners and active candidates. A paused search should not continue collecting introductions as though the process were moving normally.
Use submission limits to keep incoming work reviewable, but do not confuse a limit with a functioning review process. Someone still needs to act on the permitted submissions.
Reconcile the plan each week
Compare planned capacity with completed work. Ask whether delays came from time, unclear requirements, missing evidence, or unavailable approvals. Repeated rereading of the same profile may signal indecision rather than insufficient reviewer hours.
Update the plan when an interviewer is away, a role changes, or a new priority appears. The useful outcome is a credible promise about what the team can handle next, connected to the requisition priority plan.