The report that arrives before the casualty
A close call can reveal useful information even when nobody is injured and the vessel continues operating. The question is what the event tells us about the conditions, equipment, practices or decisions that allowed it—and what should change before something more serious happens.
Good catch reporting invites people to share what they noticed and how they helped interrupt a risk. The wording recognizes their contribution. It does not, by itself, establish a reporting culture; the organization’s response determines whether people will speak up again.
Define what belongs
A useful report describes an event, condition or recurring pattern that could plausibly have caused harm, or that reveals a meaningful safety weakness. Not every ordinary correction needs a formal report. A repeated problem, however, may deserve attention even if each individual occurrence appears minor.
Consider an illustrative departure scenario: lines are being slipped while shore power remains connected, and a crew member catches the oversight before damage occurs. The immediate risk has been interrupted. The report can help the operator understand how the departure checks, communication and responsibilities worked—and where they need attention.
Unexpected steering response, repeated hard landings, a recurring gangway problem or an equipment defect caught before departure can all provide useful signals. Immediate hazards need operational control first. Recording an observation must never delay that response.
Test the reporting route from the crew’s side
A system that requires several logins, a company laptop and a lengthy form may discourage the people who have the most useful information. Seasonal and part-time personnel need a route they can actually use during their working day.
A text, email, phone call, private conversation, short form or handwritten note can all begin the process. The designated safety lead can organize the information afterward. The crew member should not have to design a database entry in order to raise a concern.
A quiet inbox does not establish that hazards are absent. It may indicate that the reporting route is difficult to access or that previous reports received no response. Ask people what happens after they report, and test the process yourself.
Use a fair response
Learning requires a response that examines both behavior and operating conditions. An unintended mistake, a risk that has become normalized and a conscious disregard of substantial risk call for different consideration. Accountability remains part of the system, alongside support, coaching and correction of the conditions contributing to an event.
Recurring events across different crew members are especially important. Several difficult landings by competent captains may point to controls, berth geometry, changing conditions, communication or time pressure. Several slips at the same dock interface should prompt a review of that interface and the work performed around it.
Name who owns the loop
One clearly identified person needs responsibility for receiving information, ensuring it is recorded, setting priorities, assigning action and following up. This may be a safety captain, port captain, safety lead or operating manager. The responsibility must be explicit even when it is part of an existing role.
A lightweight tracker can record the vessel, location, observation, possible consequence, immediate action, priority, assigned owner and status. It should also show when the crew received feedback and whether the report is related to earlier events.
The sequence matters: receive, record, triage, assign, follow up, share and close. Closure means checking that the action achieved its purpose, rather than simply changing a status field.
Make the response visible
Crews should hear that the report was received, what was learned and what changed. If the permanent fix is pending, explain the interim action and when another update will be provided. Acknowledgment need not wait for perfect closure.
Measure useful learning and follow-through rather than rewarding report volume. Look for recurring themes across vessels, shifts and handoffs, then use them to guide maintenance, procedures, training and management decisions.
Begin with four commitments
- Captains and managers report their own good catches.
- Make reporting easy and explain what belongs.
- Name the person responsible for the response.
- Answer the first report and close the loop.
Good catch reporting adds an earlier opportunity for learning. Required incident, casualty and company reporting obligations continue to apply. The purpose is to notice and act on useful safety information before another event becomes a casualty.
Adapted from John Scannell’s PVA Western Region presentation, Nothing happened. And it may be the most valuable report you receive.
Discuss good catch reporting ↗