Last checked against AWS and UK government sources on 20 November 2026.
Councils hold an enormous amount of knowledge that staff struggle to find: policies on the intranet, procedures in SharePoint, guidance in case management systems, committee papers, performance data and years of correspondence. AWS Quick (formerly Amazon Quick) promises to let staff ask questions of all of it. Whether that works safely depends on things most councils already know are messy, chiefly permissions, content ownership and the structure of the organisation itself.
This page covers what is different for councils. For the uses themselves, see use cases for councils, central government and health.
Where it could help
The strongest council uses tend to be the ones where staff spend time looking for an answer that already exists somewhere:
- policy and procedure answers for customer services, HR and housing officers
- searching large guidance libraries in county services
- bringing together the policies of several councils during reorganisation
- summarising consultation responses and planning documents
- reporting over performance data held on AWS
Each depends on the sources being current and the permissions being right. Social care is different. Any use that touches social care decisions or records needs particular care, and should be assessed against the DfE and DHSC guidance on AI in social care, published on 20 November 2026.
Most councils already run Microsoft 365
That is not a reason to rule Quick out, or in. Copilot deserves equal consideration, and the readiness questions about permissions and content apply whichever product you choose. Quick is most likely to earn its place alongside Microsoft 365 where knowledge sits outside it, where you already hold data on AWS, or where you need its research, reporting or automation features. Our guide on how to choose between Microsoft 365 Copilot and AWS Quick sets out a fair comparison.
Reorganisation changes the decisions

Local government reorganisation is replacing county and district councils across much of England, and the timetable is moving. Surrey's two new unitary councils go live in April 2027. On 29 October 2026 the government said it was minded to establish new councils for 2029 in five further areas, subject to further representations, with elections to shadow councils in May 2028. It withdrew decisions in nine areas paused in September, saying this does not mean reorganisation has been cancelled there, and said every area will have an outcome by early 2027. The LGA's reorganisation hub tracks the position by area.
Many two-tier councils may spend the next few years preparing for reorganisation, and some do not yet know their date.
For an AI assistant, this matters in three ways.
Accounts and subscriptions. AWS allows one Quick subscription per AWS account, and the sign-in method cannot be changed once the account is created. AWS also warns that moving a Quick account that uses IAM Identity Center into an AWS organisation without that Identity Center instance permanently prevents all users from signing in. A council that sets up Quick now should plan where that account sits when it merges with its neighbours, and whether the new authority will inherit it or start again, before the merger happens.
Permissions. Reorganisation mixes staff, groups and document libraries from several organisations. Permissions built for the old structure can give the wrong people access in the new one, and an assistant will surface those mistakes quickly. Plan permission reviews around each structural change as well as at launch.
Content. Merging councils will have several versions of the same policy, each authoritative for a while and then superseded. An assistant that reads all of them will give confident answers from the wrong one. Decide which content is authoritative at each stage, and withdraw the rest.
Reorganisation can also be a good reason to use Quick, for example to help officers compare and harmonise policies across predecessor councils. That work needs a clear rule about which documents staff may rely on.
Governance for councils
Freedom of information. The ICO says that information generated by AI for work, and the prompts used, is subject to FOI if you hold it, and that stored conversations and past prompts are recorded information. Councils receive a high volume of requests, so know before launch how you will find conversations, logs and downloaded files.
Transparency. The Algorithmic Transparency Recording Standard is mandatory for central government departments and some arm's-length bodies. It is recommended across the wider public sector, including councils, and government intends to extend the mandatory requirement over time. An internal staff assistant may not need a record, but a tool that shapes decisions about residents is a stronger candidate for one.
Data protection. Screen each use case for a DPIA before sources are connected. Case files, social care records and anything about vulnerable residents should stay out of scope until the governance for them is in place.
Classification. Keep to OFFICIAL content, and decide feature by feature whether processing outside the UK is acceptable. In London, data is stored in London, AI processing may use other European regions and web search is processed in Ireland (AWS regions guidance).
Cost and starting small
Quick is priced per user per month, by role, plus a monthly account fee (AWS pricing, at 20 November 2026). Role mapping drives cost: a user in several mapped groups keeps the subscription that grants the broadest access, which can be a higher-priced subscription than intended. With council budgets under pressure, a bounded pilot for a single service, with a cost model built on actual usage, is a sensible first step before any wider commitment.
How to start
- Work through the free AWS Quick readiness checklist.
- Read what public bodies need to check before switching on AWS Quick for the reasoning.
- Look at the sample configuration decision record, which uses a fictional council.
If you would like help, our AWS Quick Readiness, Implementation & Assurance service starts with a two-week Discovery of one service, for example housing repairs guidance, and its data. A bounded Lighthouse demonstration with one team follows, and the programme ends in about 14 weeks with a decision your officers sign. A Discovery that finds your data or foundations are not ready is a useful result in its own right.
