Home › Resources › Guides › GDPR compliance

Resources · Implementation guide

GDPR compliance guide: 10 operational steps

In shortTo comply with GDPR in practice, establish whether you are a controller or a processor, record your processing, identify a lawful basis for each purpose, tell people what you do with their data, and build working processes for rights requests, processor contracts, security, impact assessments, breach notification and international transfers. Accountability means being able to prove each one.

What are the steps to run GDPR compliance?

Each step names the article it comes from.

  1. Establish your role

    Decide for each activity whether you determine the purposes (controller) or act on instructions (processor).

    Article 4
  2. Record your processing

    Keep a record of processing activities: purposes, categories of data and people, recipients, transfers and retention.

    Article 30
  3. Identify a lawful basis

    Each purpose needs one of the six lawful bases. Special categories of data need an additional condition.

    Articles 6 and 9
  4. Tell people

    Give clear information about what you do with personal data, at the time you collect it.

    Articles 13 and 14
  5. Handle rights requests

    Have a process for access, rectification, erasure, restriction, portability and objection, with a deadline tracker.

    Articles 12, 15 to 22
  6. Control your processors

    Use processors that give sufficient guarantees, under a contract with the required terms.

    Article 28
  7. Secure the data

    Apply technical and organisational measures appropriate to the risk, and test them.

    Article 32
  8. Assess high-risk processing

    Carry out a data protection impact assessment before processing that is likely to result in high risk.

    Article 35
  9. Prepare for breaches

    Detect, assess and record personal data breaches, and notify the authority and individuals where required.

    Articles 33 and 34
  10. Govern international transfers

    Transfer personal data outside the EEA only with a valid mechanism, such as an adequacy decision or standard contractual clauses.

    Articles 44 to 49

Go deeper: GDPR framework guide · data privacy articles.

Which GDPR deadlines should you track?

The time limits that most often become audit findings.

ObligationTime limitArticle
Notify the supervisory authority of a personal data breachWithout undue delay and, where feasible, within 72 hours of becoming aware33(1)
Respond to a data subject's requestWithout undue delay and within one month; extendable by two further months where necessary12(3)
Processor tells the controller of a breachWithout undue delay after becoming aware33(2)
Carry out a DPIABefore the processing starts35(1)

Read each article for its conditions and exceptions. National law and guidance from your supervisory authority also apply.

Can you evidence your GDPR compliance?

Tick what is done. Nothing is saved or sent; the list resets when you leave the page.

What goes wrong most often?

01

Policies without records

A privacy policy exists, but there is no record of processing or request log.

Instead: keep the records that prove the policy is followed.

02

Consent used for everything

Consent is chosen as the basis where another fits better and consent cannot be freely given.

Instead: choose the basis that matches the purpose.

03

Breach clock started late

The 72 hours are counted from the end of the investigation.

Instead: count from when you became aware.

How does QULDEX support this?

Multi-Framework Audit Engine

One control and one piece of evidence count towards every framework they apply to.

See the module

GDPR compliance: common questions

What does accountability mean under GDPR?

The controller is responsible for complying with the principles and must be able to demonstrate that compliance. In practice that means keeping records.

Does every organisation need a data protection officer?

No. Article 37 requires one for public authorities and for organisations whose core activities involve large-scale regular monitoring or large-scale processing of special category data.

Is there a GDPR certificate?

There is no general certificate of GDPR compliance. Approved certification schemes exist for specific processing operations under Article 42.

Is this legal advice?

No. It is general guidance. Take advice on how the law applies to you.

Sources

  1. Regulation (EU) 2016/679 (General Data Protection Regulation)
  2. European Data Protection Board, guidelines on breach notification, data protection impact assessment and transfers. edpb.europa.eu
  3. ISO/IEC 27701:2025, Privacy information management systems: Requirements and guidance

Run privacy audits with the evidence already linked

Controls, evidence, findings and corrective actions together, mapped to each framework.

Schedule
Book a Demo