S106 Spend Deadlines: What Happens When Developer Money Expires

Your council holds £2 million in unspent S106 contributions across 140 live agreements. Some of those contributions have spend-by deadlines expiring in the next 12 months. Do you know which ones?

This is the question that keeps planning obligations officers awake in December — and it's the question that spreadsheet-based monitoring systems answer poorly, if at all.

This guide covers how S106 spend-by deadlines work, what happens when they're missed, and how to build a deadline tracking process that prevents your council from returning developer money.

This covers England only. This is general guidance, not legal advice. Always refer to the specific clawback terms in each S106 agreement and consult your legal team on repayment obligations.

How S106 Spend-By Deadlines Work

Most S106 agreements include a clawback clause: if the council doesn't spend a financial contribution within a specified period, the developer can demand it back — often with interest. The legal basis for these obligations sits within each individual agreement, but GOV.UK planning obligations guidance sets out the broader framework for how planning obligations should be drafted and enforced.

The mechanics vary by agreement, but the typical structure is:

Trigger: A development milestone (commencement, occupation of the Nth dwelling, phase completion) activates the obligation
Payment: The developer pays the contribution (usually indexed to BCIS or RPI)
Spend-by period: The council has a fixed period — typically 5 to 10 years from receipt — to spend the money on its specified purpose
Clawback: If unspent after the deadline, the developer can request a refund of the unspent portion, sometimes with interest

The spend-by clock starts at receipt, not at the trigger point. This matters because there can be months between the trigger activating and the developer actually paying. If you're tracking deadlines from the wrong starting date, your calculations are wrong.

What Happens When a Deadline Is Missed

The Developer Requests a Refund

The clawback clause in the S106 agreement is a contractual right. When the spend-by period expires, the developer (or their successor in title) can write to the council requesting return of unspent funds.

The council's legal position depends on the exact wording of the agreement:

Automatic refund clauses require repayment on expiry with no council discretion
Request-based clauses require the developer to actively request a refund — if they don't ask, the money stays (but this is not something to rely on strategically)
Interest provisions may add simple or compound interest from the date of receipt — turning a £200,000 clawback into £230,000+ depending on the rate and duration

Not every developer will request a refund. Some won't notice, some won't bother, some will have dissolved. But with the Home Builders Federation actively publicising the scale of unspent contributions, developers are increasingly aware of their clawback rights.

The Reputational and Political Cost

Beyond the direct financial loss, missed deadlines create:

Audit findings. External auditors review S106 holding accounts. Contributions past their spend-by date with no allocation are flagged.
Member scrutiny. Councillors asking why developer money intended for a new playground was returned to a housebuilder because nobody tracked the deadline.
Community impact. The infrastructure that contribution was meant to fund doesn't get built. Residents see the development but not the promised school places, highway improvements, or open space.

The January 2026 Parliamentary debate on the S106 system explicitly raised the issue of unspent contributions — this is now a matter of national political attention, not just local operational risk.

Why Deadline Tracking Breaks Down

Problem 1: No Receipt Date Recorded

The spend-by clock starts on receipt. But many councils record the obligation amount and the agreement date — not the date the money actually arrived in the holding account. Without a receipt date, you can't calculate when the deadline expires.

Fix: When finance confirms an S106 receipt, immediately record the receipt date against the specific obligation. This is a 2-minute task that prevents a six-figure problem.

Problem 2: Deadlines Calculated But Not Monitored

Some councils have a "spend-by date" column in their spreadsheet. That's a start. But a date in a column is not an alert system. Nobody opens the spreadsheet on the first of every month to check which deadlines are approaching.

Fix: Deadline management needs active alerts — at 18 months, 12 months, 6 months, and 3 months before expiry. Whether that's calendar reminders, automated emails, or a dashboard with a countdown view, the deadline must find the officer — the officer shouldn't have to go looking for it.

Problem 3: Allocation vs Spend Confusion

A contribution is "safe" from clawback when it's spent — not when it's allocated. Earmarking £150,000 for a school extension project doesn't stop the spend-by clock. The money needs to be disbursed — invoices paid, contracts completed, evidence recorded.

Councils often allocate contributions to a project years before the project actually spends the money. If the project is delayed and the contribution sits allocated-but-unspent past the deadline, the developer can still request a clawback.

Fix: Track spend status separately from allocation status. An allocated contribution with an approaching deadline needs escalation to the service area responsible for the spend decision.

Problem 4: Service Area Disconnection

The planning team tracks the obligation. The finance team holds the money. The education team (or highways, or parks) decides how to spend it. None of these teams share a system, and none of them are watching the deadline.

Fix: Each obligation type needs a named service area contact who receives deadline alerts alongside the monitoring officer. If the education contribution has 12 months left and the education team hasn't committed to a project, the planning team needs to escalate — not wait and hope.

Building a Deadline Tracking Process

Step 1: Audit Your Current Exposure

Pull every financial contribution currently held by the council. For each one, record:

Field	Source
Agreement reference	S106 register
Obligation description	Agreement terms
Amount received	Finance system
Receipt date	Finance system
Spend-by period	Agreement terms
Spend-by deadline	Calculated: receipt date + spend-by period
Amount spent to date	Finance system
Allocation status	Service area confirmation
Responsible service area	S106 register

Sort by spend-by deadline. Everything within 18 months is your immediate priority.

Step 2: Categorise by Risk

Red — deadline within 12 months, not fully spent: Escalate immediately. Identify a project, confirm commitment from the service area, and establish a spend timeline.
Amber — deadline within 12–24 months, not fully allocated: Escalate to the service area for allocation. Monthly check-ins on project readiness.
Green — deadline beyond 24 months or fully spent: Monitor quarterly. No immediate action needed but don't lose track.

Step 3: Establish Alert Cycles

Set up recurring alerts for every financial contribution:

18 months before deadline: Initial alert to monitoring officer and service area contact. Confirm allocation.
12 months: Escalation if not allocated. Service area must confirm a project and spend timeline.
6 months: Senior officer escalation if allocated but not yet spent. Project team confirms spend is on track.
3 months: Final escalation. If spend is not imminent, consider whether partial allocation can be demonstrated.

Step 4: Report Quarterly

Run a quarterly at-risk report for senior leadership:

Total contributions at risk (deadline within 18 months, not fully spent)
Total value at risk
Actions taken since last report
Contributions successfully spent or allocated
Any clawback requests received

This report takes 30 minutes if your data is structured. It takes a full day if you're working from spreadsheets with inconsistent formats.

The Numbers That Matter

A few calculations that put S106 deadline risk in context:

A council holding £2 million in S106 contributions with an average spend-by period of 7 years has roughly £285,000 reaching deadline each year
If 20% of at-risk contributions are clawed back, that's £57,000 per year returned to developers — money that was meant to fund infrastructure your residents were promised
The cost of a single large education contribution clawback (£300,000–£500,000) dwarfs the annual cost of any monitoring system

The question isn't whether deadline tracking is worth the effort. It's whether your council can afford not to do it properly.

For the full monitoring process including deadline management, see our complete guide to S106 monitoring.

Need to check your deadlines right now? Use the free S106 Spend Deadline Calculator — enter receipt dates and spend-by periods to see exactly when each deadline expires, with calendar export.

S106Ledger is building automated deadline alerts and financial tracking — so your team sees approaching deadlines weeks in advance, not after the developer's solicitor sends a letter. Join the waitlist for early access.