Opportunity
Developer Contributions and Viability Review Lifecycle Tracker
Affordable-housing and infrastructure obligations can run for years across complex developments, with review points, viability reassessments, payments, triggers and evidence spread across legal agreements and spreadsheets.
Decision snapshot
- Primary user
- S106/CIL officers, planning policy teams, developers, viability consultants and regeneration teams.
- Likely buyer
- The public-sector buyer is usually a planning obligations/CIL manager, infrastructure lead or head of development management.
- Why now
- Councils already fund staff/software for S106 monitoring and developers face cash-flow and compliance risk from missed triggers. RICS emphasises continued importance of site-specific viability.
- Initial wedge
- A shared obligation ledger that converts legal agreements into dated/conditional triggers, tracks evidence and payments, and schedules viability reviews.
- Key uncertainty
- Raise above 82 if councils confirm spreadsheet monitoring alongside incumbent planning systems and will pay for a bolt-on. Reduce below 62 if existing S106 modules already provide reliable trigger, finance and developer self-service workflows.
The problem
Affordable-housing and infrastructure obligations can run for years across complex developments, with review points, viability reassessments, payments, triggers and evidence spread across legal agreements and spreadsheets. PAS's developer-contributions programme exists because councils must negotiate, monitor, allocate and spend contributions across multiple teams. The Public Accounts Committee has also scrutinised whether developer funding is translated into infrastructure effectively, so the pain extends beyond agreement capture into governance and delivery.
Operational consequences
- Trigger dates can depend on commencement, occupation, phase completion or indexed financial thresholds rather than simple dates. - Finance, planning and infrastructure teams can hold different records of what has been invoiced, received, allocated and spent. - Developers can miss evidence or payment obligations; councils can miss enforcement or spending deadlines. - Viability-review clauses create a second lifecycle of assumptions, evidence, negotiation and approvals after permission.
Who is underserved
S106/CIL officers, planning policy teams, developers, viability consultants and regeneration teams.
Buyer and user context
The public-sector buyer is usually a planning obligations/CIL manager, infrastructure lead or head of development management. On the private side, land/development finance teams need a portfolio view of future obligations and review events rather than council-only reporting.
Evidence
PM12 requires clear contributions and review mechanisms; DM5 sets evidence expectations for site-specific viability. PAS states monitoring fees can fund lifetime monitoring of obligations and Infrastructure Funding Statements create reporting duties. PAS says its governance guidance drew on workshops and health-checks with around 40 councils involved in negotiating, monitoring, allocating and spending contributions. Parliament's Public Accounts Committee has separately examined how developer funding supports schools, health facilities, roads, open space and affordable housing.
Evidence interpretation
The operational problem is established and funded, but the market already contains S106/CIL modules. The under-served angle is a shared lifecycle record across council and developer, especially for phased sites and review mechanisms.
Demand
Councils already fund staff/software for S106 monitoring and developers face cash-flow and compliance risk from missed triggers. RICS emphasises continued importance of site-specific viability. Monitoring fees can be charged in appropriate circumstances and councils maintain Infrastructure Funding Statements, creating both budget and reporting context for better tooling.
Validation approach
Partner one council still using spreadsheets with one large developer. Import 50 live agreements, measure missed/late trigger visibility, officer reconciliation time and developer queries. The product should prove recovered revenue/risk avoidance or a material reduction in monitoring effort.
Competition
DEF/MasterGov and other back-office suites are established. The gap is a modern shared developer-council lifecycle layer, especially for phased schemes and viability review triggers. MasterGov/DEF and other planning back-office suites already include contributions management, while large developers use finance/project systems. Replacing those systems would be expensive and unnecessary.
Potential defensibility
Extracting obligations into a common machine-readable trigger model, maintaining bilateral evidence and linking obligations to site phases could differentiate. Strong APIs into incumbent planning/finance systems are more defensible than a standalone register.
The opportunity
A shared obligation ledger that converts legal agreements into dated/conditional triggers, tracks evidence and payments, and schedules viability reviews. The core object should be an obligation with trigger logic, evidence requirement, responsible party, indexation/payment rule and status. Both sides should see the same factual record while retaining private notes and formal approval controls.
Intended outcome
Reduce missed triggers and disputes, improve infrastructure-funding visibility and make viability-review events predictable across long-lived developments.
Commercial model
Pricing classification
Proxy based — medium confidence.
Indicative pricing
- Paid test offer: Paid authority or developer pilot: £10,000–£25,000 £15,000–£50,000/year per authority; developer portfolio plans £5,000–£25,000/year; onboarding per agreement portfolio. Authority pricing of £15,000-£40,000/year is plausible where the system replaces manual monitoring; developer portfolios could support £5,000-£20,000/year. Agreement migration/data extraction should be priced separately.
Evidence basis: Agile AI Planning Validator (£15,000–£60,000 per licence) is the closest verified adjacent anchor used here. Its buyer, duration and scope are not assumed to be identical; implementation is separated where the opportunity requires integration, assurance or managed delivery.
Commercial test
Ask one planning authority, developer or planning consultancy with a live case pipeline to fund a paid test of Developer Contributions and Viability Review Lifecycle Tracker lasting 8–12 weeks, using an opening price of £10,000–£25,000 and covering 20 live applications, sites, conditions or evidence packs from one planning workflow. Paid scope: A shared obligation ledger that converts legal agreements into dated/conditional triggers, tracks evidence and payments, and schedules viability reviews. Charge by authority, professional team, development site or assessed case and compare the fee with planning-officer and consultant time, avoidable invalid submissions and repeated evidence assembly. Measure validation time, missing-document rate, rework, officer overrides, applicant resubmissions and decision lead time. Continue only if handling or rework falls by at least 25%, at least 90% of required evidence is correctly identified and no material planning issue is suppressed. Stop or reprice if experienced officers find material false assurance, the workflow does not beat current practice or the buyer will not renew.
Monetisation models and pricing estimates are research-informed and indicative only. Where direct pricing evidence is unavailable, estimates may use comparable products, procurement data, adjacent market benchmarks and stated assumptions. They are not financial advice, forecasts or guarantees of commercial viability. Independent market, legal and financial validation is recommended before acting.
Score rationale
Underserved score 75/100
A real funded monitoring workflow with clear value, but incumbents reduce whitespace. Shared cross-party workflow and modern trigger automation are the wedge. The workflow is expensive and persistent, but incumbents are real. The strongest wedge is shared trigger/evidence management around complex phased schemes and review clauses.
What would change the score
Raise above 82 if councils confirm spreadsheet monitoring alongside incumbent planning systems and will pay for a bolt-on. Reduce below 62 if existing S106 modules already provide reliable trigger, finance and developer self-service workflows.
The score is evidence-informed editorial judgement based on manually reviewed sources. It is not a forecast or guarantee. How we score →
Evidence sources7
- PAS – Infrastructure Funding Statements
local.gov.uk
- PAS – Infrastructure Delivery Plans
local.gov.uk
- Public Accounts Committee – Developer funding
publications.parliament.uk
Some evidence sources may require an account or sign-in to view the original content.