Last checked against AWS and UK government sources on 20 November 2026.
Large departments and their arm's-length bodies hold knowledge in many places: SharePoint and Teams, case management systems, data platforms on AWS, policy libraries, correspondence and decades of submissions. AWS Quick (formerly Amazon Quick) is designed to let staff ask questions across those sources, research a topic and build reports. For a department, the harder work is making sure it does so within the department's own controls, standards and accountability.
This page covers what is different for central government. For the uses themselves, see use cases for councils, central government and health.
Where it could help
- policy research and briefing across many internal sources
- correspondence and casework guidance for operational staff
- finance and operational reporting over data already held on AWS
- teams moving from Amazon Q Business, which is no longer open to new customers (July 2026)
Alongside what you already use
Many departments run Microsoft 365, and many are trialling or rolling out Copilot. Government has also built its own AI tools: the Humphrey suite, developed by i.AI (now part of the Government Digital Service), including Consult for consultation analysis and Minute for meeting notes. Quick does not need to replace any of these to be useful. It is most likely to earn its place where knowledge sits outside Microsoft 365, where data already lives on AWS, or where research and reporting across many sources is the need.
The Digital Assurance Playbook asks assurers to check that duplicative delivery has been avoided. Be clear which tool is for which job. Our guide on how to choose between Microsoft 365 Copilot and AWS Quick sets out a fair comparison.
Assurance has moved to departments

Central digital and technology spend controls were removed on 1 April 2026. Under the Digital Assurance Playbook, departments now run most of their own assurance and approvals. Central approval is needed only above a department's delegated authority limit, or that HM Treasury determines to be novel, contentious or repercussive. The playbook notes that AI can count as novel where an organisation lacks the internal expertise to implement it.
In practice, this means your own assurers will look at a Quick proposal against the standards the playbook names, including the Technology Code of Practice, the Service Standard, Secure by Design and Cloud First. It also expects AI initiatives to follow the AI Playbook for the UK Government and the Algorithmic Transparency Recording Standard. Bring assurance in early, before procurement or discovery activity begins.
Transparency is mandatory
The Algorithmic Transparency Recording Standard is mandatory for ministerial and non-ministerial departments, and for arm's-length bodies that provide public or frontline services or routinely interact with the general public. It applies to tools that significantly influence decisions with a public effect, or that interact directly with the public. An internal research assistant may fall outside that scope. A tool used in casework that affects members of the public is more likely to be in it. Screen each use case and record the reasoning.
Security and classification
Decide which content and features are appropriate for OFFICIAL information, informed by your SIRO and security team, and do not connect material above OFFICIAL. Describe data location feature by feature: in London, data is stored in London, AI processing may use other European regions, and web search is processed in Ireland (AWS regions guidance).
Two documented behaviours matter for departmental security policy:
- Customer-managed keys need an Enterprise subscription, and the key for Quick's AI data is permanent once that data is created. Losing access to the key means losing access to the data (AWS documentation).
- Prompt injection. Quick reads documents, and documents can contain text written to manipulate an AI system. The NCSC's guidance that prompt injection is not SQL injection is relevant to any source that takes content from outside the department.
Machinery of government
Departments merge, split and move functions through machinery of government changes. 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. Decide where Quick sits in your AWS organisation with future changes in mind, and plan any account move before a transfer of functions. Our article on machinery of government changes covers the account and data implications.
Permissions also outlive the structures they reflected. After a machinery of government change, review groups, role mapping, source permissions and knowledge base ownership before an assistant reads across them.
Records and information rights
Quick keeps conversations for up to 90 days, staff can download what it produces, and logs are delivered to CloudWatch only once configured. 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. Agree with your departmental records team how generated content is labelled, when it becomes part of the record, and how conversations and logs are found and preserved.
Buying AWS and buying help
Many departments buy AWS under the One Government Value Agreement, the arrangement between AWS and the Crown Commercial Service. Quick subscriptions are billed by AWS under your existing agreement. Professional services to help you adopt Quick are bought separately.
How to start
- Work through the free AWS Quick readiness checklist.
- Read what public bodies need to check before switching on AWS Quick and the AWS Quick FAQ.
- Look at the sample configuration decision record to see how permanent decisions can be recorded and signed.
Our AWS Quick Readiness, Implementation & Assurance service is built for how departments buy and assure. It starts with a two-week Discovery, a low-risk first commitment that starts your assurance on day one and checks your data and AWS foundations. A bounded Lighthouse demonstration with one team, for example on casework guidance for operational staff, follows, and the programme ends in about 14 weeks with a Signed Promotion Decision your assurers can rely on.
