MLC Work & Rest

What it is for

Reduce repetitive time-record administration and give officers a clearer picture of recorded hours, planned duties and possible rest shortfalls. Records support review and discussion; they do not replace fatigue management.

Main capabilities

A practical workflow

1. Check crew identity, onboard dates and the vessel’s applicable requirements.
2. Prepare working arrangements and record actual duties accurately.
3. Review warnings, rolling history and exceptions with the responsible officer.
4. Correct factual errors transparently and complete the required seafarer/officer confirmation process.

Standards and professional responsibility

The work/rest module supports review against MLC, 2006 Standard A2.3 and the STCW fitness-for-duty framework. Baseline minimum rest is 10 hours in any 24-hour period and 77 hours in any seven-day period; period splitting and other conditions also matter. Applicable flag-state law, collective agreements, permitted exceptions and the ship’s arrangements must be checked before use. Work-limit and rest-limit regimes must not be treated as interchangeable.

Regulatory changes and future amendments

The product is being developed with regulatory change in mind. New requirements are to be mapped to the affected workflows, checked against the applicable flag-state implementation and delivered through validated updates when required. Supported rule coverage, activation dates and any required configuration will be documented for each release.

Reference review: 2 November 2026. ILO lists the 2022 MLC amendments as in force from 23 December 2024 and the 2025 amendments as not yet in force, with expected entry into force on 23 December 2027. This status must be checked again for the relevant release and vessel.

Official references

• ILO — MLC text and amendments
• ILO — Standard A2.3
• IMO — STCW reference, A.1138(31)

References describe the regulatory framework; they are not endorsements or approvals of this software.

Data, access and confidentiality

The public browser demo uses temporary in-memory storage, not customer records or the working vessel database. It contains no Word documents or templates. Use fictional data only. Website access requests may still be recorded in hosting logs.

Autonomous editions work with locally selected storage. Server editions use the configured vessel database and access controls. These are separate deployment modes; data is not automatically transferred between them. Crew records are personal data: access, retention, lawful processing, backups and exports require customer-specific arrangements.

Keep a recoverable copy of important records. Restrict access to authorised personnel and review exported files before sharing. See the privacy notice and browser storage information for the website’s current draft disclosures.

Development, updates and validation

These products are under active development. Changes are reviewed and tested before release within the scenarios covered by the relevant checks. Calculation and document workflows require regression checks; release-specific validation must identify the tested scope and remaining limitations.

Testing reduces the risk of errors but does not establish that every vessel, cargo combination, rule exception or document is covered. No approval by a flag administration, classification society, IMO or ILO is claimed unless separately documented for a specific release. No guarantee of uninterrupted operation, error-free results or zero data loss is made; mandatory legal rights remain unaffected.

Maritime AI assistant

In development · Not included in the current public demo

A maritime-focused AI assistant is being developed for the product suite. It is intended to help users navigate the software, search a maintained maritime reference library, understand procedures and investigate operational questions.

Customer-controlled, local deployment

The planned architecture runs the AI model and its knowledge base on the customer’s equipment or within the customer’s approved server environment, without external AI services. Documents, drawings, diagrams, questions, prompts and conversations are intended to remain inside that environment rather than being sent to an outside model provider.

This is a development commitment, not a description of a released feature. Before delivery, deployment-specific network isolation, logs, backups, access controls and the offline update process must be verified. A model running on a customer server is local to that controlled environment; it is not necessarily running on the user’s individual computer.

The reference library and regulatory material are intended to be maintained through reviewed updates. AI answers must be checked against current authoritative sources and vessel procedures; they do not constitute operational approval or legal advice.

Try it or discuss a deployment

Open the public demo with its fictional vessel and crew. Changes remain in this tab and reset when the page reloads; there is no shared vessel database. Contact us to discuss a working deployment.

Please do not send crew records, private drawings or sensitive cargo files with an initial request.

Software licence terms remain in draft. Licence options · Full safety notice