The incident report form had seven fields: date of incident, location, personnel involved, description, root cause, corrective action taken, and estimated cost of damage. Huang had been staring at it for forty minutes.
The thing she needed to report wasn’t an incident. It was eighteen months of a chemical storage protocol that had prevented three probable spills and one near-certain contamination event. She knew this because she’d modeled it. The probability curves were clear. Without the protocol, the plant’s spill rate would have matched the industry baseline of 2.3 per year. With it, they’d had zero.
The form didn’t have a field for “date of non-incident.” There was no box for “root cause: continuous maintenance of conditions that prevented the event from acquiring a root cause.” She tried “corrective action taken” and wrote the corrective action predated the incident by eighteen months, which is why there was no incident, but the system flagged her entry as non-compliant because it referenced no incident number. She tried “estimated cost of damage” with the $340,000 the spills would have cost, but the field validated against actual expenditures and rejected the figure.
She could file an incident. She could wait for the protocol to lapse, let a spill happen, and fill out the form perfectly. Date: concrete. Location: specific. Root cause: traceable. Corrective action: implementable. Cost: calculable. The incident would be legible in every way the prevention was not.
The form could hold weather. It could not hold climate.
Huang closed the form. She opened the quarterly summary and typed what she always typed: Operations nominal.