The controls that protect contract value, from mobilisation to exit

A practical checklist for Scottish social housing contract managers and commercial leads, built around the Procurement Reform (Scotland) Act 2014 and PCIP

Value in a social housing contract isn’t won at award. It’s protected, or lost, in the months and years that follow, and in Scotland that post-award period is scrutinised more closely than many teams realise. Your contract management is assessed directly through PCIP, the Procurement and Commercial Improvement Programme, and the evidence it draws on has to be in place across the whole term, not assembled the week before an assessment.

Even a contract that was awarded impeccably will underdeliver if the foundations aren’t right. Unclear ownership. No audit trail. Invoices approved without validation. Performance discussed on the basis of what the supplier says rather than what the data shows. Community benefit commitments that were promised at tender and then quietly stopped being tracked. These are the gaps that cost money and leave you exposed when your annual procurement report comes due or a Freedom of Information request lands.

This free checklist gives contract managers and commercial leads a practical tool to use from mobilisation through to exit. It covers the five areas where controls most commonly break down, flags where Scottish regulations and PCIP place specific expectations on you, and sets out the minimum evidence you need on file to be audit-ready at any point. It’s written for contracts regulated by the Procurement Reform (Scotland) Act 2014 and the Public Contracts (Scotland) Regulations 2015.

Inside this free checklist

The checklist covers five areas of contract management where good controls protect service outcomes and value for money.

Set-up and mobilisation. The decisions made in the first weeks of a contract set the conditions for everything that follows. The checklist covers what to confirm before go-live: a named contract manager and senior responsible owner with deputies in place, a complete handover pack from procurement, a contract management plan pitched at the right tier, a single contract file with clear permissions and version control, and a governance cadence already in the diary. It also prompts you to make sure the file reflects how the regulated process was run and how community benefit requirements were set, and to complete conflict of interest declarations before go-live.

Governance, roles and record-keeping. Good governance isn’t about more meetings. It’s about the right decisions being made by the right people, documented clearly, and traceable when someone asks later. This section covers RACI documentation, delegated authority, decision logs, minutes and action tracking, and proportionate senior oversight. It matters here because PCIP assesses the clarity of roles, the quality of record-keeping and the robustness of your evidence trail directly, so strong governance lifts your assessment rating.

Performance and outcomes. This is where most contract value is sustained or quietly eroded. The checklist covers how to structure KPIs and SLAs, how to validate performance data rather than take it at face value, and how trend analysis surfaces problems before they escalate. It sets out a clear underperformance pathway from early warning through to formal remedies, and it covers how to translate community benefit requirements into measurable indicators tracked through the year, so the evidence is ready for your annual procurement report rather than scrambled together at year end.

Financial control and value for money. Paying for delivery that hasn’t been evidenced is one of the most common and most avoidable sources of contract loss. This section covers invoice validation against contract terms and performance evidence, spend tracking against budget and forecast, handling price change and indexation claims through the correct governance route, and tracking both cashable and non-cashable value. PCIP assesses financial control and value for money evidencing too, so the aim is spend that’s tracked against contract terms and value that’s demonstrated rather than assumed.

Change, risk, compliance and transparency. Contracts change. The question is whether those changes are managed in a way that’s disciplined, documented and legally sound. The checklist covers risk and issue logs, change control, supplier viability monitoring, and information governance including GDPR and the Freedom of Information (Scotland) Act 2002. It sets out how to confirm the legal basis for each modification against the permitted grounds in the Public Contracts (Scotland) Regulations 2015, since changes beyond those grounds can require a new procurement. It closes with a quick reference on Scottish publication duties, including the contract award notice on Public Contracts Scotland, and a minimum evidence list so you know exactly what to keep on file.

Who it’s for

This checklist is written for contract managers and commercial leads in Scottish social housing.

Contract managers and commercial leads who want a structured, practical framework to apply from day one of mobilisation rather than building their own from scratch. Procurement managers who want to be sure the handover from award to contract management doesn’t open up a compliance gap. Finance directors and heads of finance who need confidence that invoices are being validated, spend is tracked against budget, and the evidence trail is there if it’s ever needed. Any social housing organisation that wants a straightforward way to sense-check its post-award controls ahead of a PCIP assessment or an annual procurement report.

Good contract management isn’t about adding process for its own sake. It’s about having the right controls in place so the value you committed to at award is actually delivered, the obligations Scotland’s framework places on you are met consistently, and the evidence to prove it is always within reach.

Frequently asked questions

What’s the difference between a contract management plan and a contract management checklist in Scotland?

They do different jobs and work best together. A contract management plan is specific to one contract. It sets out how that contract will be managed across its term: who’s responsible for what, how performance is measured and reported, the governance cadence, how changes are handled, and the escalation routes. The detail should reflect the risk and value of the contract, so a complex, high-value delivery contract needs a fuller plan than a low-risk supply arrangement. A checklist works differently. It’s a structured prompt that confirms the key controls are in place at each stage, whichever contract you’re managing. It doesn’t replace the plan, it helps you check the plan has actually been implemented and nothing critical was missed during mobilisation or governance setup. For teams managing several contracts at once, a checklist is also how you keep consistency across a portfolio without relying on people to remember every obligation. In Scotland, having both matters because your contract management is assessed through PCIP and evidenced in your annual procurement report, and a plan without consistent implementation leaves gaps that are hard to explain if scrutiny follows.

What should be included in a contract handover pack from procurement in Scotland?

The handover from procurement to contract management is one of the highest-risk moments in the whole lifecycle, and it’s routinely underinvested in. When it’s rushed, the contract manager starts without the context they need, and that gap shows up later as performance problems, invoice disputes or compliance failures that were avoidable. A complete pack should include the signed contract and schedules, a summary of the key commercial terms including pricing, indexation and break clauses, the KPIs and SLAs agreed at award, the supplier’s key contacts and the agreed governance structure, any live risks identified during procurement, and the publication triggers that apply. For Scottish regulated contracts it should also capture how community benefit requirements were set during the procurement, since those commitments have to be tracked through the term and evidenced in the annual procurement report. A good test: if the contract manager left tomorrow, could their replacement pick up the contract and manage it competently from day one using what’s in the file?

How should we handle contract underperformance in a Scottish social housing context?

Managing underperformance well needs two things a lot of organisations don’t have at the same time: a clear process everyone understands, and the performance data to apply it objectively. Without both, underperformance gets managed through relationships and conversations rather than evidence, which makes it harder to escalate and harder to defend if the supplier pushes back. The starting point is an underperformance pathway documented in the contract management plan before any issues arise, moving through defined stages: early warning when performance trends the wrong way, a corrective action plan with agreed milestones, escalation when that isn’t working, and the formal remedies set out in the contract. Each stage should be triggered by validated data rather than judgment, which means your KPI framework and validation approach need to be robust from mobilisation. In Scotland there’s a reporting dimension too: where community benefits form part of the contract, sustained underdelivery against them has to be visible in your annual procurement report, so tracking it properly through the year is what keeps both the commercial and the reporting position defensible.

What financial controls should be in place for social housing contracts in Scotland?

Financial control is about more than paying invoices on time. It’s about making sure every payment links to evidenced delivery, that spend is tracked against budget and forecast consistently, and that the financial picture of the contract is always visible to the people who make decisions about it. Invoice validation is the most fundamental control and one of the first to slip under pressure. Invoices should be checked against the contract terms, the pricing schedule and performance evidence before approval, with discrepancies documented and escalated rather than resolved informally. Beyond that, the framework should include spend tracking at the agreed cadence, a route for assessing and approving price changes and indexation through the correct authority, a log of cost variations with rationale and approvals, and benefit tracking covering both cashable savings and non-cashable value. PCIP assesses exactly this, financial control, invoice validation and value for money evidencing, so you should be able to show that spend is tracked against contract terms and that value for money is demonstrated rather than assumed. For members procuring through PfH Scotland frameworks and using Quantum, consolidated spend visibility and invoice validation reduce the admin of all this without reducing the level of control.

What publication and transparency obligations apply to contracts in Scotland?

Scotland’s transparency requirements sit under the Procurement Reform (Scotland) Act 2014 and the Public Contracts (Scotland) Regulations 2015, and they’re distinct from the Procurement Act 2023 that applies in England and Wales. A contract award notice has to be published on Public Contracts Scotland within 72 days of awarding a regulated contract, and a copy should be retained in the contract record. If your organisation’s annual regulated spend exceeds £5 million, you’re required to publish and maintain a procurement strategy and to publish an annual procurement report, which covers actual expenditure, whether objectives were met, and the community benefits delivered, for regulated contracts above £50,000. Community benefit delivery has to be evidenced in that report wherever requirements were included, which is a live consideration on contracts at or above £4 million. Significant contract modifications, in value, term, scope or ownership, may trigger a fresh award notice, so publication should be assessed whenever a contract changes. And because information about regulated contracts can be subject to Freedom of Information (Scotland) Act 2002 requests, someone needs to own FOI handling and keep contract records in a retrievable format. The practical point is to confirm who’s responsible for each of these at mobilisation, rather than working it out case by case when a duty is triggered.