Last checked against AWS documentation on 20 November 2026.
Some AWS Quick settings cannot be changed once they are made. The AWS account, the sign-in method, the key that protects Quick's AI data and the permission setting on each knowledge base all fall into that group. Our AWS Quick FAQ explains why.
Because these choices are permanent, they deserve a written record: what was decided, on what evidence, and by whom. This page shows a filled-in example for a fictional council, so you can see what such a record looks like in practice. A blank template is available to download at the end.
This is a fictional example. Sample Unitary Council is invented, and so is everything in this record. The decisions below are illustrations of reasoning, and the right answers for your organisation depend on your own estate, policies and risk appetite.
How the record works
The record supports two separate decisions:
- Pilot authorisation. Before any configuration, the named officers approve the permanent and high-impact decisions and authorise a bounded pilot. This permits configuration and testing only.
- Operational decision. After the pilot, the same officers review the test results and remaining risks, then approve, condition or withhold wider use.
In our own engagements, the first decision is taken at the end of Discovery, before a Lighthouse demonstration, and the second is the Signed Promotion Decision at the end of the programme.
Each person approves only what is within their remit. Advisers, including the data protection officer and any external consultant, record their advice without approving. The record is amended and re-signed whenever an assumption changes, for example a new source, a new capability or a test result that contradicts what was expected.
The sample: Sample Unitary Council
Record control
| Field | Entry |
|---|---|
| Organisation | Sample Unitary Council (fictional) |
| Use case | Staff policy and procedure answers for HR, customer services and housing officers |
| Record version | v1.0, prepared for pilot authorisation |
| AWS account | New dedicated account in the council's landing zone ("quick-prod") |
| AWS Region | Europe (London), eu-west-2 |
| In scope | One Quick account; two knowledge bases (staff policies; service procedures); SharePoint Online connector |
| Data controller | Sample Unitary Council |
Part A: Permanent and high-impact decisions
| # | Decision | Choice | Reasoning | Approved by |
|---|---|---|---|---|
| A1 | AWS account | New dedicated account | AWS allows one Quick subscription per account. A dedicated account keeps Quick billing, logs, keys and admin access separate | Technical design authority |
| A2 | Sign-in method | IAM Identity Center, with an Enterprise edition account | Staff sign in with existing Microsoft accounts. The method cannot be changed later | Technical design authority |
| A3 | Identity Center instance | Existing organisation instance, administered from the delegated account | Already used for AWS console access; avoids a second identity silo | Technical design authority |
| A4 | Identity source | Entra ID, with SCIM provisioning and SAML sign-in | Entra ID is already authoritative. Quick groups rebuilt without nesting, because nested groups are not provisioned | Technical design authority |
| A5 | Encryption for Quick's AI data | AWS-managed key | The council's security policy does not require customer-managed keys for OFFICIAL content of this kind. Chat memory is wanted, and customer-managed keys disable it. Revisited if sensitive sources are added | SIRO, with technical design authority |
| A7a | Permissions, knowledge base 1 (staff policies) | Document permissions off | Every document is published to all staff on the intranet already. Confirmed by the HR information asset owner | Service owner, with HR information asset owner |
| A7b | Permissions, knowledge base 2 (service procedures) | Document permissions on | Some housing procedures are restricted to named teams | Service owner, with housing information asset owner |
| A8 | Research | Research allowed over knowledge base 1 only | Research cannot use permission-controlled knowledge bases. Knowledge base 1 holds only all-staff content | Service owner |
| A9 | Region | London | Data stored in London. AI processing may use other European regions; recorded in C5 | Technical design authority |
A6 (key safeguards) is not applicable, because A5 uses an AWS-managed key.
Part B: Configuration decisions
| # | Decision | Choice |
|---|---|---|
| B1 | Roles | Pilot users are Readers (Essentials). Two content leads are Author Pro (Enterprise). One Admin Pro |
| B1a | Licence mix and billing owner | 22 Essentials, 3 Enterprise (two Author Pro content leads and one Admin Pro); billed to the digital services cost centre |
| B2 | Knowledge base owners | Two owners for each knowledge base: the content lead and a deputy |
| B3 | Permission refresh | Daily, the default. SharePoint is checked in real time when results are returned |
| B4 | Connectors | SharePoint Online only for the pilot |
| B5 | Web search | Off for the pilot |
| B6 | Logs | Chat, feedback and agent-hour logs delivered to CloudWatch from day one; 12-month retention; access limited to two named analysts |
| B7 | Automation | None in the pilot |
| B8 | Outputs | Uploads to Spaces off. Downloads allowed, with guidance that generated text is a draft |
| B9 | Cost controls | Monthly budget alert at 80 per cent; agent-hour report reviewed weekly |
Part C: Information governance
| # | Item | Outcome |
|---|---|---|
| C1 | DPIA screening | Screening complete. Sources hold minimal personal data, but chat logs record staff questions against named users for 12 months. Full DPIA to be completed before staff access, covering prompts and logs |
| C2 | ATRS screening | Internal staff tool with no direct public effect. The mandatory scope covers central government departments and some arm's-length bodies. ATRS is recommended across the wider public sector, and government intends to extend the mandatory requirement over time. The council will publish a record voluntarily if use expands to public-facing work |
| C3 | FOI and subject access | Records team can retrieve CloudWatch chat logs (delivered from day one) and downloaded files. Native history is visible only to each user and cannot be shared, so it is not relied on. Procedure written and tested on a dummy request |
| C4 | Retention | Generated content is not a record unless filed by an officer. Native history (up to 90 days, visible only to each user) is not treated as a record |
| C5 | Classification | OFFICIAL only. No case files, social care records or content above OFFICIAL |
| C6 | Staff guidance | Two-page guide and a 30-minute briefing for pilot users |
| C7 to C9 | Health and social care items | Not applicable. Social care content excluded |
Part D: Known gaps and residual risks
| # | Gap or risk | Evidence class | Mitigation | Owner |
|---|---|---|---|---|
| D1 | Restricted housing procedures must not reach other teams | NOT_RUN | Positive and negative access tests with representative users before any staff use | Technical design authority |
| D2 | Some HR policies on the intranet are out of date | DOCUMENTED (content audit) | 14 superseded policies withdrawn before connection; quarterly review | HR information asset owner |
| D3 | Behaviour when SharePoint is unavailable | NOT_RUN | Test during pilot; record result | Technical design authority |
| D4 | AI processing may take place in other European regions | DOCUMENTED (AWS) | Accepted for OFFICIAL content in scope | SIRO |
Part E: Pilot authorisation
| Role | Remit | Decision |
|---|---|---|
| SIRO | Information risk acceptance | Authorise with conditions: D1 tests passed and full DPIA complete before staff access |
| Service owner | Use case, scope, users | Authorise |
| Technical design authority | Account, identity, keys, region | Authorise |
| Information asset owners (HR, housing) | Content and permissions | Authorise |
| Adviser | Advice |
|---|---|
| Data protection officer | Advises a full DPIA covering prompts and logs before staff access. Asks to be consulted before any case-related source is added |
| External adviser | Evidence and recommendations provided; no approval role |
Further reading
- AWS Quick: setting up IAM Identity Center and account subscriptions
- AWS Quick: customer-managed keys
- AWS Quick: SharePoint knowledge base permissions
- AWS Quick: user types and subscriptions
- AWS Quick: regions and data processing
- AWS Quick: chat conversations
- Algorithmic Transparency Recording Standard: mandatory scope
Using the template
The blank template has the same parts, with guidance in each row. Use it at the end of a readiness assessment or Discovery, before anything is configured, and keep it up to date through the pilot.
Work through the AWS Quick readiness checklist first, and read what public bodies need to check before switching on AWS Quick for the reasoning behind each decision.
If you would like help preparing a record like this, see AWS Quick Readiness, Implementation & Assurance.
There is a problem
Your decision record is ready
Thank you. Your download link works for the next 15 minutes, and we are also emailing you a copy.
Continue with the AWS Quick guide.
