Council, meeting, date, committee, item, subject, kind, officer recommendation, outcome, money and planning fields, with a link to the source.
The fieldsCouncil papers as structured data, with the source for every record
Product teams do not want to read council papers; they want them inside their own product. CouncilMonitor reads every paper from 194 councils, turns each item into a record with the same fields everywhere, keeps the paper and links every record back to it.
To build and maintain
each breaking the day a council changes its website.
With no structure
so the outcome, the money and the date have to be read out of prose.
The same across councils
every committee system names and shapes things its own way.
Your customers will ask for
which paper said it, and when it was published.
How it works
We read every council
Every committee from each council's own democracy system, several times a day, and keep a dated copy of every paper.
Every item a record
Each item becomes a record with the same fields at every council: date, committee, subject, kind, recommendation, outcome and money.
Delivered your way
Tools for assistants over MCP, the team briefing to your webhook, bulk export for a council, and the full archive under licence.
That used to be a scraping team. Here it is one feed.
Because every paper from every council is read, structured and kept, the council layer is ready to plug in, with the source for every record.
Inside your product
Property, risk, legal and tender platforms add council decisions to their own product: planning outcomes for a site, contract history for a supplier, decisions by area of law. The Data licence sets out use in your product and redistribution.
Inside an assistant
Connect the CouncilMonitor MCP server to an assistant or agent and it can search every paper, find decisions and read items, with each answer linked to the paper it came from.