A US Chemical Safety Board investigator arrives at a refinery aromatics unit three days after a pressure relief valve release sent a hydrocarbon cloud drifting toward the property line. She sits across a laminate table from the board operator who was on console when the alarm sounded at 03:42. He walks her through what the DCS showed, when he silenced the high level alarm, what the outside operator said on the radio, why the bypass valve was cracked open under a verbal permit. Forty five minutes of conversation. She writes eleven bullet points in a pocket notebook. The final CSB Root Cause Report is published twenty two months later.
Between the walkdown and the report is a documentation gap that determines whether the recommendations to OSHA and EPA hold up, whether the operating company's insurer settles the fenceline civil suit, and whether the operator's counsel gets to argue two years later that a specific phrase was never said.
The Console to Report Problem
The CSB investigates chemical incidents covered by OSHA Process Safety Management. Under 40 CFR 68 and the CSB investigation protocol, investigators conduct voluntary interviews with control room operators, board operators, outside operators, unit engineers, maintenance supervisors, and contract workers within days of arrival on site. Those interviews become the primary factual record. Twenty four months later they are cited verbatim in the final report, in the accompanying safety recommendations to OSHA and EPA, and in the civil suits that follow.
There is no court reporter in the meeting room. There is a paper notebook, a pen, and an investigator who is also trying to sketch a P&ID from memory while the operator explains what the sight glass looked like the morning of the release.
By the time the operator has finished walking through the sequence, the investigator has written PSV 03:42 no reseat, bypass open, verbal permit, MOC after startup, alarm silenced. Every other detail lives in her head until she opens a laptop in a hotel room six hours later.
Multiply that by twelve interviews across board operators, outside operators, unit engineers, maintenance techs, permit writers, and the shift supervisor. Twenty two months later the draft report cites a specific verbal permit exchange between the board operator and the maintenance supervisor. Neither of them remembers the exact wording. The operating company's counsel deposes both. The wording in the draft report does not survive contact with either witness. The recommendation to OSHA about verbal permit practice loses its anchoring evidence and gets rewritten.
Why Current Solutions Fail
- Voice memos on a phone. Produce one long unlabeled file per session. Whoever needs to find the exact moment the operator said "bypass" has to scrub through forty five minutes with no timestamp and no speaker separation. Twenty two months later, when the final report is being cite-checked, the file has been through four laptop refreshes and lives on nobody's known drive.
- Body worn cameras. Record every hallway conversation between investigators as well as the interview itself. That footage becomes discoverable under Federal Rule 26 in subsequent civil actions against the operating company and, more delicately, against the CSB's own draft findings. What was intended as a memory aid becomes a document production headache.
- Pen and paper. Cannot capture the twenty second pause where the operator hesitates before saying the permit was verbal. Cannot preserve the exact phrase the outside operator used to describe the sight glass. Two years later the operator's counsel will argue that phrase was never said, and the notebook is the only thing that answers.
- Standalone dictation recorders. Capture the words but strip the timing. CSB defensibility hinges on when a statement was made relative to physical evidence, DCS trend data, and Emergency Response Team logs. A single unlabeled MP3 cannot answer that. It also cannot separate the investigator's questions from the operator's answers, which matters when a leading question ends up quoted as if it were the witness's own words.
- DCS printouts alone. Show every setpoint change, alarm event, and operator action with a timestamp. What they cannot show is why the operator did what he did. That story only exists in the interview, and the interview only exists if it was captured properly.
What Actually Works
A field workflow that captures ambient interview audio continuously, timestamps every utterance against elapsed time from session start, separates speakers by role, and produces a searchable transcript indexed by process safety keyword.
AmyNote uses OpenAI's latest Speech API for transcription and Anthropic's Claude Opus for structured extraction. It runs a per session pass that separates the CSB investigator, the board operator, the outside operator, the unit engineer, and the maintenance supervisor into distinct speaker lanes. Every mention of a pressure safety valve, Management of Change filing, HAZOP finding, Lockout Tagout permit, or Job Safety Analysis is auto tagged. Investigators can later query what did the board operator say about silencing the high level alarm and get back forty two seconds of audio with the surrounding context, elapsed time from session start, and every timestamp on the DCS trend that lines up.
- Speaker-separated transcript per session: board operator vs unit engineer vs maintenance supervisor, each on their own lane, so a leading question from the investigator never gets accidentally attributed to the witness.
- Process safety tags: PSV, MOC, HAZOP, LOPA, LOTO, permit to work, alarm rationalization, safe operating limit. Every mention is indexed with a jump-to timestamp.
- Elapsed time index tied to unit clock and DCS trend markers, so the investigator can align "he silenced the alarm at 03:44" in the transcript with the historian record.
- Local storage on the investigator's device. No cloud sync required inside the plant firewall, which matters when the site's IT policy blocks outbound traffic during an active investigation.
- Semantic search across the full case file. Query "what did the maintenance supervisor say about the verbal permit" months later and jump straight to the exchange.
Both OpenAI and Anthropic contractually guarantee zero training on user data. Audio is encrypted in transit; processing copies may be retained to deliver and recover requested features. Transcripts are stored locally on device with encrypted transport. No PSM-covered facility interview audio sitting on a third party server. No draft-stage witness statement floating on someone else's disk when the operating company's law firm serves a preservation letter.
How This Changes the Report Cycle
Twenty two months is a long time to hold a conversation in memory. The moment the draft report cites a specific verbal exchange, the operating company's counsel will test that citation against the notebook and against any recording. If the citation cannot be defended, the recommendation attached to it moves from finding of fact to inference. Inferences carry far less weight when the CSB sends recommendations to OSHA and EPA, and they carry almost none in the civil litigation that follows.
A speaker-separated transcript with elapsed-time index changes that calculus. The draft report cites the exchange, the witness deposition confirms the wording, and the recommendation stays anchored to a factual record that survives cross examination. Investigators stop reconstructing at midnight in a hotel room. They stop writing eleven bullet points and hoping. The physical evidence, the DCS trend data, and the human account converge on a single case file instead of three fragments that have to be re-stitched years later.
The result is a control room interview record that survives cross examination three years later when the civil suit from the fenceline community finally reaches deposition, and that gives OSHA a defensible foundation for whatever compliance action follows.
Getting Started
Install AmyNote before your next incident response deployment. Bring it up before the first pre-interview walkdown. Let it record ambient audio through every board operator and unit engineer session. When you get back to the hotel the transcript is already parsed, speakers separated, PSV and MOC mentions tagged. Your CSB draft cites field statements you actually captured, not the ones you tried to reconstruct at midnight in a laptop.
Originally published as an X Article by @AmyNoteApp.
