An operator nearly opened a chamber that was still under pressure. Nobody was hurt, and for two weeks nobody reported it. Asked why, they said they were afraid of getting in trouble. That is a quest the Line Manager faces in First Run's semiconductor fab map.
A near-miss is an incident that happened without anyone getting hurt. Because nobody was hurt, it often leaves no record. Yet the same cause can lead to a real accident next time, which is why many organizations treat near-miss reporting as the starting point of safety management. The trouble is new hires. They don't know what to report, whether they're allowed to, or who to tell.
This article gathers the reporting moments that recur across the fab, construction site and co-op quests in First Run, and looks at how onboarding can build the habit of reporting.
Four reasons new hires don't report
Line up the wrong answers across the three maps and the reasons reports go missing fall into four groups.
1. "I already fixed it"
In a construction tutorial, a new hire sees that the cover on a third-floor opening has been moved. Putting the cover back yourself and carrying on without reporting it is Good. The hazard is smaller, but nobody knows why the cover was moved or whether it is secure.
The co-op's price label quest works the same way. Replacing one leftover sale label is Good; checking every label from the same sale and logging the cause is Excellent. A problem that only the fixer knows about comes back.
2. "Someone must have said"
In the same opening quest, assuming the safety team will find it on patrol is Poor. New hires tend to think they can't be the first to have noticed. If everyone thinks that, nobody reports.
3. "I'll report it later"
Answers that report, but late, are usually Risky.
- Take a photo of the opening and post it in the team chat at lunch (construction)
- See signs at an older member's home, finish the delivery route, then write it up in the afternoon (co-op)
- Stop a pour after an inspection finding, then write up the reason the next day (construction)
All three look conscientious. Meanwhile a worker is walking toward the opening, a member may have collapsed and subcontractors are working from different plans. A report's value lies in its timing as much as its content.
4. "I'll get in trouble", or "maybe I'm wrong"
In the fab's gas alarm tutorial, a nearby worker says it misfires sometimes and not to worry. Taking the word of someone who works there every day and carrying on is Poor. In the co-op's temperature quest, writing that the logger may have malfunctioned and moving on is Poor.
New hires tend to trust a senior colleague's word, or blame the equipment, before their own judgment. Doubting a record without evidence is close to deleting it.
Before reporting: stop the danger
Push reporting hard enough and a side effect appears: seeing a hazard and reaching for the camera before doing anything about it.
In the construction safety manager's quest, a worker at the edge of the 14th-floor slab isn't hooked on, and the foreman says it's only five minutes. Taking a photo to share at the weekly safety meeting is Poor. The worker is still standing where they could fall.
In the temporary board quest, a crew has wired around a tripping earth-leakage breaker. Telling the crew off and reporting it to safety, but leaving the board live until an electrician arrives, is Risky. The report was made, but someone can use that board again in the meantime.
So the Excellent answers across all three maps follow the same order.
- Stop the danger. Halt the work, move people back, cut the power.
- Report right away. Tell the owner and the person in charge exactly what you saw.
- Record it. When, where and what you saw.
- Fix the cause. Look at why it happened, not just who did it.
The board quest's Excellent answer shows the whole sequence. Take the board out of use, remove the bypass and lock and tag it; while a qualified electrician traces the fault, feed the crew from another checked board, and explain why bypassing is forbidden. The danger is removed, the work continues and the same bypass doesn't happen again.
A bypass sends the signal "just don't get caught"
All three maps keep offering ways around safeguards and procedures. In the fab: a jumper on an interlock sensor, skipping a 20-minute LOTO, starting hot work and getting the permit signed tomorrow. On the construction site: bypassing a breaker and welding before the permit.
The worst answer of all is in the fab's hot-work quest: telling the crew to finish quietly before the safety team arrives, so the schedule doesn't slip. The feedback points out that this tells workers the rules only matter if you get caught. Once one bypass is allowed, the next one goes unreported. A culture that hides bypasses and a culture that hides near-misses grow from the same root.
What happens after a report shapes the culture
Telling new hires to report isn't enough, because they learn from what happens after someone reports. That is why First Run asks about the same topic from the manager's side.
In the fab near-miss quest above, the Line Manager's options are these.
- Discipline the operator and the shift lead who kept quiet, so hiding has a visible cost: Poor
- Set a near-miss KPI and reward the shift with the fewest each month: Poor
- Launch a reporting campaign with posters and talks at every shift meeting: Risky
- Thank the reporter, hold a no-blame review of system causes and fix things visibly on every shift: Excellent
The feedback says plainly why the KPI is Poor: the easiest way to lower the number is to stop reporting, so it rewards exactly the wrong behaviour. The campaign is Risky because the message is right but it doesn't remove the fear.
The construction crane near-miss has the same shape. Part of a load fell, nobody was hurt, and the subcontractor blames the signaller. Replacing the signaller and resuming, or skipping the report because nobody was hurt, is Poor. Excellent stops the related lifts, reports through procedure, finds and fixes the root cause in rigging, signalling and the exclusion zone with the subcontractor and workers, shares the lessons at an all-hands toolbox meeting, then resumes. If the response ends at replacing a person, the next near-miss won't be reported.
Designing the reporting habit into onboarding
- Put a reporting moment in the tutorials. New hires who have seen and reported a hazard once in their first week hesitate less on the real job.
- Grade handling a hazard alone differently from reporting it. With handling-alone as Good and reporting-so-the-cause-gets-fixed as Excellent, the feedback carries the difference.
- Grade late reports as Risky. It shows that timing is part of the judgment.
- Write a senior colleague's "it's fine" into the wrong answers. Like the gas alarm and the five-minute edge job, use words new hires will actually hear.
- Include manager quests. Covering how the person receiving a report should respond keeps reporting culture from becoming only the new hire's job.
- Don't rate new hires by report counts. A target to raise the count lowers report quality, and a target to cut it cuts reporting.
Checklist for near-miss reporting in onboarding
- Do the scenarios cover "already fixed", "someone must have said", "later" and "I'll get in trouble"?
- Does removing the danger come before reporting and recording?
- Is bypassing a safeguard wrong under any schedule pressure?
- Are late reports never graded as correct?
- Are disciplining reporters and count-based KPIs explained as wrong answers?
- Is there a manager quest about finding root causes rather than replacing people?
- Is it clear the quests don't replace mandatory safety training or company reporting procedures?
The industry quests are covered in more detail in Semiconductor new hire training scenarios, Construction site onboarding and Co-op and grocery onboarding scenarios.
Try workplace scenarios as onboarding quests
Pick the construction site in a new game and you'll meet a reporting moment in the second tutorial. Play the Onboarding