1
Enter requestor and department details
Fill in your full name, job title, department, and email address at the top of the form. This identifies the person accountable for the request and provides a contact for follow-up.
π‘ If your organization uses employee ID numbers for expense tracking, add yours here β it speeds up cost-center validation in the finance system.
2
Assign a requisition number
Use your organization's sequential numbering format β for example, REQ-2026-0042. If no system exists, create one using YYYY-NNNN so requests sort chronologically.
π‘ Record the number in a shared departmental log the moment you assign it, before the form is submitted, to prevent duplicate numbers.
3
Set the submission date and required-by date
Enter today's date and the latest date by which you need the goods or services. Factor in your supplier's typical lead time when setting the deadline.
π‘ Add three to five business days to the supplier lead time to account for internal processing β requisitions rarely move through approval in under a day.
4
List each item with a specific description and quantity
Use a separate row for each distinct item. Include make, model, size, or specification β not just a category name. State the quantity and the unit of measure.
π‘ Attach a screenshot or product link for items with multiple variants β this eliminates back-and-forth between procurement and the requestor.
5
Estimate unit costs and calculate line totals
Look up current pricing from a supplier website or last purchase order. Enter the estimated unit cost and multiply by quantity to populate the line total. Sum all lines for the total estimated spend.
π‘ If the actual price is unknown, use the highest reasonable estimate β it is easier to release unused budget than to request a top-up approval.
6
Enter the account and cost-center code
Confirm the correct GL account and cost-center code with your finance team before submitting if you are unsure. A wrong code creates rework at month-end close.
π‘ Keep a one-page cheat sheet of your department's most-used cost codes taped inside a supply cabinet or saved in a shared folder.
7
Write the business justification
In two to three sentences, explain what the items are for, which project or operation they support, and what would be delayed or disrupted without them.
π‘ Frame the justification around the operational consequence of not having the items β approvers respond faster to impact statements than to feature descriptions.
8
Route for approval and file the signed copy
Submit the completed form to the authorizing manager. Once signed and dated, send a copy to procurement and retain the original in your department's records.
π‘ Scan or photograph the signed form immediately β paper requisitions go missing, and a digital backup protects the audit trail.