Public Service ITSM Reference

Playbooks

Supplier management under public procurement

Turning contracts into managed services: KPIs, reviews, exit and assurance.

Most relevant to Central gov Wider public Suppliers

The public sector difference

Public bodies buy under procurement law. Contracts are harder to renegotiate, changes may need publishing, and poor performance needs evidence to act on. So supplier management starts before the contract is signed.

Before contract

Make sure the contract includes:

  • a clear service description and service levels tied to user outcomes, not just component uptime;
  • KPIs suitable for publication where the Procurement Act 2023 requires them;
  • service credits or other remedies that are proportionate and actually used;
  • security requirements: certifications (Cyber Essentials, ISO/IEC 27001), right to audit, vulnerability and patching timescales;
  • incident and breach notification timings short enough for your own legal deadlines;
  • data protection terms, data location and sub-processor approval;
  • ITSM integration: how tickets, changes and problems flow between you;
  • FOI and records cooperation;
  • an exit plan: data return, knowledge transfer, parallel running and costs.

During the contract

Activity Frequency Evidence it produces
Service performance review Monthly Performance against service levels and KPIs, incidents, problems
Security and risk review Quarterly Vulnerabilities, audit findings, certification status, sub-processor changes
Relationship and improvement review Quarterly or six-monthly Improvement plan, user feedback, roadmap
Contract performance assessment As the Procurement Act requires Published assessment for in-scope contracts
Exit plan refresh Annually Current, tested exit plan

Record supplier performance issues as you go: the incident, its impact, and what was agreed. Under the Procurement Act, documented poor performance can matter well beyond the current contract.

Suppliers: what customers will ask of you

If you supply IT services to public bodies, expect:

  • to provide evidence for their assurance schemes (DSPT, CAF, GovAssure) as well as your own certifications;
  • incident notification within hours, not days;
  • cooperation with FOI requests and audits;
  • transparency about sub-contractors and offshoring;
  • to align with their ITSM processes, especially change and major incident.

Exit

Exit is where public sector contracts most often go wrong. Test the exit plan, keep data portable, and make sure knowledge is documented in your own systems, not only in the supplier's.