Summary
- The four business days in Item 1.05 of Form 8-K come from General Instruction B.1, which starts them when the registrant determines that the incident is material — not when the incident happens.
- UnitedHealth Group's 2024 Change Healthcare series prints 21 February 2024 as the earliest event and 22 February 2024 as the filing date, and prints no determination date in the original report, either amendment or either staff letter.
- One extra field — the determination date, beside the event date — would let any reader subtract two printed dates and test the deadline. Until then the judgement at the centre of the clock stays inside the company.
The interval is not in Item 1.05
Item 1.05 tells a registrant what to describe once an incident is material: its nature, scope and timing, and its material impact or reasonably likely material impact. It does not say how long the registrant has. That sentence sits in General Instruction B.1 to Form 8-K, and it contains two verbs and one number — file "within four business days after the registrant determines that it has experienced a material cybersecurity incident" (Form 8-K).
Read it twice. The experience is the incident. The determination is a judgement about the incident, made by the party that has to file. The four days hang off the second, not the first. A registrant that experiences a material incident and takes three weeks to decide that it is material has, on the text of B.1, three weeks plus four days.
The other clock carries no number
Instruction 1 to Item 1.05 adds a second timing obligation: the registrant discloses the incident "without unreasonable delay after discovery of the incident" (Form 8-K). No days, no hours, no reasons field. Two clocks, then, both started by something that happens inside the company — one by a discovery and governed by a standard with no unit, one by a determination and governed by a figure of four business days.
What the form printed
The original report is dated 22 February 2024, states "Date of earliest event reported: February 21, 2024", carries Item 1.05 as its operative item and is signed by /s/ Kuai H. Leong, Deputy Corporate Secretary (original report; EDGAR filing index). One calendar day separates the two printed dates.
That pair is the whole of the interval arithmetic available to a stranger, and it does not touch the deadline. Four business days measured from a determination need the determination's date. The form prints the incident, then the filing. The middle is empty.
Two written statements of non-conclusion
The original report says: "As of the date of this report, the Company has not determined the incident is reasonably likely to materially impact the Company's financial condition or results of operations" (original report).
Amendment No. 1, filed 8 March 2024, repeats the sentence as of that date (Amendment No. 1). Amendment No. 2, filed 24 April 2024, reduces Item 1.05 to an update pointing at a 22 April 2024 press release attached as Exhibit 99.1, keeps 21 February 2024 as the earliest event and states no determination (Amendment No. 2).
Then the correspondence. On 14 June 2024 the company told the staff: "To date the Company has not concluded the cyber incident to be material or reasonably likely to be material", and declined to amend again (June 2024 letter). The 11 October 2024 letter answers a staff comment of 4 October that quotes the June sentence, and identifies no date on which materiality was determined (October 2024 letter).
Five documents in a fixed order: the report, two amendments, two letters. Two explicit statements that no materiality conclusion had been reached, and no determination date in any of them. That is the finding, and it is bounded to those five.
The rule, its author and its gloss
Item 1.05 arrived with the Commission's cyber disclosure release, 33-11216 (release 33-11216), published in the Federal Register on 4 August 2023 (Federal Register). The Attorney General route was set out by the Department of Justice in guidance dated 12 December 2023 (DOJ guidance), and the Division of Corporation Finance's director addressed the disclosure practice on 21 May 2024 (Gerding statement). Instruction 3 borrows the definition of "cybersecurity incident" from 17 CFR 229.106(a) (eCFR 229.106) — Item 106, the annual risk-management disclosure, not the incident rule. Its codified text was not read for this piece, so nothing here paraphrases what it requires.
The limb that lets the government move a deadline
Item 1.05(c) opens "Notwithstanding General Instruction B.1". It permits delay when the Attorney General determines that disclosure poses a substantial risk to national security or public safety and notifies the Commission in writing: up to 30 days, up to 30 more, and in extraordinary circumstances a final period of up to 60 days where a substantial national-security risk persists. Beyond that only a Commission exemptive order moves the date (Form 8-K; DOJ guidance). The registrant may delay only after the Commission has the notification, and the department tells the registrant separately.
The staff has been explicit about the sequence. Interpretation 104B.01 says the Attorney General's determination and the Commission's receipt of written notice must both occur before the Item 1.05(a) deadline, and that a request for delay, a declination, or silence from the department does not suspend the four days. Interpretation 104B.05 says a ransom payment, or the end of a ransomware attack, does not relieve the registrant of deciding whether the incident was material (C&DIs). Item 1.05(d) opens a second, narrower route for incidents subject to a delay of no more than seven business days under 47 CFR 64.2011, paired with a notice filed on EDGAR (Form 8-K).
One field would end the argument
Add a single entry to the filed Item 1.05: the date on which the registrant determined the incident was material, printed beside the date of the earliest event reported. The four-business-day ceiling then becomes arithmetic anyone can do — two dates, one subtraction — and a judgement that currently lives entirely inside the company becomes an entry a stranger can check. That is a recommendation about the design of a form, not a finding about a filer. The 2024 record reviewed here contains no filing outside the permitted window.
What this adds
BTW has written about this corporate group and this intrusion before. A 17 November 2026 briefing read two public registers against each other and found 500 people in one and approximately 192.7 million in the other, 377 days apart. Four research pieces in July 2026 followed the revenue-cycle stoppage, the financing shock to providers, the care-continuity question and the identity-control failure behind the intrusion. None of them read a securities-disclosure clock, and none is re-argued here. The company's directory entry is at UnitedHealth Group Incorporated.
The boundary
Everything above rests on five documents read on 20 November 2026, plus the instrument and its guidance. Exhibit 99.1 to Amendment No. 2 was not inspected, and the 11 October 2024 letter was only partly read. No reviewed document states whether the Attorney General route was invoked at any point. The absence of a determination date is bounded to those five filings; whether the company fixed a determination on a date it has never published is a question the reviewed record cannot answer.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






