What a Ship Management Company Loses When an Experienced Superintendent Leaves

When a technical superintendent hands in their notice, the handover meeting covers the vessels, the open dockings, the class surveys falling due, and the two or three problem ships that always need watching. It runs a couple of hours, maybe a day if the person is conscientious. Everyone shakes hands. On paper, the fleet has been handed over.

What has actually been handed over is a list. What leaves with the person is everything that made the list mean something.

The knowledge that never made it into a system

A superintendent who has run the same six vessels for eight years knows things that are nowhere in the PMS, the class records, or the shared drive. They know which chief engineer flags a problem early and which one waits until it is expensive. They know that the port-side generator on one ship has been temperamental since a repair in 2021 that was signed off but never quite right. They know which yard did good work last time and which one to keep off the tender list regardless of price. They know why a particular deferral was agreed with class two years ago, and what the understanding was about putting it right.

None of that is written down anywhere, because none of it is the kind of thing anyone writes down. It lives in the person. It is the difference between managing a vessel and knowing a vessel.

When they leave, the replacement inherits the records but not the reasons. They inherit a defect list without the history of what has already been tried. They inherit a maintenance plan without knowing which jobs are done properly and which are done to close the work order. They start, in effect, from the position of someone who has never met these ships - because as far as the recorded information is concerned, they haven't.

The cost is paid slowly, and out of sight

The loss rarely shows up as a single event. It shows up as a series of small, avoidable ones over the following year.

A problem that the previous superintendent would have recognised in a sentence takes the new one three weeks and a superintendent visit to diagnose, because the earlier occurrence was never connected to the equipment. A supplier who underperformed last time is used again, because the reason they were dropped left with the person who dropped them. A decision that was settled two years ago is reopened and re-argued, because nobody can find the record of why it was decided the first time. A recurring defect is treated as new each time it appears, because each occurrence was closed as an isolated job.

Individually, each of these looks like ordinary operational friction. Collectively, they are the sound of an organisation paying, again, for knowledge it already had.

Why handovers cannot fix this on their own

The standard answer to this problem is a better handover - a longer overlap, a more detailed handover note, a checklist. These help, but they cannot solve it, for a simple reason: the person leaving does not know what they know. Most operational knowledge is invisible to the person who holds it. It surfaces only when a situation calls for it. Ask a superintendent to write down everything important about their fleet and they will produce the list - the vessels, the surveys, the known problems. The deeper knowledge does not come out on demand, because it is not stored as a list. It is stored as the ability to recognise a situation and know what it means.

You cannot hand over recognition in a meeting. It has to be built into the record while the work is being done - not summarised at the end, but captured as it happens, connected to the vessel, the equipment, the decision and the outcome.

What it means to keep the knowledge in the organisation

The alternative is not more documentation for its own sake. It is making sure that the context around operational work stays attached to the work, so that it remains available when the person who created it has gone.

In practice that means an organisation should be able to look at a vessel and see not only the current defect list, but the history behind each item - what was tried, what worked, what did not, and why. It should be able to see not only that a decision was made, but the reasoning, the information it rested on, and who was involved. It should be able to see that a supplier was used before, how they performed, and whether they should be used again. It should be able to see that this fault has appeared three times in two years, not treat it as new on the fourth.

When that context is held by the organisation rather than the individual, the departure of a superintendent becomes a change of personnel rather than a loss of capability. The new person inherits not just the list, but the understanding behind it. They start where their predecessor left off, not where the records happen to begin.

The question worth asking before it happens

Most companies discover how much they depended on a person only after that person has gone, when the gaps start to show and there is no longer anyone to ask. The more useful time to ask the question is before: if this superintendent left next month, what would leave with them - and how much of it would the organisation have to learn again, at its own cost?

The honest answer, for most organisations, is: more than they would like, and more than they can see. The purpose of keeping operational knowledge within the organisation is to make that answer smaller.