A Solvent Spill the Coordinator Wants Quiet

First, do not walk into the solvent or create an ignition source. I would ask the coordinator to stop work nearby, keep people out of the area, and ventilate if safe. The immediate environmental question is whether the drain is still flowing to the storm outfall; if so, the site needs to contain it now - booms, drain covers, or a vacuum truck - and should notify the state hotline if the release is reportable. I would escalate above the coordinator to the plant manager or corporate EHS, because the coordinator has already proposed not reporting it. I would document before cleanup: photos, time, location, estimated quantity, the drain map, the empty spill kit, and the absence of an incident entry. I would ask for the safety data sheet and the stormwater permit/outfall map. I would not physically clean it up myself, because that destroys evidence and takes over the operator's role. I would make clear that I cannot agree to omit it, and that the audit report is addressed to the client organization, not to the coordinator personally. If the release is ongoing and no one acts, I would call the client's corporate contact immediately.

The finding is a nonconformity against EHS-12 (containment, 24-hour incident entry, and 48-hour reportability assessment) and against emergency preparedness (ISO 14001 clause 8.2). The empty spill kit and the missing log entry are objective evidence that the process failed, not just that one employee forgot. At site level this is major because a possible reportable release went unlogged and unassessed. I would sample the corporate incident inbox and the other distribution centers' logs to determine whether the failure is systemic; that is within scope because the scope includes the corporate EHS management system. I would report the facts and require the organization to make and document the reportability determination - I would not make a legal conclusion for them. The request to omit the finding is an independence and integrity threat. I would decline, explain why, and document the conversation, the date, and the people present in the audit file, and inform my audit programme manager. The refinancing is irrelevant to the audit conclusion and increases the pressure to conceal, which is exactly why the finding must be reported.

Yes, but narrowly and with a documented rationale. The incident-reporting process is already in scope, so following the failure into the corporate incident inbox and a sample of other sites is not a scope expansion - it is proper follow-through on a process finding. The spill itself raises a stormwater question: the drain discharges to the outfall, so I would check the facility's stormwater permit coverage, whether the outfall is a permitted discharge point, whether the SWPPP identifies the drain, and whether any monitoring or inspection records exist. I would not turn the audit into a full stormwater compliance audit without client agreement, but I would document the scope change and get the client representative's approval if I extend time. I would also check whether the spill kit inspection log exists and when it was last filled, because an empty kit suggests a preventive-maintenance failure. Any expansion should be recorded in the audit plan and report so the conclusion is transparent.