What to Look for in S106 Monitoring Software

If your council manages S106 obligations in spreadsheets, you've probably considered whether dedicated software would help. The question isn't whether to replace the spreadsheet — it's what to replace it with, and whether the cost and implementation effort are justified for your team's size.

This guide sets out the evaluation criteria that matter for smaller English district councils and unitary authorities — the 150–200 LPAs managing 50–500+ live agreements without the budget or procurement bandwidth for enterprise systems.

This is general guidance, not a product recommendation or legal advice.

Why Spreadsheets Fail at S106 Monitoring

Spreadsheets aren't inherently bad. For a council managing 20 live agreements, a well-structured Excel file with conditional formatting is workable. The problems emerge at scale:

• No alerts. Excel doesn't send you an email when a spend-by deadline is 90 days away. Conditional formatting only works if someone opens the file and looks.
• No audit trail. When a value changes, you can't see who changed it, when, or what it was before. For financial tracking subject to audit queries, this is a gap.
• No multi-user access. Shared files on network drives create version conflicts. SharePoint and OneDrive help but don't solve the structural problem — the data model is still flat.
• No structured reporting. Producing your annual Infrastructure Funding Statement means manually filtering, pivoting, and cross-referencing. Every year. From scratch.
• No integration. Trigger point data comes from building control. Financial receipt data comes from your finance system. In-kind delivery data comes from service areas. A spreadsheet can't pull from any of these automatically.

The tipping point for most councils is between 50 and 100 live agreements. Below 50, spreadsheets are painful but manageable. Above 100, they're a liability.

The Seven Criteria That Matter

1. Obligation-Level Tracking

The most important feature — and the one most tools get wrong — is the data model. S106 monitoring is not agreement-level. It's obligation-level.

A single S106 agreement can contain 12 or more individual obligations: financial contributions to education, highways, open space, community facilities, plus in-kind obligations like affordable housing delivery and junction improvements. Each obligation has its own trigger, its own terms, its own deadline, and its own status.

Any monitoring tool worth using must let you:

• Record each obligation as a separate tracked item within an agreement
• Assign a trigger type and milestone to each obligation independently
• Track financial obligations through the full lifecycle: due → received → allocated → spent
• Track non-monetary obligations through: agreed → commenced → delivered
• Filter and report at the obligation level, not just the agreement level

If the tool treats each agreement as a single record with a notes field, it's a database — not a monitoring system.

2. Deadline Alerts

Spend-by deadline management is the highest-value feature for most councils. The consequences of missed deadlines are direct and financial — developers can reclaim unspent contributions, often with interest.

What to look for:

• Automated alerts at configurable intervals (12 months, 6 months, 3 months, 1 month)
• Alerts sent via email — not just displayed in a dashboard nobody checks daily
• Escalation capability — flag overdue items to a manager or senior officer
• A clear view of all contributions approaching deadline, sorted by urgency

A tool without deadline alerts is not solving the problem that costs councils the most money.

3. Financial Ledger

S106 financial tracking is more complex than a simple income/expenditure record. The tool needs to handle:

• Indexation. Most S106 contributions are index-linked. The tool should record the indexation basis (BCIS, RPI, CPI) and either calculate the indexed amount or flag when indexation needs applying.
• Split receipts. Developers often pay a single lump sum covering multiple obligations. The tool must allow you to split a receipt across obligations and record each allocation separately.
• Spend tracking with evidence. When a contribution is spent, you need to record what it was spent on, the date, and the amount — with enough detail to satisfy an audit query or a developer asking where their money went.
• Clawback tracking. If a contribution is returned to a developer (because a spend-by deadline was missed or an obligation was modified), that needs to be recorded as a distinct transaction.

4. IFS Generation

If you're compiling your annual Infrastructure Funding Statement manually from spreadsheets, it takes days. The right monitoring tool should generate your IFS — or at least the S106 section of it — directly from the data you've been maintaining all year.

Minimum requirements:

• Export of all S106 contributions received, spent, allocated, and retained during the reporting year
• Breakdown by infrastructure type
• Non-monetary obligations status report
• Ability to filter by financial year (1 April – 31 March)

If the tool stores structured data at the obligation level (criterion 1), IFS generation becomes a reporting function rather than a data-compilation project.

5. Self-Serve Setup

Enterprise S106 monitoring systems exist — they serve larger councils with dedicated IT teams and procurement budgets. For smaller councils, the implementation model matters as much as the feature set.

Look for:

• No IT department required. The planning team should be able to set up and use the tool without raising a service request.
• Data import. You have years of S106 data in spreadsheets. Any tool should accept a structured CSV import to avoid months of manual re-entry.
• Training requirements proportionate to team size. If a tool requires 3 days of paid training for a 2-person planning team, the implementation cost outweighs the benefit.
• Pricing below formal procurement thresholds. Many councils can direct-award contracts below their standing-order threshold (often £5,000–£10,000, though this varies by authority). A tool priced above this triggers a formal procurement process that can take months.

6. Data Ownership and Export

Council data is public data. Any tool you use must give you:

• Full data export at any time, in a standard format (CSV, Excel)
• No lock-in — your data is yours, and you can leave without losing it
• Clear data processing agreements (for GDPR compliance)
• UK-hosted or UK-adequate data storage

This matters more than it seems. If a vendor goes out of business or raises prices, you need to be able to extract your data and move on. If the only way to get your data out is to ask the vendor to run a custom export, you're locked in.

7. Reporting and Dashboards

Beyond the IFS, your tool should help you answer routine questions without manual analysis:

• How much S106 money are we holding, and how much is at risk of clawback?
• Which agreements have unrecorded trigger points (obligations due but not yet invoiced)?
• What's our total obligation exposure across all live agreements?
• Which service areas have allocated but unspent contributions?

A dashboard isn't a nice-to-have. It's how you make S106 monitoring visible to leadership — and how you justify the monitoring function's existence when budgets are reviewed.

Build vs Buy vs Status Quo

For smaller councils, the decision isn't really "which tool" — it's whether to invest at all. Three paths:

Keep the spreadsheet. Viable for councils with fewer than 50 live agreements and a monitoring officer who has built institutional knowledge. The risk is succession — when that person leaves, the knowledge goes with them.

Build a custom database. Some councils have built Access databases or SharePoint solutions. This works until the person who built it leaves, or the council's IT policy changes, or the database outgrows its original design. Maintenance cost is hidden but real.

Buy dedicated software. The right choice when you're managing 50+ agreements, have spend-by deadlines you can't afford to miss, and spend days on IFS reporting. The cost of the tool is typically less than the cost of a single missed deadline clawback.

The decision comes down to risk tolerance and team size. If a missed spend-by deadline on a single large contribution would cost more than a year's software subscription, the business case writes itself.

Evaluation Checklist

Use this when assessing any S106 monitoring tool:

• Obligations tracked individually within agreements, not as a single record
• Automated deadline alerts via email at configurable intervals
• Financial tracking through the full lifecycle with indexation support
• IFS report generation from structured data
• Self-serve setup without IT department involvement
• Full data export in standard formats
• Dashboard showing total obligations, at-risk amounts, and upcoming deadlines
• Pricing within direct-award procurement limits
• UK data hosting

For the broader monitoring workflow these tools support, see our complete guide to S106 monitoring.

S106Ledger is designed for planning teams at smaller councils who need structured monitoring without enterprise pricing. Join the waitlist to be notified when it launches.

Sources

• Town and Country Planning Act 1990, Section 106
• Community Infrastructure Levy Regulations 2010
• PAS — Infrastructure Funding Statements Guidance
• GOV.UK — Planning Obligations Guidance