EU GDPR
Map your processing and put data rights, safeguards and breach decisions into daily operations.
UK GDPR and Data Protection Act 2018
Build a UK privacy program and account for UK-specific rules and recent amendments.
Controllers and processors in scope of UK GDPR territorial rules.
Documented UK processing, rights, accountability and incident-response controls.
Check the ICO’s current guidance for phased Data (Use and Access) Act amendments and apply separate PECR duties where relevant.
Review rights requests approaching deadline, DPIAs and transfer assessments awaiting action, and changes that could reopen an approved use.
Fill this in with your sponsor and send it to the people who own the work.
UK GDPR kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Confirm scope and roles · Privacy lead + legal [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Observe how HR, Support and Marketing use personal data. Write down the software, destinations, vendor access and retention they actually use. 2. Run a practice access request from intake to secure response. Identify what facts change the applicable deadline and any missing source systems. 3. Review one high-risk proposal and one supplier. Give each unresolved assessment, contract or transfer issue a named owner.
A company prepares two launch reviews for its UK checkout. One checks lawful grounds and the privacy notice. The other verifies what the browser stores before a visitor makes a choice.
Check the separate device-storage and marketing rules.
Notify without undue delay and within 72 hours where feasible when the notification criteria are met.
Official reference (opens in a new tab)Checklist, instructions and 10 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm scope and roles | Privacy lead + legal | At initiation | Set a start date | Coverage memo; Processing inventory | Open |
| Implement lawful processing and rights | Privacy operations + product | Before processing and on request | Set a start date | Privacy notices; Lawful-basis record; Rights workflow | Open |
| Manage risks and disclosures | Legal + security | Before high-risk processing or transfers | Set a start date | DPIA register; Contracts; Transfer documentation | Open |
| Prepare for breaches | Security + privacy lead | At incident and during exercises | Set a start date | Breach log; Escalation and notification playbook | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map UK targeting and establishments, processing purposes, controller or processor roles, exemptions and local requirements.
UK entity and activity records, contracts, data flows, vendor terms and customer-facing services.
A UK customer support workflow links the role decision, actual systems, vendor access and the named person who checks changes.
Raise overlapping UK and EU obligations or a vendor responsible for processing whose role is unresolved.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Set the lawful basis, special category conditions and notice. Test access and other rights intake, verification and fulfillment.
Processing register, lawful-basis and notice records, rights queue and relevant current ICO guidance.
A practice access request shows when it arrived, the applicable response date, systems and teams searched, the decision and secure delivery record.
Raise a missing system owner, approaching deadline or possible disclosure of another person’s information.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Perform DPIA screening, establish processor terms and assess UK international transfer mechanisms as needed.
Proposed activity, vendor terms, data locations and applicable UK DPIA and transfer guidance.
The supplier record identifies real storage and remote access locations, transfer mechanism where relevant, safeguards and review date.
Escalate a high-risk activity or restricted transfer before release if approval or safeguards are missing.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
Record every breach and the risk decision. Notify the ICO when required and inform affected people when the high-risk trigger is met.
Incident contact list, incident logs, processor contacts, affected systems and current ICO guidance.
The incident record shows why a notice was or was not required, time of the decision, reviewer and supporting facts.
Route a potential breach to the on-call privacy and incident team early so it can track the applicable deadline while facts develop.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.