A purchase requisition is the internal step before a purchase order: someone on the job asks to buy something, says why, codes it to a cost code and estimates the cost, and someone with authority approves it before purchasing commits the company to a supplier. It turns “the super ordered it” into a decision someone can see and check against the budget.
How it works
- The need is raised. The field or the project team records the items, quantities, where and when they’re needed, a suggested supplier and the cost code.
- It’s estimated. An estimated unit cost and total, from a quote or recent pricing.
- It’s reviewed against the budget. The approver checks the cost code’s budget and what’s already committed, and whether the item is already in someone’s subcontract.
- It’s approved, returned or rejected by someone other than the requester, with a note.
- Purchasing issues the PO. The approved requisition becomes a purchase order to the supplier, which becomes the commitment that receipts and invoices are matched to.
Requisition vs purchase order
| Purchase requisition | Purchase order | |
|---|---|---|
| Audience | Internal | The supplier |
| Commits money | No | Yes, once accepted |
| Prices | Estimate | Agreed price and terms |
| Who prepares it | Field or project team | Purchasing or the PM |
| What it’s matched to | The budget | Receipts and the supplier’s invoice (three-way match) |
Why it matters
Purchases made without an approved request show up as cost nobody expected, often coded to the wrong line, and sometimes for scope a subcontractor already owns. A requisition gives the PM one look at the budget before the money is spent, and gives purchasing a clean record to build the PO from. Tying a requisition to an approved submittal also stops material being ordered against a revision that was later superseded.
Worked example
Illustrative: the superintendent requests 40 fire-rated access panels for the level 3 corridors, coded to 09 29 00, estimated at $185 each, $7,400 total, needed on site in three weeks. The PM sees the cost code has $21,000 of budget left with $16,500 already committed, so this request would put the line $2,900 over. She checks the drywall subcontract, finds access panels are in the sub’s scope, and returns the request with a note to issue them through the sub instead. No PO is written and no cost is double-counted.
Common mistakes
- The requester approving their own request.
- Approving without looking at the cost code’s remaining budget and commitments.
- Ordering by phone and writing the requisition afterward.
- Buying material already included in a subcontract.
- Changing quantities or prices after approval without a new review.
How os.construction handles it
The Purchase Requests tool records the items, supplier, cost code, delivery location, reason and estimated cost, and shows the cost code’s current budget figures next to the estimate. A reviewer other than the requester approves, returns or rejects it with a note, and editing an approved request creates a new revision that needs its own review. An approved request can be turned into one draft purchase order, which is executed as a separate step. A request can be prepared from an approved submittal revision, and it shows when that submittal has since been superseded. See commitments and budget.
FAQ
What is a purchase requisition in construction?
A purchase requisition is an internal request, usually from the field or the project team, to buy materials, equipment or services. It records what is needed, the quantity, the supplier if known, where and when it's needed, the cost code and an estimated cost. Once approved, purchasing turns it into a purchase order with the supplier.
What is the difference between a purchase requisition and a purchase order?
A requisition is internal: it asks for permission to buy and commits nothing to the supplier. A purchase order is sent to the supplier and, once accepted, is a commitment to pay for the goods on its terms. The requisition comes first; the PO is the contract.
Who approves a purchase requisition?
Usually the project manager or someone with spending authority for the job, set by the company's approval limits. Good control means the person approving isn't the person who asked, and the approver can see the cost code's budget and what is already committed against it.
Is a purchase requisition needed for every purchase?
Not always. Many contractors require them above a dollar threshold, for anything not already in a subcontract, or for long-lead and stock items, and let small field purchases go on a card with a receipt. Set the rule in writing and apply it consistently.