Crew Management and MLC 2006 Compliance: Automating the Hardest Audit

Ask any technical superintendent which compliance regime consumes the most senior crew time, and the answer is almost always the same: the Maritime Labour Convention. MLC 2006 compliance is a continuous obligation that touches every seafarer on every ship every day. The records pile up. The records are inspected. And, increasingly, the records are the difference between a routine port state control visit and a public-record detention.

This article is for HR managers, crew managers, technical superintendents and masters who already know the convention exists and now have to live with it. We will look at what MLC 2006 actually requires, how the 2014, 2016, 2018 and 2022 amendments have widened its scope, why rest hour records are the most fragile part of the regime, where STCW 2010 hours of rest overlap and conflict with MLC, what PSC regimes focus on, and what disciplined crew management software does and does not do.

What MLC 2006 actually requires

The ILO Maritime Labour Convention, 2006, sometimes called the seafarers' bill of rights, consolidates more than sixty earlier ILO instruments into a single framework. It applies to almost every commercially operated ship of 500 GT or more on international voyages, and many flag states extend it further. For an operator, the convention is structured around five Titles; operational obligations cluster around a few practical pillars.

• Seafarers' employment agreement (SEA). Every seafarer must have a written, signed agreement that they have had time to review. Wages, leave, repatriation entitlements and termination conditions must be transparent. Verbal arrangements and ad-hoc addenda are non-compliant.
• Hours of work and hours of rest. Either a maximum work hour regime or, more commonly, a minimum rest hour regime applies. Minimum ten hours of rest in any 24 hour period, and 77 hours in any seven-day period, divisible into no more than two periods, with one period of at least six consecutive hours.
• Wages. Paid in full, on time, and at intervals no longer than monthly. Allotments to family members must be honoured. Account statements must be itemised and provided to the seafarer.
• Repatriation. The right to be repatriated at no cost, with maximum service periods (commonly twelve months) before mandatory repatriation. Financial security to cover abandonment and unpaid wages was added by the 2014 amendments.
• Accommodation, food and catering. Specific minimum standards for cabins, sanitation, recreational facilities, and the quantity and quality of provisions. The cook must hold a certificate of competency.
• Health protection, medical care, welfare and social security. Onboard medical care, access to shore-based medical facilities, and protection from harassment and bullying, formally added by the 2018 amendments.
• Onboard complaint procedures. A documented procedure that allows a seafarer to raise a grievance without fear of retaliation, with escalation paths to flag and port states.

Each pillar is documented through the Declaration of Maritime Labour Compliance (DMLC) Parts I and II, the Maritime Labour Certificate, and the records an inspector will ask to see.

The amendments: a moving target

MLC 2006 is not a static document. Four substantive amendment cycles have widened operator obligations.

• 2014 amendments (in force 2017). Mandatory financial security for abandonment and for liability arising from death or long-term disability. Operators must carry certificates of insurance, post a copy in a conspicuous place onboard, and ensure the seafarer can call on the insurer directly.
• 2016 amendments (in force 2019). Extension of the validity of medical certificates and seafarers' employment agreements during voyages where renewal is impractical, plus protection against shipowner liability where harassment or bullying causes harm.
• 2018 amendments (in force 2020). Continuity of the seafarers' employment agreement during captivity from piracy or armed robbery, including continued payment of wages.
• 2022 amendments (in force 2024). A package addressing recruitment and placement transparency, internet access at sea (where reasonably practicable and at reasonable cost), personal protective equipment fitted for all seafarers including women, and reinforced provisions on harassment, bullying and the right to shore leave.

Each new cycle adds records, postings and procedural touchpoints. None is technically difficult. All compound the administrative load.

Why rest hours go wrong

Rest hour records are the single most-cited MLC deficiency in PSC statistics, and not because masters are dishonest. The operating reality of a port call frequently makes the convention's letter very hard to keep.

The classic failure modes:

• Ad-hoc paper logs filled in days later. The deck and engine officers complete their hours of rest sheets at the end of the week, from memory, often during a quiet moment that itself reduces their actual rest. Memory smooths the record; small breaches disappear.
• Retroactive backfilling under pressure. A short-handed port call produces real breaches. The pressure to record compliant hours is implicit. When a system makes it easier to enter retrospective hours than to record an actual breach with cause, the records drift away from reality.
• Cumulative port-induced fatigue. A vessel on short hops does not breach the daily ten hour rule on any single day, but accumulates fatigue across a week of port calls, bunkering, surveys, and short sea passages. The 77 hour rule exists precisely to catch this, and it is the most-violated rule in practice.
• Master-versus-charterer pressure. The master is responsible for the records. The charterer is responsible for the schedule. When the schedule is incompatible with rest hour compliance, the records often flex to make the schedule possible.
• Drill, watchkeeping and call-out blurring. A safety drill at 0930 is work. A call-out at 0240 to handle a moor is work. A standby watch where the seafarer is not actively working but cannot leave the engine room is, under MLC, not rest. The boundary lines are routinely crossed by accident.

None of these failure modes are solved by software alone. But the right software prevents them from being invisible.

STCW 2010 hours of rest: the overlap and the conflict zone

The STCW Convention as amended in Manila 2010 sets its own minimum hours of rest for watchkeepers: ten hours in any 24-hour period and 77 hours in any seven-day period, divisible into no more than two periods, with one of at least six consecutive hours. Read narrowly, the regimes look identical. They are not.

STCW allows for limited exceptions for emergency drills and operational requirements, with conditions on compensatory rest. MLC's 77-hour rule applies to all seafarers, not just watchkeepers. STCW exceptions cannot be used to backfill MLC breaches. A common error is to log a port call as a permitted STCW exception when the actual conditions do not meet the exception's threshold, then carry that logic into the MLC return.

The practical consequence: any rest hour system worth using must record both regimes simultaneously, flag the points at which they diverge, and force the operator to face a real breach rather than choose the more flattering classification.

Port state control: where attention is concentrated

The big regional MoUs publish their inspection priorities and detention statistics, and crew issues feature heavily in all of them.

• Paris MoU. Concentrated Inspection Campaigns (CICs) on rest hours have run repeatedly. Detentions citing crew-related deficiencies, including missing or falsified rest hour records, are a recurring presence in the annual report.
• Tokyo MoU. Similar pattern, with the 2024 CIC on crew familiarisation and STCW certification a noteworthy recent example. Asia-Pacific inspectors have become methodical at sampling rest hour records against port stay logs and bunker delivery notes.
• USCG. While the United States has not ratified MLC 2006, the Coast Guard inspects to STCW and to its own crew endurance management framework, and it has memoranda of understanding with flag states that effectively reach MLC compliance through the back door.
• FONASBA and shipping agents. Ship agents increasingly receive flagging from PSC inspectors when a vessel's documentation arrives late or in poor order. The reputational hit lands on the operator, not just the master.

Detentions are public. Equasis, the Paris MoU public list and the Tokyo MoU detention list are read by charterers, P&I clubs and major shippers. A crew-related detention is expensive long after the vessel has sailed.

What good crew management software actually does

A serious crew management system is not a glorified Excel sheet. It is the operational backbone for a regime that touches every seafarer every day. The features that matter, in order of compliance impact:

• Rest hour automation with real-time entry. Hours are recorded as close to the event as practicable, ideally on a tablet at the watch handover. The system computes both MLC and STCW compliance against the entries, flags breaches as they occur, and forces a breach to be recorded as a breach with operational cause, not silently corrected.
• Certificate of competency tracking. STCW certificates, medical certificates, flag state endorsements, GMDSS, tankerman, firefighting, advanced training. The system tracks expiry, plans renewal windows around rotation cycles, and alerts the manning office before a seafarer arrives onboard with a soon-to-expire document.
• Repatriation management. Service period counters per seafarer per ship per contract, with automatic alerts before the twelve-month MLC ceiling, integration with travel booking, and a clear record that repatriation was offered and exercised in line with the SEA.
• Payroll-to-record reconciliation. Hours worked, allotments paid, deductions taken, leave accrued, all reconciled against the SEA. Pay slips itemised. Allotments routed and confirmed. A complete record that wages were paid in full and on time.
• Complaint workflow with audit trail. The onboard complaint procedure as a documented system rather than a paper form. Submission, acknowledgement, investigation, resolution, escalation, all timestamped, all visible to the seafarer who raised the complaint.
• PSC-ready export. When the inspector boards, the master should be able to print or hand over a clean, complete record set in minutes. Rest hour summaries, certificates, SEAs, complaint logs, financial security certificates, all up to date and consistent across copies.
• Integration with ISM and the safety management system. Crew issues feed into the ISM Code's continuous improvement loop. Near-miss reports about fatigue, complaint outcomes that reveal training gaps, and audit non-conformities should appear in the same management review as the rest of the SMS.

The human factor: software is not a substitute for welfare

This section matters more than the rest of the article. A crew management system can make compliance visible, repeatable and auditable. It cannot make a fleet a good employer. Tools that simply make falsification easier, by letting an office user retroactively edit hours without an audit trail, by hiding breaches in summary reports, or by allowing the master to be the sole gatekeeper of the record, do not solve the MLC problem. They worsen it, because they give a paper veneer to a real welfare failure.

The serious operators we work with start from the opposite premise. The records exist to make breaches visible, so that the operator can act on the cause. A short-handed port call that produced a real breach should produce a real conversation about manning, not a flatter version of the timesheet. A complaint that exposes a junior officer to bullying should produce a real investigation, not a closed ticket. Software supports that culture; it does not create it.

A practical compliance posture for a fleet operator preparing for audit

For a superintendent preparing for the next MLC audit, or for a crew manager writing the next manning office quarterly, a small number of disciplines repay the time spent.

• Reconcile the SEA, the payroll and the rest hour record for a sample of seafarers each month. The auditor will. If the three documents do not tell a coherent story, the issue is found internally first.
• Treat the 77-hour weekly rule as the binding one. Daily breaches are rare. Weekly breaches are common and structural. A schedule that produces weekly breaches needs a manning conversation, not a record-keeping fix.
• Audit the financial security postings on every vessel each quarter. The 2014 amendments require a conspicuous posting of the abandonment and shipowner liability certificates. Auditors check. Crews change. Postings disappear.
• Run a complaint procedure drill annually, the way you run a fire drill. A complaint procedure that has never been used is a procedure no one believes in.
• Brief the master before every PSC zone change. A master joining a vessel that will trade Paris MoU and Tokyo MoU waters in the same rotation should know the current CIC priorities for both. Five minutes of briefing prevents an avoidable detention.
• Keep the DMLC Part II living. The DMLC Part II is the operator's own statement of how it meets MLC requirements. It should be updated when manning practices change, when amendments come into force, and when audit findings reveal gaps. A DMLC Part II that has not been touched in three years is itself a finding.

Where SupaMaritime fits

SupaMaritime builds operational software for commercial maritime: ferry operators, merchant fleets, port and ship agents. Crew management, rest hour discipline, certificate tracking and PSC readiness sit alongside the rest of our commercial stack. Explore the merchant and ferry modules at /merchant and /ferry, the full set at /modules, and our platform audit posture at /security.