A clear job requisition gives hiring managers and recruiters a shared answer to five questions: why the role exists, what the person will do, what they must be able to do, how success will be measured, and how the hiring process will run. This guide explains how to write a job requisition, compare requirements with preferences, set a defensible salary range, and create checkpoints that keep the hiring plan accurate from approval through offer.
Overview
A job requisition is an internal hiring request, not simply an early version of a job advert. It records the business case, role design, approval owners, recruitment plan, and practical employment details needed before a vacancy is opened. A strong requisition reduces avoidable changes later, such as rewriting the advert, widening the search, changing the interview panel, or discovering that the proposed salary does not match the intended level.
Use the requisition for a new position, a backfill, a role redesign, a headcount request, or a compensation review. The document should be specific enough for finance, leadership, recruiting, and the hiring team to review the same proposal. It should also leave room for evidence-based adjustments if the market, business need, or candidate supply changes.
Before drafting, speak with the person accountable for the work and any teams affected by it. Ask what problem the hire will solve, which work will move to the new employee, and what would be different six months after a successful hire. These answers are usually more useful than copying an old job description.
What to track
1. Business need and role purpose
Start with a short business case. State whether the request is for growth, a replacement, a temporary capacity gap, a new capability, or a change in operating model. Include the consequence of leaving the work unfilled and identify the budget or cost centre, if applicable.
Then write a two- or three-sentence role purpose. It should describe the outcome the role owns rather than list every task. For example, “Improve the reliability of customer onboarding by coordinating implementation steps, documenting recurring issues, and working with product and support teams” is more informative than “Help with onboarding activities.”
2. Responsibilities and decision rights
List the main responsibilities in order of importance. Group related work and distinguish between ownership, contribution, and administrative support. A useful list normally explains:
- the recurring outcomes the role is accountable for;
- the decisions the person can make independently;
- the people, customers, systems, or budgets they will work with;
- the work that is explicitly outside the role’s scope.
Avoid inflated lists that combine several jobs. If the role covers unrelated functions, decide whether the responsibilities belong in one position or should be split into separate hiring plans.
3. Requirements versus preferences
Separate requirements into three categories: essential on entry, trainable after joining, and preferred. A requirement should be essential only when lacking it would prevent the person from performing a core responsibility within a reasonable learning period.
| Category | Definition | Example | Review question |
|---|---|---|---|
| Must-have | Needed to perform a core responsibility at the expected level. | Ability to work with the reporting system used by the team, or a directly transferable equivalent. | Would the role fail without this capability? |
| Trainable | Can be learned through onboarding, coaching, or normal role development. | Knowledge of the company’s internal workflow. | Can we provide a realistic path to competence? |
| Preferred | May improve performance but is not necessary for a successful hire. | Experience with an additional tool or sector. | Will this affect the shortlist, or is it only a bonus? |
Be cautious with vague requirements such as “polished,” “high energy,” or “culture fit.” Replace them with observable behaviours linked to the work. Instead of “excellent communication,” specify the communication needed: writing clear customer updates, presenting a recommendation, or explaining technical information to a non-specialist audience.
4. Success measures and reporting line
Define three to five early success measures. They might cover delivery, quality, customer outcomes, risk reduction, process improvement, or team contribution. Avoid promising precise targets before the team has reliable baseline data; describe the measure and the review period instead.
Record the direct manager, team, key internal partners, and any people-management responsibility. If the role has a dotted-line relationship, explain what that means in practice. Candidates and interviewers need the same understanding of accountability.
5. Work arrangement, eligibility, and compensation
Specify the intended location, work arrangement, expected schedule, travel, shift requirements, and whether the arrangement is onsite, hybrid, remote, part time, fixed term, seasonal, or project based. Separate genuine operational requirements from habits that could be reconsidered. For example, identify the meetings or service hours that require availability instead of simply stating “flexible.”
Record the proposed employment type, expected start window, and any work eligibility or notice-period considerations that the organisation needs to plan for. Local employment terminology and disclosure requirements vary, so have the appropriate internal reviewer confirm the wording before publication.
Set a salary range using the role level, internal pay structure, budget, location, working pattern, and relevant benefits. Do not use a range so broad that it conceals the actual level. Record who approved it and when it was reviewed. A salary calculator guide can help teams check how hourly, annual, monthly, or take-home figures are being described, but it should not replace internal compensation governance.
6. Hiring plan and approvals
Document the target opening date, desired start date, recruitment owner, hiring manager, interview panel, assessment stages, decision maker, and approval owners. Give each interview stage a purpose tied to the requirements. A structured scorecard makes this easier; see the structured interview scorecard template for a way to define consistent criteria and ratings.
Keep the process proportionate to the role. Identify where a work sample, technical exercise, or portfolio review is genuinely needed, how long it should take, and what will be assessed. Avoid adding stages simply because they were used for a different vacancy.
Copyable job requisition template
Role title and level: Request type: New position / backfill / redesign / temporary need Business reason: Role purpose: Key responsibilities: 1. 2. 3. Decision rights and scope: Must-have capabilities: Trainable capabilities: Preferred capabilities: Success measures for the first review period: Reports to: Key partners: People-management responsibility: Location and work arrangement: Schedule, travel, or shift requirements: Employment type and expected duration: Salary range and benefits summary: Target opening date: Target start date: Recruiter or process owner: Interview stages and assessment methods: Hiring decision maker: Budget and approval owners: Risks, dependencies, and open questions: Last reviewed:
Cadence and checkpoints
Review the requisition at four practical checkpoints rather than treating approval as the end of the process.
- Before approval: Confirm the business case, level, budget, requirements, work arrangement, and decision owner. Resolve contradictions, such as a senior scope paired with an entry-level salary.
- Before publication: Read the requisition and advert together. Check that the public wording reflects the approved role, identifies material schedule or location requirements, and does not add informal preferences.
- During the search: Review progress at least weekly while active. Track qualified applicants, recurring questions, decline reasons, sourcing channels, time in each stage, and whether the shortlist reflects the intended requirements. Record changes rather than relying on memory.
- Before offer: Reconfirm the compensation range, approval status, start-date assumptions, reporting line, and any changes to responsibilities. If the role has materially changed, pause and reapprove the requisition instead of treating the offer as an exception.
A monthly or quarterly review of recurring requisitions can reveal patterns across roles. Look for repeated changes to salary, recurring confusion about responsibilities, interview stages that do not distinguish candidates, or requirements that are regularly waived. Those patterns may indicate a role-design or approval problem rather than a sourcing problem.
How to interpret changes
Not every change requires restarting the process. Minor wording improvements can usually be logged by the recruiter or hiring manager. Material changes should trigger a deliberate review. These include a different level, a new manager, a substantially different scope, a changed work arrangement, a new schedule requirement, a revised salary range, or a different employment type.
When applicant quality is low, diagnose the requisition before adding more requirements. Ask whether the salary range matches the level, whether the location or schedule is clear, whether essential criteria are unnecessarily narrow, and whether the advert explains the work well enough. Adding credentials can reduce the pool without addressing the underlying issue.
When many candidates meet the requirements but decisions are inconsistent, strengthen the assessment design. Link each interview question to a requirement and use defined rating guidance. The interview question generator guide can support question planning from the approved job description.
When the role becomes harder to fill after a business change, update the business case and success measures. Do not quietly expand the scope while retaining the original title, level, and salary. Clear documentation protects the candidate experience and gives approvers a fair basis for deciding what should change.
When to revisit
Revisit each open requisition weekly during active hiring and formally review it at least monthly if the search remains open. Close or refresh it when the role is filled, paused, cancelled, materially redesigned, or carried forward into a new planning period. For evergreen or recurring vacancies, review the template quarterly and compare outcomes across the previous hiring cycle.
Update the guide and internal template whenever compensation practices, work arrangements, employment terminology, approval rules, or relevant hiring requirements change. A six-month editorial review is a practical minimum for published guidance, with an earlier review after any material legal or recruiting-process change.
Before opening your next role, copy the template, complete the business case, classify every requirement as must-have, trainable, or preferred, and name the owner for each approval. Then test the draft against the pre-publication checklist:
- Is the role purpose connected to a clear business need?
- Are responsibilities prioritised and within a realistic scope?
- Can every must-have requirement be justified by a core responsibility?
- Are trainable skills and preferences labelled honestly?
- Are location, schedule, travel, employment type, and salary information clear?
- Do success measures and interview stages assess the same capabilities?
- Have vague, inflated, or potentially exclusionary phrases been removed?
- Are approval owners, dates, open questions, and the last review date recorded?
Save the completed requisition with the final scorecard and hiring-plan decisions. That record becomes a useful starting point for the next backfill, role redesign, compensation review, or quarterly workforce-planning discussion.