How S106 Developer Contributions Work: A Guide for Monitoring Officers

Developer contributions through S106 agreements fund critical local infrastructure — schools, roads, parks, community facilities. But between the agreement being signed and the contribution actually building something, there's a lifecycle of monitoring steps that falls squarely on the planning obligations officer's desk.

This guide traces the full contribution lifecycle and highlights where monitoring effort should focus.

This covers England only. This is general guidance, not legal advice.

The Contribution Lifecycle

Every S106 financial contribution moves through six stages. Your monitoring system needs to track transitions between each one.

Stage 1: Obligation Agreed

The S106 agreement is signed. Each financial obligation is recorded with:

• Purpose (education, highways, open space, healthcare, community facilities)
• Base amount
• Indexation basis and base date (usually BCIS All-in Tender Price Index or RPI)
• Trigger event (commencement, occupation threshold, phase completion)
• Spend-by period (from the clawback clause — typically 5–10 years from receipt)

At this stage, no money changes hands. The obligation exists on paper. Your job is to extract it from the legal agreement and record it as a separate tracked item in your register.

Stage 2: Trigger Activated

A development milestone activates the obligation. How you find out about triggers depends on:

• Commencement notices — developers must notify the LPA before commencing development. Cross-reference with building control records.
• Building control completions — for occupation-based triggers, completion certificates indicate when dwellings are being occupied.
• Developer notifications — some agreements require the developer to notify the council when triggers are reached. Don't rely on this alone.
• Site visits — periodic site visits can verify milestones, particularly for non-residential triggers.

When a trigger fires, record the trigger date and update the obligation status. This is the point where you can invoice the developer.

Stage 3: Invoice Issued

Calculate the indexed amount at the invoice date and issue the demand. The indexed amount will differ from the base amount in the agreement:

Example:

• Base amount: £200,000
• Agreement date (base date): January 2022
• Invoice date: April 2026
• BCIS index change: +18%
• Indexed amount: £236,000

If you invoice the base amount (£200,000), you're under-collecting by £36,000. For a council managing 50+ financial contributions, systematic under-indexation could cost hundreds of thousands across the portfolio.

Record: invoice date, indexed amount, invoice reference, developer contact.

Stage 4: Payment Received

Finance confirms the payment has arrived. This is the critical monitoring point because:

• The spend-by deadline clock starts here. Not at the trigger date, not at the invoice date. At the receipt date. Record it.
• Split receipts need matching. If the developer pays a lump sum covering multiple obligations, split and allocate each portion to the correct obligation.
• The amount may not match the invoice. Developers sometimes dispute the indexation calculation. Record the actual amount received and flag any shortfall.

Calculate the spend-by deadline: receipt date + spend-by period from the agreement. Set alerts at 18, 12, 6, and 3 months before expiry.

Use the S106 Spend Deadline Calculator to calculate deadlines and export them to your calendar.

Stage 5: Allocated to Project

The contribution is earmarked for a specific infrastructure project:

• Education contribution → new classroom block at Elm Road Primary
• Highways contribution → junction improvement at A456/B789
• Open space contribution → playground equipment at Riverside Park

Allocation is a planning/service area decision, not a finance action. Record: project name, service area contact, allocation date, expected spend timeline.

Allocation does not stop the spend-by deadline. The money needs to be spent — not just earmarked. If the project is delayed, the deadline still applies.

Stage 6: Spent and Evidenced

The contribution is disbursed — invoices paid, contracts completed, infrastructure delivered. Record: spend date, amount spent, project reference, evidence (invoices, completion certificates).

If the full contribution is spent, the obligation can be marked as discharged. If partially spent, record the balance and continue tracking the remainder against the spend-by deadline.

Where the Lifecycle Breaks Down

The Gap Between Stages 2 and 3

Triggers fire but nobody invoices. This happens when trigger monitoring relies on the developer to self-report. If the development reaches its 50th occupation and nobody records it, the obligation sits in Stage 1 indefinitely — money owed but never collected.

Fix: Monthly cross-referencing of building control data against your S106 register. This takes 2–3 hours per month and is the single highest-ROI monitoring activity.

The Gap Between Stages 4 and 5

Money is received but never allocated. Contributions sit in a holding account because no service area has claimed them. This is how councils accumulate millions in unspent S106 funds.

Fix: When a contribution is received, notify the relevant service area immediately. Set a 6-month allocation deadline. If unallocated after 6 months, escalate to a senior officer.

The Gap Between Stages 5 and 6

A project is identified but never spends the money. Capital programmes slip. Budget priorities change. The contribution sits allocated-but-unspent while the deadline approaches.

Fix: Track spend status separately from allocation. An allocated contribution with 12 months left on its deadline needs the same urgency as an unallocated one.

Non-Financial Contributions

Not all developer contributions are cash. In-kind obligations follow a parallel lifecycle:

1. Agreed — obligation recorded in the S106 agreement
2. Triggered — development milestone reached
3. Commenced — works started or units under construction
4. Delivered — completed to specification and accepted/adopted
5. Discharged — obligation formally discharged

For in-kind obligations, Stage 4 (delivery verification) requires coordination with the service area that will adopt or accept the infrastructure — highways authority for roads, housing team for affordable units, parks team for open space.

For a complete monitoring setup process, see The Complete Guide to S106 Monitoring for Planning Officers.

Sources

• Town and Country Planning Act 1990, Section 106
• GOV.UK — Planning Obligations Guidance
• PAS — Infrastructure Funding Statements
• Home Builders Federation — S106 Unspent Contributions Report