Requisition approval as a routed workflow
A 30-day operational improvement plan for moving requisition approvals from email chains into a routed workflow, with a clear measure for approval cycle time.
Trusted by frontline teams 15 years of frontline software
Built for: Technology And Software · Healthcare Organizations · Financial Services · Manufacturing · Professional Services
Overview
This operational improvement plan helps recruiting teams replace informal requisition approval by email with a routed workflow. Its central measurement is days from request to approved requisition, tracked across a 30-day window so the team can compare the existing process with the new approval path.
Use it when requisitions regularly wait in inboxes, approvers are unclear, hiring managers cannot see status, or recruiting operations cannot reliably explain where approval time is being lost. The plan is especially useful for teams handling multiple departments, budget owners, or approval tiers. Configure the workflow around the actual decision points: request submission, manager approval, finance or headcount validation, HR review, and final approval where applicable.
This is not a replacement for workforce planning, compensation review, job description approval, or a full applicant tracking implementation. It also should not be used to bypass required budget, legal, security, or executive controls. The 30-day window produces a measurement for the tenant running the plan; any example improvement from email to routed approval is a pattern to test, not a guaranteed customer outcome. Review exceptions such as missing information, paused hiring, unavailable approvers, and requisitions reopened after approval before interpreting the result.
Standards & compliance context
- The routed workflow can support auditability for headcount and budget approvals by preserving request details, approver identity, decision status, and timestamps.
- Align routing and records retention with your organization’s HR, finance, internal-control, and employment-record policies.
- Do not use workflow speed as a reason to skip required review for job classification, compensation, privacy, accessibility, or equal employment considerations.
- Have authorized HR, finance, and legal stakeholders approve the final workflow and exception rules before production rollout.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Record the current days from request to approved requisition for a defined set of recent or open requisitions and document how start and end timestamps are determined.
- 2. Configure the routed workflow with named approvers, approval order, required fields, escalation timing, and exception paths for new headcount, backfills, and special reviews.
- 3. Assign the recruiting operations owner to launch the workflow and instruct hiring managers and approvers to submit and approve requisitions in the routed path rather than by email.
- 4. Monitor each request during the 30-day measurement window, recording approval timestamps, stalled stages, rejected requests, reopened requests, and documented exceptions.
- 5. Review the resulting cycle-time data with recruiting, HR, finance, and business stakeholders, separating normal workflow performance from delays caused by incomplete requests or policy holds.
- 6. Convert the review into actions by adjusting approver ownership, required fields, escalation rules, or training, then schedule the next measurement cycle.
Best practices
- Define the measurement start time as the moment a complete requisition request enters the approval process, not when an approver first notices an email.
- Use named roles and backup approvers instead of shared inboxes or manually maintained recipient lists.
- Require budget, headcount type, department, role details, and hiring manager information before routing begins.
- Set an escalation rule for approvals that remain untouched and direct escalations to a documented delegate.
- Separate rejected, canceled, paused, and reopened requisitions from completed approvals when calculating cycle time.
- Photograph the process in timestamps and workflow history rather than relying on recollection from email threads.
- Review seasonal hiring surges, quarter-end budget holds, and approver absences before attributing every change in cycle time to the workflow.
- Keep the route short enough to reflect actual decision authority and remove approval steps that add review without changing the decision.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this requisition approval plan cover?
This plan covers replacing email-based requisition approval with a routed workflow and measuring the days from request to approved requisition. It is designed for recruiting and hiring teams that need a consistent approval path, visible ownership, and a defined comparison window. Customize the route, approvers, and measurement rules to match your organization.
Who should run this improvement plan?
A recruiting operations lead, HR operations owner, or talent acquisition program manager can coordinate the plan. Hiring managers, finance partners, and department approvers should validate the route before launch. Assign one person to maintain the baseline, monitor the workflow, and review exceptions.
How often should requisition approval performance be reviewed?
Use the 30-day measurement window in this template for the initial comparison. Review open requests weekly during rollout so stalled approvals are corrected before they distort the result. After launch, continue reviewing cycle time on a recurring cadence that matches hiring volume.
Does this template address compliance requirements?
It supports documented approval controls by making the request path, approvers, timestamps, and decisions easier to track. It does not replace your organization’s requirements for budget authorization, headcount control, equal employment practices, records retention, or audit review. Have HR, finance, and legal stakeholders confirm the final routing rules.
What is a common pitfall when replacing email approvals?
A frequent pitfall is copying every historical email recipient into the workflow without defining who has decision authority. That can create duplicate approvals or new queues instead of reducing delay. Establish a single owner for each approval stage and define what happens when an approver is unavailable.
Can I customize the workflow for different requisition types?
Yes. Create separate routes or conditional steps for new headcount, backfills, contractors, executive roles, and roles requiring finance or legal review. Keep the metric definition consistent so cycle-time comparisons remain meaningful across the 30-day window.
Can this plan connect to recruiting or HR systems?
The plan can be adapted to the systems your team already uses for requisitions, approvals, notifications, and reporting. Preserve the request-created timestamp, approval timestamps, final decision, and exception reason wherever the workflow runs. Confirm that integrations do not reset the start date or omit approvals from the audit trail.
How does a routed workflow compare with ad-hoc email approval?
Email can work for low-volume, informal decisions, but it often makes ownership, status, and elapsed time difficult to verify. A routed workflow gives each request a defined path and creates usable timestamps for review. Keep email only for documented exceptions rather than as the default approval channel.
Related templates
Go deeper on the topic
-
Talent acquisition (TA) is the organizational function responsible for attracting, evaluating, and hiring employees — what was historically called recruiting...
Ready to use this template?
Get started with MangoApps and use Requisition approval as a routed workflow with your team — pricing built for small business.
