From award to renewal - in one place.

Does it track social value delivery?

Yes. Commitments captured at award are tracked through the lifecycle. Suppliers report quarterly through the portal.

Can it track CO₂ and ESG commitments?

Yes. Carbon reduction and ESG obligations tracked against supplier delivery with automated reporting against your baseline.

Does it generate Contract Change Notices?

Yes. When a material modification is flagged, the system generates the required PA23 Contract Change Notice for publication.

What contract management covers after award

Contract management is the ongoing work of making sure a supplier delivers what was bought, that the authority meets its own obligations, and that changes, disputes, renewals and exit are handled deliberately rather than by default. It spans the contract register, obligation tracking, performance monitoring, relationship governance, variation control, risk management, financial reconciliation and the decision about what happens at the end of the term.

The transition from procurement to delivery is where most of it breaks. The procurement team holds the tender, the evaluation record and the commitments accepted at award. The service manager holds the day to day relationship. If the commitments do not travel from one to the other in a usable form, they simply stop existing. Social value pledges are the clearest example: scored at tender, celebrated at award, then never mentioned again.

A contract management approach does not have to be heavy. Most authorities have a small number of contracts that warrant intensive management and a long tail that needs little more than an accurate record, a renewal date and a named owner. Applying the same level of rigour to everything is a good way to apply it properly to nothing.

The contract register: the thing most authorities get wrong first

A contract register is the foundational asset and it is remarkably often incomplete. The test is not whether a register exists but whether it can answer basic questions immediately: what contracts expire in the next six months, which ones have automatic renewal clauses, which supplier holds the largest aggregate exposure across departments, and who owns each one by name. Most registers built in spreadsheets can answer the first question and none of the others.

Completeness matters because the gaps are where uncontrolled spend lives. Contracts that were let quickly, extended informally or inherited through a service transfer are the ones missing from the register, and they are disproportionately the ones that cause problems. Reconciling the register against accounts payable data is an uncomfortable but revealing exercise, and it usually surfaces suppliers being paid regularly under no live contract at all.

The register also has an external face. Contract details notices and, for larger contracts, performance information are published under the Act, so the internal record and the public record need to agree. An authority that publishes from a register it trusts spends far less time on transparency compliance than one that assembles publications by asking around.

• Named owner for every contract, not a team mailbox
• Expiry, break and renewal dates with automated lead time alerts
• Aggregate supplier exposure visible across departments
• Register reconciled periodically against actual spend

Turning tender commitments into tracked obligations

The contract is the terms plus the specification plus everything the supplier committed to in its winning response. That last part is where the value promised at evaluation actually sits, and it is the part most likely to be lost. The practical fix is to extract obligations at mobilisation into a structured list: what is promised, by when, by whom, how it will be evidenced, and what happens if it is not met. This is tedious work done once and it pays for itself repeatedly.

Obligations run both ways. Authorities routinely fail to provide the data, access, decisions or client side resource a contract requires, then attribute the resulting delay to the supplier. An obligation register that includes the authority's own commitments changes the tone of governance meetings and, more usefully, prevents the authority from creating a claim against itself.

Mobilisation is also the moment to set the measurement regime properly. If a KPI cannot be measured from data that will actually exist, it will be reported as a narrative and the narrative will always be broadly positive. Agreeing the data source, the reporting frequency and the definition of each measure before the service starts avoids a year of arguing about whether performance is good.

Performance management that changes behaviour

Performance monitoring only works if something happens as a result of it. A monthly report that is filed and never discussed teaches the supplier that performance is a documentation exercise. A short, structured governance meeting that reviews a small number of meaningful measures, agrees actions with owners and dates, and escalates when actions are missed, changes behaviour within a couple of cycles.

Choose few measures and make them matter. Five well chosen indicators covering delivery, quality, user experience, commercial position and social value commitments will drive more improvement than thirty measures reported in a pack nobody reads. Where a measure is not improving, the useful question is usually whether the contract mechanism supports improvement, not whether the supplier is trying hard enough.

The Act's contract performance notice regime gives this an external dimension for larger contracts. Where performance against KPIs, or a breach or poor performance, has to be published, the internal record needs to be robust enough to support publication. That is a healthy discipline, because a measure you would be uncomfortable publishing is usually one you do not fully trust.

Variations, extensions and the limits on change

Contracts change. Volumes shift, requirements evolve, legislation moves and services get reorganised. The Procurement Act 2023 permits modification in defined circumstances, including changes provided for in the original contract through clear review clauses, and modifications that are not substantial. Some modifications trigger a contract change notice, and some changes are simply not permissible because they would alter the contract so significantly that it should have been re competed.

The practical risk is cumulative drift. Individually small variations, each reasonable on its own, add up over three years into a contract materially different from the one that was tendered. Recording every variation against the original contract, with the value impact and the legal basis for the change, is what allows an authority to see the cumulative position before it becomes a problem rather than after.

Extensions deserve particular care because they are so easy. An extension exercised because nobody started the re procurement in time is a decision made by inertia, and it is the most common route to a contract running years beyond its intended life. Building the re procurement start date into the register, working backwards from expiry with a realistic lead time, converts extension into a choice.

• Record the legal basis for every modification, not just the change itself
• Track cumulative variation value against the original contract
• Diarise the re procurement start date, not just the expiry date
• Treat extension as a decision requiring justification

Risk, assurance and supplier financial health

Supplier failure is rare and expensive, and it is usually visible in advance to anyone looking. Monitoring the financial position of strategically important suppliers, watching for changes in ownership, group structure or filing behaviour, and keeping an honest view of how quickly a service could be transferred elsewhere, is standard practice for critical contracts. The judgement that matters is not whether a supplier might fail but how long the authority could operate if it did.

Assurance evidence also decays. Insurances lapse, certifications expire, key personnel named at tender leave, and subcontractors change. Contract management should refresh these on a cycle rather than trusting a snapshot taken at award. Where a contract depends on named individuals or specific accreditations, the change control process should cover them explicitly.

Risk should be proportionate. A high value, hard to replace, safety relevant contract justifies continuous attention. A low value commodity supply does not, and pretending otherwise consumes the capacity that the important contracts need. Segmenting the portfolio by criticality rather than by value alone is the fastest improvement most authorities can make.

Renewals, exit and re procurement

The end of a contract should be planned from the start. Exit provisions, data return, transition assistance, TUPE implications, asset ownership and intellectual property need to be workable, not just present. The moment an authority discovers its exit arrangements are inadequate is usually the moment it has already decided to leave, which is exactly when it has the least leverage.

Re procurement lead times are routinely underestimated. A meaningful competition needs time for review of the current arrangement, market engagement, specification development, publication, evaluation, standstill, award and mobilisation. Working backwards from expiry, an above threshold service contract can easily need the best part of a year. Registers that alert twelve months before expiry are not being cautious, they are being realistic.

The end of a contract is also the best available source of intelligence for the next one. What did the specification get wrong, which KPIs proved meaningless, where did variations cluster, what did the market tell you during delivery that it did not tell you during procurement. Capturing that at exit, while people still remember, is worth more than any amount of desk research at the start of the next competition.

Sector specifics and route to market

Local authorities typically hold the largest and most varied contract portfolios with the smallest central contract management capacity, which makes segmentation and automation essential rather than optional. NHS bodies manage a mix of Procurement Act contracts and Provider Selection Regime arrangements, often with clinical governance requirements layered on top. Housing associations carry long running repairs and major works contracts where cumulative variation and building safety obligations are the dominant risks.

Education buyers manage many small contracts across sites, where the register itself is often the main gap. Charities delivering public services frequently manage contracts as both supplier and commissioner, and utilities operate under a distinct regime, including utilities dynamic markets which replaced qualification systems under the Act, with the ability to charge suppliers membership and award fees and to run member only tenders.

Where a contract came from a Dynamic Market, contract management feeds back into market health. Members that consistently underperform, or that no longer meet the conditions for membership, need to be dealt with through the market's own rules rather than informally excluded from future competitions, since Dynamic Markets are permanently open and membership cannot be capped.

How eSourcing Data supports contract management

eSourcing Data covers source to contract in a single platform, so the contract record inherits the tender, the winning response, the evaluated commitments and the evaluation trail rather than starting empty. Obligations, KPIs, variations, renewal dates and assurance expiry live against the same record, and governance, analytics and reporting give heads of service a portfolio view rather than a folder per contract.

That continuity is the point. Contract management tools bought separately from sourcing tools tend to be populated by hand, which means they are populated partially and then trusted incorrectly. Data is held in the UK and the platform operates in line with GDPR, and audit functions record who changed what, which matters when a variation is questioned two years later.

Buyers can access eSourcing Data software through RM1557.15 G-Cloud 15, where 28 software services are listed on the Digital Marketplace alongside cloud support services, purchased as call off contracts. Where the constraint is capacity rather than software, outsourced procurement and consulting support can run competitions or manage a contract portfolio on an authority's behalf.