Movements

Running the day: starting moves, finishing them, and what blocks each one.

The movements board is the working screen for a duty officer. It lists every move across every open call, ordered the way a shift actually cares about them: what is happening now, then what is late, then what is planned.

Starting a move

A move can be started when all of these hold:

  • the call is approved
  • the previous move on that call has finished
  • the move has an estimated time
  • every check is ticked
  • every requirement is satisfied

If any is outstanding, the start control is disabled and says which one — by name, not as a generic refusal. "Cannot start: Draft verified" tells you what to go and do.

Starting a move records its actual time of move. Censerva also closes off the vessel's previous stay at that moment, because a vessel that has begun moving is no longer alongside.

Finishing a move

Finishing records the actual time of finish and opens the stay that follows. A move cannot be finished before it has started, and the times cannot be recorded out of order.

Ticking checks and requirements

Checks and requirements are ticked directly on the board, without opening the call. They can only be ticked once the call is approved.

Each tick shows its own state. A tick that has reached the server is quiet; one still held on the device is marked, and says so. That distinction is deliberate and appears everywhere an operational record does — a change that has not been confirmed is never shown as though it had been.

Delays

A move that has passed its estimated time without starting is shown as delayed, and a reason can be recorded against it. Those reasons feed the delay analysis report, so a pattern — one berth, one tide window, one tug operator — becomes visible rather than anecdotal.