Start hereConfirm scope and roles
~84 days leftOpen step
Guide library
Regulation Europe

UK GDPR

UK GDPR and Data Protection Act 2018

Build a UK privacy program and account for UK-specific rules and recent amendments.

Who it applies to

Controllers and processors in scope of UK GDPR territorial rules.

What you’ll produce

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.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which processing and obligations are UK-specific?
Have Legal determine entity roles and territorial scope and check the current UK rules and ICO guidance. Where EU GDPR also applies, record the distinct requirements for the same workflow.
Who can approve a new use or vendor?
Appoint a privacy lead to check lawful grounds, data sharing, transfer risks and DPIAs. Put the review into Product and Procurement approval and fund any changes.
Who can answer a rights request or notify the ICO?
Name an intake owner and backup, determine how you log and calculate deadlines, and agree who escalates or approves a breach notification.

How to spend the 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.

What to review each week

Review rights requests approaching deadline, DPIAs and transfer assessments awaiting action, and changes that could reopen an approved use.

Kickoff brief to share with your team

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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What is the UK connection for each processing activity?
  • Does collection also depend on a cookie or similar technology that reads or writes on a device?

Worked scenario

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.

What to read next

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 72 hours after awareness

    Report eligible breaches to the ICO

    Notify without undue delay and within 72 hours where feasible when the notification criteria are met.

    Official reference (opens in a new tab)
The whole journeyabout 84 days across 4 steps
  1. 01Confirm scope and rolesPrivacy lead + legal · ~14 days
  2. 02Implement lawful processing and rightsPrivacy operations + product · ~28 days
  3. 03Manage risks and disclosuresLegal + security · ~28 days
  4. 04Prepare for breachesSecurity + privacy lead · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 10 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Confirm scope and rolesPrivacy lead + legalAt initiationSet a start dateCoverage memo; Processing inventoryOpen
Implement lawful processing and rightsPrivacy operations + productBefore processing and on requestSet a start datePrivacy notices; Lawful-basis record; Rights workflowOpen
Manage risks and disclosuresLegal + securityBefore high-risk processing or transfersSet a start dateDPIA register; Contracts; Transfer documentationOpen
Prepare for breachesSecurity + privacy leadAt incident and during exercisesSet a start dateBreach log; Escalation and notification playbookOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Confirm scope and roles

    Who Privacy lead + legal When At initiation

    Map UK targeting and establishments, processing purposes, controller or processor roles, exemptions and local requirements.

    How to do this step

    Before you start

    UK entity and activity records, contracts, data flows, vendor terms and customer-facing services.

    1. Determine UK scope for each activity and identify which parties decide how and why data is used. Record actual roles and differences from contract wording.
    2. List the systems, data subjects, recipients, access locations and retention in the processing inventory.
    3. Name owners for updates and review applicable obligations such as registration or fees, representative or DPO duties with the privacy lead.

    What a reviewer should see

    A UK customer support workflow links the role decision, actual systems, vendor access and the named person who checks changes.

    When to escalate

    Raise overlapping UK and EU obligations or a vendor responsible for processing whose role is unresolved.

    What to produce

    Coverage memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    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.

    Processing inventorySpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    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.

  2. 02

    Implement lawful processing and rights

    Who Privacy operations + product When Before processing and on request

    Set the lawful basis, special category conditions and notice. Test access and other rights intake, verification and fulfillment.

    How to do this step

    Before you start

    Processing register, lawful-basis and notice records, rights queue and relevant current ICO guidance.

    1. Document the lawful basis per purpose and additional conditions where needed. Check the live notice against the record.
    2. Define what happens at intake, including proportionate identification, dates, search scope and who handles any exceptions or extensions under the applicable rules.
    3. Test search and redaction across systems and suppliers. Record responses and use the current ICO guidance on what is required.

    What a reviewer should see

    A practice access request shows when it arrived, the applicable response date, systems and teams searched, the decision and secure delivery record.

    When to escalate

    Raise a missing system owner, approaching deadline or possible disclosure of another person’s information.

    What to produce

    Privacy noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    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.

    Lawful-basis recordSpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    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.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    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.

  3. 03

    Manage risks and disclosures

    Who Legal + security When Before high-risk processing or transfers

    Perform DPIA screening, establish processor terms and assess UK international transfer mechanisms as needed.

    How to do this step

    Before you start

    Proposed activity, vendor terms, data locations and applicable UK DPIA and transfer guidance.

    1. Screen the activity and document whether a DPIA is required. Record advice where applicable and test the mitigations before launch.
    2. Confirm recipients and their roles and check contracts or sharing arrangements. Document the lawful transfer route and assessment if applicable.
    3. Create a release condition for any unresolved issue and a review trigger for expanded use or a new recipient.

    What a reviewer should see

    The supplier record identifies real storage and remote access locations, transfer mechanism where relevant, safeguards and review date.

    When to escalate

    Escalate a high-risk activity or restricted transfer before release if approval or safeguards are missing.

    What to produce

    DPIA registerSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    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.

    ContractsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    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.

    Transfer documentationSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    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.

  4. 04

    Prepare for breaches

    Who Security + privacy lead When At incident and during exercises

    Record every breach and the risk decision. Notify the ICO when required and inform affected people when the high-risk trigger is met.

    How to do this step

    Before you start

    Incident contact list, incident logs, processor contacts, affected systems and current ICO guidance.

    1. Set an out-of-hours contact and record the timeline of awareness, containment, known facts and reporting decision.
    2. Review whether the breach is reportable and whether affected individuals must be informed. Keep an explanation and approval regardless of the result.
    3. Exercise notification with incomplete facts, including gathering updates and preserving the submission record.

    What a reviewer should see

    The incident record shows why a notice was or was not required, time of the decision, reviewer and supporting facts.

    When to escalate

    Route a potential breach to the on-call privacy and incident team early so it can track the applicable deadline while facts develop.

    What to produce

    Breach logSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    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.

    Escalation and notification playbookMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes