Council technology decisions, before the requirement is locked.
Every core council system gets replaced eventually, and every replacement starts life as a business case in a public paper. Finance and HR. Revenues and benefits. Social care and housing case management, planning, land charges. The decision to move, the money to do it and the shape of the programme all go through cabinet or a resources committee. GovLeads reads those papers across more than 200 English local and strategic authorities every weeknight.
What we watch for
Council technology procurement is unusually front-loaded, so the document worth having is nearly always the business case, not the notice. Here's what we go looking for.
- Core system replacements – finance and HR, revenues and benefits, social care and housing case management, planning and land charges.
- Digital strategy and target operating models – strategy refreshes, transformation programmes, and the capacity brought in to deliver them.
- Cloud, hosting and infrastructure. Data centre exit, cloud migration decisions, managed service re-procurements.
- Cyber security – investment cases, assurance and testing programmes, and the incident recovery reports nobody enjoys writing.
- AI and automation – pilot approvals, business cases, governance policies, and the procurement route chosen for each.
- Customer contact and channel shift – CRM replacement, contact centre technology, self-service programmes.
- Data, insight and shared services. Data platform investment, business intelligence programmes, IT partnership reviews.
By the time a requirement reaches a framework call-off or a portal, the operating model, the integration constraints and often the shortlist logic are already settled – settled in a business case published weeks or months earlier. That business case is a committee paper. It's public, and almost nobody reads it.
What lands in your inbox
Pulled from a digital and technology brief. This is the format, and the level of detail.
Business case approved for core finance system replacement
Cabinet approves funding for an ERP replacement, with an implementation partner still to be appointed.
Why it matters: the integration requirements are already written down.
Cyber assurance programme to be commissioned
Audit committee paper sets out a programme of testing and assurance work over the coming year.
Why it matters: the scope is spelled out in public, before the procurement.
Illustrative sample
How it works
- Set your brief. Describe what you sell and who buys it. Plain English, not a keyword list.
- We scan, every weeknight. Our AI goes through the committee and cabinet papers of more than 200 English local and strategic authorities.
- Your signals, every morning. A ranked digest. Every item explains itself and links to the paper it was pulled from.
Frequently asked questions
Which system replacements do you pick up?
Any that reach a committee, which in practice is most of the significant ones – they need funding approval. Finance and HR, revenues and benefits, social care and housing case management, planning and land charges, customer contact platforms: all of them turn up regularly.
Most council IT goes through frameworks. Does that matter?
It's the whole reason to read papers rather than portals. A framework call-off might never appear as an open notice, but the decision to spend the money almost always appears in a public report first. We surface the decision, whatever route follows it.
Do you cover AI and automation work?
Yes, and it's a fast-growing category in council papers. Pilots, automation business cases and AI governance policies are nearly always approved in public before anything gets bought.
Is this useful for a smaller supplier?
Yes. Because the signal is the decision rather than the notice, you get the same lead time an incumbent gets, and lead time is normally where the asymmetry sits. Every item links to the source paper, so you can check it yourself.