Start hereMap data and establish scope
~98 days leftOpen step
Guide library
Regulation Europe

EU GDPR

General Data Protection Regulation · Regulation (EU) 2016/679

Map your processing and put data rights, safeguards and breach decisions into daily operations.

Who it applies to

Controllers and processors in scope under Article 3, including some organizations outside the EU that offer goods or services to people in the Union or monitor their behavior there.

What you’ll produce

A demonstrable privacy program with documented accountability controls.

Evaluate controller and processor duties separately. Local rules can affect employment, minors, health data and regulator jurisdiction.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which processing and legal entities are in scope?
Ask Legal and the privacy lead to determine territorial scope and controller or processor roles for each activity. Confirm whether DPO or representative duties apply. Preserve the analysis for activities that may have more than one role.
Who can stop a launch or an unsafe transfer?
Name product and data owners and define how the privacy lead can bring an unresolved legal basis, high-risk activity or transfer to leadership. Reserve Engineering time for product and vendor changes.
Who responds when a request or incident arrives?
Set the queue owner, backup, escalation channel and authority to notify. Ensure service and vendor contracts route privacy and incident requests to a staffed contact.

How to spend the first week

  1. Have Product, HR, Marketing, Support and Procurement each bring one live workflow. Observe real screens or system exports and mark recipients, transfers and retention.
  2. Choose one workflow and follow it from collection to deletion. Review the role, purpose, basis, notice, contract and retention with the people who operate it.
  3. Test one rights request and one incident call. Record who answers out of hours, where decisions are logged and which contacts are missing.

What to review each week

Track processing activities without a documented purpose or basis, rights cases near deadline, unresolved DPIAs and vendor changes missing a transfer review.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

EU 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  Map data and establish scope · Privacy lead + data owners [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. Have Product, HR, Marketing, Support and Procurement each bring one live workflow. Observe real screens or system exports and mark recipients, transfers and retention.
2. Choose one workflow and follow it from collection to deletion. Review the role, purpose, basis, notice, contract and retention with the people who operate it.
3. Test one rights request and one incident call. Record who answers out of hours, where decisions are logged and which contacts are missing.
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

  • Are you a controller, processor, or both for different activities?
  • Where are your customers, processing staff, vendors and personal data located?

Worked scenario

An analytics service handles usage data for its customers and account data for its own billing. Legal separates the two roles, then assigns who answers rights requests and who contacts the authority for each activity.

What to read next

  • UK GDPR

    Plan separately for processing covered by the UK regime.

  • EU Data Act

    Check whether connected-product data access or cloud switching work is also relevant.

FROM THE SOURCE

Cases and numbers

Court judgment · 16 July 2020

Schrems II changed how organizations assess transfers

The Court of Justice of the European Union invalidated the EU–U.S. Privacy Shield decision then in force and upheld the use of standard contractual clauses in principle. It examined whether safeguards can actually protect the data in the circumstances of a transfer.

What to check Map where data is accessed and what protections exist there. When relying on clauses, check whether additional safeguards are needed and record the decision under current transfer rules.

CJEU judgment in case C-311/18 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
Plan evidence for EU GDPR and other programs
The whole journeyabout 98 days across 5 steps
  1. 01Map data and establish scopePrivacy lead + data owners · ~14 days
  2. 02Document lawful bases and noticesLegal + product · ~21 days
  3. 03Manage suppliers and transfersLegal + vendor management · ~21 days
  4. 04Run rights requests and impact assessmentsPrivacy operations + DPO if required · ~28 days
  5. 05Exercise security and breach responseSecurity + privacy lead · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 14 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map data and establish scopePrivacy lead + data ownersAt initiation and on material changesSet a start dateProcessing inventory; Role and territorial scope memoOpen
Document lawful bases and noticesLegal + productBefore processingSet a start dateLawful-basis register; Privacy notices; Consent recordsOpen
Manage suppliers and transfersLegal + vendor managementBefore sharing or transferring dataSet a start dateProcessor agreements; Transfer register; Transfer assessmentsOpen
Run rights requests and impact assessmentsPrivacy operations + DPO if requiredBefore high-risk processing and when requests arriveSet a start dateRights workflow; DPIA screening and register; Training recordOpen
Exercise security and breach responseSecurity + privacy leadOngoing and within legal deadlines when an incident occursSet a start dateIncident log; Notification templates; Tabletop evidenceOpen
0 of 5 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

    Map data and establish scope

    Who Privacy lead + data owners When At initiation and on material changes

    Identify establishments, targeting and monitoring. Document controller/processor relationships, purposes, retention and recipients. Determine Article 30 recordkeeping obligations.

    How to do this step

    Before you start

    Legal entities, system and vendor inventory, data flows, product terms, processing locations and business owners.

    1. Interview teams with live workflows. Trace personal data from collection through systems, support, vendors, backups and deletion. Record approximate volumes and retention source where relevant.
    2. Record a distinct purpose and factual role for each activity. Compare what the contract says with who actually determines purpose and essential means.
    3. Populate the processing record with applicable fields. Ask each owner to review their rows and set triggers for updates when products or vendors change.

    What a reviewer should see

    A support ticket activity lists purpose, role, categories, recipients, transfer details where relevant, retention and safeguards. A named owner verifies it against the actual ticketing system.

    When to escalate

    Escalate processing whose owner, location, role or purpose is uncertain, especially where children, employees or sensitive data are involved.

    What to produce

    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.

    Role and territorial scope 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.

  2. 02

    Document lawful bases and notices

    Who Legal + product When Before processing

    Select the Article 6 basis for each purpose and apply Article 9 conditions where relevant. Draft notices and build consent withdrawal where consent is relied on.

    How to do this step

    Before you start

    Processing inventory, collection screens, contracts, existing consent logs and local law questions.

    1. Evaluate a lawful basis for each purpose. Where special category data is involved, document the applicable additional condition. If relying on legitimate interests, record purpose, necessity and the balancing assessment.
    2. Map required notice information to collection and indirect receipt. Update the notices and verify which version people actually see.
    3. Test any consent flow used from presentation through withdrawal. Capture the purpose, notice version and how downstream systems receive the withdrawal.

    What a reviewer should see

    A user can withdraw a test marketing consent and the suppression is reflected in the mailing platform. The record shows when and what consent was obtained, where consent is the basis.

    When to escalate

    Raise purposes assigned a basis without supporting facts, sensitive processing lacking an identified condition, and consent that cannot be withdrawn in practice.

    What to produce

    Lawful-basis registerSpreadsheet

    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.

    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.

    Consent recordsSpreadsheet

    Gather first

    • Approved consent language and purpose IDs
    • User interface or paper form
    • Audit event and withdrawal behavior

    How to prepare it

    1. Record the exact consent version, the purpose, the decision and its timestamp. Link to the interface or form shown to the person.
    2. Use an internal reference to the person or parent. Limit access and avoid placing underlying identity documents in the log.
    3. Exercise refusal and withdrawal. Verify that each downstream system stops relying on consent when required, and record the result.

    Worked example

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

    Subject reference
    Account reference C-018
    Purpose and notice version
    Optional product updates, notice v4
    Decision and timestamp
    Opted in, 2026-11-02 14:12 UTC
    Capture channel
    Account preferences, unchecked by default
    Withdrawal and effect
    2026-11-12, active list updated, ticket P-123

    Check before handing it over

    You can demonstrate what the person saw, how they acted and how the decision was honored.

    Provide the consent log and tested withdrawal flow to privacy operations and downstream system owners.

  3. 03

    Manage suppliers and transfers

    Who Legal + vendor management When Before sharing or transferring data

    Put Article 28 terms in place for processors. Map international transfers and document a Chapter V mechanism and assessment where required.

    How to do this step

    Before you start

    Supplier register, DPA and subcontractor terms, data locations, remote access arrangements and current legal mechanisms.

    1. Ask each vendor where data is stored, supported and transferred and who the subprocessors are. Check production access and routine support against the answers.
    2. Match processor contracts and transfer review to the activity and actual destination. Where required, document the mechanism, assessment and supplementary measures.
    3. Set reminders for subprocessor or location changes. Require Procurement and Engineering to clear the privacy review before rollout.

    What a reviewer should see

    A vendor record links actual support and storage locations to the contract, subprocessors, documented mechanism where applicable and decision owner.

    When to escalate

    Raise unknown destinations, a missing processor agreement or a new transfer that lacks defensible coverage before production use.

    What to produce

    Processor agreementsMemo

    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 registerSpreadsheet

    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.

    Transfer assessmentsSpreadsheet

    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

    Run rights requests and impact assessments

    Who Privacy operations + DPO if required When Before high-risk processing and when requests arrive

    Set up identity checks and deadlines for rights requests. Screen changes for DPIAs and document mitigation and regulator consultation where needed.

    How to do this step

    Before you start

    Requests queue, processing inventory, identity verification procedure, product change register and applicable DPIA criteria.

    1. Log receipt and deadline, verify identity proportionately, then assign search, correction or deletion tasks to system owners. Route exceptions, extensions and third-party data questions to the privacy lead.
    2. Test a case across production systems and processors. Keep confirmation of what was searched and how the decision and response were made.
    3. Screen new or changed processing against DPIA requirements and local supervisory authority lists. Where needed, document risks to people, mitigations and any need for prior consultation.

    What a reviewer should see

    A practice access case tracks request scope, search systems, third-party review, approval and secure response. A DPIA records who assessed the residual risk and when.

    When to escalate

    Escalate cases likely to miss their deadline or processing with unmitigated high risk before launch.

    What to produce

    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.

    DPIA screening and registerSpreadsheet

    Gather first

    • Specific data-processing proposal and affected groups
    • DPO input where appointed
    • Article 35 and national authority lists and guidance

    How to prepare it

    1. Record the activity, purposes and data flows. Check the high-risk indicators and relevant authority lists. Save the screening decision and who made it.
    2. Where a DPIA is required, describe the processing and its necessity and proportionality. Identify risks to people and practical measures to address them. Record DPO advice and consultation where applicable.
    3. Take the finding to the person who can authorize or stop the activity. If high risk remains without sufficient mitigation, evaluate prior consultation under Article 36 before processing.

    Worked example

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

    Activity and purpose
    DPIA-008, customer support quality review. The proposal was to transcribe every call from French and German accounts and look for repeated product issues.
    Screening and decision
    The Privacy Lead determined a DPIA was required on 2026-09-09. The original design involved systematic review of caller and employee speech, and recordings might include sensitive details.
    Necessity and alternatives
    Ticket categories alone missed repeated installation issues. The team chose a four-week sample with manual removal of direct identifiers before analysis. The tool produces issue categories only.
    Harm and treatment
    A transcript could expose a caller’s health information or be used to score staff. Exclude sensitive calls, restrict access to two reviewers, bar staff scoring and delete the pilot transcripts after 30 days.
    DPO advice and remaining risk
    The DPO asked for a deletion check and confirmation that the provider will not reuse data for training. On those conditions, the controller recorded residual risk as moderate and prior consultation as unnecessary for the revised pilot.
    Release gate and review
    The controller’s Product Director approved the scoped pilot on 2026-10-01 after vendor confirmation and deletion test DT-016. Return to Privacy before increasing volume, adding individual scoring or extending retention.

    Check before handing it over

    A reviewer can trace the screening result, assess its evidence and see who decided whether processing may begin.

    Give the register and full DPIA, where required, to the processing owner and DPO.

    Training recordSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

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

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  5. 05

    Exercise security and breach response

    Who Security + privacy lead When Ongoing and within legal deadlines when an incident occurs

    Test escalation from processors and internal teams. Document the risk decision, regulator notice if required and high-risk data subject communications.

    How to do this step

    Before you start

    On-call roster, incident logs, affected data and users, processor contacts and supervisory authority details.

    1. Record detection, when the organization became aware of the personal data breach and what facts were known at each point. Identify the entity’s role and the competent authority.
    2. Assess risk to individuals and document the decision. A controller generally notifies the authority within 72 hours of awareness unless the breach is unlikely to result in risk, and assesses whether high risk triggers communication to people. A processor notifies the controller without undue delay.
    3. Exercise staged notification with incomplete facts. Keep copies, receipts, approvals and the rationale for any delay or decision against notification.

    What a reviewer should see

    A tabletop packet contains a timestamped incident record, risk assessment, decision owner, draft notice and record for any non-notification decision.

    When to escalate

    Use the on-call escalation for a suspected personal data breach. Have Privacy and Legal calculate the clock while Security investigates.

    What to produce

    Incident 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.

    Notification templatesMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

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

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

    Tabletop evidenceMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

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

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    An absent participant can see what was tested, what happened and why an action was assigned.

    Send approved findings to action owners and file the record for governance or assessment.

Common questions

Is the GDPR breach deadline always 72 hours?

For a reportable personal data breach, a controller notifies the competent authority without undue delay and, where feasible, within 72 hours of awareness. An exception applies where the breach is unlikely to create a risk to people’s rights and freedoms. Document how you reached the decision.

EUR-Lex · Regulation (EU) 2016/679 (opens in a new tab)

What is the difference between a processing record and a DPIA?

An Article 30 record describes processing activities. A DPIA evaluates the necessity, proportionality and risks of a proposed activity when it is likely to result in high risk. A processing inventory gives you inputs for the DPIA screening decision.

EUR-Lex · Regulation (EU) 2016/679 (opens in a new tab)
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