Chapter 26: Ordinary Safety
Grant made retaliation sound exactly like workplace safety, which was why I needed him to define both.
On Monday morning, he sat across from me in a WMG conference room with Dana, Daphne, and the company records custodian present, each holding a separate authority record.
The first page in front of him answered Friday's protection request for the unidentified active employee.
Daphne had authorized restricted access to that record ID while the request was reviewed.
No identity, department, complaint, or contact information appeared.
Only the custodian and the designated employee-relations officer could open the file during the interim period.
Protection was a responsible action, not evidence that the protocol had been abused.
Grant turned to the explanation he wanted entered into the board record.
He described D05 as a coordination tool for ordinary moments when separate departments could otherwise make an emergency worse.
A threat at a worksite might require security, legal, and employee-relations staff to act together.
A reporter waiting outside an employee's home could require privacy support and a controlled communications response.
A false online claim about a hospital project could require monitoring until verified facts were available.
None of those examples sounded sinister.
“That is what the protocol is for,” Grant said.
“In the abstract, that is reasonable,” I replied.
The concession changed the room more than an accusation would have.
“Then what exactly are you challenging?” he asked.
Grant began another example, but Dana raised one hand.
“Put the standard in writing,” she said.
He asked which standard we believed was missing.
“Begin with the standard WMG says should govern normal use,” I said.
I laid Friday's page-number index beside his blank statement page without claiming the index proved any employee had been harmed. I was not shopping for a confession inside a safety policy.
I was demanding a test that a future independent reviewer could apply to actual records after lawful selection and authorization.
The first question was what documented condition allowed a protocol file to open.
The second was which roles had to approve an external-stability designation.
The third was when an auditor, complainant, or protected issue required separation from threat and media categories.
Any emergency exception also needed a deadline, a reviewing role, and a visible correction path.
Grant said no responsible policy could predict every emergency.
“Then define discretion without pretending it has no boundary,” I said.
That made him pause over his own wording.
He did not like my premise, but he could answer it without conceding misconduct.
Daphne directed that his final explanation be entered into the WMG board channel as the company's current position.
The custodian typed while Grant dictated, then projected each paragraph for correction.
Grant read the completed statement aloud before signing it.
Normal use required a documented safety, legal, privacy, or verified communications trigger tied to an identified operational risk.
Media monitoring alone could not authorize an employment action or public characterization of an employee.
Employee identities were to remain limited to personnel with an assigned operational need.
External-stability designations required approval from two designated roles outside the requesting manager's sole control. An emergency exception could begin with one approver, but a second review had to be recorded within one business day.
If the second review failed, the designation had to be suspended and its access narrowed.
Grant signed beneath a sentence stating that the document described WMG's standard, not a finding about any historical case.
WMG had gained the strongest version of its defense: a safety explanation that made sense on its face.
I gave up the easier argument that every protective mechanism was only a weapon with polite branding.
The custodian then displayed only the trigger date, designation, and approval field for the Issue 17 record.
Grant's written standard required two approving roles.
Jonah's row contained one: Andrew Whitmore.
I asked where the second approval was.
Grant did not explain the missing field.
Instead, he slid a one-page count memo across the table and turned the discussion from authorization to scale.
Only nine current external-stability records.