Most hiring delays don't start in recruiting — they start in the approval process before a single job is posted. A new role sits waiting for sign-off from a line manager who is in meetings, then a finance director who is waiting for updated headcount data, then an HR Director who wasn't copied on the original request. By the time the role reaches the recruiter, three weeks have passed and the candidate pipeline you could have been building is empty. Designing a job requisition workflow that moves fast without losing financial accountability or compliance documentation is one of the highest-leverage process improvements an HR team can make.
Why Job Approval Workflows Matter
The business case for formalising job approval workflows is straightforward: time-to-hire is one of the most directly actionable metrics in talent acquisition, and pre-requisition delay is typically its largest controllable component. Analysis of hiring cycle data across mid-market companies consistently shows that the time between "hiring manager decides they need a role" and "recruiter receives an approved requisition" averages 2–4 weeks — often exceeding the time to fill the role once it is actively sourced.
Beyond speed, structured approval workflows provide three operational benefits that informal processes cannot:
- Financial governance: New headcount represents a material financial commitment. A formal approval workflow ensures that roles cannot be posted — and salary offers cannot be extended — without the sign-off of those responsible for budget authorisation. This protects against both budget overruns and the operational disruption of a hire that finance did not plan for.
- Consistency and fairness: Informal approval processes create inconsistency. A popular hiring manager's requests move fast; a less senior or visible manager's requests stall. Formalised workflows create an equitable process where all requisitions move through the same stages on the same timeline.
- Audit trail: For regulated industries and for any organisation subject to employment law scrutiny, a documented trail of who approved what — and when — is a compliance requirement, not optional process documentation. When a redundancy claim or an EEOC complaint involves a question about why a role was created or why certain candidates were progressed, the approval audit trail is the evidentiary foundation.
The Cost of a 3-Week Approval Delay
For a senior engineering role with a £90,000 salary and a market that moves quickly, a 3-week approval delay typically means the best candidates available when the role was identified are no longer accessible when recruiting begins. Candidates in active search modes make decisions on 2–3 week timelines. A systematic 3-week pre-posting delay at an organisation hiring 30 roles per year adds over 1,500 hours of hiring delay per year — equivalent to losing multiple weeks of recruiter productivity before a single application is reviewed.
The Typical Job Requisition Process (and Where It Breaks)
Most organisations without a formal approval system operate a de facto process that looks something like this: a hiring manager sends an email to HR stating they want to hire someone; HR checks verbally whether the role is in the headcount plan; finance is consulted separately by a different person using a different channel; the request moves forward only when all parties respond — which happens at their individual convenience, not against a shared deadline.
The failure points in this informal model are predictable:
- No single source of truth: Requisition details exist across email threads, Slack messages, and verbal conversations. When a new recruiter picks up the role, they may be working from incomplete or contradictory information.
- No accountability for response time: Without a defined SLA for approver response, the process moves at the speed of the slowest respondent. A single busy approver blocks the entire pipeline.
- Lack of structured information capture: A two-line email ("We need a senior developer") does not provide the recruiter with salary band, reporting line, required qualifications, or start date. The recruiter must chase back through multiple stakeholders to fill in the gaps before they can write a job description.
- No version control: If requirements change between the initial request and the actual posting, there is no systematic way to ensure the final job description reflects the approved requirements rather than an intermediate draft.
Designing a Multi-Stage Approval Workflow
An effective job requisition workflow balances three competing interests: speed (approvers should respond quickly), thoroughness (the right information must be captured before approval), and governance (the right people must sign off at the right stage). The stages below represent a model for mid-market companies; the exact structure should be adjusted to reflect your organisation's decision-making hierarchy.
| Stage | Owner | Inputs Required | Target SLA | Output |
|---|---|---|---|---|
| Requisition submission | Hiring manager | Role title, department, reports-to, justification, salary range, start date, FTE/contract status | N/A (initiation) | Draft requisition created in system |
| Department head review | Functional lead | Headcount alignment confirmation, business case endorsement | 48 hours | Approved or returned with comments |
| Finance approval | Finance business partner / CFO | Budget availability confirmation, salary range approval | 48–72 hours | Approved with confirmed budget code |
| HR review | HR Director / HRBP | Role levelling, salary band alignment, compliance review | 24 hours | Approved requisition with grading confirmed |
| Recruiter activation | Recruiting team | Job description draft, sourcing strategy, target start date | 24–48 hours post-approval | Live job posting and active pipeline |
Designing Requisition Forms That Capture Enough — Not Too Much
Requisition forms fail in two directions: too sparse (the recruiter needs to chase for basic information) or too burdensome (hiring managers abandon the form partway through). The optimal form captures: role title and seniority level; reporting line; department and cost centre; business justification (new headcount vs replacement); approved salary range and variable compensation; required start date; minimum qualifications; and whether the role has been previously approved in the annual headcount plan. Fields beyond this should be optional or moved to the job description stage. A form that takes more than 10 minutes to complete will be routinely bypassed in favour of informal channels.
Clarification Requests: Handling Ambiguous Requisitions
Even well-designed requisition forms produce submissions that require clarification before approval can proceed. Common ambiguities include: role scope that does not clearly distinguish between a junior and senior hire; salary ranges that span two pay bands without a clear level decision; start dates that conflict with budget cycle constraints; or business justifications that reference projects or customer commitments the approver cannot verify.
Handling clarification requests well is critical because this is where informal workarounds emerge. If an approver cannot easily return a requisition with specific questions and the submitter cannot easily address them without a meeting, the approval process defaults to email — losing all the governance and visibility benefits of a formal workflow.
Effective clarification handling requires: a structured mechanism for approvers to add specific questions to a requisition and return it to the submitter; notification to the submitter of exactly what is needed and by whom; a deadline for the clarification response; and automatic re-routing to the approver when the clarification is provided. The requisition should not return to the beginning of the approval chain — it should continue from the point where clarification was requested once the submitter responds.
Audit Trail: Why Every Approval Decision Must Be Logged
The audit trail for job approval decisions is not a bureaucratic nicety — it is a compliance requirement in regulated industries and a practical necessity for any organisation that may face employment-related legal proceedings.
An adequate audit trail for job requisitions documents:
- Who submitted the requisition, and when
- The original content of the submission (immutable — editing after submission should create a new version, not overwrite the original)
- Each approver, their decision (approved / returned), and the timestamp of their action
- Any clarification requests, their content, and the responses provided
- Any amendments to the requisition after initial submission, who made them, and when
- The final approved requirements that were used to create the job posting
This documentation becomes directly relevant in several scenarios: an employment tribunal claim that a role was created as a pretext for a particular hiring decision; an OFCCP audit of federal contractor hiring practices (US); an ICO investigation of discriminatory hiring practices (UK); or an internal dispute about whether a promoted candidate's salary matches the approved band. In each case, the audit trail is the difference between a documented and defensible process and an informal process that cannot be reconstructed.
Requisition Workflows and Headcount Planning Integration
The most efficient organisations integrate job requisition approval with annual headcount planning, creating a two-tier approval model: roles already approved in the annual headcount plan move through an expedited track (typically just HR and finance confirmation that the role is being activated within the planned parameters); roles that represent unplanned headcount additions or changes to approved scope require full approval chain review. This differentiation dramatically reduces approval latency for planned hiring while maintaining appropriate governance for unplanned additions.
How Treegarden's Job Approval Module Works
Treegarden's job requisition approval module provides the end-to-end structured workflow that replaces email-based approval chains with a transparent, accountable, and audited process. The workflow operates as follows:
Requisition creation: Hiring managers submit new role requests through a structured form in Treegarden's platform. The form captures all required fields — role details, salary range, reporting line, business justification, and requested start date — and can be customised to add organisation-specific fields. Submissions cannot progress without required fields being completed, eliminating the "incomplete email" problem.
Multi-stage routing: Treegarden's approval chains support configurable multi-stage routing. Each stage can be assigned to specific roles (Finance Director, HRBP, Department Head) or individual users. Parallel approval stages — where Finance and a Department Head must both approve before proceeding — are supported alongside sequential stages. Approval routes can be configured differently by department, seniority level, or geographic location.
Notification and SLA management: Approvers receive notifications when a requisition is pending their action. Configurable reminder escalations are triggered when approvers do not respond within defined timeframes — bringing visibility to stalled approvals without requiring HR to manually chase each one. Escalation paths can be configured to route to a backup approver when the primary approver is unavailable.
Clarification workflow: Approvers can return a requisition with specific questions using Treegarden's built-in comment and clarification tools. The submitter receives notification with the specific questions, responds within the system, and the requisition automatically returns to the approver at the correct stage — no email chain required.
Full audit trail: Every action in the approval workflow is logged with user identity and timestamp. The complete approval history — submissions, approvals, returns, amendments, and final approval — is stored immutably and accessible for compliance review, internal audit, or legal proceedings. Treegarden's audit logs are exportable for external review.
Recruiter activation: When full approval is received, Treegarden notifies the recruiting team and creates a draft job record pre-populated with the approved requisition details — including the approved salary band, reporting structure, and minimum qualifications. This ensures the posting accurately reflects the approved requirements without manual re-entry.
Free Calculators for This Topic
Save time with these free HR calculators — no sign-up required:
Frequently Asked Questions
How many approval stages should a job requisition go through?
Most organisations operate effectively with 2–4 approval stages for standard headcount additions. Adding more stages reduces speed without proportionate governance benefit. The minimum effective structure for most mid-market companies is: (1) Department or functional head for business justification, (2) Finance for budget confirmation, (3) HR for levelling and compliance. C-suite roles, roles that represent unplanned headcount additions, or roles that involve international hiring may justify additional approval stages. Senior leadership should not be the default approver for all roles — this creates bottlenecks and delays that undermine the entire hiring capability of the organisation.
What information should a job requisition form capture?
An effective requisition form captures: job title and seniority level; department and reporting manager; business justification (replacement vs new headcount); cost centre and budget code; approved salary range; employment type (full-time, part-time, fixed-term, contractor); target start date; minimum qualifications and experience; whether the role is in the approved headcount plan; and any known urgency factors. The form should not be longer than 10 fields to complete — additional detail about the role should be captured at the job description stage, not the approval stage.
What SLA is reasonable for a job approval workflow?
Best-practice target: total approval cycle of 5–7 business days for standard roles, 2–3 days for replacements within an approved plan. Per-stage SLAs of 24–48 hours for each approver are reasonable. Organisations with approval cycles consistently exceeding 10–15 business days should audit whether the bottleneck is approver availability, information quality (approvers waiting for clarification), or unnecessary approval stages. Approval cycle time is a leading indicator of overall time-to-hire performance.
Can job requisition workflows integrate with headcount planning tools?
Yes, and the integration is valuable. When headcount planning and requisition approval are in the same system, roles that were approved in the annual planning cycle can be flagged as pre-approved, moving them through an expedited review track. Treegarden supports headcount planning within the platform, allowing planned positions to move to the approval workflow with pre-populated details when activated, and unplanned additions to route through full approval chain review. This differentiation is the most impactful structural improvement most organisations can make to their approval cycle time.
Is an audit trail for job approvals legally required?
In regulated industries (financial services, healthcare, government contractors) and for OFCCP-covered federal contractors in the US, documented approval processes are a regulatory requirement. In the UK, while there is no specific statute requiring job approval audit trails, they are essential evidence for responding to employment tribunal claims, EHRC investigations into discriminatory hiring, or ICO inquiries. From a practical risk management perspective, any organisation that hires regularly should treat approval documentation as a compliance necessity — the cost of implementing it is negligible compared to the cost of defending a claim without it.
Job approval workflows are infrastructure, not bureaucracy. Done well, they make hiring faster by eliminating the informal back-and-forth that slows informal processes, more accountable by creating financial governance over headcount decisions, and more defensible by producing the audit trail that employment law requires. Treegarden's job approval module was built to deliver these outcomes without creating a system that is harder to use than the email chains it replaces. Book a demo to see how the approval workflow integrates with the full hiring pipeline.