Procurement Template: Three Stages, Then Yours
Requested, In Review, Approved. It is a deliberately small starting point, because approval thresholds are the one thing no template can guess. Add your stages once, and every request after that is visible.
Runs on Cloud and Self-Hosted · Not an ERP, and this page is clear about the boundary
What the Procurement template sets up
Choosing Procurement starts the project on a board with the Procurement Workflow, which is three statuses: Requested, In Review, and Approved. Each purchase request is a card. Work is grouped into task groups, which most teams use as cost centres or as categories. Three stages is intentionally minimal, because approval routing is specific to every organisation and any default would be wrong for you. The template gives you a queue with a front door and an approval gate, and the stages you add are the ones that match your own thresholds.
Three stages, as a foundation
Approved is where the shipped workflow ends, which is not where procurement ends. Add Vendor Selection, Ordered, Received, and Closed so a request is only finished when the goods have arrived and the invoice matches.
What you get on day one
Who picks this one
The stages and fields to add straight away
- Vendor Selection, between In Review and Approved
- Ordered, so the queue shows what has been placed
- Received, confirmed by whoever takes delivery
- Closed, once the invoice matches what was approved
- Estimated value, which decides the approval path
- Cost centre, so spend rolls up to the right budget
- Category: software, hardware, services, travel
- Needed by date, which is different from the raised date
- Approval thresholds by value, and who approves each band
- When legal or compliance review is required
- How many quotes are needed above each threshold
- The supplier due diligence checklist everyone must complete
Once your queue is configured, save the project as your own template. Your version carries the task groups, tasks, labels, task types, and workflow automation rules into every future procurement project.
What this template fixes
Start a project from this template
- 1Agree the approval thresholds firstValue bands, who approves each, and when legal is required. This is the actual work, and the tool part takes minutes.
- 2Create a project and choose ProcurementThe project opens on a board with Requested, In Review, and Approved in place.
- 3Add the stages you are missingVendor Selection, Ordered, Received, and Closed. Approved is not the end of procurement.
- 4Add the submission fieldsEstimated value, cost centre, category, and needed by date. Value and category are what decide the approval route.
- 5Build the due diligence checklistReferences, insurance, terms, data processing agreement. Reusable, so every supplier gets the same check.
- 6Give requesters accessUnlimited users on every plan means everyone who raises a request can watch it, which removes most of the chasing.
- 7Set the budgetEnter budgets at the project or cost centre level so committed spend is tracked as approvals happen.
- 8Review where the queue stallsMonthly. It is nearly always either approval sitting with a busy person, or waiting on a vendor to reply, and those need different fixes.
The features this template leans on
Procurement template FAQ
What statuses does the Procurement template create?
Why only three stages?
Is Orangescrum a procurement or ERP system?
How do we make approvals auditable?
Should the request close at Approved?
Can requesters see their own requests?
Where should supplier contracts be stored?
Can we track spend against a budget?
Give procurement a queue people can see
Three stages to start, your approval routing added in the first hour.