The rest rules come with a paperwork rule attached: the hours have to be recorded, in a form an inspector can read, signed by both sides. In practice the record is where compliance is won or lost, because the inspector was not aboard for the month; the record is the month, as far as the inspection is concerned. Your flag's notices govern the exact format for your vessel; this is what the regime asks for and how the questions usually run.
What the record must be
- A record of each seafarer's daily hours of rest, kept in a standardised format based on the IMO/ILO guidelines, in the working language of the ship and in English
- Signed twice: by the master or a person authorised by the master, and by the seafarer themselves
- Copied to the seafarer, so the crew member holds their own record
- Kept so that the monthly totals and each day's periods can be examined against the limits
The questions an inspector asks of it
- Do the recorded days actually comply, tested over rolling windows rather than the calendar days a form makes easy?
- Where a day did not comply, was it noticed at the time, or is the inspector the first person to spot it?
- What happened next: is there a documented reason, a review by someone senior, and evidence the pattern was addressed?
- Do the signatures exist, and do the crew's copies match the vessel's?
The second and third questions are the ones that separate vessels. A record with an unexplained breach a month old says nobody is reading the record. The same breach with a same-day comment from the crew member, a note from their head of department and a captain's acknowledgement says the system works, which is what the ISM Code is actually asking to see.
Non-conformities are records too
A non-conformity is not a failure of the record; hiding one is. The record's job is to show the breach, the reason, and the response. That means the comment trail matters as much as the numbers: who explained the day, who reviewed it, and when. On paper forms this history lives in margins and memory. Whatever system you use, the standard to hold it to is that the full story of a flagged day can be produced at the gangway, not reconstructed after the inspector leaves.
How The Muster App keeps this record: crew log their days on their own phones, and a day that crosses a limit cannot be saved until a comment explains it, so the explanation is captured on the day, not invented at month-end. The crew member's head of department is notified on their phone when a non-conformity lands, admins by email, and the day carries its thread: the crew comment, the HoD's note, the acknowledgement. The monthly record then prints in the standardised format with both signatures, and where a day carries comments the export includes an appendix sheet with each full comment, so the inspector reads the story exactly as it was written at the time. Once reviewed and signed, the month locks. The result is that the four questions above answer themselves in the order they are asked.
For the rules the record evidences, start with MLC hours of rest explained.