The Evidence Trail in a Maritime Incident Investigation: What Investigators Look For
There is a particular moment that comes after a serious maritime incident. The immediate emergency may have passed, the vessel may be safe or at least stable, shore management is involved, and the first reports are being prepared. Then the questions begin.
What happened? When did you first become aware of the problem? Who did you tell? Why did you make that decision? What information did you have at the time? What procedure were you following? Was the defect known previously? Why was the corrective action closed? Why was the vessel allowed to continue operating?
For the person being asked those questions, the experience can be deeply uncomfortable, even where nothing improper has occurred. Decisions that may have been made quickly, under pressure and with incomplete information are now being examined slowly, methodically and with the benefit of hindsight. The environment in which the original decision was made and the environment in which that decision is later assessed can be very different.
That difference matters.
You remember the pressure. The investigator sees the record.
At the time of the incident, you may have been dealing with several competing pressures at once: weather, operational commitments, crew limitations, technical uncertainty, commercial demands, incomplete information, a defect that appeared manageable, or a procedure that did not quite fit the circumstances.
You may also have spoken to a superintendent, consulted an engineer, referred to a manual, reviewed previous maintenance, or made a judgement call based on years of experience. At the time, those things may have formed part of a perfectly rational decision-making process.
Months later, however, much of that context is no longer immediately visible. What remains is the record: a maintenance entry, an email, a logbook, a risk assessment, a defect report, a photograph, a procedure, a closed corrective action, perhaps a few messages, and the recollections of the people involved.
This is where one of the most important realities of any investigation becomes apparent: what you remember doing and what the organisation can demonstrate you did may not be the same thing. That does not mean the recollection is wrong. It means the evidence trail may be incomplete.
“But everyone knew about it.”
This is a sentence that can sound entirely reasonable when it is said. The defect had been discussed. The chief engineer knew about it. The master knew. The superintendent had been told. People ashore were aware. It was not hidden.
The investigator will then begin to ask a different set of questions:
Who knew about the issue?
When did they first know?
How was the issue reported?
Was it recorded formally?
Who was responsible for acting on it?
Was the risk assessed?
Were temporary controls introduced?
Was the matter escalated?
Who was responsible for follow-up?
What evidence was relied upon when the issue was eventually considered closed?
This is where informal organisational knowledge can become fragile. Maritime organisations function through conversations, telephone calls, messages, meetings and professional relationships. Much of that information can be operationally real without being formally captured.
The difficulty appears later, when someone has to reconstruct what the organisation actually knew and what happened as a result of that knowledge. There can be a substantial difference between something being known somewhere inside an organisation and the organisation having properly managed that knowledge.
The decision made at 0200 looks different at 1000 six months later
Hindsight has enormous power. Once the outcome is known, information that appeared ordinary before the incident can suddenly appear significant. A warning that seemed minor can look obvious. A defect that appeared manageable can look critical. A decision to continue operations may appear questionable because everyone now knows what happened afterwards. But the person making the decision did not know the ending.
A fair reconstruction therefore requires more than simply identifying what decision was made. It requires understanding the information environment in which that decision was made.
If your decisions are being examined, you would want the evidence to show:
what information was available to you at the time;
what information was not available;
what procedures or technical guidance you relied upon;
who you consulted;
what alternatives were considered;
what risks were identified;
what controls were put in place; and
why the eventual decision appeared reasonable at the time.
That is the difference between a record of an action and a record of a decision.
The latter is considerably more valuable.
Finding your own evidence should not become another investigation
One of the more frustrating situations after an incident is knowing that supporting information exists but not knowing exactly where it is.
The maintenance record may sit in one system. The OEM instruction may be buried inside a lengthy technical manual. The relevant email may have been sent months earlier. Inspection photographs may sit in a shared drive. A corrective action may be recorded somewhere else. A superintendent’s comments may exist in correspondence that the vessel cannot easily access. Another vessel in the same fleet may even have experienced a similar problem, but that information may never have reached the people dealing with the present issue.
The person being questioned can therefore find themselves saying things such as, “I know we dealt with this,” or, “I know there was an email,” or, “I know this happened before.” Those statements may all be true. The problem is that truth becomes much easier to establish when the relevant information can actually be found, connected and understood in context.
This is why centralised information is not merely an administrative convenience. It is part of organisational memory.
The worst time to reconstruct organisational memory is after something has gone wrong
Most maritime organisations do not design their information systems around investigations, nor should they. The primary purpose of those systems should be to provide accurate and current information; strengthened by senior expertise that helps junior personnel interpret, apply and act on that knowledge with confidence and judgement. Hence those same systems should allow important operational information to be found and connected when it matters.
If a technical issue develops, the people responsible for managing it should ideally be able to see the relevant history without searching across half a dozen disconnected systems. That might include previous defects, maintenance activity, manufacturer guidance, inspection findings, risk assessments, corrective actions, technical correspondence and lessons from similar events elsewhere in the organisation.
The point is not to create more documentation. The objective is to reduce the effort required to understand the situation.
That is one of the ideas behind the Nijhof Central Intelligence Library (Maritime) | NCIL(M) being developed by Nijhof Consulting & Solutions - MARITIME DEPLOYABLE AI SOLUTIONS FOR SEAFARERS. The concept is to bring fragmented maritime knowledge into a controlled environment where people can retrieve relevant information and trace that information back to its original source.
The important distinction is that this should not become just another repository. A centralised system is most useful when it helps the user see relationships between information. A person dealing with a machinery problem should not need to remember that a relevant limitation appears on page 347 of a manual, that a similar defect was reported eight months earlier, and that a related corrective action remains open. The system should help bring those pieces together.
The decision must still belong to the accountable human being. The value of the technology is that it gives that person a better information picture.
Sometimes the problem is not information. It is responsibility.
Not every failure is caused by missing information. Sometimes everyone knows about the issue, but responsibility is unclear.
The vessel believes shore management is dealing with it. Shore management believes the technical department owns it. The technical department believes the vessel is monitoring it. Someone is waiting for approval. Someone else is waiting for parts. The repair is planned but not scheduled. A corrective action exists but has not been followed through. From each individual position, nothing may look particularly unreasonable. Yet the issue remains unresolved.
This is where governance becomes just as important as information.
A useful governance framework should make several things clear:
Who owns the issue?
Who has authority to make the decision?
Who needs to be consulted?
Who needs to be informed?
When does the issue require escalation?
Who verifies that the action has been completed?
What evidence is required before the matter can genuinely be considered closed?
This is the thinking behind tools such as the NCS Octopus governance model and Collaboration Charter - MARITIME FRAMEWORKS | NIJHOF Consulting & Solutions
The purpose is not to create another layer of bureaucracy. It is to reduce ambiguity between people, functions and organisations that need to work together. Centralised information without clear responsibility can become a very sophisticated library. Governance without accessible information can become a very tidy organisational chart. The real value comes from connecting the two.
What you would want the record to show
If your decisions were being examined after a casualty, ideally the organisational record would allow somebody to understand the situation as you understood it at the time. Not a sanitised version. Not a perfect version. The real version.
The investigator should be able to follow the issue from the first indication through to the eventual decision and action. That means being able to see the condition that was identified, the information that was available, the procedures or technical guidance that applied, the people who were consulted, the risks that were considered, the decision that was made, the actions that followed and the basis on which the matter was eventually considered resolved.
If mistakes were made, the evidence should allow those mistakes to be understood properly. If the decision was reasonable, the evidence should allow that to be understood as well. This matters because maritime operations will never be perfect. People will continue to make difficult decisions using imperfect information. Equipment will fail. Plans will change. Procedures will encounter circumstances their authors did not anticipate. Commercial and operational pressures will continue to exist.
The objective should not be to create an environment where everyone operates defensively, worried that every judgement call may later be questioned.
The objective should be to create an environment where decisions are informed, accountable and reconstructable.
That is ultimately what a good evidence trail provides. It allows an investigator to understand what happened after something goes wrong, but more importantly, it allows the organisation itself to understand what is happening while there is still time to do something about it.
When the questions eventually come, the most useful thing an organisation can provide is not a perfect story.
It is an accurate one.
Comments