Job Requisition: Meaning, Template, and Approval Guide

A job requisition is an internal request to authorize hiring for a role or a defined number of openings. It records the business need, budget ownership, hiring manager, timing, and approval decision. A job description explains the work; a job posting advertises it to candidates.

Your requisition should give someone else enough detail to approve the hiring request and carry it out. “We need another engineer” leaves the most important questions open: which work, how much capacity, under whose budget, and with what evidence of success?

Use the template below as a working document. Adapt the approval steps to your organization rather than creating a committee for every hire.

How does a job requisition differ from a job description?

A requisition requests and records authorization for hiring, a job description defines the role, and a job posting explains the opportunity to applicants. They share information but serve different decisions and audiences.

SAP’s official recruiting overview describes a requisition as a hiring request containing role and organizational information, followed by configured approvals and posting. That is a concrete product workflow, not a rule that every employer must use the same sequence.

Keep confidential approval information out of the public advertisement. Internal budget notes, replacement details, and organizational plans may be relevant to approvers without belonging in candidate-facing copy.

What should a job requisition include?

A useful requisition defines the hiring commitment and the conditions attached to it. Include the information needed to approve the request and hand it to recruiting without another round of basic fact-finding.

Start with these fields:

• Business need: the work or problem that justifies hiring.
• Role and ownership: title, team, hiring manager, and recruiting owner.
• Opening count: how many people the request authorizes.
• Request type: a new role, replacement, or another clearly described change.
• Working arrangement: worker type, location, schedule, and relevant constraints.
• Budget: compensation parameters, other expected costs, and the accountable budget owner.
• Timing: when recruitment may start and the desired start window.
• Selection plan: job-related requirements, evidence, and decision owner.
• Approval: who decided, when, and under what conditions.

A requisition number is a reference for the record. It does not tell you how many people are authorized. Oracle’s recruiting requisitions API represents the requisition number, hiring manager, and number of openings as separate information. Track seat count explicitly in your own document too.

Copy this job requisition template

The template below is an original operational starting point, not a legal form or a universal policy. Replace bracketed text, remove fields you do not need, and link supporting documents instead of copying them into several places.

Request and business need

Role, budget, and timing

Outcomes, selection, and decision

Do not leave “approved” as an unexplained checkbox. State what was approved. Permission to explore a role is different from permission to recruit immediately or make an offer within agreed terms.

What does a completed requisition look like?

A completed example should show the reasoning, not just filled boxes. The following fictional request illustrates a support-engineer hire. Its figures, dates, workload, and outcomes are invented to show how the form works; they are not compensation or staffing benchmarks.

Request: one support engineer reporting to the support lead. This is a new role, not a replacement. The team needs someone to investigate technical customer issues and turn recurring problems into reusable guidance.

Business need: product engineers are handling routine investigations that the support team cannot yet resolve. The request proposes adding technical support capacity while keeping product engineering responsible for code changes.

Alternatives considered: improve help documentation, rotate an engineer through support, or narrow support coverage. The manager records why those options do not fully meet the intended service coverage and which improvements will still happen.

Decision record:

These example amounts demonstrate how a range and cost ceiling differ. Use your own approved figures and cost definitions. The public posting should carry the compensation and working-arrangement information appropriate for disclosure; keep the restricted finance breakdown in its approval record.

Illustrative initial outcomes: independently investigate a defined class of customer issues, write clear escalation notes for product engineering, and publish approved troubleshooting guidance. These are proposed expectations for this role, to be checked against training and support available.

Approval: finance approves the linked budget envelope; the hiring manager owns the role and assessment plan; the recruiting owner confirms the posting and review capacity. Any additional opening or material cost change returns to the appropriate approver.

The connection between work and assessment matters. The U.S. Office of Personnel Management’s job-analysis guidance examines tasks, competencies, and their relationship. Use that methodological question when drafting your brief; its federal procedures are not a template for every private company.

Who should approve a job requisition?

Route the request to people who hold the relevant decision rights. Your organization may need separate budget, role, and recruiting checks, but the workflow should match its actual authority structure.

A small team might combine several responsibilities in one person. A larger organization may need additional reviews for location, employment arrangements, or organizational changes. Name an owner for each decision so the request does not circulate without one.

Give approvers a clear response: approve within stated conditions, decline with a reason, or return for a named revision. Name a response owner and due date so the recruiting team knows who will resolve a stalled request.

Separate approval from publication. Oracle’s documented requisition lifecycle distinguishes draft, approval, formatting, posting, and open phases. Your labels can be simpler, but they should still distinguish authorization from a live advertisement.

When should an approved requisition be reviewed again?

Review a requisition when the hiring commitment changes materially or its assumptions no longer hold. Agree on those triggers when you approve it, so a title edit does not receive the same treatment as adding another employee.

Useful triggers to consider include:

• More openings than originally authorized.
• Compensation or expected costs outside the agreed envelope.
• A different worker arrangement or employing location.
• A substantial change in responsibilities or level.
• A business dependency that has not been met.
• A pause long enough that the original need or funding needs checking.

These are suggested controls, not claims about what your ATS enforces automatically. Keep a dated change note showing the previous decision, the revision, and the person with authority to approve it.

If candidates are already involved, assign someone to communicate the change. A paused search, revised role, or canceled opening affects their time and expectations. An internal document update does not tell candidates what happened.

How do you turn approval into a usable hiring process?

Translate the approved role into candidate-facing information and a short evidence plan. Keep the authorization record available to the people who need it, while giving interviewers the role and criteria relevant to their work.

The handoff should answer four practical questions:

1. What are we advertising? Confirm the title, responsibilities, location, terms, and application route.
2. What are we assessing? Map essential requirements to evidence you can reasonably collect.
3. Who will do the work? Assign application review, interviews, feedback, and the final decision.
4. What will candidates hear? Explain the expected process, contact route, and how changes will be communicated.

Use structured interview scorecards to keep observations connected to the approved requirements. Check that each interview has a purpose before adding it; the guide to interview-round design helps you review that burden.

If the handoff exposes a confused role, return to the brief. Our role-definition checklist focuses on that earlier scoping problem. Revise the approved brief if you discover that it describes different jobs to different people.

Common questions about job requisitions

Is a job requisition the same as an open position?

No. The requisition is the request or record used to authorize and manage recruiting. The position or opening is what you intend to fill. Your system may connect them closely, so write down how many hires the record authorizes.

Does a replacement hire need a requisition?

That depends on your organization’s policy. A replacement still raises practical questions about budget, responsibilities, location, and whether the role should change. Use the existing approval process rather than assuming the previous employee’s role automatically authorizes identical hiring.

What does a requisition number mean on an application?

It identifies the employer’s recruiting record. Keep it when asking about a specific role, especially if the employer has similar titles. The number alone does not reveal your application status, approved headcount, or whether the role will be filled.

Can one requisition cover several hires?

Some systems support multiple openings on a requisition. Confirm your system’s behavior and your approval policy, then record both the authorized count and filled count. A public advertisement by itself is not a reliable statement of remaining openings.

How can Kit help after the role is approved?

Use the approved brief to configure the posting, application steps, assessments, and team review. Kit supports job postings and candidate applications with stages including interviews, work samples, and code assignments. You can use the relevant parts of that workflow to collect the evidence your role requires.

Keep headcount and budget approval in your existing approval record. Kit’s hiring pipeline does not by itself establish that finance has authorized a role, and this template does not claim a dedicated requisition-approval module.

A clear requisition gives your team an agreed starting point: the work, the hiring commitment, and the people responsible. You can explore hiring templates or try Kit to turn that brief into a process candidates and reviewers can follow.