An AI incident can trigger a potentiallyapplicable reporting period you can’t see.
The deadline is rarely the hard part. Different regimes attach reporting periods to different facts, knowledge standards, or determinations, and the hard part is recognizing and assessing a potential trigger within the applicable period, before days burn. Drill it before it’s real.
Not legal advice. This is a readiness drill that grades your notification process from your own marks. It is date-agnostic and asserts no deadline; it files nothing, confirms no regulatory obligation, and scores no people. Notification duties (GDPR, the EU AI Act, SEC, HIPAA, and US state breach laws) vary by jurisdiction and change often — confirm which apply to you and every deadline with qualified counsel.
Update notice — version 1.2.0 (2026-10-10). This package replaces version 1.1.0 of the AI Incident Reporting & Regulatory-Notification Drill. Weights are unchanged. Numerical thresholds are unchanged (75 and 50). The original gate triggers are unchanged. Results were renamed on 2026-10-09: NOTIFIABLE-READY AS DESCRIBED became NOTIFICATION PROCESS READY AS DESCRIBED, TIGHTEN became PROCESS GAPS, and WOULD MISS THE CLOCK became CRITICAL NOTIFICATION-PROCESS GAP; the program roll-ups DRILL-READY, GAPS and WOULD MISS NOTIFICATION became PROGRAM READY AS DESCRIBED, PROGRAM GAPS and CRITICAL PROGRAM GAP. No result is renamed in version 1.2.0. New qualifications: every result prints its result note, the three marks are defined as evidence marks, and the “drill first” line is now Priority control, named whenever any control is below 2. New top-band eligibility condition: a scenario that scores 75 or more, with the gate not fired and any control marked 0, now reads PROCESS GAPS instead of NOTIFICATION PROCESS READY AS DESCRIBED, and a program cannot read PROGRAM READY AS DESCRIBED while any scenario contains a zero. The bottom result is not split: CRITICAL NOTIFICATION-PROCESS GAP comes from a score below 50 or from the gate, as before. Re-run earlier rows: yes. A row that read the top result with any control marked 0 now reads PROCESS GAPS; scores do not change. Existing buyers: the download link in your original purchase email now serves version 1.2.0.
You knew the deadline. You missed it anyway.
Each regime has its own trigger
Under GDPR Article 33 the period runs from awareness of a personal-data breach. Domestic registrants generally file Item 1.05 Form 8-K within four business days after determining that a cybersecurity incident is material; the determination may not be unreasonably delayed following discovery. For a covered entity, HIPAA discovery occurs when the breach is known or would have been known through reasonable diligence; analyze individual, HHS, media, and business-associate notification paths separately. Record each potential trigger point separately.
One incident, several potentially applicable reporting periods
The same event can implicate a data-breach reporting duty, an AI safety report, and a securities disclosure at once — each with a different deadline and a different start.
No one was authorized to act on it
A plan that routes the decision to a committee that meets next week can miss a reporting period. Someone has to be authorized to assess and document potential trigger points and activate the appropriate escalation path, even at 2am.
Drill a scenario. Read the result your marks produce.
This is the live scoring logic from the engine. The “AI Act serious incident” preset scores 82 and still reads CRITICAL NOTIFICATION-PROCESS GAP — because no one is authorized to assess potential trigger points and escalate. Give it an authorized decision-maker and it clears. A zero on any other control prevents the top result: the score can sit in the top band and the result reads PROCESS GAPS.
2 = Documented evidence identified and recorded for review
Context: Defined, rehearsed path; awareness time recorded
2 = Documented evidence identified and recorded for review
Context: Potentially applicable regimes are mapped to their scope, triggers, recipients, required content, timing, exceptions, and responsible owners, with legal review where appropriate.
0 = No documented evidence of the control
Context: No one authorized to assess and document potential awareness, discovery, materiality, or other applicable trigger points and to activate the appropriate escalation path
2 = Documented evidence identified and recorded for review
Context: Authorities, portals, channels mapped in advance
2 = Documented evidence identified and recorded for review
Context: Templates and internal records are maintained, and any staged-reporting path is documented for the regimes that permit or require it.
2 = Documented evidence identified and recorded for review
Context: Rehearsed cross-functional parallel-track process
The top mark records the user’s assessment of process evidence. It does not certify that the process satisfies an applicable notification rule or deadline.
This reflects the marks you entered, not a review of your process, and it is not a prediction about any actual incident. It means that your score is below 50, or that detection-to-awareness, regime, trigger, and severity triage, or the named, authorized decision-maker is marked at zero. It is not a legal conclusion about any obligation, deadline, filing, proceeding, or enforcement action. A missed internal escalation can consume time after a legal trigger has occurred — or delay a determination that must be made without unreasonable delay. This drill does not decide whether or when either event occurred.
Trigger-assessment gate fired: no one is authorized to assess and document potential trigger points and activate the appropriate escalation path. The score alone would read NOTIFICATION PROCESS READY AS DESCRIBED, but a potential trigger nobody assesses can consume time a reporting period allows.
Priority control: A named, authorized decision-maker for trigger assessment and escalation
Weighted to 100. The gate forces CRITICAL NOTIFICATION-PROCESS GAP when you could not recognize and assess a potential trigger within the applicable period (⚡ detection or triage) or no one is authorized to assess potential trigger points and escalate (⚡ authority). A zero on any control prevents NOTIFICATION PROCESS READY AS DESCRIBED. Date-agnostic — it grades your process, never a specific deadline. Not legal advice.


How the gate works, in one image
How the AI Incident Reporting & Regulatory-Notification Drill scores notification readiness and reads CRITICAL NOTIFICATION-PROCESS GAP when the authorized decision-maker is missing — the same math the demo runs, as a diagram you can share or embed anywhere.
View & embed the full diagramThe same verdicts, from the runnable engine.
Verbatim output from the included Python engine on the six-scenario sample. The workbook reproduces these byte-for-byte.
==========================================================================
AI INCIDENT REPORTING & REGULATORY-NOTIFICATION DRILL
==========================================================================
Customer PII leak via AI chatbot
verdict: NOTIFICATION PROCESS READY AS DESCRIBED (score 94/100)
Priority control: Cross-track coordination
note: This is not a determination that any incident is reportable, that
any deadline applies to you, or that any notification you make would
be timely or sufficient. It means only that, on your own marks, the
six controls this drill grades read as in place for the one scenario
you ran. It grades a rehearsal, not an incident — and the six controls
are not a list of your obligations. Confirm which regimes apply to
you, and every deadline, with qualified counsel. RedHub did not test
the process, verify any incident facts, determine legal reportability,
or assess whether a deadline applies.
Model failure harms a user (AI Act serious incident)
verdict: CRITICAL NOTIFICATION-PROCESS GAP (score 82/100)
gate: CRITICAL NOTIFICATION-PROCESS GAP — no one is authorized to assess and document potential trigger points and activate the appropriate escalation path
Priority control: A named, authorized decision-maker for trigger assessment and escalation
note: This reflects the marks you entered, not a review of your process,
and it is not a prediction about any actual incident. It means that
your score is below 50, or that detection-to-awareness, regime,
trigger, and severity triage, or the named, authorized decision-maker
is marked at zero. It is not a legal conclusion about any obligation,
deadline, filing, proceeding, or enforcement action. A missed internal
escalation can consume time after a legal trigger has occurred — or
delay a determination that must be made without unreasonable delay.
This drill does not decide whether or when either event occurred.
Same incident after naming an on-call authorized decision-maker
verdict: NOTIFICATION PROCESS READY AS DESCRIBED (score 100/100)
No scored control is below the top mark.
note: This is not a determination that any incident is reportable, that
any deadline applies to you, or that any notification you make would
be timely or sufficient. It means only that, on your own marks, the
six controls this drill grades read as in place for the one scenario
you ran. It grades a rehearsal, not an incident — and the six controls
are not a list of your obligations. Confirm which regimes apply to
you, and every deadline, with qualified counsel. RedHub did not test
the process, verify any incident facts, determine legal reportability,
or assess whether a deadline applies.
Material cyber incident in a public-co AI system
verdict: PROCESS GAPS (score 50/100)
Priority control: Detection-to-awareness path
note: This reads your own marks against the scoring bands; it is not an
assessment of your incident-response program. Gaps named here are the
ones this drill grades — it does not enumerate every notification duty
that may apply to you.
Vendor/sub-processor breach reaches your data
verdict: CRITICAL NOTIFICATION-PROCESS GAP (score 50/100)
gate: CRITICAL NOTIFICATION-PROCESS GAP — you could not recognize and assess a potential trigger within the applicable period
Priority control: Regime, trigger, and severity triage
note: This reflects the marks you entered, not a review of your process,
and it is not a prediction about any actual incident. It means that
your score is below 50, or that detection-to-awareness, regime,
trigger, and severity triage, or the named, authorized decision-maker
is marked at zero. It is not a legal conclusion about any obligation,
deadline, filing, proceeding, or enforcement action. A missed internal
escalation can consume time after a legal trigger has occurred — or
delay a determination that must be made without unreasonable delay.
This drill does not decide whether or when either event occurred.
Prompt-injection exfiltrates regulated records
verdict: CRITICAL NOTIFICATION-PROCESS GAP (score 56/100)
gate: CRITICAL NOTIFICATION-PROCESS GAP — you could not recognize and assess a potential trigger within the applicable period
Priority control: Detection-to-awareness path
note: This reflects the marks you entered, not a review of your process,
and it is not a prediction about any actual incident. It means that
your score is below 50, or that detection-to-awareness, regime,
trigger, and severity triage, or the named, authorized decision-maker
is marked at zero. It is not a legal conclusion about any obligation,
deadline, filing, proceeding, or enforcement action. A missed internal
escalation can consume time after a legal trigger has occurred — or
delay a determination that must be made without unreasonable delay.
This drill does not decide whether or when either event occurred.
--------------------------------------------------------------------------
PROGRAM: CRITICAL PROGRAM GAP (3 of 6 CRITICAL NOTIFICATION-PROCESS GAP · exposure 50.0%)
--------------------------------------------------------------------------
Marks: 0 = no documented evidence of the control; 1 = partial or
incomplete evidence; 2 = documented evidence identified and recorded for
review. The top mark records the user’s assessment of process evidence. It
does not certify that the process satisfies an applicable notification
rule or deadline.
It grades whether selected notification-process controls are documented
from the user’s marks; it does not predict whether the organization will
meet a particular deadline. It encodes no specific deadline, so it does
not break when a regime's dates shift. It grades a process, never people,
and confirms no actual regulatory obligation. A readiness drill, not legal
advice. Confirm which regimes apply, and every deadline, with counsel.The AI Act scenario above is a hypothetical future-state rehearsal. Under the Digital Omnibus, the Annex III high-risk obligations apply from 2 December 2027, and serious-incident reporting falls primarily on providers; a deployer’s information duties, and any circumstances in which Article 73 applies to a deployer, should be mapped separately. Confirm system classification, your operator role, territorial scope and the applicable date before relying on any scenario here.
Six controls, weighted to 100. The weakest trigger-assessment control is dispositive.
⚡ Detection-to-awareness path
Regimes use different triggering events and knowledge standards. Record detection, discovery, awareness, escalation, and any required legal determination separately; confirm the applicable start point, decision-maker, recipient, and deadline with counsel. Here “awareness” is operational shorthand rather than a universal legal trigger.
⚡ Regime, trigger, and severity triage
Which regimes may apply, what event or determination starts each reporting period, and which potentially applicable period is shortest? For rehearsal purposes, use the shortest potentially applicable period as the initial internal triage target. Each regime retains its own scope, trigger, recipient, required content, timing, and exceptions; satisfying one does not satisfy the others.
⚡ A named, authorized decision-maker for trigger assessment and escalation
Someone authorized to assess and document potential awareness, discovery, materiality, or other applicable trigger points and to activate the appropriate escalation path, at any hour — not a committee that meets Monday.
Regulator contact map & filing channel
Authorities, a lead supervisory authority where one applies, portals, and channels mapped before the incident, not during it.
Notification drafting and incident-record path
Pre-drafted templates, a maintained internal incident record, and — where the applicable regime permits or requires staged reporting — an initial report that can be supplemented as additional information becomes available. GDPR Article 33(4), for example, permits information to be provided in phases when it cannot be provided at the same time.
Cross-track coordination
One incident can trigger several potentially applicable reporting periods at once — legal, security, comms, privacy pre-aligned.
⚡ = a trigger-assessment gate control. If detection-to-awareness or severity triage is absent, or no one is authorized to assess potential trigger points and escalate, the scenario is CRITICAL NOTIFICATION-PROCESS GAP regardless of score. The gate worsens only — it never promotes a verdict.
The marks, for every control: 0 = no documented evidence of the control; 1 = partial or incomplete evidence; 2 = documented evidence identified and recorded for review. The top mark records the user’s assessment of process evidence. It does not certify that the process satisfies an applicable notification rule or deadline.
Top-band rule: a zero on any control prevents NOTIFICATION PROCESS READY AS DESCRIBED. A scenario that scores 75 or more with the gate not fired and any control marked 0 reads PROCESS GAPS, and the result says so. It is an eligibility condition for the top band, not a gate. Every result names a priority control whenever any control is below 2.
A readiness drill, not a compliance ruling.
It is
- A rehearsal of your incident-notification process.
- Date-agnostic — it grades the process, never a deadline.
- A deterministic, offline engine + workbook you control.
It isn’t
- Legal advice, a filing service, or a certification.
- A ruling on whether an incident is legally reportable.
- A score of people — it grades a process.
Not legal advice. This is a readiness drill that grades your notification process from your own marks. It is date-agnostic and asserts no deadline; it files nothing, confirms no regulatory obligation, and scores no people. Notification duties (GDPR, the EU AI Act, SEC, HIPAA, and US state breach laws) vary by jurisdiction and change often — confirm which apply to you and every deadline with qualified counsel.
Whoever owns the first hour of an AI incident.
- Security, privacy, and compliance leads who own incident response.
- Legal and DPO functions tracking potentially applicable GDPR, AI Act, SEC, HIPAA, and state reporting periods.
- Teams deploying high-risk or customer-facing AI that could cause a reportable incident.
- Not a filing tool — it rehearses readiness, it doesn’t notify anyone.
- Not a ruling on what’s reportable — confirm that with counsel.
- Not a postmortem tool — that’s the close-out gate it pairs with.
Detect and notify, then recover and close out.
Ransomware & AI-Outage Recovery Readiness Drill
Would you actually recover? The recovery-side drill to this notification-side one.
ViewAI Incident Postmortem & Readiness Gate
Close the loop after: grade the blameless writeup and gate the close.
ViewNIST AI RMF / US AI Governance Readiness Kit
The governance program this incident drill lives inside.
ViewAnswers before you buy.
It grades whether selected notification-process controls are documented from the user’s marks; it does not predict whether the organization will meet a particular deadline. It works scenario by scenario. For each drilled incident you mark six controls 0/1/2 (0 = no documented evidence of the control; 1 = partial or incomplete evidence; 2 = documented evidence identified and recorded for review): your detection-to-awareness path, regime, trigger, and severity triage, whether a named person is authorized to assess potential trigger points and escalate, your regulator contact map and filing channel, your notification drafting and incident-record path, and cross-track coordination. The six are weighted to a 0–100 score banded NOTIFICATION PROCESS READY AS DESCRIBED, PROCESS GAPS, or CRITICAL NOTIFICATION-PROCESS GAP, and the program rolls up to PROGRAM READY AS DESCRIBED, PROGRAM GAPS, or CRITICAL PROGRAM GAP. A zero on any control prevents NOTIFICATION PROCESS READY AS DESCRIBED: a scenario that scores 75 or more with the gate not fired and any control marked 0 reads PROCESS GAPS, and a program cannot read PROGRAM READY AS DESCRIBED while any scenario contains a zero or reads CRITICAL NOTIFICATION-PROCESS GAP. The top mark records the user’s assessment of process evidence. It does not certify that the process satisfies an applicable notification rule or deadline. It grades the process, never people, and never asserts a deadline as the verdict.
Because of the trigger-assessment gate, which is the heart of the drill. A scenario is forced to CRITICAL NOTIFICATION-PROCESS GAP regardless of score when either gate-triggering pattern is present: you could not recognize and assess a potential trigger within the applicable period (your detection-to-awareness path or your regime, trigger, and severity triage is absent), or no one is authorized to assess and document potential trigger points and activate the appropriate escalation path. The deadline is rarely the hard part — the hard part is that a potentially applicable reporting period can begin at a trigger you may not recognize or assess, so days burn before anyone registers it. Different regimes attach reporting periods to different facts, knowledge standards, or determinations. Record detection, discovery, awareness, escalation, materiality assessment, and other potentially relevant trigger points separately. In the worked example a model-failure scenario scores 82 yet reads CRITICAL NOTIFICATION-PROCESS GAP because no one is authorized to assess potential trigger points and escalate; the next row is the same incident after naming an on-call authorized decision-maker, and it clears at 100. The gate worsens only — it never promotes a verdict.
An AI incident rarely triggers only one reporting period. The same event can trigger a personal-data breach notification (e.g. GDPR Article 33, under which, where required, a controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of a personal-data breach), an AI safety / serious-incident report (e.g. EU AI Act Article 73, which principally imposes serious-incident reporting duties on providers of covered high-risk AI systems, with different periods for specified incident categories), a material-cyber disclosure (e.g. SEC Item 1.05, under which domestic registrants generally file Item 1.05 Form 8-K within four business days after determining that a cybersecurity incident is material; the determination may not be unreasonably delayed following discovery), sector duties like HIPAA breach notification (for a covered entity, HIPAA discovery occurs when the breach is known or would have been known through reasonable diligence; analyze individual, HHS, media, and business-associate notification paths separately), and US state breach laws with their own windows. Potentially applicable regimes may use different triggers, recipients, content, deadlines, and exceptions. For rehearsal only, the drill uses the shortest potentially applicable period as an internal triage target; meeting one regime’s process does not establish that another is satisfied. These specifics are named in the playbooks as planning references — the engine itself is deliberately date-agnostic so it does not break when a regime’s dates shift. Which regimes apply to you, and every deadline, must be confirmed with qualified counsel.
Because the deadlines move, and a tool that hard-codes a date is wrong the moment a regime shifts. The EU AI Act’s high-risk timeline, state breach windows, and sector rules all change. So the drill grades the thing that actually determines whether you meet the applicable notification deadline — your process for recognizing and assessing potential trigger points, escalating, and filing — rather than checking a calendar. That makes the verdict durable, and it keeps the tool honest: it grades whether selected notification-process controls are documented from the user’s marks; it does not predict whether the organization will meet a particular deadline. It also does not decide whether a specific statute applies to you. Which regimes apply, and every deadline, must be confirmed with counsel.
No. It is a readiness drill that grades your notification process from your own marks. It files nothing, contacts no regulator, connects to no system, and confirms no actual regulatory obligation — it cannot tell you whether a given incident is legally reportable or to whom. It is not legal advice, a filing service, a certification, or a safe harbor, and it scores a process, never people. Use it to find and close the gaps in your incident-notification readiness, then confirm which regimes apply to you and every applicable deadline with qualified counsel.
A runnable zero-dependency Python engine, a workbook that reproduces it exactly (Start Here, Dashboard, and a Drill Scorecard with the mark definitions built into each column), a six-scenario worked example, and two playbooks: a Drill Facilitator Playbook for running the tabletop and marking honestly, and a Notification-Readiness Runbook that sets the controls beside several regimes as planning references and walks the trigger-assessment, triage, and filing steps. Pick the incident types that matter to you — a data breach, an AI serious incident, a material cyber event — drill each one, and, where a control is below the top mark, start with the priority control the tool names. Deterministic and offline; one-time purchase, lifetime access, 12 months of updates.
Don’t discover an applicable notification
period after it expires.
One purchase, lifetime access, 12 months of updates. $79, once.
Not legal advice. This is a readiness drill that grades your notification process from your own marks. It is date-agnostic and asserts no deadline; it files nothing, confirms no regulatory obligation, and scores no people. Notification duties (GDPR, the EU AI Act, SEC, HIPAA, and US state breach laws) vary by jurisdiction and change often — confirm which apply to you and every deadline with qualified counsel.
Sold by RedHub AI LLC · Secured by Stripe · redhub.ai