Crew and welfare · Module 16
Messaging on board and notices from the office
Person to person, office to fleet, and a notice whose acknowledgements are counted per version in force.
Arbeidsmiljøloven § 9-5
What it is for
The requirement, and the problem
Crews already have messaging, and it is WhatsApp. Replacing it is not the goal and would not work. What this module is for is the class of message that has to be on the record: a bridge order, a notice from the office that people are required to have read, a message to a position rather than to a person.
And it is for the two things a consumer messenger cannot do: reach exactly the people who are currently embarked, and count acknowledgements against the version of a notice that was in force when each person read it.
How it works
Three steps, on board and ashore
- 1
Person to person
Messages between people on board and ashore, found by name, rank or department — and read by nobody else, including us.
- 2
Notices to an audience
The office sends a notice to a department, a shift, a vessel or the fleet, and a broadcast reaches the crew actually embarked.
- 3
Read and understood
Acknowledgement is tracked per version in force, so a revised standing order is acknowledged again.
Example with demo data
What it looks like
A working picture of the module with demo data from the Ocean Pioneer — the same ship you find in the demo.
Try the demo — no account, in your browser, with the PIN 1234.
- Messages — the inbox and the directory
- Notices — what the office has published and who has acknowledged it
In detail
What the module does
No permission reads another person’s conversation
There is no administrative override, no support view and no export that includes it.
A directory that knows the ship
Search by name, by rank or by department, and the result is the people on this vessel now — not a company phone book of eight hundred names.
One conversation per pair
Two people have one thread, ever. There is no way to start a second one that splits the history in half.
Audiences that mean something
A message can be addressed to a department, a shift, a set of positions, a vessel, a fleet or the company — and a broadcast to the vessel reaches the embarked crew, not everybody who has ever sailed on her.
Notices as living documents
A notice has a version chain. When it is amended, the acknowledgement count resets for the people the change affects and the previous version stays readable.
Bridge orders, signed
Standing orders and night orders are written, signed with a drawn or PIN signature, and read by the watch with the reading recorded.
In the app
On the bridge, on deck and in the office
The same records on a phone in a machinery space and on a screen in the office — with no signal, and synchronised when the link returns.
- Bridge orders — standing and night orders, signed and read
The decision
A refusal we will not sell our way out of
Being asked for an administrator who can read the crew’s messages is a matter of when, not whether. The answer is no, and it will stay no: a messenger the crew believes is being read is a messenger the crew does not use, and then the bridge orders go unread too because nobody opens the app.
If a company genuinely needs lawful access to an employee’s communication, Norwegian law sets out how — and it does not run through a vendor’s admin panel.
Works with
One product, not nineteen
Crew and certificates
Who is on board, what each position must hold, and which certificate expires before the crew change.
FOR-2011-12-22-1523The fleet office
Every vessel on one screen, the certificate matrix across the fleet, the rotation planner and the relief pool.
ISM Code, clause 12Handovers and forms
One form engine behind every signed piece of paper on board, with the wording frozen at the moment of signature.
ISM Code, clause 11
Put one vessel on it for two months
No card and no implementation project. A company adds its own vessel and its own people on its own afternoon — and if it is not for you, you stop, with your data exported first.