The Complete Guide to S106 Monitoring for Planning Officers

Your council signed dozens of section 106 agreements last year. Each one contains 5–15 individual obligations with different trigger points, financial terms, and spend deadlines. If you're tracking all of this in spreadsheets, you already know the problem.

This guide covers the practical reality of S106 monitoring — what you actually need to track, where monitoring typically fails, and how to build a process that stops contributions falling through the cracks.

This guide covers England only. This is general guidance, not legal advice. Always refer to the specific terms of each S106 agreement and consult your legal team on enforcement matters.

What S106 Monitoring Actually Involves

Section 106 of the Town and Country Planning Act 1990 allows local planning authorities to enter planning obligations with developers. Most guidance online focuses on negotiating these agreements — explaining what they are to homebuyers and developers. That's not what this guide is about.

For planning teams, the harder work starts after the agreement is signed. S106 monitoring means tracking every obligation from agreement to discharge. That covers six distinct activities:

• Agreement registration — recording terms, parties, land parcels, and each individual obligation as a separate tracked item
• Trigger point tracking — monitoring development milestones (commencement, occupation thresholds, phase completion) that activate obligations
• Financial tracking — recording contributions due, received, allocated to projects, and spent
• Deadline management — tracking spend-by periods (typically 5–10 years from receipt) before contributions must be returned to developers
• Compliance verification — confirming in-kind obligations (affordable housing units, highway works, open space) are delivered to the agreed specification
• Annual reporting — producing the Infrastructure Funding Statement required under the Community Infrastructure Levy Regulations 2010 (as amended)

Most planning officers know the list. What's less obvious is the scale of what goes wrong when monitoring breaks down.

Where S106 Monitoring Fails — and What It Costs

The Home Builders Federation found that the 171 councils surveyed — roughly half of all LPAs — held £2.8 billion in unspent S106 contributions, suggesting the true national figure is substantially higher. That includes contributions at risk of being returned to developers because spend deadlines are approaching or have already passed.

Officers at Bristol City Council reported managing 700+ live S106 agreements across multiple spreadsheets — describing the system as "not efficient or effective." Wokingham Borough Council described "years of unsatisfactory work with Excel spreadsheets and duplication." Both accounts were shared on the PAS Knowledge Hub S106 database discussion thread, which has drawn responses from planning officers across the country.

These aren't outliers. At most smaller district councils — the 150–200 LPAs managing 50–500+ live agreements — S106 tracking lives in a combination of spreadsheets, shared drives, and institutional memory. When a monitoring officer leaves, half the knowledge goes with them.

The consequences are specific:

• Missed spend deadlines mean developers can reclaim contributions — often with interest. A single missed deadline on a large education contribution could cost a council hundreds of thousands of pounds.
• Unrecorded trigger points mean contributions go uncollected. If a development reaches its 50th occupation and nobody records it, the indexed financial contribution tied to that milestone never gets invoiced.
• IFS reporting becomes a crisis. Regulation 121A of the CIL Regulations (inserted by the 2019 Amendment Regulations) requires every LPA to publish an annual Infrastructure Funding Statement by 31 December. Compiling this from unstructured spreadsheets takes days — and the accuracy is questionable.

The January 2026 Parliamentary debate on the S106 system confirmed this remains a live political issue, with the government signalling a full reset of S106 processes.

The Five Pillars of Effective S106 Monitoring

1. Structured Agreement Registration

Every S106 agreement should be recorded with a consistent structure the moment it's signed:

• Planning application reference and site address
• Agreement date and parties
• Each individual obligation listed separately — not buried in a paragraph summary
• Obligation type: financial contribution, in-kind delivery, restriction, or specific action
• Trigger point for each obligation, linked to a development milestone
• Financial terms: amount, indexation basis, payment schedule, spend-by period
• Responsible officer

The mistake most councils make is recording the agreement as a single entry. An agreement with 12 obligations needs 12 tracked items, each with its own trigger, deadline, and status. Thirty minutes of structured data entry per agreement saves days of forensic spreadsheet archaeology later.

2. Trigger Point Tracking

Triggers activate obligations. Common types:

• Commencement — development starts (usually evidenced by a commencement notice or building control notification)
• Occupation thresholds — e.g., "prior to occupation of the 50th dwelling"
• Phase completion — phased developments trigger different obligations at each stage
• Time-based — "within 12 months of commencement"

The challenge is that planning officers don't automatically know when these milestones occur. You need a process for receiving trigger notifications — whether from building control, site visits, or developer notifications required by the agreement.

Cross-referencing building control commencement and completion data against your S106 register monthly is the single most impactful process improvement for most councils. Missed triggers are the top source of lost contributions.

3. Financial Tracking

Financial contributions flow through four stages:

1. Due — trigger activated, contribution owed
2. Received — payment received from developer (check indexation)
3. Allocated — earmarked for a specific project or infrastructure
4. Spent — funds disbursed, evidence recorded

Each transition needs a date, a reference, and an audit trail. The spend-by deadline clock typically starts at stage 2 (receipt), not stage 1 (trigger).

Indexation catches out many councils. Most S106 financial contributions are index-linked — commonly to the BCIS All-in Tender Price Index or RPI. The amount due at the trigger point is the indexed amount at the date of calculation, not the base figure in the agreement. If you invoice the base figure, you're under-collecting.

4. Deadline Management

Spend-by deadlines are the highest-risk element of S106 monitoring. The pattern varies by agreement, but typically:

• Developer pays contribution upon trigger
• Council has 5–10 years to spend it on the specified purpose
• If unspent after the deadline, the developer can demand a refund — often with interest

With 200+ live agreements, each containing multiple financial obligations with different receipt dates and spend periods, you can have hundreds of active deadlines running concurrently.

Effective deadline management means:

• Recording the exact spend-by date for every financial contribution at the point of receipt
• Flagging contributions approaching their deadline at 12 months, 6 months, and 3 months
• Escalating at-risk contributions to senior officers and relevant service areas
• Maintaining an audit trail of allocation and spend decisions

For a detailed guide to the clawback process and how to build a deadline tracking system, see S106 Spend Deadlines: What Happens When Developer Money Expires.

5. Infrastructure Funding Statement Reporting

Since December 2020, every LPA must publish an annual IFS covering the previous financial year. Schedule 2 of the CIL Regulations sets out the minimum reporting requirements: S106 obligations entered into, contributions received, allocated, spent, and retained.

If your monitoring data is well-structured, the IFS should be a report you generate — not a project you start in November. The councils that struggle with IFS are invariably the ones whose underlying monitoring data is fragmented across spreadsheets with inconsistent structures.

The IFS also requires data on non-monetary obligations — affordable housing units delivered, highway works completed, open space provided. This is often the hardest data to compile because in-kind delivery is tracked (if at all) by service areas outside the planning team.

Building a Monitoring Process That Works

The gap between the five pillars above and what most smaller councils actually do is significant. Closing it doesn't require a large budget — it requires consistency:

1. Break every agreement into individual obligations at the point of signing. Don't summarise. List each obligation with its own trigger, terms, and deadline. This takes 30–60 minutes per agreement but prevents the data gaps that cause missed contributions later.

2. Set up monthly trigger checks. Cross-reference building control commencement and completion data against your S106 register. If you do nothing else on this list, do this.

3. Record receipt dates, not just amounts. The spend-by clock starts when money arrives. If you don't record the receipt date, you can't calculate the deadline.

4. Assign service area contacts for each obligation type. Education contributions need a named person in the education team who confirms allocation and spend. Highways contributions need a highways contact. Without ownership, contributions sit in holding accounts because nobody makes the spending decision.

5. Run a quarterly at-risk review. Pull every contribution with a spend-by deadline within 18 months. Confirm allocation status. Escalate anything unallocated. This is a 2-hour quarterly exercise that prevents six-figure refund demands.

S106 Monitoring Checklist

Use this to audit your current monitoring process:

• Every S106 agreement is broken into individual obligations with separate tracking
• Each obligation has a recorded trigger point type and development milestone
• Financial contributions are tracked through due, received, allocated, and spent stages
• Indexation basis is recorded and applied when invoicing
• Spend-by deadlines are calculated and recorded at the point of receipt
• Deadline alerts are set at 12, 6, and 3 months before expiry
• Building control data is cross-referenced monthly against S106 triggers
• Each obligation type has a named service area contact responsible for spend decisions
• Quarterly at-risk reviews are conducted for contributions approaching deadline
• IFS data can be extracted without manual compilation
• Non-monetary obligation delivery is recorded with evidence

If your monitoring process doesn't cover all of these, you have gaps that will cost your council money — either in returned contributions or in officer time spent firefighting. For a framework to evaluate monitoring tools, see What to Look for in S106 Monitoring Software.

For a deeper look at the IFS process, see How to Produce Your Infrastructure Funding Statement in Half the Time. You can also try the free IFS Template Generator, S106 Spend Deadline Calculator, and S106 Agreement Checklist Generator.

S106Ledger is building structured S106 tracking with deadline alerts, financial ledger, and one-click IFS reporting — designed for planning teams at smaller councils. Join the waitlist for early access.

Sources

• Town and Country Planning Act 1990, Section 106
• Community Infrastructure Levy Regulations 2010
• Community Infrastructure Levy (Amendment) (England) (No. 2) Regulations 2019 — inserted Regulation 121A (IFS requirement)
• Home Builders Federation — Section 106 Agreements and Unspent Developer Contributions
• PAS Knowledge Hub — Section 106 Databases Discussion
• PAS — Infrastructure Funding Statements Guidance
• Hansard — Planning: Section 106 System debate (January 2026)
• National Planning Policy Framework — Decision-making (Planning Obligations)