Every charter company thinks it has good organisation — until peak season arrives. That is when it shows whether the system is really in order or the entire season rests on one person holding everything together.
That person is almost always the base manager. The one who takes a call at midnight because a generator died, a fridge stopped cooling or a toilet is blocked; who calms a guest unhappy with the check-in; and who simultaneously has to tell management why cleaning is late and why certain boats have not yet been handed over. The base manager does not burn out because they don’t know how to do their job, but because they do their own job and the jobs of everyone who is missing or not doing theirs.
Why is the base manager always the first to break?
The base manager is the only link in the chain standing between two (sometimes three) sides with completely different expectations. Management wants the fleet to be functional, inspected, complaint-free and costs under control. The guest wants everything to be ready on time, without compromise, because he paid for a week’s holiday. Between those two sides there is no third person to absorb the pressure — only the base manager.
When you add that they have to coordinate skippers, technicians, cleaners and the booking team, you get a position that is operationally overloaded by design — not by accident. The problem is not the person. The problem is that the organisation is arranged so that everything passes through one point.
What happens when the team is not organised before the peak?
Most charter companies solve team organisation reactively — meaning when something jams, someone jumps in to help, someone works overtime, and the season somehow passes. That works in the pre-season. It does not work in peak season, because there is no reserve.
In the last few seasons this is compounded by a shortage of qualified skilled staff. The HGK Nautical Tourism Association has publicly confirmed that the lack of experienced personnel is still the main challenge of the charter season, even though the market is otherwise stable. Technicians, electricians and mechanics are positions that cannot be filled overnight, and they are precisely the people without whom a charter fleet physically cannot go to sea.
When that staff is missing, the work is not lost — it is transferred. Most often onto the base manager, because he is the one who will “somehow sort it out”. And while that can be done once or twice, over the whole peak season it becomes unsustainable.
How to schedule shifts so the team survives until the end of August?
It is easy to say “schedule shifts in advance”, and harder to apply it when there are not enough staff for the existing schedule as it is. That objection is fair and worth taking seriously.
Yet this is not a problem charter invented. Hospitals and emergency services have worked with the same constraint for decades — a shortage of specialised staff and work that must not stop. Their solution is not “hire more people” but a clear on-call system: in advance it is known who is “on call”, who is the backup and who may be completely unreachable that day or night. Transferred to a charter base, the same principle means that rotation of shifts, extra coverage on critical days (Saturday) and pre-assigned “on call” staff are not a luxury but the minimal protection against everything automatically landing on one person — in this case the base manager.
The second link often forgotten in this story is the reception. In practice reception is treated as the place for guest check-in, but in a well-organised base it filters what actually has to reach the base manager and what it can solve itself. Without that mandate, a question about cleaning, a question about check-in and a real malfunction on a boat all travel the same path — towards the same person.
When and whom to call in as reinforcement?
Here the same objection usually appears: an external technician does not know your boats, their faults, their “quirks”. And that is true! There are jobs in charter that simply cannot be done by someone who does not know the fleet.
The question worth considering is not “how to find more people from outside”, but which part of the work can actually be separated from knowing the specific boat. Preparation, transport of equipment, basic logistics do not require the same knowledge as diagnosing a fault or talking to an unhappy guest. If that boundary does not exist on paper either, even the best external collaborator does not know where their job begins and where someone from the established team must step in.
How exactly to draw that boundary, and how to organise the team so that bottlenecks do not always occur at the same place, is a topic worth looking at how industries with the same problem solve it — from healthcare to IT, where “knowledge locked in one head” has long been recognised as an organisational risk, not a personal flaw of the employee.
Who is responsible for the solution — the director or the base manager?
Here the most common misunderstanding happens, one that takes the whole story back to the beginning. Management knows the team is breaking, the base manager knows the team is breaking, but no one has formally decided whose job it is to fix it.
The base manager is, by the nature of the position, middle management: implements decisions on the ground, assigns people, puts out fires. What they most often lack is the authority to change the framework they work in: whether reinforcement will be hired, how much may be spent on an external technician, whether Saturdays will be staffed with more people even if that makes the shift more expensive. Those decisions are not operational but strategic, and their place is with the director or owner, before the season — never in the middle of it.
When that framework does not exist, the base manager finds themselves in an impossible position: responsible for the result, but without authority over the resources that make the result possible. The solution is not that the base manager must learn to “organise better”, but that management decides in advance what the base manager is authorised to solve alone and what they must escalate — and that for the latter there is a clear and fast channel, not waiting for the next meeting.
This applies equally to a company with seventy boats and one with five. The difference is not the size of the fleet, but whether that division exists at all — and in smaller teams, where the same person is often both owner and base manager, that division means something else: consciously separating the moments when you wear the “management” hat from those when you put out an operational fire, instead of doing both simultaneously, all the time, alone.
Instead of a conclusion
August will not become an easier month. But a team that enters it with a clear schedule, agreed reinforcement and a clear division of who decides what, exits it differently from a team that relies on someone “somehow holding on”.
If you recognise your own base in this description — especially the part where everything ends up back on one person — that question is worth considering before the next season, not in the middle of it.
Part of this load is also solved with tools; we wrote about that in the text on software for operations beyond the booking system. But software solves the organisation of tasks — who decides what is still a question of organisation and leadership, not tools.