A purchase order request gives an authorised reviewer the information needed to decide whether the business should commit to a purchase. Prepare it before placing an order or accepting supplier terms, following the organisation’s actual purchasing process.
The request is not itself a purchase order or spending approval. Make its status clear so a supplier enquiry or internal draft does not become an unintended commitment.
Describe the business need
State what is required, why it is needed and when the work depends on it. Use a clear specification rather than only a familiar product name or a link that may change. Preparing requests is one way to demonstrate the document and coordination skills relevant to administration roles; keep that preparation distinct from the purchasing approval held by the authorised person.
Check whether suitable stock, an existing agreement or another approved arrangement already meets the need. Record the result instead of assuming every request requires a new supplier.
The Australian Government’s supplier guidance provides broader context for business supply arrangements. Follow the actual purchasing controls and obtain advice where terms, authority or requirements are unclear.
Use a practical request checklist
Provide:
- Need: purpose, intended use and relevant requirement.
- Specification: item or service description, quantity and acceptable scope.
- Timing: required delivery or completion point and its basis.
- Supplier information: verified proposal or quotation, where required.
- Cost: quoted amounts, currency, applicable charges and uncertainties to review.
- Budget: relevant reference and approval still needed.
- Receiving: location, contact and acceptance responsibility.
- Authority: approver and the point before which no commitment may be made.
Use the organisation’s required form or system. Attach only necessary documents through approved channels, especially where commercial or payment information is involved.
A fictional office purchase
In this invented example, an administrator requests twelve packs of stationery for an internal workshop. The request describes the pack contents, required arrival date, delivery contact and quotation reference.
The administrator labels the request “awaiting approval”. They may clarify information with the supplier under their role, but they do not say the order is confirmed or provide payment details before the authorised decision.
If the quotation expires before approval, the administrator obtains current information rather than assuming the earlier price and timing remain available. No real supplier, fee or stock availability is claimed in this example.
Make exceptions visible
If the request is urgent, explain the dependency and consequence rather than using urgency to bypass the controls. Identify any approved exception process and the person authorised to decide it.
Where only part of the requirement is clear, mark the missing information. A blank cost or delivery field should not be interpreted as zero cost or immediate availability.
Check whether changes after approval require a revised request or purchase order. Approval for one specification does not necessarily cover a different quantity, supplier or set of terms.
Carry the decision into the order process
Record the approval, refusal or request for more information. If approved, the authorised person or system should issue the purchase commitment under the actual process.
Keep the approved reference available to the person receiving the goods or service and to the relevant finance staff. Later invoice matching depends on being able to identify what was authorised and received. A complete purchase request creates that connection without confusing preparation with permission to spend.
