MLC turns crew welfare into an enforceable standard, not a courtesy. The officer who plans work around rest, treats a complaint as information rather than a threat, and keeps discipline procedural is the one whose ship actually meets that standard — not just the one whose files say it does.
MLC 2006 is not a list of aspirations sitting alongside the safety conventions — it is enforceable in the same way SOLAS and MARPOL are, through the Maritime Labour Certificate and the Declaration of Maritime Labour Compliance that every ship over a certain size now carries, and through port state control officers who can detain a vessel over a breach as readily as over a fire door left open. Treat it with that level of seriousness, because inspectors do.
The Convention is organised into five Titles, and it helps to think of them as a life-cycle rather than a checklist: minimum requirements to work aboard (age, medical fitness, training, recruitment through a properly licensed agency), conditions of employment (the seafarer employment agreement, wages, hours, leave, repatriation), accommodation and recreational facilities, health protection and welfare, and finally compliance and enforcement — the certification and inspection machinery that makes the first four Titles mean something in practice.
MLC works because it is checked — by the flag state, by port state control, and by the crew themselves through the complaints procedure. As master, you are not the only line of compliance; you are one link in a chain designed to catch you if you drop it.
The rest-hour numbers are not arbitrary — they exist because fatigue accumulates faster than most people admit, and because one good night's sleep does not repay several short ones. The minimum is ten hours' rest in any twenty-four, and seventy-seven hours in any seven days, but the structure matters as much as the total: no more than two rest periods in the twenty-four hours, and one of them must be at least six hours long, because rest broken into short fragments does not produce the same recovery as one consolidated block.
A second, less quoted rule matters just as much in practice: the interval between consecutive rest periods should not exceed fourteen hours. It stops a watch pattern that is technically compliant on paper — enough total rest, correctly split into two periods — from still leaving someone awake and working an unreasonably long unbroken stretch in the middle.
The practical discipline this creates is that you plan the work around the rest, not the rest around the work. If a job genuinely cannot be done without breaching the minimum, the answer is to change the job — bring in extra hands, split it across more people, or delay it — not to adjust what gets written in the record afterwards. A rest-hour record that is compliant but does not reflect what actually happened is not a paperwork shortcut; it is a falsified safety record, and it is treated that way by inspectors.
Fatigue management is a planning problem, solved before the watch starts, not a records problem, solved after it finishes.
Every ship covered by MLC must have an on-board complaints procedure, and every seafarer must be given a copy of it, along with the contact details of the competent authority ashore. The procedure has to let a seafarer complain about anything covered by the Convention — pay, hours, accommodation, treatment by a superior — through a defined chain, normally starting with the seafarer's immediate superior or head of department and rising to the master, without having to go over anyone's head to be heard.
Two features do the real work. First, the seafarer has a right to complain without fear of victimisation — no reduction in duties, no unfavourable treatment, no quiet punishment for having raised something. Second, if the on-board route genuinely fails to resolve the matter, the seafarer can take it outside the ship entirely, to the flag state or to a port state control officer at the next port, and that right is not something the on-board procedure can quietly make conditional on trying everything else first.
Discipline is a process with a fixed order, and the order exists precisely because skipping steps under pressure is where most disciplinary decisions go wrong. Establish the facts before forming a view. Hear the person's own account, properly, even when the facts already look clear — an explanation can change what a proportionate response looks like, even if it rarely changes what happened. Decide a sanction that is proportionate to the conduct, not to how inconvenient the incident was for you. Record what was found, what was said, and what was decided. Then follow the company's own disciplinary procedure for anything beyond an informal word, because that procedure is itself part of what a flag state or a court will check afterwards.
Summary dismissal at sea should be treated as a last resort, not a first response, for reasons that go beyond fairness to the individual. A seafarer who is dismissed still generally retains a right to repatriation, so removing someone from duty does not remove the company's obligations to them. A dismissal made in anger, without a proper process, is also the kind most likely to be successfully challenged later — by the seafarer, by their union, or by a flag state investigating a complaint — which leaves the company worse off than if the master had taken a day to do it properly.
A disciplinary decision that could not survive being read back to an inspector six months later is not ready to be made yet.
The working language requirement is a SOLAS obligation, not a cultural nicety, and the reason is entirely operational: muster instructions, safety briefings and orders given in an emergency have to be understood by everyone who needs to act on them, immediately, without translation happening in someone's head first. A ship can run day-to-day with several languages spoken informally among the crew, but the working language — the one used for orders, briefings and anything safety-critical — has to be genuinely common ground, posted, and actually used, not just declared in the SMS.
Multicultural crews add a layer beyond language: differences in how comfortable people are challenging a superior, admitting a mistake, or raising a problem before it becomes serious. A junior officer from a background where hierarchy is rarely questioned will not necessarily speak up just because you have told them your door is open — that behaviour has to be actively built, through how you respond the first few times someone does bring you a problem, not assumed because you said the right thing once in a briefing.
Leadership aboard comes down to a short discipline: delegate, verify, record. Delegating a task to a competent person is correct practice, not an abdication — but responsibility for the outcome stays with the master regardless of who did the work, which is exactly why verification is not optional. Check that the delegated task was actually done, and to the standard required, and keep a record that shows you did. A master who delegates without verifying is not leading a team; they are hoping one exists.
A crew that will bring you bad news early, in a language you both understand, is the outcome that every requirement in this chapter is ultimately built to produce.
Both scenarios below are judgement calls, not calculations — work through the reasoning as you would talk it through in an oral exam, before stating the decision.
You are Chief Officer on a ro-ro alongside for a 24-hour cargo operation. The bosun submits tomorrow's watch plan for AB Rahman: rest 0000–0600, cargo watch 0600–1200, rest 1200–1400, cargo watch 1400–1800, rest 1800–2400. The bosun points out that total rest comes to 14 hours, well above the 10 hour minimum, and asks you to sign it off. Do you approve the plan as submitted?
Alongside for a 24-hour cargo operation Bosun's plan for AB Rahman: rest 0000–0600, cargo 0600–1200, rest 1200–1400, cargo 1400–1800, rest 1800–2400 Bosun's total rest as calculated: 14 h MLC/STCW minimum: 10 h rest in any 24 h; no more than two rest periods, one of at least 6 h Interval between consecutive rest periods should not exceed 14 h
Check the total rest against the daily minimum first.
Since that is the figure the bosun quoted.
Then count the rest periods.
Because MLC and STCW test structure as well as quantity.
The two tests are independent.
Meeting the 10-hour total does not cure a periods violation, so the plan cannot be approved as submitted.
Replan by consolidating the two cargo watches into one spell.
| Time | Activity |
|---|---|
| 0000–0600 | Rest — 6 h |
| 0600–1400 | Cargo watch — 8 h |
| 1400–2400 | Rest — 10 h |
| Rest periods | 2, one ≥ 6 h — 16 h total, compliant |
So rest falls into two blocks instead of three.
Check the gap between the two rest blocks against the interval rule before signing it off.
AnswerDo not sign off the original plan; require the bosun to resubmit with the two cargo watches consolidated into one 0600–1400 spell, giving two rest periods of 6 h and 10 h that satisfy both the daily total and the periods rule.
The trap: Treating the 10-hour daily total as the whole test — a plan can clear that figure comfortably and still breach the separate rule limiting rest to no more than two periods, one of which must be at least six hours.
During evening meal service the Chief Cook comes to your cabin, agitated, and reports that an Ordinary Seaman (OS) shouted at him in the galley, partly in a language other than the ship's declared working language, and refused to stop when told. The Chief Cook wants the OS logged for insubordination and removed from galley duties immediately. When you go down, you find the OS standing by the stove pointing at a steam pipe fitting that is hissing and weeping at a joint, still talking rapidly in his own language. No statements have been taken and no one else has been interviewed yet. The OS is four months into a nine-month SEA. How do you handle the next ten minutes, and what do you decide about the Chief Cook's request?
Ship's declared working language: English OS was shouting partly in his own language when the Chief Cook intervened A steam pipe fitting near the stove is visibly hissing and weeping at the joint No statements taken; no witnesses interviewed yet Chief Cook is requesting immediate removal of the OS from duty for insubordination OS is four months into a nine-month SEA
How do you handle the next ten minutes, and what do you decide about the Chief Cook's request?
Deal with the hazard first.
A hissing, weeping steam joint next to a galley is a live safety issue regardless of how it was reported.
Reconsider what actually happened: a shout in the wrong language.
Next to a genuine defect, is more consistent with a failed hazard report than with insubordination.
Apply the discipline process before any sanction is considered.
The sequence matters and none of it has happened yet.
Weigh the request for summary removal against that process.
No facts are established and the OS has not been heard, so removing him now would not be defensible.
Separately, treat the working-language failure as its own finding, not just background noise — the OS could not raise an emergency in a way the Chief Cook understood.
AnswerSecure and inspect the steam fitting immediately; take separate written statements from the Chief Cook and the OS, with an interpreter or a shared-language crewmate present for the OS; hear both before deciding anything; and record the incident as two findings — a hazard reported imperfectly, and a working-language gap to correct — not as insubordination. No dismissal or removal from duty on the Chief Cook's say-so alone.
The trap: Accepting the 'insubordination' framing at face value and pulling the OS off duty before any facts are established — that skips the discipline process, ignores the safety issue he was trying to raise, and risks the removal looking like victimisation for reporting a hazard.
Rest: 10 h in 24, 77 h in 7 daysMax two periods; one of at least 6 hoursInterval between rest periods ≤ 14 hSTCW and MLC minimum standardSEASeafarer employment agreement — signed, understood, aboardMLC titles 1–5Minimum requirements, employment, accommodation, health, complianceOn-board complaints procedureCopy given to every seafarer; no victimisationEscalationFlag state or port state control, if on-board route failsRepatriationEntitlement and maximum service period; survives dismissalWorking languageSOLAS requirement; posted and used for safety-critical ordersDiscipline sequenceFacts → hearing → proportionate decision → recordDelegate, verify, recordResponsibility for the outcome stays with the master