Log an event in the diary

If something during your shift needs to leave a trace — a fault, an HSE event, a material release, a process deviation — you log it under the Events element of the diary. A logged event is closed together with the diary, goes into the diary PDF, and can later be filtered and exported from the Events tab under Reports.

Before you start

Two conditions must hold, otherwise the add button will not even appear:

• Permission: the “Log event” right (event:create). By default this belongs to the Shift leader — if another role has it in your organisation, your admin configured it that way.
• An open diary: the diary must still be editable. A closed or archived diary can only be viewed; you can no longer add events to it.

The element name can differ per plant: your admin may rename it (for example to “Abnormal events”). If you cannot find the “Events” label, look for the name used in your own plant.

Steps

1. Open the diary the event belongs to and scroll to the Events element.
2. Click Add event. The logging form opens. (The same button closes it again — it then reads “Cancel”.)
3. Choose the Event type. There are seven: HSE · Technical fault · Quality deviation · Maintenance-requiring · Process · Material release · Other information.
4. If you chose HSE, the HSE severity field appears — it is required for an HSE event. Its values are: Near miss · Incident · Accident (or “— (non-safety)”). For any other type the field is not shown at all.
5. Give a Short title — this becomes the identifiable name of the event in lists and in the report. Be specific: “P-15-03 pump bearing failure”, not “fault”.
6. Write the Description: what happened, and what action was taken. This is the field a later investigation will actually read — you are writing it for your future self.
7. Fill in the Installation location if it applies (“reactor line 2, P-15-03”).
8. Enter the From and — if the event went on — the To time. The date comes from the diary, so here you only give hours and minutes, and only within the shift window. For a one-off event (flaring, for example) “To” can safely stay empty.
9. Tick Caused downtime and/or Caused production loss if true. These are filterable in the report — an unticked box means it did not.
10. Click Log event.

If it worked

You get the “Event logged.” confirmation, the form closes, and the event appears immediately in the Events list — with a “Logged by <your name> · <time>” line underneath. That signature is automatic and not editable: it is what makes the trail auditable.

Common problems

What you see	Why	What to do
“The time is outside the shift window.”	The hour and minute you gave do not fit the diary’s shift window.	Check the hint under the field — it prints the exact window. If the event really happened during another shift, it belongs in that shift’s diary.
“Select an event type.”	The type was left empty.	This is the one field you cannot save without — otherwise the event could not be classified in the report.
“Give the event a short title (min. 2 characters).”	Empty or one-character title.	Write a meaningful title — it is the only thing visible in the list.
“HSE severity is required for an EBK event.”	You chose the HSE type but left the severity empty.	Pick a severity. If the event is not actually safety-related, HSE is probably the wrong type. (The message says “EBK” — that is the Hungarian abbreviation for HSE; it refers to the same type.)
No “Add event” button	Either you do not have the event:create permission, or the diary is no longer editable (closed / archived / view-only).	If the diary is open, ask your admin for the permission; if it is closed, the event can no longer be added to it.

What happens to the event afterwards

• It goes into the diary PDF — into the “Events” block, if your report template includes it.
• It appears under Reports → Events, where all events of the site sit in one table that can be filtered, sorted and exported. Which site’s data you see is decided by your role’s site access.