How the shift diary works

The shift diary is a structured, signed record of a shift: what happened, who was present, which orders were in force, what became of the tasks, and what events occurred. It is not free text in a box — it is made of well-separated elements, each leaving its own auditable trace. The diary closes at the end of the shift, and the closed content becomes the PDF and the report.

If you have never used it, this page orients you: what the elements are, what the daily flow is, and where to go next.

What the diary is made of

Orders

Standing instructions you acknowledge (your signature that you are aware of them). They live until revoked or until a deadline.

Tasks

What has to be done in the shift. Your job is not to finish everything but to report honestly where it stands. An unfinished task carries over to the next shift.

Events

Whatever needs to leave a trace: a fault, an HSE event, a material release, a process deviation. With a type and a severity, so the report can filter later.

Roster and attendance

Who was on the shift. Recorded in the diary header; it goes into the PDF and the report too.

Diary elements (data points)

Your plant’s own fields — readings, flags, notes — set up by your admin. They can differ per plant.

The daily flow

A shift always runs the same chain:

Start the shift → fill in the diary elements → acknowledge orders · report tasks · log events → close the shift → PDF + report.

Every step leaves a signed trace (who, when) that cannot be edited afterwards — and that is exactly what makes the diary auditable. A closed diary is view-only; the data inside it also appears, aggregated per site, on the Reports tabs.

Why it works this way — the background

The shift diary is not an end in itself: it is the daily record of the operating rhythm and the MOS (Management Operating System). For what that means and why it matters, see the Knowledge base: the operating rhythm · MOS. Help is the HOW, the Knowledge base is the WHY.

Who does what

The diary elements are tied to permissions — who can do what is set by your admin on the roles. A shift leader typically logs events, reports tasks and acknowledges orders; an administrator additionally issues orders/tasks and builds the report. If you cannot see a button, it is usually either the permission or the diary’s state (open/closed).

Start here

Log an event in the diaryA fault, an HSE event, a material release — this is how you leave a trace.

Report a task's statusFour statuses, and why a reason beats an empty task.

Acknowledge a management orderYour signature on a standing instruction — the trace an audit looks for.