Buying GuidesSoftware Buying

How to Build a Yearly Procurement Calendar: Renewals, Budgets and Supplier Reviews Month by Month

Build a yearly procurement calendar: map contract renewals, notice deadlines, budget cycles and supplier reviews month by month, with a template and owners.

Buying Guides: How to Build a Yearly Procurement Calendar: Renewals, Budgets and Supplier Reviews Month by Month

Most procurement problems in small and mid sized businesses are timing problems. A contract renews automatically because nobody noticed the notice deadline. A price increase lands after the budget was set. A key supplier's performance slips for months before anyone raises it. A yearly procurement calendar fixes this by putting every recurring purchasing decision on one dated plan, with an owner and enough lead time to act.

This guide shows how to build one: what to collect, how to set lead times, which four tracks to layer on the calendar, and a month by month template you can adapt to your fiscal year.

What a procurement calendar is and what it prevents

A procurement calendar is a shared schedule of every recurring purchasing event in the year. It covers when contracts renew, when you must give notice, when budgets are set, when key suppliers are reviewed and when recurring checks happen.

Without a calendar With a calendar
Contracts renew automatically on old terms Each renewal is reviewed and decided before the notice deadline
Price increases surprise the budget Expected increases are known before budgets lock
Supplier issues build up unnoticed Key suppliers are reviewed on a set rhythm
Leavers keep access to tools for months Access and seat reviews happen on schedule
Buying decisions bunch up at year end Work is spread across the year

It also supports good governance. The NIST Cybersecurity Framework 2.0 includes supply chain outcomes such as planning and monitoring supplier relationships over their life, and the CIS Controls v8.1 ask for recurring account and access reviews. A calendar is the simplest way to make those recurring tasks actually happen.

Step 1: Collect every contract, renewal date and notice deadline

Start from your contract list or software inventory. If you do not have one, our guide on how to build a SaaS software inventory shows how to find every subscription from payments, admin consoles and team surveys. Include non software suppliers too: facilities, insurance, logistics, professional services, telecoms and key materials.

For each contract, capture:

Field Where to find it
Supplier and contract name Contract, order form or invoice
Owner The manager accountable for the relationship
Annual value Accounting system
Start date, term and renewal date Contract or order form
Auto renewal (yes or no) Renewal clause
Notice period and notice deadline Termination or renewal clause
Price change terms Pricing or renewal clause
Criticality High, medium or low, based on cost, data and how hard it is to replace

If a contract is unclear, ask the supplier to confirm the renewal date and notice period in writing.

Step 2: Set lead times by contract size and risk

Work backward from the notice deadline, not the renewal date. The deadline is the last day you can cancel or change terms, so all review, negotiation and approval must be done before it.

Contract type Review starts before notice deadline Why
Low value, monthly or easily replaced 2 to 4 weeks Quick keep or cancel decision
Standard annual subscription 60 to 90 days before renewal Time to check usage and negotiate
High value or business critical 4 to 6 months before renewal Time to run alternatives, an RFP or a pilot
Multi year or complex services 6 to 12 months before renewal Time for a full tender and transition planning

For each contract, add two events to the calendar: review start and notice deadline. Invite the owner and the person who runs procurement.

Step 3: Add your budget cycle milestones

Procurement and budgeting depend on each other. Put your fiscal year milestones on the same calendar:

  • Budget kick off: when finance asks for next year's numbers.
  • Supplier and software review window: the weeks when owners confirm needs, seat counts and expected prices.
  • Budget submission and approval dates.
  • Fiscal year start: contracts renewing in the first quarter must be decided before this date.
  • Mid year budget check: compare actual spend with plan.

Price trends matter here. Gartner's October 2026 forecast projects worldwide software spending to grow 14.6% in 2027. Your own vendors may differ, but it is a reminder to check price terms before the budget locks. Our guide on how to plan your software budget covers the budget side in detail.

Step 4: Schedule supplier performance reviews

Not every supplier needs the same attention. Set review frequency by criticality.

Supplier tier Examples Review frequency What to cover
Critical Core systems, key materials, payroll provider Quarterly Service levels, issues, costs, roadmap, risk
Important Department tools, regular service providers Twice a year Performance, cost, user feedback
Routine Low value, easily replaced Annually, before renewal Still needed? Fair price?

Use a consistent scoring method so reviews are comparable over time. Our guide on how to build a vendor scorecard gives a template, and our guide on how to write a vendor SLA helps define what "good" looks like for service suppliers.

Step 5: Add recurring controls and compliance checks

Some procurement tasks are not tied to one contract but should happen on a rhythm:

Recurring task Suggested frequency
Software seat and usage review Quarterly
Access review for business applications Quarterly for critical systems, at least annually for all
Supplier risk and security questionnaire refresh Annually for critical and important suppliers
Insurance certificates and compliance documents from suppliers Annually, or at expiry
Software and contract inventory reconciliation Annually
Purchasing policy and approval limits review Annually

For access reviews, the CIS Controls v8.1 recommend disabling dormant accounts after 45 days of inactivity (Safeguard 5.3) and revoking access promptly on termination or role change (Safeguard 6.2). Our guide on how to run a year end access review explains the process.

Step 6: Lay it out month by month

Combine the four tracks. The template below assumes a January to December fiscal year with budgets set in the fourth quarter. Shift the months to match your own fiscal year.

Month Renewals and notice deadlines Budget cycle Supplier reviews Recurring controls
January Act on Q1 renewals; start reviews for April renewals New budget live; load renewals into plan Q1 review of critical suppliers Q4 access review results filed
February Start reviews for May renewals Confirm locked savings Seat and usage review
March Start reviews for June renewals Supplier compliance documents check
April Start reviews for July renewals; plan any RFPs for large Q4 renewals Q2 review of critical suppliers; half year review of important suppliers Quarterly access review
May Start reviews for August renewals Seat and usage review
June Start reviews for September renewals Mid year budget check
July Start reviews for October renewals Q3 review of critical suppliers Quarterly access review
August Start reviews for November renewals; run RFPs for large contracts Seat and usage review
September Start reviews for December renewals Budget kick off; owners confirm needs Annual review of routine suppliers due for renewal Supplier risk questionnaire refresh
October Start reviews for January renewals Draft budget with renewal decisions Q4 review of critical suppliers; half year review of important suppliers Quarterly access review
November Start reviews for February renewals; notice for early Q1 renewals Budget submission Inventory reconciliation
December Start reviews for March renewals Budget approval Year end access review

Add your actual contracts to the renewal column: for example "Notice deadline: CRM, January 30" in December or January, depending on lead time.

Step 7: Assign owners and set reminders

Every event needs one owner. Typical roles in a small business:

Role Calendar responsibilities
Procurement or operations lead Owns the calendar, adds new contracts, chases overdue reviews
Contract or tool owner Runs reviews, decides keep, change or cancel, attends supplier reviews
Finance Budget milestones, spend comparisons, price change checks
IT or security Access reviews, security questionnaires, offboarding checks
Leadership Approves high value renewals and RFP decisions

Set two reminders for each review start: one at the review start and one two weeks before the notice deadline. Link each calendar event to the contract record.

Step 8: Keep the calendar current

Review the calendar every quarter:

  • Add new contracts from the last quarter, with their deadlines.
  • Remove cancelled contracts and record why.
  • Update renewal dates after renegotiations or term changes.
  • Check for overdue reviews and missed deadlines, and fix the cause.

Make the calendar part of your small business purchasing process: no new contract is signed until its renewal date, notice deadline and owner are on the calendar.

Using the calendar for renewals and negotiations

A calendar only saves money if each review leads to a decision. For each renewal, confirm usage and need, compare price with alternatives, decide keep, right size, renegotiate or cancel, then act before the notice deadline. For tactics, see our guide to negotiating SaaS pricing and renewals. For large contracts where you want competing offers, schedule an RFP early using our guide on how to write an RFP. If you decide to leave, our guide on how to write a vendor contract termination notice helps you give notice correctly.

Common mistakes

  • Tracking renewal dates but not notice deadlines. The deadline is what matters.
  • Starting large reviews too late. Big contracts need time for alternatives and transition.
  • One person holds all the dates. Use a shared calendar so it survives holidays and staff changes.
  • Reviews without decisions. Record a decision and next action for every review.
  • Ignoring non software suppliers. Insurance, facilities and services renew too.

The bottom line

A yearly procurement calendar puts every renewal, notice deadline, budget milestone, supplier review and recurring check on one shared, month by month plan, with an owner for each. Build it from your contract list, work backward from notice deadlines, layer on your budget cycle and supplier reviews, and review it every quarter. Start this week by listing contracts that renew in the next six months and adding their notice deadlines.

Frequently asked questions

What is a procurement calendar?

It is a shared, dated plan of every recurring purchasing event in the year: contract renewals and notice deadlines, budget planning milestones, supplier reviews, tender or RFP windows and recurring checks. It turns procurement from reacting to invoices into planning ahead.

How far ahead should I start reviewing a contract renewal?

A common rule is 90 days before the renewal date for standard subscriptions and three to six months for large or complex contracts. Always check the notice period in the contract and start early enough to finish the review, negotiate and give notice before the deadline.

Which suppliers need quarterly reviews?

Review quarterly the suppliers that are expensive, hard to replace, hold sensitive data or are critical to daily operations. Smaller, low risk suppliers can be reviewed once a year, usually before renewal.

What tool should I use for a procurement calendar?

A shared calendar plus the contract or software inventory spreadsheet is enough for most small businesses. Each calendar event should link to the contract row. Contract management or procurement software becomes useful when you have many contracts and several people buying.

How does a procurement calendar fit with the budget cycle?

Place budget milestones on the same calendar. Supplier reviews and renewal decisions in the months before budgets lock give finance real numbers, and renewals early in the new fiscal year must be decided before the budget starts.

Sources

  1. NIST: The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29 (checked November 18, 2026)
  2. CIS Critical Security Controls Navigator v8.1 (checked November 18, 2026)
  3. Gartner: Gartner Forecasts Worldwide IT Spending to Grow 15% in 2027, Totaling $7.35 Trillion, press release, October 21, 2026 (checked November 18, 2026)

Related guidance