A purchase requisition is the short internal request that starts a controlled purchase. Without it, buying begins wherever it likes: a chat message, a verbal promise, a card payment nobody reviewed. The requisition slows nothing down. It simply records what is needed, why, from whom and at what cost, before the business commits. This guide explains what a requisition must state, who handles it, and how it protects renewals as well as new orders.
Key Points
- A requisition records need, reason, supplier, cost and date.
- Approval happens before orders, cards, commitments or renewals.
- Set a second approver above a clear amount.
- Renewals and subscriptions use the same request route.
- Keep the form short, or people will bypass it.
Where Uncontrolled Buying Begins
Uncontrolled buying rarely begins with a reckless purchase. It begins with a reasonable one that nobody recorded. A developer needs a tool today, a marketer books a service before a campaign, an office manager replaces broken equipment. Each buy makes sense on its own. Together, without requests, they form a pattern nobody approved: duplicate tools, drifting prices and commitments that surface only when the invoice or the renewal charge arrives weeks later. None of it required bad intent, only the absence of one small checkpoint.
The damage is not the single purchase but the missing moment of review. Nobody asked whether the business already owned the tool, whether the budget had room, or whether a cheaper contract already covered the need. A requisition creates that moment at the cheapest possible point, before money moves and before a supplier treats the conversation as an order. It turns scattered good intentions into one visible, reviewable flow of buying decisions. It also gives finance a forecast instead of a pile of surprises.
What A Purchase Requisition Must State
A useful requisition states six things in plain words: what is needed, why it is needed, the preferred supplier, the expected cost, the date it is needed by, and which budget it belongs to. Add quantity or seats where they matter, and a link to a quote when one exists. That is enough for an approver to judge the request without a meeting, a call or a long email thread asking for missing details. Anything beyond that belongs in an attachment, not in the form itself, ever.
Keep required fields few and make them specific. A cost field that accepts a range invites vague requests; an exact expected price, or a stated ceiling, forces the requester to check before submitting. A reason field with one honest sentence beats a dropdown of generic purposes. Our wider guide to the purchase request process shows how these fields sit inside the full buying routine from request to recorded commitment. The fields stay identical for every team, so approvals stay comparable.
Who Raises Reviews And Approves
Anyone with a real business need should be able to raise a requisition, and the route after that should be fixed in advance. The requester raises it. A team lead reviews whether the need is real and the timing is right. A budget holder approves the cost. For small teams one person may hold two of those roles, but the steps still happen in order and stay visible to everyone involved. Publish the route once, and new joiners learn it on their first request.
Permission rules decide who sees and approves what. A department head approves their own team requests, finance sees the whole queue, and nobody approves their own purchase above a small limit. Clear team spending permissions remove the awkward part of approvals: the decision follows the role, not the relationship. When the route is predictable, requesters stop shopping for a friendly approver and start writing better requests. Approvers also improve, because the same kinds of requests reach them repeatedly.
Amounts That Need A Second Pair Of Eyes
Not every request deserves the same scrutiny. A small, routine buy inside an agreed budget can pass with one approver in minutes. Above a set amount, add a second pair of eyes: the budget holder plus finance, or the owner. The threshold should be low enough to catch real commitments and high enough that daily buying never queues behind one busy person for days. Publish the tiers where everyone can see them before they buy anything.
Set thresholds by commitment, not by invoice size. A modest monthly subscription commits the business for a year, so judge it by its annual value. A one off purchase above the threshold gets the same second look. Review the limits twice a year: as the team grows, yesterday's large amount becomes routine, and thresholds that never move either block normal work or stop catching the purchases that genuinely matter. A short note beside each tier explains the reasoning to new managers.
From Approved Request To Recorded Commitment
Approval is not the end of the requisition; it is the start of the commitment. The approved request becomes the record the order, the delivery and later the invoice are checked against. Whoever places the order works from the approved supplier, price and terms, and any change goes back for a fresh decision rather than a quiet adjustment nobody sees until the bill lands at month end. The record also names who placed the order, on which day, and against which budget line.
This chain is what makes later checks fast. When the invoice arrives, matching it takes minutes because the approved request already states what should arrive and what it should cost. The same record feeds the wider spend control process: budgets show the commitment, the supplier record gains the purchase, and the review at month end compares what was approved with what the business actually received and paid for. Nothing needs reconstructing when a supplier dispute arrives months later.
Requisitions For Renewals And Subscriptions
Renewals need requisitions too, in a lighter form. A renewal is a decision to buy again, and it deserves the same questions as a new purchase: do we still use this, at this level, from this supplier, at this price? Raise the request before the notice window closes, attach current usage and the agreed terms, and let the approver decide with time to act on the answer. Skipping this review is exactly how unused tools survive for years untouched.
The routine is short because the record already exists. The subscription entry carries the owner, the renewal date, the notice period and the last agreed price, so the request writes itself from the register. What changes is the habit: no renewal passes silently. Teams that review renewals through requisitions find their savings in the tools that shrank, the seats that emptied and the tiers that quietly crept upward. Each reviewed renewal also refreshes the budget for the year ahead.
Keep The Form Short Enough To Use
A requisition form fails when it asks for more than the purchase deserves. Every extra field is a small tax on honesty, and staff pay it by moving buying back into chats and personal cards. Protect the six core fields, make everything else optional, and let recurring requests start from a copy of the last approved one. A form that takes three minutes will be used; one that takes fifteen will be routed around. Measure completion time honestly, like you would measure any other promise to staff.
Test the form with a real purchase before you roll it out. Time a team member raising a typical request, watch where they hesitate, and remove or clarify those fields. Repeat the test after a month of live use. The goal is a form so plain that skipping it feels stranger than using it, and so short that nobody can claim the process slowed the work it was meant to protect. Revisit the form whenever a new field is proposed, and demand a reason.
Where Requisitions Fail In Practice
The first failure is approval after the fact, where the request is written to match a purchase already made. The second is the empty queue problem: approvers who sit on requests until requesters give up and buy anyway. The third is silent drift, where approved prices and suppliers change without a new decision. Each failure has the same cure: visibility, deadlines and a route short enough that following it beats avoiding it. None of these failures needs new software; each needs the routine defended.
Anchor the routine in policy so expectations survive busy weeks and staff changes. A short company spending policy that names who raises, who approves, the thresholds and the response times gives every new joiner the same map. Review the queue monthly, publish how fast approvals actually moved, and fix the step where requests stall. Requisitions work when the whole business can see them working. That monthly evidence is what keeps the habit alive under pressure.
Final Verdict
A purchase requisition is a small form with an outsized job: it moves the buying decision to the moment when changing it costs nothing. State the need, the reason, the supplier, the cost and the date. Route it to a named approver, add a second pair of eyes above a clear threshold, and let the approved request become the record every later check relies on. It costs minutes at the start and saves hours at the end.
Keep the form short, the route predictable and the deadlines real. Teams do not resist requisitions; they resist slow, unclear ones. Build the routine around real purchases, review where it stalls, and the business gains control of its buying without gaining a layer of theatre that nobody respects or follows. The routine should feel like a handrail, not a locked gate.
Frequently Asked Questions
What Is A Purchase Requisition?
A purchase requisition is an internal request to buy something for the business. It states what is needed, why, the preferred supplier, the expected cost and the date it is needed. A named approver reviews it before any order is placed. It is not an order and not a payment; it is the recorded decision that a purchase should happen, on stated terms, from a stated budget.
Who Can Raise A Purchase Requisition?
Any employee with a genuine business need should be able to raise one. The request then follows a fixed route: a team lead checks the need, and a budget holder approves the cost. Permissions decide who sees which requests, so staff raise requests for their own work while managers and finance see the queues they are responsible for approving. That visibility keeps requests moving.
What Details Must A Requisition Include?
Keep it to the essentials: the item or service, the reason it is needed, the preferred supplier, the expected cost, the quantity or seats where relevant, the date it is needed by, and the budget it belongs to. A quote or link helps the approver judge price. Anything beyond that should be optional, so the form stays faster than buying without it.
How Is A Requisition Different From A Purchase Order?
A requisition is internal: an employee asks the business for permission to buy. A purchase order is external: after approval, the business instructs the supplier to deliver on agreed terms. The requisition comes first and justifies the spend; the order follows and commits it. Small teams may skip formal orders for tiny buys, but skipping the requisition removes the approval itself.
Should Renewals Use Requisitions Too?
Yes, in a lighter form. A renewal repeats a purchase, so it deserves the same questions: is the tool still used, at the right level, at the agreed price? Raise the request before the notice window closes, attach usage and terms from the register, and let the approver decide while cancelling or renegotiating is still possible, not after the charge lands.
