Public Service ITSM Reference

Government

The Service Standard and live services

What the GOV.UK and NHS service standards expect of services once they are live.

Most relevant to Central gov NHS England

The standards

The GOV.UK Service Standard has 14 points that government services must meet. The NHS service standard adapts it for health and care in England. Both are assessed mainly during development (discovery, alpha, beta), but several points are about running a live service, which is where ITSM comes in.

Points that matter for live services

Service Standard point What it means once live ITSM practice
Solve a whole problem for users Support covers the whole journey, including offline and assisted routes Service desk, relationship management
Provide a joined-up experience across all channels Phone, face-to-face and online give consistent outcomes Service design, knowledge management
Make sure everyone can use the service Accessibility is maintained through change, not tested once Change enablement, service validation and testing
Iterate and improve frequently Continuous, safe change based on user feedback Change enablement, release, continual improvement
Create a secure service which protects users' privacy Security and privacy are operated, monitored and improved Information security management
Define what success looks like and publish performance data Measures like completion rate, user satisfaction and cost per transaction Service level management, measurement and reporting
Operate a reliable service Uptime, monitoring, incident response and recovery Monitoring, incident, problem, availability, continuity

"Operate a reliable service"

This point is the closest to classic ITSM. Assessors will want to see that the team:

  • monitors the service and alerts before users notice problems;
  • has a tested way to respond to incidents, including out of hours;
  • can deploy safely and often, and roll back;
  • has planned for the service being unavailable, including how users are told and helped;
  • learns from incidents.

Bridging agile teams and ITSM

Digital service teams often work in a product-led, agile way, while central IT runs ITIL processes. Agree a lightweight path: standard changes for automated pipelines, a shared incident process, and clear handover of support responsibilities before a service goes live. Neither side should have to work around the other.

Accessibility and the accessibility statement

Live services must keep meeting the accessibility regulations and keep their accessibility statement accurate. Build accessibility checks into release testing.