Ask five people in a health-services administration team when the clock starts after a data incident and you may get five answers: when the alert fired, when the vendor called, when the lawyer confirmed, when the investigation finished, or when the newspapers noticed. In fact the answer depends on which rule applies, and the rules do not agree. This comparison, drawn from the Ops Atlas discussion of ResponseOps, sets several reporting regimes side by side so administrators can see what really starts each timer. It covers non-clinical administration only and is background information, not legal advice.
Why compare the clocks at all
Reporting deadlines sit at the end of the response sequence the Atlas describes, yet they shape the beginning of it. A team that knows a short deadline may apply will declare an incident sooner, assign a decision-maker earlier and keep cleaner notes. A team that treats reporting as an afterthought discovers the constraint only when the deadline has passed. The Atlas lists missed deadlines due to unowned awareness decisions among its standard anti-patterns, which tells you how often it happens.
The comparison framework
To compare regimes fairly, examine four properties: what event begins the clock, how long the first deadline is, how many stages follow, and who receives the notice. The snapshot below reflects the Atlas as of October 2026. Regulations move, so treat each line as a prompt to confirm the current text with counsel.
Regime one: a European privacy regulation
- Trigger: awareness of a personal-data breach. The European data-protection board describes awareness as reasonable certainty that a breach has occurred.
- First deadline: seventy-two hours.
- Later stages: updates may follow in phases as facts emerge.
- Practical consequence: the argument about when you were “aware” is the real battleground, so write down the reasoning at the time.
Regime two: a European network and information security directive
- Trigger: a significant incident at an in-scope entity.
- First deadline: an initial alert in the first day, a fuller notification at three days, and a final report at one month.
- Practical consequence: a three-stage cadence rewards teams that keep a running fact sheet, because each stage reuses the previous one.
Regime three: a financial-sector resilience regulation
- Trigger: classification of an incident as major, with an outer limit measured from first awareness.
- First deadline: four hours after classification, never more than a day after awareness, with an intermediate report at three days and a final at one month.
- Practical consequence: the trigger is an internal judgement, so the classification step needs an owner and criteria in advance.
This regime is not specific to health services, but it illustrates a general point: some clocks are tied to your own classification, which makes the discipline of classifying quickly a regulatory matter.
Regime four: a United States securities filing rule
- Trigger: a determination that a cyber event is material to a listed company.
- First deadline: four business days after that determination.
- Practical consequence: business days, not calendar days, and a judgement-based start. The Atlas also notes a 2025 petition asking the regulator to rescind the item; its status was unchanged at the Atlas’s mid-October 2026 check.
Regime five: an Indian national agency
- Trigger: occurrence of a reportable cyber incident, as defined by the agency.
- First deadline: six hours, the shortest on this list.
- Practical consequence: there is almost no room to deliberate, so reporting contacts and templates must exist before an event.
Regime six: a United States health-privacy rule
- Trigger: discovery of a breach of unsecured protected information.
- First deadline: up to sixty days.
- Practical consequence: the long window can create complacency, though the clock is a ceiling, not a target, and the Atlas notes that other duties may bite sooner.
A seventh item sits in a separate category. A U.S. law on reporting for critical infrastructure, carrying a three-day incident notice and a one-day ransom-payment notice, is described by the Atlas as not yet in force. Watch it, since planning costs less before a rule applies.
A worked illustration of two clocks colliding
Consider an invented administrative office that discovers, on a Friday afternoon, that a shared document store has been reached by an unknown party. The first question is whether anything was taken. At this stage the facts are thin, and the team’s instinct is to wait until Monday. The comparison shows why that instinct is risky. If an Indian agency rule applies, six hours is already running; if a European privacy rule applies, the three days could expire on Monday afternoon, depending on when awareness is judged to have begun; and a four-hour clock tied to classification would start only when someone decides to classify, which is itself a decision that can be delayed.
The Atlas does not ask teams to report prematurely. It asks them to make a recorded judgement: what is known, what is not, who decided and when. A short note saying “awareness not yet established, because the access log is incomplete, review at 18:00” is far more defensible than silence. The ResponseOps discipline treats the awareness decision as a defined task with a named owner, and treats the note as evidence.
What the comparison reveals
Three patterns stand out. First, the starting points differ in kind: some begin with a fact such as an occurrence, others with an internal judgement such as awareness, classification or materiality. Judgement-based triggers put weight on your documentation. Second, the lengths range from six hours to two months, a ratio of more than two hundred. Third, most regimes involve more than one stage, so a running fact sheet beats one-off reports.
The Atlas draws a practical conclusion: build a clocks map with counsel, assign one person to decide awareness, and rehearse the decision in an exercise. Our own reading is that preparation has to happen inside the organisation: a deadline does not pause while a team hunts for a phone number.
Applying it without a large team
An administrative office can act on this in a week. Draw a one-page table with the six regimes above in rows and the four properties in columns, then mark which rows plausibly apply to you after talking with an adviser. Next, store the contact details for each recipient offline. Lastly, schedule a thirty-minute rehearsal where the group practises saying the declaration sentence and naming who decides awareness.
People who like structured planning may recognise the format from household budgeting guides such as our budget-planner walkthrough for a festival month, where the benefit comes from writing categories down in advance. The same logic appears in a simple budget book for village households: a plain ledger beats memory.
Keeping the table alive
A clocks map is a living document. Give a single owner the job of reviewing it each quarter against official regulator pages, not third-party summaries, and stamp the review date on top. When the map changes, tell the incident lead. Add a line for each partner whose contract imposes its own notice period, because contractual deadlines are often shorter than statutory ones and are easy to forget. Finally, attach the map to the plan used in tabletop exercises so that every drill includes the question “which clock is running now?”.
Document ownership also matters for continuity. If the person who maintains the map is on leave when an incident begins, the deputy should know where the latest copy lives, both on paper and in an offline folder. Include recipients’ preferred channels and any forms they require. A fifteen-minute tidy-up each quarter is far cheaper than discovering that a template has been withdrawn on the very day it is needed.
Sources and a caution
For the underlying detail, consult the Ops Atlas entry covering ResponseOps. It states clearly that the term is the Atlas’s own and that contracts should say incident response. It also reminds readers that regulations are changing, which is the best reason to review your clocks map each year rather than treating the first version as final.