Vendor governance meeting: agenda, indicators and minutes template
A vendor governance meeting is a short, recurring review in which the contract owner and the vendor go through the month's service levels, consumption and invoicing, the vendor's improvement plan and the contract's upcoming dates, then record decisions and actions with an owner and a due date. A workable format is thirty minutes and six agenda points, held monthly for critical contracts, quarterly for major ones and once a year before the notice deadline for minor ones, with one-page minutes sent within 48 hours. The figures are prepared before the meeting, by the customer, from its own readings.
What the meeting is for
It is where figures, decisions and actions meet: service credits are settled rather than forgotten, disputes on invoices are cleared, renewal dates are seen early, and actions from last time are checked. It is not a sales presentation, and it is not where the vendor reports on itself unchallenged.
Two references frame the habit. ISO/IEC 20000-1:2018, Service management system requirements, has an abstract that addresses customers requiring a consistent approach from all their service providers, including those in a supply chain. For entities within the scope of the NIS 2 Directive, Article 21(2)(d) of Directive (EU) 2022/2555 lists supply chain security among the required measures, and Article 21(3) asks entities to take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of their suppliers' products and cybersecurity practices; a regular review is one place to gather that evidence (see the NIS 2 compliance checklist).
Frequency and attendees
| Contract criticality | Frequency | Attendees |
|---|---|---|
| Critical: a stoppage halts production, invoicing or security within a day | Monthly | Contract owner (chair), IT buyer, vendor account manager and service manager, security officer when security is on the agenda |
| Major: a stoppage degrades service, with a workaround | Quarterly | Contract owner, vendor; buyer before a deadline |
| Minor: a stoppage is a nuisance | Yearly, before the notice deadline | Contract owner, vendor |
These frequencies are a proposal; write yours into the contract's governance schedule so that the vendor commits to attend and to send its figures on time. The contract owner chairs and signs the minutes; the buyer holds the budget, the credits and the dates; the vendor presents its improvement plan but does not write the record.
The six-point agenda
- Minutes 0 to 3: round table and status of last review's decisions, read from the decision log.
- Minutes 3 to 10: service levels for the month: indicators against target, major incidents, service credits due.
- Minutes 10 to 17: consumption and invoicing: committed spend, forecast against budget, disputed invoices.
- Minutes 17 to 23: improvement plan and vendor-side projects.
- Minutes 23 to 28: contract matters: upcoming deadlines, amendments, exit readiness.
- Minutes 28 to 30: decisions, actions, date of the next review.
Indicators to review
| Area | Indicator | Source |
|---|---|---|
| Service | Availability, resolution time, on-time rate, Met or Missed, credits computed | Your monthly readings against the contract schedule |
| Incidents | Number of priority 1 incidents, recurring incidents, root-cause analyses outstanding | Ticketing tool |
| Money | Spend to date, full-year forecast, variance against budget | Budget line of the contract |
| Contract | Days to the notice deadline, pending amendments | Contract register |
| Follow-up | Open and overdue actions, days overdue | Decision log |
| Exit and security | Exit readiness, subcontractor changes, security incidents notified | Exit checklist, security clauses |
Put the figures on screen from minute three: the vendor comments on numbers you already hold. The notice dates come from the IT contract register, which is also where a decision to renegotiate is recorded.
The improvement plan
When an indicator misses its target more than once in a period you have set, ask the vendor for a written plan: cause, corrective action, owner on the vendor side, date, and the expected effect on the indicator. Review it at every meeting until the indicator holds. If it does not, the escalation path, the service credits and any termination right for repeated failure are those of the contract: check them with your lawyer under its governing law before relying on them.
Minutes template (fictitious data)
Vendor review, managed network contract C-07, 15 October 2026. Attendees: contract owner (chair), IT buyer, vendor account manager, vendor service manager.
- Service, September: availability 99.82% against 99.9% (missed); on-time rate 96% against 95% (met). Credit under the schedule (1.5% of the monthly fee of 24,000 per tenth of a point missed): 0.8 × 1.5% × 24,000 = 288, below the 10% cap (2,400).
- Money: full-year forecast 3% above budget, driven by two extra site connections ordered in July.
- Contract: notice deadline 31 January 2027, 108 days away: renewal position needed.
- Overdue from last review: update of the exit plan, 12 days late.
| ID | Type | Subject | Owner | Due date |
|---|---|---|---|---|
| R-31 | Decision | Credit note of 288 to appear on the November invoice | IT buyer | 2026-11-10 |
| R-32 | Action | Root-cause analysis of the 4 October outage | Vendor service manager | 2026-10-29 |
| R-33 | Action | Updated exit plan, including data export formats | Vendor account manager | 2026-11-05 |
| R-34 | Decision | Renewal options (renegotiate or re-tender) to the steering committee | Contract owner | 2026-11-30 |
Next review: 12 November 2026. Minutes sent within 48 hours; the vendor has one week to object, after which they stand as the agreed record, if the governance schedule says so.
FAQ
Who writes the minutes?
The customer: the contract owner or the buyer. The vendor receives them and may object within the period agreed in the governance schedule.
Should the vendor send its report before the meeting?
Yes, a few days before, in a fixed format. Compare it with your own readings so that the meeting starts from agreed figures.
Can several contracts with one vendor share a meeting?
Yes, with one section per contract and a single decision log, so that each decision stays attached to its contract.