Operational GDPR: obligations, roles and auditable evidence

Pubblicato:
GDPR compliance GDPR registro dei trattamenti DPIA +2
Operational GDPR: obligations, roles and auditable evidence

The most common GDPR advice—update your privacy notices and the record of processing activities—won't get you through an audit by itself. Audits fail when an organization cannot demonstrate who performed an activity, when it happened, which data were involved and what the outcome was. Policies can be correct on paper while execution remains undocumented.

This guide is practical, not legal advice. It shows how to design responsibilities, approval paths and verifiable evidence so the chain from requirement to remediation is demonstrable: requirement → control → owner → dated evidence → immutable audit trail → issue management → remediation. An audit checks this chain over time, not whether a folder was prepared right before the auditor arrived.

H2: What GDPR means in practice

Translate legal principles into checkable questions:

  • Lawfulness, fairness and transparency: is that new use of data based on an appropriate legal ground and understandable to data subjects?
  • Purpose limitation: is the usage consistent with declared purposes?
  • Data minimisation: do we really need every field exported from the CRM?
  • Accuracy: who corrects contact information?
  • Storage limitation: who enforces retention and deletion rules?
  • Integrity and confidentiality: who can export data and what protections apply?
  • Accountability: which records prove these checks were made?

Example: a marketing manager launches a campaign using CRM contacts for a new purpose not covered by existing notices. Having a campaign approval procedure is insufficient unless you can show the approval relating to that campaign, by a named approver, on a specific date and linked to the privacy notice version in force.

H3: From principle to evidence

Principles become auditable only when turned into documented decisions and dated records. A policy states expectations; a dated approval record tied to the campaign demonstrates a concrete decision.

H2: Core obligations and the minimum evidence auditors expect

Ensure you prepare both the documents and the execution records linked to the relevant processing activity. Below are the common obligations, the typical owner for the operational control and the minimum evidence that makes the control auditable:

  • Record of Processing Activities (Art. 30)

    • Typical operational owner: DPO or designated privacy lead
    • Minimum evidence: versioned record with date, purposes, legal basis, categories of data, recipients and retention criteria
  • Privacy notices (Arts. 13–14)

    • Owner: privacy function with process owners
    • Minimum evidence: dated notice version, publication record and mapping to covered processing
  • Legal basis and purpose assessments (Art. 6)

    • Owner: data controller (or delegated role)
    • Minimum evidence: documented legal-basis assessment, signer and review date
  • Security measures (Art. 32)

    • Owner: CISO/IT manager
    • Minimum evidence: control test results, remediation tickets and proof of closure
  • Data Protection Impact Assessment (DPIA) (Art. 35)

    • Owner: process owner with DPO input
    • Minimum evidence: DPIA document, DPO opinion (if designated), controller decision and residual risk
  • Contracts with processors (Art. 28)

    • Owner: procurement/legal
    • Minimum evidence: signed contract, list of sub-processors and periodic verification
  • Breach notification (Arts. 33–34)

    • Owner: CISO and DPO
    • Minimum evidence: internal breach log, timestamp of detection, and rationale for notification decisions
  • Data subject rights (Arts. 12–22)

    • Owner: requests coordinator and DPO
    • Minimum evidence: requests log with dates, decisions and communications sent

Note: designating a DPO does not transfer legal responsibility to them. Contracts with processors must also be tested in practice: signature alone does not prove that access, deletion and incident handling work.

H3: Give documents context

exemptions based solely on headcount do not apply universally. Activities that are regular, carry risk, or involve special categories of data still require records. An updated notice without a publication date does not prove which text was available at the time of collection—keep the published version, its publication date and the scope it covered.

For every obligation, define the control, assign the executor and identify the event that produces the proof. Trigger reviews both on a justified periodic cadence and when purposes, systems or vendors change.

H2: Roles, responsibilities and segregation of duties

The controller determines purposes and means and retains accountability. It can delegate tasks but cannot delegate accountability to the DPO or to technology.

The processor acts on documented instructions. Contracts open the relationship, but auditors expect evidence that contractual obligations are enforced.

Typical roles in an operational control cycle:

  • Controller: proposes governance, approves decisions, owns accountability and receives independent verification
  • Processor: proposes technical controls, executes and reports
  • Co-controllers: formal allocation of responsibilities and joint processes for data subject contacts
  • DPO: provides advice, monitors compliance and keeps records of opinions
  • Control owner: defines controls and collects evidence, subject to independent verification

H3: Separate advice, decision and execution

Keep the DPO’s opinion, the controller’s decision and the operational evidence distinct. Record instances where the controller departs from the DPO's advice and the reason for that deviation.

Avoid situations where the same person configures an access right, approves the change and verifies the outcome. If full segregation is impractical (e.g., in small organizations), implement compensating review controls from someone not involved in the execution.

H2: Data subject rights — process and deadlines

All incoming rights requests must be logged, regardless of which mailbox they arrive through. Loss of the receipt timestamp destroys the ability to prove deadlines were met.

Relevant rights include access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20), objection (Art. 21) and automated decision protections (Art. 22).

H3: Intake, assessment and response

The standard deadline is one month from receipt, extendable by two months for complex cases or a high volume of requests—notify the data subject of the extension within the first month and explain the reasons. Internally, distinguish deadlines for the data subject from internal SLAs for IT, operational teams and external processors.

Verify the requester’s identity with proportionate means and avoid unnecessarily intrusive documentation requests.

H3: Minimum case file

Each request case file should contain: date of receipt, right claimed, identity verification steps, owner, systems and vendors involved, internal deadlines, reasoned decision, communications sent and closure date. Keep identity-check evidence without retaining unnecessary sensitive copies.

When erasure collides with a legal retention obligation (e.g., taxation), record precisely which data must remain, on what legal basis, and how their use will be limited.

H2: Minimum fields for an auditable record of processing

Operational registers must let an auditor reach systems, decisions and controls without manual reconstruction. The legal minimum record is not the same as the operational dataset needed to make processing auditable.

Useful operational fields include:

  • Unique identifier and processing name
  • Responsibilities: controller, process owner, operational contact
  • Legal basis and documented purpose
  • Scope: categories of data and data subjects, systems and processes
  • Recipients: categories, processors and links to contracts
  • Transfers: outside-the-EEA destinations and safeguards
  • Retention: retention criteria, triggers, deletion method
  • Security: applied measures and linked tests
  • Reviews: last review date, approver and next due date
  • Risk and actions: residual risk, compensating controls, findings, owner and remediation deadline
  • Evidence references: pointers to the records that prove actions and verified closures

Keep descriptive metadata separate from open remedial actions. A field marked “accesses verified” is weak unless accompanied by a dated list of reviewed accesses and the outcome of any revocations.

H2: DPIA as a documented decision process

A DPIA should follow a clear lifecycle:

  1. Describe the processing, purposes and context
  2. Assess necessity and proportionality
  3. Identify risks to rights and freedoms
  4. Define protective measures and corrective actions
  5. Gather the DPO’s opinion and record the controller’s decision
  6. Schedule periodic review and re-assessment triggers

Example: switching the supplier of a video interview tool may introduce new access paths and storage locations. That change can trigger a DPIA re-evaluation rather than a simple administrative update.

H2: Breach handling — the 72-hour window and internal logging

Not every incident is a personal data breach, but a breach is any destruction, loss, alteration, unauthorized disclosure or access to personal data. Unavailability of systems can also be a reportable issue depending on the risk.

Controllers should be prepared to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless it is unlikely the breach poses a risk to people’s rights and freedoms. Decisions to delay must be justified. Communication to data subjects is required when the breach is likely to result in a high risk.

H3: Typical breach handling sequence and minimum evidence

  • Detection: log or ticket with timestamp and reporter details
  • Risk assessment: documented assessment by DPO/CISO and controller, with rationale
  • Notification to authority: submission receipt and any explanation for delay
  • Data subject communication: message text and recipient list
  • Internal register entry: always record the event, even if no notification is made
  • Remediation: findings, corrective plan, owner and evidence of closure

Document separately: time of the event, time of first report and time the controller became aware. Waiting for a final technical report before taking decisions can block timely notifications.

H2: Common mistakes that weaken auditability

  • Backdated approvals: signing a DPIA after deployment does not prove a prior assessment
  • Perpetual exceptions: temporary derogations renewed without re-evaluation become de facto permanent and often unjustified
  • Scattered evidence: emails and chats can be evidence, but only if collected with context and linked to the control
  • Self-closed tickets: closure by the executor is not proof of effective remediation; require independent verification
  • Context-free screenshots: images without source, timestamp and operation description are weak evidence

A screenshot can be acceptable when system exports are unavailable, but attach system identifiers, acquisition time and a short description to avoid collecting excess personal data.

H3: Fix the process, not just the files

Regulators have broad corrective powers and fines that can reach substantial amounts depending on the infringement and turnover. Operational responses should document the identified gap, assign remediation and verify its effectiveness. Rewriting history makes evidence less trustworthy.

AuditReady helps centralise findings from audits, incidents, tests and manual inputs with severity, responsible owner, deadline, action and proof of closure. AuditReady does not guarantee legal compliance or assign legal responsibility—those remain with the organisation.

H2: Practical pre-audit checklist and FAQs

A perfectly ordered folder may indicate evidence created just for the audit. The most reliable test starts with a sample selected by the auditor and reconstructs decisions using only existing records. Choose a recently changed processing activity, a completed data subject request and an active supplier, then follow the trace. The point where obligation → owner → evidence → review breaks is the finding.

Pre-audit checklist:

  • Assignment: does every control have a named owner and date of assignment?
  • Temporal coverage: does the latest evidence cover the period under review with verifiable production dates?
  • Approval trail: can you reconstruct who approved, when and on which document version?
  • Exceptions: does every derogation have a justification, compensating controls, expiry and an approver different from the requester?
  • Findings: do findings have an owner, deadline and independent verification of closure?
  • Real scope: does the register reflect actual systems, vendors and data flows in use?

If the answer to any checklist item is no, create a targeted remediation task with a clear acceptance criterion: obtain the missing evidence, assess it and record the outcome.

FAQs (brief answers):

  • Is a DPO required for every small organisation? No. Article 37 lists specific cases where a DPO is mandatory (e.g., systematic monitoring on a large scale or processing special categories of data at scale). Document the assessment and re-check it when activities change.
  • Is consent always the correct legal basis? No. Article 6 sets out multiple lawful bases. Choose the basis that matches the purpose and be prepared to handle revocations of consent where it was used.
  • Do small businesses always need a record of processing? Not automatically. Article 30 includes exemptions tied to organisational size but not where processing is regular, risky or involves special categories of data. Record your assessment rather than assume an exemption.
  • Is a signed processor agreement enough? No. Contracts are necessary but not sufficient. Auditors expect proof that contractual obligations are enforced, including evidence about sub-processors and control tests.

H2: Closing note — preparing an Audit Day Pack

A reliable audit posture is built from everyday operations, not last-minute folder filling. Pick a representative processing activity and prepare an Audit Day Pack: responsibilities, deadlines, dated evidence and links to system records. Test that the pack stands up to a sample audit.

AuditReady can help you gather and preserve evidence with immutable audit trails, link controls to findings and remediation plans, and centralise the operational dataset needed for an audit. Request a demo of AuditReady (https://audit-ready.eu/?lang=en) with a concrete processing example to see how to prepare an Audit Day Pack with assigned responsibilities, deadlines and verifiable evidence.