Headcount Request and Approval Process: Template, Stages & Automation Guide

Every hire starts with a headcount request. Yet in most companies, the process for submitting and approving that request is either non-existent (the hiring manager calls HR) or so poorly defined that every request moves through a different set of conversations, takes a different amount of time, and generates a different quality of documentation. The result is unpredictable hiring timelines, budget surprises, and frustrated hiring managers who can't understand why their request is taking three weeks while the person down the hall got approved in two days.

A well-designed headcount request and approval process solves this by standardising three things: what information is required to make an approval decision, who is responsible for each stage of that decision, and how long each stage is allowed to take. This guide provides the operational templates and frameworks to build that process from scratch — or to replace a broken one.

The Anatomy of a Headcount Request

Finance and leadership need specific information to approve a headcount request with confidence. Requests that lack this information get sent back for revision, which is the single biggest source of avoidable approval delay. The fields below represent the minimum required for a complete request — every field directly answers a question that an approver needs to make a decision.

• Role title and level. The formal title (e.g., Senior Account Executive) and seniority level (e.g., L4, or equivalent grade in your compensation structure). This anchors the compensation range review — Finance needs to confirm the proposed compensation fits within the approved grade band.
• Department and cost centre. Which department the role sits in and which budget code the personnel cost is charged to. Essential for Finance to identify which department's headcount budget absorbs the hire.
• Reporting manager. Who the new hire will report to. Establishes org chart placement and determines the correct approval routing — different departments may have different approval chains.
• Request type. Backfill (replacing a specific departing employee already in the headcount plan) or net-new (adding headcount beyond the approved plan). This is the most important field for routing: backfills typically require significantly lighter approval than net-new additions.
• For backfills: departing employee name and exit date. Finance needs to confirm the role being backfilled was in the approved headcount plan and that the timing creates a genuine vacancy.
• Business justification. A concrete, specific statement of what will not get done, what revenue is at risk, or what objective is blocked if this role is not filled. "We need additional capacity" is not a justification. "Filling this role unblocks the Q3 product launch currently at risk due to engineering capacity constraints, representing $400K in deferred ARR" is a justification.
• Compensation range. Expected base salary range (minimum and midpoint), and whether the total compensation structure includes bonus, equity, or commission. Finance uses this to calculate the full-year personnel cost including benefits load.
• Target start date. The date by which the new hire needs to be in seat. This allows recruiting to assess whether the timeline is achievable given typical time-to-fill for this role type, and to flag when the request needs to be fast-tracked.
• Work model and location. On-site, hybrid, or remote; city and country. Required for employment law compliance review — particularly for first hires in jurisdictions where the company does not have existing legal entity or payroll infrastructure.
• Within approved headcount plan? Yes/No, with reference to the plan document. If Yes, the role moves to a lighter approval tier. If No, the request is flagged as incremental and requires a fuller business case and broader sign-off.

Headcount Request Form Template

The template below can be copied directly into your HR system, headcount planning tool, or ATS. Fields marked with an asterisk (*) are required; the form should not be submittable without them.

Approval Matrix: Who Approves What at Different Company Sizes

The approval matrix defines who must sign off at each stage, based on role type and company size. A common mistake is applying the same matrix regardless of company size — a 500-person company applying startup-level approval governance creates budget risk, while a 50-person company applying enterprise-level approval governance creates unnecessary delay. The tables below provide calibrated matrices for three size ranges.

The 5 Stages of Headcount Approval

A structured headcount approval process moves through five distinct stages. Each stage has a defined owner, a defined output, and a defined SLA. Requests that skip stages or have unclear ownership are the requests that sit unresolved for weeks.

Stage 1 — Request Submission. The hiring manager completes the standardised headcount request form with all required fields. The form validates completeness before submission — a request missing the business justification or compensation range is returned immediately with a specific error, not accepted and reviewed later. This stage takes 30 minutes to complete; if it takes longer, the form has too many fields.

Stage 2 — HR Review and Routing. An HR business partner reviews the submission within one business day of receipt. The review covers three checks: (1) Is the form complete and all required fields populated? (2) Is the request correctly classified as backfill or net-new? (3) Is the proposed compensation within the approved grade band? If all three pass, HR routes the request to the correct approval tier based on the approval matrix. If any check fails, HR returns the request to the hiring manager with specific instructions for revision. SLA: 1 business day.

Stage 3 — Department Head Approval. The hiring manager's department head reviews the business justification and confirms the role priority relative to other team needs. The department head is not expected to reassess budget (that is Finance's role) but to confirm that the business case is sound and that this role is a genuine priority for the team. Department heads who approve every request without scrutiny undermine the process; those who consistently reject well-justified requests create morale and hiring pipeline problems. SLA: 1-2 business days depending on tier.

Stage 4 — Finance Budget Confirmation. Finance confirms whether the requested role fits within the approved personnel budget, calculating the full-year cost including base salary at midpoint, benefits load (typically 20-25% of base), and any additional compensation components. For in-plan roles, this is typically a confirmation step. For out-of-plan roles, Finance assesses the incremental budget impact and either approves within existing budget flexibility, requests a budget reforecast, or escalates to the CFO or CEO. SLA: 1-2 business days.

Stage 5 — Final Sign-off and Requisition Creation. The final approver in the chain grants approval. In a well-automated system, this approval triggers the immediate creation of an open requisition in the ATS, pre-populated with all approved role data, and sends a notification to the assigned recruiter. In a manual system, HR must now create the requisition manually — introducing a handoff delay that is typically 3-7 business days in organisations without ATS integration. SLA for final sign-off: 1-2 business days. SLA for requisition creation: zero days in automated systems.

Common Reasons Headcount Requests Get Rejected — and How to Pre-empt Them

Most headcount request rejections are avoidable. They are caused by predictable submission problems that a well-designed form and a brief pre-submission checklist can eliminate. The five most common rejection reasons:

1. Insufficient business justification. The most common rejection reason by a significant margin. Finance and department heads see dozens of requests per year. Generic justifications ("the team is overwhelmed," "we need to grow the function") do not give approvers confidence that the role is a genuine business priority versus a manager's preference. Pre-empt this by requiring the justification to reference a specific OKR, project, or revenue target, and to state the consequence of not hiring in quantifiable terms.

2. Compensation range outside the approved grade band. Hiring managers frequently propose compensation ranges that reflect market rates they have seen on LinkedIn or from recruiters, without checking whether those rates align with the company's compensation framework. Finance will reject or escalate any request where the proposed range materially exceeds the approved grade band. Pre-empt this by building a comp range lookup into the request form — when the hiring manager selects a role title and level, the form displays the approved range for that grade, and the hiring manager can either work within it or explicitly flag a grade exception request.

3. Role duplication with an existing open requisition. In organisations without centralised headcount visibility, hiring managers sometimes submit requests for roles that are already in the pipeline under a slightly different title. HR reviews catch most of these, but they are embarrassing and create approval delays. Pre-empt this by surfacing currently open requisitions in the relevant department when the hiring manager begins a new request.

4. Incorrect classification as backfill. Requests submitted as backfills for roles that Finance does not recognise as existing approved positions — because the departing employee's title, level, or department in the headcount plan differs from the request — trigger Finance queries that delay approval. Pre-empt this by having HR confirm the backfill classification against the live headcount plan before routing to Finance, not after.

5. Missing or unrealistic target start date. A target start date that is in the past, or that falls within a timeline that is clearly impossible given typical time-to-fill for the role type, generates a return-for-revision from HR. Pre-empt this by having the form calculate a realistic earliest start date based on the average time-to-fill for similar roles in your ATS history, and flagging when the requested start date is earlier than the realistic minimum.

Automating the Approval Process with an ATS

Manual headcount approval processes — those managed via email, Slack, or shared spreadsheets — have a structural disadvantage: they have no SLA enforcement mechanism. When an approver is on vacation, travelling, or simply deprioritising the request, it sits invisibly in their inbox with no mechanism to escalate or even make the delay visible.

An ATS with built-in headcount approval automation solves this through four capabilities:

• Digital form with validation. The request form is completed in the system, not in email. Validation rules prevent submission of incomplete forms. HR receives a structured, complete request every time — not a free-form email they must parse for the relevant information.
• Automatic approval routing. Based on the role attributes submitted — type, department, level, in-plan or out-of-plan — the system routes the request to the correct approvers in the correct sequence. When a department head approves, the request moves to Finance automatically. No manual forwarding, no missed steps.
• SLA enforcement with escalation. Each approver receives an immediate notification when a request enters their queue, with the SLA deadline stated. Reminders go out at 50% and 80% of the SLA window. If the SLA is breached, an escalation notification goes to the approver's manager and to HR leadership, with the stalled request clearly identified.
• Automatic requisition creation on approval. Final approval triggers immediate requisition creation in the ATS pipeline, with all approved role data pre-populated and the recruiter assigned and notified. The approval-to-active-search lag drops from 3-7 business days to zero.

Treegarden implements all four capabilities natively — because the approval workflow is built into the ATS rather than integrated from a separate tool, the requisition is created at the exact moment approval is granted, with no integration latency, no manual step, and no risk of data drift between the approved request and the active search.

Metrics: How to Measure Headcount Approval Velocity

A headcount approval process that nobody measures is a process that nobody improves. The metrics below provide a complete view of process health and identify exactly where bottlenecks are concentrated:

• Approval cycle time. Median and 90th-percentile time from form submission to final approval, by tier, department, and role type. This is the primary process health metric. Target: median below the SLA for each tier.
• Stage-level cycle time. Breakdown of cycle time by approval stage. This identifies whether delays are at the HR review stage (suggesting form quality problems), the department head stage (suggesting an approver bottleneck), or the Finance stage (suggesting budget uncertainty or under-resourced Finance review).
• First-pass completion rate. The percentage of submitted requests that pass HR review without being returned for revision. A rate below 75% indicates the request form is not doing its job — either the form itself is unclear, or hiring managers are not being coached on what constitutes an adequate business justification.
• Approval rate by tier. The percentage of requests approved at each tier. Persistently high rejection rates suggest that the standards for a successful submission are not clearly communicated to hiring managers, or that there is a genuine misalignment between what managers want to hire and what Finance has budgeted.
• Approval-to-active-search lag. Time between final approval and the recruiter beginning active sourcing. In a system with ATS integration, this should be near-zero. A persistent lag here points to a broken handoff between the approval workflow and the ATS.

Frequently Asked Questions

What should a headcount request form include?

A headcount request form should include: role title and level (anchors compensation review), department and cost centre (for Finance budget routing), reporting manager (determines approval routing), request type — backfill or net-new (determines the approval tier), business justification tied to a specific objective or quantifiable business impact, compensation range (base salary range and total comp structure), target start date, work model and location, and a declaration of whether the role is within the approved headcount plan. Fields marked as required should prevent submission until completed — a form that accepts incomplete submissions is equivalent to having no form at all.

What are the 5 stages of headcount approval?

The five stages are: Stage 1 — Request submission by the hiring manager via a structured form; Stage 2 — HR review for completeness, correct classification, and compensation range check, followed by routing to the appropriate approval tier; Stage 3 — Department head approval of the business justification and role priority; Stage 4 — Finance budget confirmation, calculating full-year personnel cost and confirming fit within approved budget; Stage 5 — Final sign-off and requisition creation, where the final approver grants approval and — in a well-automated system — the open requisition is created in the ATS immediately without any manual handoff. Each stage should have a defined SLA and an escalation path for when the SLA is breached.

Why do headcount requests get rejected?

The most common rejection reasons are: insufficient business justification — vague statements of need rather than a specific, quantified business impact; compensation range outside the approved grade band for the requested level; role duplication with an existing open requisition the manager was not aware of; incorrect classification as a backfill for a role Finance does not recognise in the approved headcount plan; and unrealistic target start dates that are either in the past or earlier than the achievable minimum given typical time-to-fill. Most rejections are avoidable with a well-designed request form that validates completeness and surfaces relevant context — like the approved compensation range for the role level — at the time of submission.

How do you automate the headcount approval process?

Automating the headcount approval process requires four capabilities: a digital form with validation that prevents incomplete submissions; configurable approval routing that sends requests to the correct approvers in the correct sequence based on role attributes; SLA tracking and escalation that sends reminders and escalates to management when approvers are unresponsive; and automatic requisition creation that converts an approved headcount request directly into an open requisition in the ATS without any manual re-entry. An ATS like Treegarden implements all four capabilities natively in a single platform, so the request-to-requisition journey is fully automated — the recruiter receives a notification with a ready-to-post requisition the moment final approval is granted.