Notification clock
The regulatory time window (for example, GDPR Article 33's "without undue delay and, where feasible, not later than 72 hours") that begins running from an organization's awareness of a qualifying personal data breach, requiring notification to the relevant supervisory authority. The precise jurisdiction-by-jurisdiction analysis of who must be notified and when is owned by Topic 11.4. (see Topic 11.4)
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Certified AI Data Governance Professional (CADGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The regulatory time window (for example, GDPR Article 33's "without undue delay and, where feasible, not later than 72 hours") that begins running from an organization's awareness of a qualifying personal data breach, requiring notification to the relevant supervisory authority. The precise jurisdiction-by-jurisdiction analysis of who must be notified and when is owned by Topic 11.4. (see Topic 11.4)
A binding deadline for reporting an incident to a regulator, stated at clause level with its exact trigger event. The PDPA clock (s 26D(1)) runs from the day the organisation makes its s 26C assessment, not from the day of the breach; the MAS Notice FSM-N05 clock (para 7) runs from discovery of a relevant incident for banks, with parallel notices for other financial-institution sectors.
The legally mandated time window, most often triggered by a breach, within which an organization must notify a supervisory authority, affected individuals, or both, once it becomes aware of the incident. GDPR Article 33 sets a without-undue-delay standard with a 72-hour benchmark for notifying the supervisory authority; many jurisdictions set separate clocks for notifying affected individuals.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Mock Defense I · The Capstone: Deploy and Defend, Certified Agentic AI Governance Professional (CAAGP)
- The taxonomy of data incidents: breach, leak, poison, drift, and wrongful training · Data Incidents, Certified AI Data Governance Professional (CADGP)
- The 2 a.m. data incident: run the response live, stakeholders calling · Data Incidents, Certified AI Data Governance Professional (CADGP)
Where it shows up at work
A definition is where Notification clock starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Classifies AI incidents by severity, runs containment, preserves evidence, manages notification, and closes the loop with lessons learned.
One lesson on this page teach it as a primary outcome.
Classifies information, applies least privilege, sets retention and acceptable-use rules, and controls what may enter a prompt, a log or an embedding.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Chief Privacy Officer, AI privacy editionneeds working knowledge
- AI Security Architectneeds working knowledge · 8 open postings this week
- Chief Information Security Officer, AI security focusneeds it at depth
- AI Incident Response Leadneeds it at depth · 1 open posting this week
- Chief Risk Officer, AI risk editionneeds working knowledge
- Physical AI Safety Engineer, autonomous systems editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: EU AI Act Article 73; ISO/IEC 42001 Annex A incident controls; NIST AI RMF MANAGE 4; ISO/IEC 27001.
One interview question about it
An AI system has just caused harm to a customer. Walk me through the first 48 hours.
Asked of candidates for ai incident response and recovery. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Cybersecurity and IT carries it as work you can show: Incident playbooks and post-incident reviews are your artifacts.
- A cybersecurity or information assurance degree carries it as a claim to back up: Incident response is a course; AI incidents add model failure to the playbook.
- Privacy and data protection carries it as a claim to back up: Classification and retention rules are familiar territory.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.