Construction Purchase Requisition Template: Which Fields Do You Need?

Why does a consistent structure help field and purchasing teams?

A free-form message is easy to send but may leave the purchasing manager without a unit of measure, specification, or delivery location. A short, consistent structure gathers the information needed for the next step and reduces follow-up questions.

The goal is not a long form. Keep fields that support selection, ordering, or receipt. If a field is only relevant to some requests, define when it is required instead of making the team enter a meaningless value.

Fields to include in a requisition

Start with the request context: project, requester, and date. Then describe the item clearly enough for another person to order it without guessing. Give each item separate fields for its quantity and unit of measure.

A required delivery date is not the same as an urgency level. State the date and the operational impact of a delay. For site receipt, identify the unloading point and receiving contact. Do not include personal information that is unnecessary for handling the request.

• Project and internal requisition number
• Requester name and role
• Item description, specification, and code if available
• Quantity and unit of measure
• Required delivery date and reason for urgency
• Jobsite, unloading point, and receiving contact
• Budget category and approver required by company procedure
• Relevant documents or drawings

A short example you can copy

The following fictional example illustrates the structure. Adapt the item specification to the project's technical requirements; a generic description is not a substitute for an approved specification.

• Project: Example Site A; requisition: REQ-001
• Requester: Site supervisor
• Item: As specified in the attached document; code: ITEM-01
• Quantity: 100; unit of measure: each
• Required date: Complete before submitting
• Delivery: Site warehouse, coordinated with the receiving contact
• Budget: Relevant materials category
• Status: Awaiting specification review and approval

What should you check before creating a purchase order?

Confirm that the specification is clear, the quantity meets the need, and no parallel request exists for the same materials. Check available stock against the records and a field verification. A request with a missing specification should remain incomplete until the responsible person approves it.

Once the supplier and terms are agreed, create a purchase order linked to the requisition. If the quantity or specification changes, document the difference and the required approval. The requisition preserves the original need; the purchase order records what was agreed with the supplier.

How to adopt the template without adding friction

Try the structure on a few requests over one week. Note which details purchasing still has to chase and which fields do not help. Update the template to reflect real work and assign someone to maintain its definitions.

When moving to a system, check how each field is represented and what carries through to the purchase order. Every screen does not need every detail, but the person approving an order or receiving a delivery should easily find the information needed for the decision.

Frequently asked questions