UK cookie and marketing rules
Test what your site stores or reads on a device, then document when consent or an exception applies.
Data Act, Regulation (EU) 2023/2854
Plan data access for connected products and switching support for data processing services.
Actors covered by the relevant parts of the Data Act, including some makers of connected products, providers of related services, data holders, recipients and cloud service providers.
Documented data access, sharing and switching workflows for the chapters that apply to your role.
Personal data remains subject to data protection law. A Data Act request also needs recipient, rights, security and any trade-secret checks.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
EU Data Act 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 each chapter to roles and services · Legal + product [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
An industrial equipment customer moves to a new maintenance provider and requests telemetry access. The manufacturer verifies the customer’s request, identifies relevant data and safeguards, and tests that the export can actually be read by the new provider.
Confirm the scope of the ban and distinguish switching charges from other permitted charges.
Official reference (opens in a new tab)Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map each chapter to roles and services | Legal + product | At scoping and new product design | Set a start date | Applicability matrix; Data-flow diagram | Open |
| Build data access and controlled sharing | Engineering + data governance | Before applicable product design or access obligations | Set a start date | Data access specification; Rights workflow; Transfer assessments | Open |
| Make cloud switching work in practice | Cloud operations + contracts | Before relying on standard contract terms | Set a start date | Contract gap analysis; Exit plans; Test reports | Open |
| Track exceptions, disclosures and fees | Compliance + service owners | At requests and on legal changes | Set a start date | Request log; Exception register; Phased legal register | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Classify connected products, related services, users, data holders and processing services. Record which chapters apply, relevant dates and data exclusions.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.
Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.
Identify retrievable product data, metadata and secure channels. Verify authorized users, handle third-party requests, and protect personal data and trade secrets.
Fictional details. Use the same fields with evidence from your work.
The declared fields and units match the export, and an unauthorized account cannot access it.
Give engineering the reviewed specification and support staff the request and escalation workflow.
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.
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.
Check switching clauses, format and interfaces, exportable data and removal of obstacles. Test transfer and continuity without exposing other tenants.
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.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Document refusals, safeguards and commercial terms. Check applicable switching charges by date and keep service teams aligned with the contract.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Fictional details. Use the same fields with evidence from your work.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.