An investigation report is written for accuracy. Getting it right — establishing the timeline, tracing the causation chain, confirming findings before they’re published — takes days or, for a serious incident, weeks. The public doesn’t wait that long to form an opinion about what happened. Employees talk. Photos from a site can circulate before the first shift ends. Families, clients, and the community start asking questions almost immediately. Whatever fills that gap in the first few hours largely determines how the incident is understood, regardless of what the eventual investigation finds.
Two Different Documents, Two Different Jobs
It’s worth being precise about what’s being discussed here, because it’s easy to conflate with a genuine legal obligation. Under Malaysian OSH law, employers have a mandatory duty to notify DOSH of reportable incidents within a defined timeframe. That notification is a statutory requirement, non-negotiable, and separate from everything discussed in this article.
A press release, or a prepared public statement, is a different thing entirely — not a legal requirement under the OSH Act, but a deliberate communications practice. Its audience isn’t the regulator. It’s everyone else who’s watching: employees who need to know their workplace is being managed responsibly, families of anyone affected, clients assessing whether to keep working with the company, and a wider public that will draw conclusions with or without input from the company itself.
What Happens Without a Plan
Companies that have prepared for the technical investigation but not for this window tend to handle it the same way: someone improvises a response under pressure, often before the facts the eventual investigation will establish are even confirmed. That improvised statement — made too early, sometimes contradicted by what the investigation later finds — creates a second problem stacked on top of the first. It’s rarely intentional. It happens because nobody had already decided, in advance, who speaks, what gets said before the investigation concludes, and what explicitly doesn’t get said until it does.
The absence of any statement carries its own risk. Silence in the hours after a serious incident is frequently read as evasiveness or a lack of concern, even when the internal response was fast, appropriate, and genuinely focused on the people affected. What’s visible from the outside isn’t the quality of the internal response — it’s whether anyone from the company said anything at all.
What a Prepared Response Actually Requires
A workable approach doesn’t mean having a press release pre-written for every hypothetical incident. It means deciding, ahead of time, on a small number of things: who within the company is authorised to speak publicly, what can be confirmed and said in the first hours without waiting for the full investigation, and what specifically should not be said until findings are verified — because premature detail is exactly what gets contradicted later and damages credibility on both fronts at once.
It also means recognising that this preparation sits alongside the investigation, not after it. A company that only starts thinking about its public response once the technical report is finished has already missed the window where most of the public narrative gets set.
Why This Belongs in the Same Conversation as Investigation Quality
A rigorous, well-structured investigation report and a considered public response are solving two different problems, but they’re connected. An investigation that’s genuinely thorough gives a company something honest to say in the following days and weeks. A company with no communications plan, even with an excellent eventual investigation, has already let the first few hours be defined by rumour, a hurried statement, or silence — and the eventual report rarely gets the same audience the initial narrative did.
The Practical Question
If a serious incident happened at your workplace tomorrow, ask who would speak to the outside world in the first few hours — before the investigation has even properly started. If there’s no clear answer, that’s the gap worth closing, alongside whatever work is already going into the investigation process itself.
Want your team prepared for both the technical investigation and the response that has to happen around it? Cikgu Barrier’s Incident Investigation Basics programme covers the practical structure of a credible investigation — the foundation any honest public response has to be built on. Available in-house and as a public workshop across Malaysia.