Skip to content

A round in the shift log and the closing setting

If a round is due in the shift, the shift log shows an Operator rounds element: the round’s name, status (Due, In progress, Done, Missed, possibly Overdue) and due window. It is not a pop-up: it does not interrupt your work, but the shift cannot be closed unnoticed without it.

  • Right: to manage a round, “Operator rounds: record” — opround:record; to change the closing mode, “Operator rounds: settings” — opround:configure.
  1. Start / Continue. The element’s main button is Start (new round) or Continue (open round); without the record right, View. It takes you to the walk-through screen.
  2. Close as missed. If the round cannot be walked: Close as missed; a reason can be given (optional). The round does not roll over; the metric counts missed rounds separately.
  3. Override close with a reason. In blocking mode an open round blocks closing the log. If you must close anyway: Override close with a reason (the reason is required). The round stays open but the log can be closed; on closing the round is closed as missed and this reason becomes the reason it was missed. The override is audited.

The log’s close form does not change; you give the override on the round’s own element, before closing.

On the Settings tab of the Operator rounds page, the Closing mode decides what happens if a due round is still open when the log is closed by hand:

Mode Behaviour
Warn The log closes; the open round is closed as missed. Before that the log says “N round(s) open. When the log is closed they are closed as missed.”
Block Closing does not go through until the open round is closed (as missed, with a reason) or the close is overridden with a reason. Message: “The log cannot be closed: N round(s) still open (…).”

The setting applies to closing the log by hand.

The nightly (automatic) log close is not blocked by the Block mode, otherwise the log would never close. Open rounds are then closed as missed, with a system marker (“Missed — closed by the system (automatic close or expiry).”), and the audit records the reason and that the block was passed. A round that expired and stayed open is likewise missed by the system at the next log opening, but only if its log is no longer a draft.

The start-of-round plant-status question (see the phone article) blocks only closing that round by hand, not closing the log or the automatic close.

“Round closed as missed.” or “Override reason saved; the log can be closed.” The reason shows in the log and on the Rounds tab; in the closed log’s shift PDF the round is one summary line.

What you see Why What to do
“The log cannot be closed: N round(s) still open (…)” Block mode, open round. Close it as missed, or give an override reason.
“This needs the “Operator rounds: record” right.” The right is missing. Ask your administrator.

Last updated: