HEW-NODE-0143 · How Education Works · contract management, supplier performance, service-level agreements, key performance indicators, change control, remedies, vendor lock-in, transition, exit planning, knowledge transfer, data portability, contract renewal and education procurement
The most important day in a procurement is often not the day the contract is signed.
It is the first ordinary Tuesday six months later, when schools are using the service, invoices are arriving, staff have forgotten the tender language, the supplier has changed personnel, one integration is failing and nobody can remember whether the contract ever defined what “available” was supposed to mean.
Procurement creates a contract. Contract management determines whether that contract becomes a dependable education service.
This node sits beside the How Education Works hub, Education Procurement, Education Procurement Framework Agreements & Dynamic Purchasing Systems, Budget Execution & Public Expenditure Tracking, Education Financial Audit & Assurance, Education Internal Controls & Fraud Risk Management and Education Digital Public Infrastructure & Public Digital Learning Platforms.
Those pages keep their jobs. Procurement owns competition, tendering and contract award. Framework Agreements owns repeated purchasing architecture. Budget Execution owns the movement of approved money. Audit owns financial assurance. Internal Controls owns fraud and control design. This node owns the post-award operating relationship: how education authorities turn contractual promises into measurable service, manage supplier performance and change, protect knowledge and data, apply remedies proportionately, and preserve continuity when the contract ends.
The 60-Second Read
- A signed contract is not a managed service.
- Contract management begins before award because service levels, data rights and exit terms must already be written.
- Service levels should measure what matters to the education service, not what is easiest for the supplier to report.
- Availability percentages can hide long outages during critical periods.
- KPIs and service levels perform different jobs.
- Supplier performance should include quality, responsiveness, security, continuity and educational fit where relevant.
- Change control prevents informal scope drift.
- Contract variations should preserve value-for-money and authority requirements.
- Invoice approval should connect to verified delivery.
- Remedies should create repair incentives rather than turn every minor failure into litigation.
- Repeated underperformance needs escalation rules.
- Critical services need named continuity obligations.
- Data ownership, export formats and knowledge-transfer duties should be clear before problems appear.
- Vendor lock-in often grows gradually through integrations, proprietary formats and staff dependence.
- Exit planning should begin at contract design, not three months before expiry.
- Transition plans need activities, owners, milestones, assets, data, interfaces and acceptance criteria.
- Extensions should be decisions, not defaults caused by late planning.
- Contract closure should reconcile data, assets, final payments and unresolved obligations.
- Post-contract review should feed lessons into the next procurement.
- The goal is a service that remains governable from mobilisation to exit.
One-Sentence Definition
Education contract management is the disciplined governance of a supplier relationship after award, covering mobilisation, service levels, performance, payments, changes, risk, remedies, knowledge, data, renewal, transition and exit.
The First Distinction: Procurement Is Not Contract Management
Procurement chooses a supplier and forms an agreement. Contract management asks whether the supplier delivers the agreed service over time and whether the agreement still protects the education system as needs change.
A brilliant tender can fail in operation if the post-award governance is weak.
The Second Distinction: SLA Is Not KPI
A service-level agreement usually defines a measurable service commitment such as response time, restoration time or system availability. A key performance indicator can be broader, tracking trends such as satisfaction, backlog, error rates or improvement.
Some KPIs trigger contractual consequences; others guide management. Mixing the two creates confusion about what failure actually means.
The Third Distinction: Exit Is Not Failure
Every fixed-term contract ends eventually. A planned transition at expiry is normal governance, not a hostile event. Treating exit as something relevant only when the supplier fails is one reason organisations become locked in.
Current Public-Sector Guidance Treats Exit as Part of Contract Design
The UK Government’s Digital, Data and Technology Playbook states that planning for contract end is essential to avoid new legacy IT and recommends early attention to knowledge transfer, data return, support, assets, decommissioning and transition. The updated Government Functional Standard GovS 008: Commercial similarly treats transition and exit as defined contract-management responsibilities.
OECD public-procurement work also treats performance measurement across the procurement lifecycle, including contract management, as a core governance function rather than a separate administrative afterthought.
Contract Management Begins During Specification
If a contract does not define service levels, data return, intellectual-property rights, change procedures, escalation and exit assistance, the contract manager cannot invent strong rights later simply because they would be useful.
The post-award operating model should therefore influence the tender before suppliers bid.
Define the Service, Not Only the Product
A learning platform licence may include hosting, support, updates, security patches, integrations, data exports and teacher training. If the contract names only the software product, expectations around these service components can become ambiguous.
Mobilisation Is the First Test
- implementation plan;
- named supplier and authority leads;
- data migration;
- security review;
- integration testing;
- user acceptance;
- training;
- service desk setup;
- baseline performance;
- asset and licence register;
- go-live criteria;
- fallback if mobilisation slips.
A rushed mobilisation can create defects that persist through the entire contract because everyone later treats them as normal operating conditions.
Write Service Levels Around Educational Consequence
A 99.5 per cent monthly uptime target sounds strong. But if the system is unavailable during national examination registration or the first morning of school, the average can conceal serious harm.
Critical windows, severity levels and time-of-day conditions can matter more than one headline percentage.
Measure Response and Restoration Separately
A supplier can respond to an incident in five minutes and take two days to restore service. Both metrics matter. Response shows acknowledgement and mobilisation; restoration shows when the user gets the service back.
Define Incident Severity Before the Incident
A login problem for one user is not the same as a nationwide identity outage. Severity classes should specify scope, consequence and target response rather than allowing classification to be renegotiated while the service is failing.
Use KPIs to See the Direction of Travel
- open incidents;
- repeat incidents;
- first-contact resolution;
- average restoration time;
- security patch timeliness;
- data-quality defects;
- integration failures;
- support satisfaction;
- unplanned change failure rate;
- teacher or school support burden;
- contractual deliverables on time;
- backlog age;
- cost variance;
- service-credit events.
The most useful dashboard distinguishes isolated failure from repeated deterioration.
Performance Meetings Need Evidence
Monthly meetings become ceremonial when every discussion relies on supplier slides. The authority should retain access to independent usage, incident, invoice and technical evidence where proportionate.
Invoice Approval Should Follow Delivery Evidence
Payment controls should connect invoice line items to contract rates, accepted milestones and verified service where appropriate. This is different from refusing payment whenever a minor SLA misses. The contract defines what is billable and which failures trigger credits or remedies.
Service Credits Are Not Compensation for Every Harm
A service credit can create a simple financial consequence for missed performance. It may not reflect the full educational or administrative cost of failure. Treat credits as one management mechanism, not proof that a failure has been made harmless.
Remedies Should Escalate
- informal correction;
- formal incident review;
- service-improvement plan;
- enhanced reporting;
- service credits or contractual remedies;
- senior escalation;
- step-in or contingency measures where contracts permit;
- termination only when proportionate and legally justified.
A contract manager needs a repair ladder rather than only two choices: tolerate or terminate.
Change Control Protects Both Sides
Education needs change. New policy, curriculum, data or security requirements can alter the service. Formal change control records what changes, why, price impact, delivery timing, risk and authority.
Without it, small informal requests accumulate until neither side can reconstruct the actual scope.
Not Every Change Requires a Contract Variation
Some operational adjustments already sit within agreed scope. Others materially alter obligations and require formal variation under the applicable procurement and contract rules. The governance process should distinguish them rather than treating every configuration change as legal renegotiation.
Control Scope Creep
A supplier can become indispensable by continuously adding adjacent services. Each addition may seem efficient. Over time the authority may discover that data, expertise and integrations have concentrated in one provider.
Contract review should ask whether convenience today is creating switching cost tomorrow.
Vendor Lock-In Has Several Forms
- proprietary data formats;
- undocumented interfaces;
- exclusive licences;
- custom workflows only the supplier understands;
- staff skills tied to one tool;
- integrations built around one ecosystem;
- high egress fees;
- long renewal notice periods;
- intellectual-property restrictions;
- no practical export of historical records.
Lock-in is rarely one clause. It is the accumulated cost of leaving.
Maintain an Authority Knowledge Base
If only the supplier knows how the service works, the authority is not managing the service. Architecture diagrams, runbooks, configuration records, interface documentation, decision logs and contact maps should remain current enough for continuity.
Knowledge Transfer Should Be Contractual
Staff turnover happens on both sides. Knowledge-transfer requirements reduce dependence on particular individuals and make transition feasible later.
Data Return Needs a Format and Clock
“Supplier will return all data on termination” is weaker than a clause defining formats, metadata, encryption, timing, validation and deletion certification. Export rights that cannot be exercised operationally are not true portability.
Exit Planning Starts at Day One
The UK DDaT Playbook recommends early planning for contract end because exit affects knowledge transfer, data, support, assets and legacy risk. Education authorities should apply the same principle to critical learning and administrative services.
An Exit Plan Needs More Than a Date
- exit scenarios;
- trigger dates;
- outgoing supplier duties;
- incoming supplier or in-house responsibilities;
- data extraction and validation;
- knowledge transfer;
- asset and licence transfer;
- user-account migration;
- interface transition;
- parallel running where needed;
- security revocation;
- records retention;
- acceptance criteria;
- final payment conditions;
- contingency if transition slips.
Test Exit Before You Need It
Periodically export data, restore a sample in another environment or rehearse key transition steps. A data-export clause that has never been tested can fail exactly when bargaining power is weakest.
Extensions Should Be Analysed, Not Drifted Into
Late procurement planning can turn extension into the only safe option. This weakens competition and can preserve poor service. Renewal calendars should begin early enough to compare recompetition, extension, insourcing, replacement and redesign.
Supplier Concentration Is a Portfolio Risk
One supplier may perform several unrelated services across identity, devices, cloud hosting and learning software. Each contract can look reasonable individually while the overall estate becomes dependent on one corporate failure or commercial negotiation.
Portfolio review should therefore track total exposure, not only contract-by-contract performance.
Critical Suppliers Need Continuity Plans
If a supplier becomes insolvent, suffers a major cyber incident or exits the market, which services stop? Which data remain accessible? Which licences expire? Which functions have substitutes?
Continuity planning is especially important for systems that schools cannot operate manually for long.
Contract Closure Is a Controlled State
- services accepted or handed over;
- final data returned;
- accounts removed;
- supplier access revoked;
- assets reconciled;
- open incidents transferred;
- final invoices reconciled;
- credits or claims settled;
- records archived;
- confidential data deleted as required;
- lessons captured.
Post-Contract Review Improves the Next Tender
Which service levels mattered? Which never changed behaviour? Which supplier evidence was difficult to verify? Which exit clause was missing? Which requirement inflated cost without improving service?
Contract management should return evidence to procurement rather than ending in an archive box.
Case Study: The 99.9 Per Cent Platform
Invented example: a platform meets 99.9 per cent monthly uptime but experiences three forty-minute outages during the first hour of school on separate Mondays. Technically the SLA passes; operationally teaching is repeatedly disrupted.
The authority redesigns the SLA to include critical teaching windows and repeated-incident thresholds rather than relying only on monthly availability.
Case Study: The Data Export Nobody Tested
Invented example: a student-information contract guarantees full data export. At re-procurement, the export arrives as flat files without historical relationships or field definitions.
The next contract defines schema documentation, metadata and annual portability tests. Exit becomes an operating capability rather than a legal promise.
Case Study: The Informal Change
Invented example: over three years, school administrators request many “small” custom features through email. The supplier delivers them, then claims they are outside support when the platform is upgraded.
A formal change register would have recorded whether each request changed scope, support obligations and price.
Case Study: The Extension by Default
Invented example: a contract expires in six months. Re-procurement was never started, so changing supplier would threaten continuity. The authority extends at weak negotiating terms.
The repair is portfolio-level renewal planning with trigger dates twelve to twenty-four months ahead for critical contracts.
Failure Modes and Repairs
- Tender finished, governance finished: repair with a named contract owner and operating plan.
- SLA vanity metrics: repair by measuring educationally consequential service conditions.
- Supplier-only reporting: repair with independently available operational evidence.
- Informal scope drift: repair with proportionate change control.
- Remedy only at termination: repair with escalation and service-improvement stages.
- Knowledge lives with vendor staff: repair through documentation and transfer duties.
- Portable in law, trapped in practice: repair with tested export formats and metadata.
- Exit begins at expiry: repair by designing transition at contract formation.
- Extension by panic: repair with early commercial-option review.
- Contract-by-contract blindness: repair by monitoring supplier concentration across the portfolio.
The Education Contract Management Operating Chain
- Define the post-award operating model before tender.
- Write measurable service commitments.
- Define evidence sources.
- Define remedies and escalation.
- Define change control.
- Define data, IP and knowledge rights.
- Define exit and transition obligations.
- Award the contract.
- Mobilise the service.
- Validate baseline performance.
- Operate service-level monitoring.
- Review KPIs and incidents.
- Verify invoices.
- Run supplier-performance meetings.
- Require improvement plans when thresholds are breached.
- Control scope and variations.
- Maintain authority knowledge.
- Monitor supplier concentration and continuity risk.
- Test data portability.
- Review exit plan periodically.
- Start renewal analysis early.
- Choose extend, compete, replace, redesign or insource.
- Run transition.
- Validate data and service handover.
- Close access and accounts.
- Reconcile final financial obligations.
- Archive contract records.
- Capture lessons for the next procurement.
A Contract Management Dashboard
- contracts by criticality;
- service-level compliance;
- repeat incidents;
- open service-improvement plans;
- invoice disputes;
- contract variations;
- unresolved data or security issues;
- supplier concentration;
- portability test date;
- exit-plan version;
- knowledge-transfer completeness;
- renewal decision deadline;
- contracts inside twelve months of expiry;
- transition risks;
- closure actions outstanding.
Canonical Owner Boundaries
- Education Procurement owns sourcing, tendering and contract award.
- Education Procurement Framework Agreements & Dynamic Purchasing Systems owns repeated purchasing architectures.
- Budget Execution & Public Expenditure Tracking owns approved-budget execution and spending flow.
- Education Financial Audit & Assurance owns financial audit and assurance.
This node owns post-award service governance: mobilisation, service levels, supplier performance, contract change, remedies, knowledge, portability, renewal, transition and exit.
The Return Path
Return to that ordinary Tuesday six months after award.
The tender team may have moved on. Schools have not. They need the service to work, the data to remain safe, problems to be repaired, invoices to match delivery and the education system to retain enough knowledge and leverage to change course later.
The contract manager’s job is therefore not clerical administration. It is preserving governability across time.
A good education contract is not merely enforceable when things go wrong. It is operable while things are still going right.
Return to the How Education Works hub.