GDPR programme readiness

How we suggest the programme is built Four steps in order: map the processing and transfers, settle roles and contracts, run the assessments, then rehearse the breach procedure. 1 Map processing and transfers What, where, who receives it. 2 Settle roles and contracts Controllers, processors. 3 Run the assessments Where risk is high. 4 Rehearse the breach procedure Against the 72 hours.
The order is our working method, not a requirement of the Regulation.

The GDPR is not one task. It is a set of records, notices, contracts, assessments and procedures that have to agree with one another, and with what the systems really do.

The short version

GDPR programme readiness is building and evidencing the records, notices, contracts, assessments and breach procedures that Regulation (EU) 2016/679 expects of an organization that handles personal data of people in the Union.

Whether the GDPR applies to you, which basis you rely on and whether a breach must be notified are legal questions that your counsel answers; we prepare the facts, the records and the procedures they work from. As of November 2026 the points below are from the Regulation as published in the Official Journal; the current consolidated text and any later amendment govern.

Who it reaches

The GDPR applies to processing in the context of an establishment in the Union, and to a controller or processor outside the Union where the processing is related to offering goods or services to people in the Union or to monitoring their behaviour there.

Where the GDPR applies to an organization outside the Union because of that offering or monitoring, it must designate a representative in the Union in writing, unless an exception in Article 27 applies; we do not act as the representative.

What the programme consists of

Each part has its own page; this one is the map. The duties are the Regulation’s and the work is ours.

DutyWhat we prepareWhere
Records of processing (Article 30)The record, built from the systemsData mapping
Impact assessments (Article 35)Assessments and the screening that decides when one is neededPrivacy impact assessments
Processors and vendorsThe vendor register and the terms to checkVendor management
Transfers (Chapter V)The transfer inventoryCross-border transfers
Data subject rightsIntake, search and response procedureRequest operations
Cookies and consentA test of what the site really doesConsent review
Breach procedure (Articles 33 and 34)The playbook and the rehearsalIncident readiness
Data protection officerA fractional officer or the programme behind oneFractional DPO

Records, assessments and officers

Article 30 requires a record of processing activities that includes the purposes, the categories of data subjects and personal data, the recipients, transfers to third countries, retention time limits where possible, and a general description of the security measures.

Article 35 requires an impact assessment before processing that is likely to result in a high risk to people, and lists three cases: systematic and extensive profiling that leads to decisions with legal or similar effects, large-scale processing of special categories of data, and large-scale systematic monitoring of a publicly accessible area.

A data protection officer must be designated by public bodies, and by controllers and processors whose core activities are large-scale regular and systematic monitoring or large-scale processing of special categories of data; others may designate one.

We build the record from the systems rather than from interviews alone, and keep the screening for assessments in the same register, so that a new system raises the question before it launches.

The breach clock

A controller must notify the supervisory authority of a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to people; a processor must tell the controller without undue delay. The Regulation also requires the controller to document each breach, with the facts, the effects and the remedial action, so that the authority can verify compliance. The European Data Protection Board explains how it reads the duty in its Guidelines 9/2022.

The 72 hours run alongside other clocks for organizations in scope of the EU’s security laws; they are set out beside each other on the incident readiness page.

The GDPR breach duty, in order Three points in order: the controller becomes aware of a breach, the authority is notified within 72 hours where feasible unless there is no risk, and the breach is documented either way. Controller becomes aware The clock starts here. Notify within 72 hours Where feasible; reasons if later. Document the breach Notified or not.
A processor tells the controller without undue delay.

What is at stake

The GDPR sets two ceilings for administrative fines: up to 10 million euros or 2% of worldwide annual turnover for breaches of obligations such as records, security, breach notification and impact assessments, and up to 20 million euros or 4% for breaches of the basic principles, data subject rights and transfer rules, in each case whichever is higher. The ceilings are the Regulation’s, and a fine is set case by case by the supervisory authority.

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What does GDPR programme readiness cover?

GDPR programme readiness is building and evidencing the records, notices, contracts, assessments and breach procedures that Regulation (EU) 2016/679 expects of an organization that handles personal data of people in the Union.

Who does the GDPR apply to?

The GDPR applies to processing in the context of an establishment in the Union, and to a controller or processor outside the Union where the processing is related to offering goods or services to people in the Union or to monitoring their behaviour there.

What must a record of processing contain?

Article 30 requires a record of processing activities that includes the purposes, the categories of data subjects and personal data, the recipients, transfers to third countries, retention time limits where possible, and a general description of the security measures.

How fast must a breach be notified?

A controller must notify the supervisory authority of a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to people; a processor must tell the controller without undue delay.

When is an impact assessment required?

Article 35 requires an impact assessment before processing that is likely to result in a high risk to people, and lists three cases: systematic and extensive profiling that leads to decisions with legal or similar effects, large-scale processing of special categories of data, and large-scale systematic monitoring of a publicly accessible area.

Do you decide whether the GDPR applies to us?

Whether the GDPR applies to you, which basis you rely on and whether a breach must be notified are legal questions that your counsel answers; we prepare the facts, the records and the procedures they work from.

Tell us where your data subjects are

Say what you do, where your systems and customers are, and what is already in place. The reply says what a scope would cover. Related: the European Union page.

Discuss a scope