Most offshore companies have grown to where they are today by building processes around the people they had. Somewhere along the way, one person became the real owner of the rotation plan — the one who knows every vessel, every rotation cycle, every exception, and every quiet arrangement that was never written down anywhere. Maybe it’s an Excel file on a shared network drive. Maybe it’s a combination of spreadsheets, inboxes, and experience. It works. The coordinator is good at their job and operations run smoothly. Then one Monday morning, that person doesn’t show up.
Situation 1: The coordinator is sick — and the vessel departs in two days
Ben is the crew coordinator at a subsea company with six vessels. On a Tuesday evening, two days before a scheduled vessel changeover, he calls in sick. His planning file is on the shared network drive, but it only contains the numbers — not the mind that knows how to read them. Who has which certifications? Who is already offshore and when are they due back? Who had actually confirmed this changeover, and who was only on the tentative list?
Management starts calling around. Emails go out. Half the night is spent assembling a plan nobody is entirely confident is correct. The vessel departs — but it was luck that things went smoothly.
Situation 2: The coordinator leaves — and takes their knowledge with them
Karen has been coordinator for eight years. She knows every employee by name, knows who doesn’t work well together on board, and remembers that one of the regular rotators always needs extra time to renew their medical. When she resigns to join another company, there are three weeks’ notice.
Her replacement is capable and motivated. But he inherits a set of Excel files, a few weeks of handover, and a flood of verbal explanations that are impossible to fully reconstruct. It takes months to rebuild the quiet institutional knowledge that walked out the door with Karen — and in the meantime, mistakes happen that wouldn’t have happened while she was still there.
Situation 3: The coordinator is on holiday — and someone needs a last-minute replacement
A Saturday afternoon. One of the people scheduled to go offshore on Monday has suddenly fallen ill and can’t travel. The coordinator is on holiday in Portugal and isn’t answering their phone — it’s the weekend, and that’s fair enough.
Who can substitute? Who has the right certifications? Who hasn’t just come back from a long rotation and therefore needs rest time? Without a system that answers these questions, you end up calling through a half-outdated list and hoping someone picks up. Sometimes you find someone. Sometimes it’s too late.
The real problem
These three situations are symptoms of the same structural issue — the rotation plan lives in one person’s head and one person’s files. The coordinator isn’t doing anything wrong; the system is built around a single point of failure. Companies rarely notice this until the failure actually happens.
And by then, there’s usually nothing to do but manage the fallout.
What does it look like differently?
When the plan lives in a shared system — where all personnel data, certifications, and assignments are visible to anyone with access — the operation is no longer dependent on one specific person being available.
If Ben is sick, a colleague opens the same overview and picks up where he left off. If Karen leaves, her replacement sees everything from day one — not just the numbers, but the whole picture. And if it’s Saturday and someone needs a last-minute replacement, the system shows who is available and qualified within seconds.
That’s what Markular is built for. Not to replace the coordinator, but to make sure the knowledge and overview don’t disappear when she does.