What Is a Requisition?

A requisition is an internal request that lets an organization review a proposed hire, purchase, or service before committing resources. The requester explains what is needed and why, and provides details that help the appropriate people assess the request. Depending on the request and the organization’s process, reviewers may consider the business need, budget, timing, and relevant requirements. Approval usually authorizes a next step rather than completing the transaction: recruiting can begin, purchasing can issue an order, or a service provider can be selected. A clear requisition creates a record of the decision and can prevent delays caused by missing information or unclear responsibilities.

What Does a Requisition Include?

A requisition is usually the starting point of a controlled business process. It records what someone needs, why they need it, and how the request may be funded. Organizations may collect this information through a form, email workflow, spreadsheet, procurement platform, or human resources system. The format varies, but the purpose is consistent: give reviewers a clear record before action is taken.

Requisitions can cover many needs, such as hiring an employee or contractor, buying office supplies or equipment, obtaining software or professional services, replacing damaged tools, or requesting a project expense. The person who submits the request is often called the requester. Depending on the request, reviewers may include a manager, department leader, finance representative, procurement professional, or HR team.

How Does the Requisition Process Work?

The exact workflow depends on the organization, the type of request, and the amount involved. Most processes follow a similar sequence: define the need, provide relevant details, obtain approval, and document the decision.

Identify and Describe the Need

The process begins when someone identifies a practical business need. It might be another team member, a replacement laptop, specialized software, or outside expertise for a project. The requester should explain the need clearly. Vague requests can slow approval because reviewers may have to ask for more information before deciding.

Provide the Details Reviewers Need

A requisition should contain enough information for reviewers to understand the request and evaluate it. Depending on the request, it may include the requester’s name and department, a description of the item or role, the reason for the request, and an estimated cost or pay range. It may also identify the budget or cost center, quantity, timing, suggested supplier, and required approvals.

For a job requisition, useful details may include the position title, responsibilities, location, employment type, and business reason for hiring. Information about the role’s reporting structure or required skills can also help reviewers assess the request.

Review and Approve the Request

Approvals help confirm that a request is necessary, affordable, and consistent with organizational priorities. A direct manager may assess the operational need, while finance checks budget availability. Procurement may review supplier requirements, and HR may review a staffing request. A routine low-cost purchase may need fewer approvals than a new leadership role or a major service contract.

Take the Authorized Next Step and Keep a Record

Approval generally authorizes the next stage rather than completing the request. An approved purchase requisition may go to purchasing, where a buyer obtains quotes or creates a purchase order. An approved job requisition may go to HR or recruiting so the role can be prepared for posting. An approved service requisition may lead to vendor selection and a statement of work.

The requisition also records who requested the action, who approved it, and why. This record can help teams monitor spending and plan staffing. It can also help answer questions about the decision later.

What Is a Job Requisition?

A job requisition is an internal document or workflow used to request approval to hire for a role. It comes before the public-facing job posting. Department managers and other leaders use it to describe the hiring need and secure approval for the position. Indeed’s overview of job requisitions describes common components such as position details, the business justification, budget information, and required approvals. Including enough detail can prevent later confusion about the role’s level, responsibilities, or manager.

A job requisition may be created because an employee has resigned or changed roles, a team is growing, or a new project requires additional skills. It may also request a temporary worker or contractor, or propose replacing a role identified in a business review. The review gives leaders a chance to assess the need before recruiting begins.

Job Requisition, Job Description, and Job Posting

These documents are related but serve different purposes. A job requisition requests internal approval to hire. A job description defines the work, responsibilities, and qualifications. A job posting advertises an open role to job seekers. After the requisition is approved, the organization can use its details to create or update the job description and publish a posting.

What Is a Purchase Requisition?

A purchase requisition is an internal request to obtain goods or services. It may begin when an employee or department needs something that involves organizational spending, such as replacement equipment or a software tool. The request helps reviewers confirm the business purpose, expected cost, budget source, and necessary approvals before the purchase is made.

Purchase Requisition Versus Purchase Order

A purchase requisition is generally an internal request for permission to buy. A purchase order is generally the document sent to a supplier to place or authorize an order. The typical process is:

1. An employee requests a purchase.
2. The request is reviewed and approved.
3. Purchasing may create a purchase order.
4. The supplier provides the goods or services.
5. The organization receives and processes the invoice.

The requisition begins the internal decision process. The purchase order connects the approved request to the transaction with the supplier.

Why Do Requisitions Matter?

A requisition process can feel like extra administration when work is urgent, but it can help prevent larger problems. Reviewing requests against budgets before money is committed supports spending control. Visibility into planned hiring and purchases helps leaders plan resources. A record of requests and approvals also clarifies who authorized an action and the reason for it.

For workforce planning, a job requisition creates an opportunity to reconsider a vacancy before recruiting starts. Rather than automatically replacing a departing employee, leaders can assess whether responsibilities have changed or whether the remaining team can take on the work. They can also consider whether a different type of worker, such as a contractor, would better meet the need.

How Can You Write a Clear Requisition?

Describe the request specifically. Instead of writing “need new software,” identify its purpose, the team that will use it, and the problem it is intended to solve. Then connect the request to a business need, such as supporting a project, replacing an essential resource, addressing a capacity limit, or enabling a planned service.

Include realistic cost and timing information when possible. An estimate does not have to be exact, but it gives approvers context for evaluating the request. Identify relevant stakeholders early as well. A job requisition may need input from the hiring manager, HR, finance, and the role’s eventual supervisor. A purchasing request may require input from the requester, budget owner, procurement team, and IT or security reviewers.

*This article is for general informational purposes only and is not legal advice.