Turn purchasing needs into clear, reviewable requisitions.
Collect request category, department or project, item or service details, quantity, estimated cost, vendor status, justification, required date, budget status, urgency, alternatives, and requester contacts.
Creates an editable copy in your workspace.
Preview the visitor experience, then copy everything into your own workspace.
Ready to customize
Start with a working structure, then make the messaging, logic, branding, and next steps your own.
Use this template for businesses, schools, nonprofits, associations, facilities teams, project offices, and other organizations that review internal requests for goods, software, subscriptions, equipment, professional services, or operational resources.
Client intake guide
A purchase requisition form is an internal request for permission to obtain goods, software, subscriptions, equipment, or services. It records the business need before an authorized person commits organizational funds.
A requisition is not a purchase order. Approval, supplier engagement, contracting, payment, and ordering happen later under the organization's procurement policy.
Collect enough context for a manager, budget owner, or purchasing team to understand need, timing, likely cost, and available alternatives.
No need to rebuild the flow from scratch.
Add the template to your workspace with its questions, outcomes, and flow intact.
Update the copy, logic, colors, lead capture, and completion actions for your audience.
Share a hosted page or add the experience to your website, campaign, or bio link.
Create an editable copy and adapt every question, outcome, color, and next step to your audience.
The requisition asks for internal approval. A purchase order is an authorized commercial document sent to a supplier after required review. Do not provide a requisition number as though it were a supplier-facing order number.
State who can approve spending and prevent requesters from ordering, signing, or telling a supplier to begin work before authorization.
Ask for a realistic estimate and explain whether taxes, delivery, installation, licences, renewals, maintenance, currency conversion, or implementation costs should be included. An estimate is not a final price.
Required-by dates should reflect genuine operational need and normal purchasing lead time. Marking every request urgent weakens prioritization and may bypass useful competition or due diligence.
A preferred supplier can provide useful context, but requesters should explain whether the vendor is approved, incumbent, uniquely qualified, or simply suggested. Purchasing teams may need competitive quotes or another supplier.
Disclose personal, financial, family, gift, referral, or other conflicts under the organization's policy. This Free form does not collect quote files, contracts, tax records, banking details, or supplier credentials.
Use budget-status choices as planning context, not proof of available funds. Define thresholds, cost-centre ownership, delegated authority, finance review, IT or security review, and legal review outside the generic form.
Do not include card numbers, bank details, passwords, access keys, confidential bids, personal identifiers, or sensitive employee or customer data. Use secured systems for necessary financial, legal, security, or supplier records.
Provide an accessible submission alternative and test keyboard, screen-reader, and mobile use. Explain who receives requests, retention, and the expected response period.
A reviewer should approve, decline, request clarification, or propose an alternative with a concise reason. If timing changes, tell the requester rather than leaving the requisition without an owner or status.
