A procurement plan template sets out what goods or services you need to buy, how you will choose a supplier, and the timeline and budget for the purchase. It gives everyone involved one agreed plan before any vendor is contacted.
It is the document that decides how a purchase will be made before anyone speaks to a supplier. It records the requirement, the business reason, the sourcing route, how bids will be judged, the key dates and the money available.
Procurement teams and project leads write one for any purchase large or risky enough to need a competitive process. Some organisations call it a procurement management plan when it covers every purchase in a project rather than a single buy.
Procurement plans pay off in approvals and audits. With the method and criteria written down first, nobody can say the winning supplier was chosen on a whim.
Project name and ID, requesting department, plan owner, approval date and status.
What is being bought, why the business needs it and where the scope stops.
Make-or-buy view, market conditions, the method (RFI, RFP, RFQ or direct award) and the contract type.
A weighted evaluation matrix covering price, quality, delivery and past performance, plus a shortlist target.
Dates from plan approval to contract signature and delivery.
Cost lines, contingency, the budget code and who approved the funds.
Ready to use in Word, Google Docs and PDF. Fill it in, save it, reuse it.
The requester explains what is needed, why now and what happens without it.
Turn the need into a specification, with must-haves separated from nice-to-haves.
Check suppliers, typical prices and lead times, then decide whether to make or buy.
Pick the sourcing route and contract type, and fix the weighted selection criteria.
Schedule each milestone, confirm funding and get the plan approved.
A simple procurement plan fits on one page: What, Why, Budget, Method, Selection criteria, Deadline, Owner. Add market research and risks for larger or riskier purchases.
Each section has a short prompt in the download. Keep entries specific enough that someone outside the project could run the purchase from the plan alone. The sample shows the level of detail to aim for.
Project name and ID, requesting department, plan owner, approval date and current status.
Description of the goods or services, business justification, quantities and what is out of scope.
Make-or-buy analysis, supplier market, the procurement method and the contract type: fixed price, cost-reimbursement or time and materials.
Weighted criteria for price, quality, delivery and past performance, the scoring scale and how many suppliers to shortlist.
Dates for approval, market engagement, responses, evaluation, award and delivery.
Cost lines, contingency, budget code and the approver of the funds.
Supply, price, delivery and compliance risks, each with an owner and a response.
Who signs off the plan and the award, and who manages the contract after signature.
1. General and administrative information Project name and ID: [CRM replacement, PRJ-2027-014] Requesting department: [Sales operations] Plan owner: [Procurement manager, name] Approval date and status: [Draft, for approval 20 Jan 2027] 2. Statement of requirements and scope Description: [Cloud CRM for 120 sales and support users, with email and calendar sync] Business justification: [Current CRM reaches end of support in June 2027, and pipeline reports take two days to compile.] In scope: [Licences, implementation partner, data migration of 85,000 records, training] Out of scope: [Marketing automation, to be planned separately]
Illustrative sample for a fictional company, Orbit Analytics. Replace every bracketed entry.
The example continues the sample above. It shows how the sourcing strategy and selection criteria sections look once completed, using illustrative figures.
| Section | Entry |
|---|---|
| Make or buy | Buy: building a CRM in-house is not viable for a 120-user team |
| Market conditions | Many established suppliers, pricing per user per year, discounts common for multi-year terms |
| Procurement method | RFP to five suppliers, shortlist of three for demos |
| Contract type | Fixed price: three-year subscription plus fixed-fee implementation |
| Shortlist target | Three suppliers scoring 3.5 or above on paper responses |
Scores from 1 to 5. Weighted total = sum of score × weight.
| Criterion | Weight | Supplier A | Supplier B | Supplier C |
|---|---|---|---|---|
| Price | 30% | 4 | 5 | 3 |
| Quality and functionality | 30% | 5 | 3 | 4 |
| Delivery and implementation | 20% | 3 | 4 | 4 |
| Past performance and references | 20% | 4 | 3 | 5 |
| Weighted total | 100% | 4.10 | 3.80 | 3.90 |
Illustrative scores. Supplier A wins on quality without being the cheapest.
A reusable template saves the team rewriting the same headings for every project. The aim is a document a budget owner can start on their own, with procurement completing the sourcing sections.
Use the eight sections above as headings, in the same order every time.
Under each heading, add a one-line prompt and fixed options for method and contract type.
Decide the spend level above which a full plan is required, and when one page is enough.
Run one live purchase through it, then cut any section nobody could fill in.
Most delays come from underestimating evaluation and legal review, so give each a full fortnight. Build the budget from total cost, not just the headline price, so implementation and training are funded too.
| Week | Milestone | Owner |
|---|---|---|
| 1 | Plan approved | Head of sales ops |
| 2-3 | Requirements signed off | Requester |
| 4 | RFP issued to five suppliers | Procurement |
| 7 | Responses due and scored | Evaluation panel |
| 8-9 | Shortlist demos and references | Evaluation panel |
| 10-11 | Negotiation and legal review | Procurement, legal |
| 12 | Contract signed, implementation booked | Plan owner |
Illustrative twelve-week schedule for the sample CRM purchase.
| Budget line | Amount |
|---|---|
| Licences, year 1 (120 users × 900) | 108,000 |
| Implementation partner, fixed fee | 25,000 |
| Data migration | 6,000 |
| Training | 4,000 |
| Contingency, 10% | 14,300 |
| Total year 1 | 157,300 |
Illustrative figures. Check software prices against pricing benchmarks before setting the budget.
The plan says what will happen; the action plan tracks whether it is happening. Keep it to tasks someone can finish in a week or two, and mark anything late in red at the weekly check-in.
| Action | Owner | Due | Status |
|---|---|---|---|
| Confirm user count with sales and support | Requester | 27 Jan | Done |
| Draft RFP requirements | Procurement | 3 Feb | Done |
| Agree evaluation panel and weights | Plan owner | 3 Feb | Done |
| Collect security questionnaires | IT security | 24 Feb | In progress |
| Book supplier demos | Procurement | 3 Mar | In progress |
| Confirm budget code with finance | Finance partner | 10 Mar | Overdue |
Illustrative action plan for the sample CRM purchase.
Every procurement plan starts with a request. Spendflo runs intake and approvals in one place.
See how it worksRequest for information: a first look at the market before requirements are fixed.
Request for proposal: suppliers propose a solution and price against your requirements.
Request for quotation: suppliers price a clearly specified product or service.
Buying from one supplier without competition, usually below a threshold or where only one can deliver.
One agreed price for the defined scope, so the supplier carries the cost risk.
Paying for hours and materials used, suited to work that is hard to define up front.
Set weights before responses arrive, so scoring cannot be shaped around a favourite.
Mark which requirements are essential, so suppliers know what rules them out.
Include implementation, training and contingency, not just the purchase price.
Two weeks is a sensible default for anything with a new contract.
Update dates and status weekly so approvers see the real position.
Early vendor conversations can quietly shape the requirement around one product.
An unclear scope invites change requests and price increases after award.
The cheapest bid often costs more once delivery and quality problems arrive.
Someone must manage the supplier after signature, or the plan's benefits slip.
Meet the requester and complete sections 1 and 2, including what is out of scope.
Check likely suppliers, typical prices and lead times, and note the make-or-buy decision.
Pick the sourcing route and contract type, and agree weights with the evaluation panel.
Build the timeline backwards, total the budget and send the plan for sign-off.
Orbit Analytics plans a CRM purchase for 120 users. Market research puts licences near 900 per user a year, so the budget rises from an early 120,000 estimate to 157,300 once migration, training and 10% contingency are added. Supplier B is cheapest, but Supplier A wins 4.10 to 3.80 on the weighted matrix. The contract is signed in week 12. Illustrative example.
Every part on this page, in Word, Google Docs and PDF, with the examples filled in.
One page covering what, why, budget, method, criteria and deadline. Three quotes and a signed approval are usually enough.
Add security review, integrations and renewal terms to the requirements, and benchmark prices before setting the budget.
One plan listing every package in a project, each with its method, budget and dates, approved once at the start.
Best for formal approval and audit files.
Best when several teams fill in sections.
Plan and action plan, ready to print.
Budget with real numbers. Spendflo pricing benchmarks show what others pay for software.
See pricing benchmarksA good procurement plan fixes the requirement, method, criteria, timeline and budget before anyone talks to a vendor. That makes the decision defensible and the approval quick.
Quick answers to what people ask most about the procurement plan template.
Start with the requirement and business reason, then research the market, choose the sourcing method and contract type, set weighted selection criteria, and add a timeline and budget. Get it approved before contacting suppliers. Download the template to follow the eight sections in order.
There is no single official list, but most versions follow the five rights of purchasing: the right product or quality, quantity, price, place and time. A procurement plan writes each of them down before sourcing starts. Download the template to capture them in one document.
A common seven-step version is: identify the need, define requirements and budget, research suppliers, request proposals or quotes, evaluate and select, negotiate and contract, then receive, pay and review. The procurement process steps guide covers each one, and you can download the plan template to cover the first six.
A procurement plan is a document that sets out what will be bought, how the supplier will be chosen, when each step happens and what it will cost. It is agreed before sourcing starts. You can download a ready-made template from this page.
You can download it free from this page in Word, Google Docs or PDF. It includes the eight-section plan, a worked example with a weighted selection matrix, a timeline, a budget table and an action plan.
Procurement
Purchase orders
Contracts
Vendor management
Sourcing and RFx
Budgets and business cases
Accounts payable
Purchasing
Software buying
Supply chain
Spendflo runs intake, approvals, software pricing benchmarks and contracts, so the planned purchase is approved, priced and signed in one place. Budgets are coming soon.
Enter your work email and we'll unlock every format.
Didn't start, or need another format? Pick one below.
Google Docs: upload the file to Google Drive, then open it with Google Docs.
