You notified on partial facts and the affected-record count later grew tenfold — how do you handle it?

## Growth is normal; contradiction is not Scope almost always grows. The first determination is made on partial telemetry under time pressure, and every subsequent week of analysis — recovered archive logs, a second egress path, the originals for another few hundred object ids inspected — adds records. Regulators and customers see revised figures constantly and do not treat an increase as a failure in itself. What they do treat as a failure is a second filing that **contradicts** the first. The difference is set entirely by the wording of the original notification, which is why the way you write the first one is the real subject of this question. ## Wording that survives a tenfold increase Three properties make a first notification amendable: - **Scope as of a date, not as a total.** `800 individuals identified to date` rather than `800 individuals affected`. - **The method stated alongside the number.** `Identified from provider audit events covering 12 March to 24 April; earlier activity is outside our retained telemetry.` A reader can then see exactly why the figure could move, and in which direction. - **The open questions named.** `The review of the remaining period and of a further set of transferred objects continues; we will supplement.` A promise to supplement makes the second filing an expected event rather than a surprise. And one sentence to avoid: `no evidence of access to other records` where the truth is that no telemetry existed to look at. That is the sentence that converts a routine scope increase into a question about whether the organisation misled anyone — and it is a wording problem, not an evidence problem, because `our telemetry over the earlier period cannot establish whether further records were retrieved` says the same operational thing and stays true. ## The mechanics of supplementing - **File against the original reference.** It is one incident with a revised scope, not a new incident. Withdrawing and refiling breaks the chain of what was known when. - **State the delta and its cause.** What changed, by how much, and which analytic step produced it. `Retention on the egress path was recovered from an archive, extending the window by nineteen days and adding roughly 11,000 individuals` is a sentence a reader can accept. - **Say whether the categories changed.** Ten times as many people is one thing; the appearance of a new category of data is a materially different notification and may change who must be told and how. - **Handle the individuals already notified.** People told they were affected do not need telling again, but people newly identified do, and anyone whose risk profile changed because a new data category emerged may need a second, different message. - **Restate what is still open.** If the window is still not fully covered, say so again. A supplementary notification that quietly implies completeness sets up a third correction. - **Keep one case record with versions.** The internal record should show the determination memo, the first filing, the analytic step, and the revised scope in sequence. Overwriting the earlier figure destroys the evidence that the process worked. ## The internal half of the problem A tenfold increase lands on people who thought the incident was closing. Two failures are common. The first is a scope increase discovered by someone who does not know it is a scope increase — an analyst finishing a backlog of object inspections with no route back to the notification owner. The fix is that the case stays open with a named owner until the scope statement is final, and every analytic thread reports into it. The second is re-litigating the original decision instead of processing the delta; the earlier determination was correct on the facts then available, and the memo is what shows it. ## What an interviewer is listening for The weak answer treats this as an unfortunate event to be managed. The strong answer says: this was foreseeable, the first notification was written to be amended, here is the sentence that made that possible, here is the sentence I refused to write, and here is the mechanism that guaranteed the new records reached the notification owner rather than dying in an analyst's queue.