Skip to content
English
  • There are no suggestions because the search field is empty.

Logbook Entries

 What is a Logbook Entry?

A logbook entry records an event, handoff note, or operational update so the right people see it and confirm they have read it. Entries live on the Operator Dashboard (across your sites) and on each Location page (one site).

Key point: Most entries need acknowledgement. Log Book Supervisors for a location are required by default. Safety notices and organization-wide announcements can require acknowledgement from a much wider set of users.

How to open Logbook
Surface What you see
Operator Dashboard Sticky nav Logbook (unacknowledged count badge). Panel title: Logbooks.
Location page Panel title: Logbook.
Equipment {Equipment name} Logbook Entries on the equipment widget when applicable.

Visibility needs the Logbooks org module and a role with Logbooks permission. After sync, empty lists usually mean no entries for your filters — not a missing module.

How to create an entry
  1. On the Operator Dashboard or a Location page, click New Log (equipment widget uses New Logbook Entry).
  2. Fill the form (modal title: New Logbook Entry).
  3. Click Create Logbook Entry.

Fields operators use most

Field Notes
Location Required for location-specific entries.
Logbook Category Required. Categories come from org dropdown lists.
Description Required.
Equipment / Sub Equipment Optional when the location has equipment.
Attach Files/Take Picture Optional — max 20 files, 20 MB each.
Notify and require acknowledgement Optional extra users (hidden for safety / org-wide flows).

Safety concerns

Shown when your org has Allow Safety Log Entries enabled.

  1. Check This affects the safety of myself and others (helper text: safety concerns notify related users).
  2. Confirm the I Understand / Cancel safety notice modal if prompted.
  3. Related users for that location are required to acknowledge; a list warning can show There are outstanding active safety concerns.

On an open safety entry you may see This is an active safety concern. Creators, Admins, and Programmers can click Rectify Safety Notice when the hazard is resolved (confirm dialog explains that the entry stays in the logbook but is no longer an active concern).

Organization-wide announcements

Shown when Allow Org wide notifications is enabled.

  1. Switch from Specific Location Logbook to Organization-wide Announcement.
  2. Confirm I understand that this will notify all users in my organization. with I Understand.
  3. Org-wide entries require acknowledgement from users across the organization (users opted out of mass acknowledgements are skipped).

Who must acknowledge by default

  • Location entries: selected notify users plus Log Book Supervisors on that location (plant user column / setting).
  • Safety entries: users connected to the site (respecting mass-acknowledgement opt-out).
  • Org-wide announcements: org users (with the same opt-out rules).

Log Book Supervisors are configured on plant user assignment (and org-wide supervisor can be set on the user profile). They appear with a star in acknowledgement lists.

How to acknowledge
  1. Open Logbook / Logbooks — nav badge shows how many need your acknowledgement.
  2. Optionally filter to Unacknowledged or Active Safety Concerns.
  3. Open the entry (Logbook Details).
  4. Click Acknowledge Logbook.

An entry stays “unacknowledged for you” until you have acknowledged the entry and any EZ Messages on it that still require your acknowledgement.

Filters, columns, and styling

Filter (multi-select) includes:

  • Active Safety Concerns (with count)
  • Unacknowledged (with count)
  • Category
  • Equipment (when entries have equipment names)

Also: Search. On the dashboard, Filter Field still limits which sites appear. Pad wells can use Filter by Location on Pad.

Column When it appears
Location, Description Always
Date When not on the safety filter
Days Active When filtering Active Safety Concerns
Files Wider screens
Equipment Name When org setting Equipment Name in Table is on

Unacknowledged rows:

  • Org setting Unacknowledgment display pink on → full pink row
  • Setting off → bell icon beside the description

Empty list: There are no logbooks to display.

EZ Messages (comments)

On a synced entry:

  1. Click Add EZ Message.
  2. Enter Your Message.
  3. Optionally choose Who should acknowledge this message? and attachments.
  4. Click Create Message.

Acknowledge a pending message with Acknowledge Comment. Unsynced local entries (method still new) cannot add EZ Messages yet — sync first.

Editing and deleting
Situation What you can do
Entry created offline and not yet synced Edit (pencil) and delete (trash) in Logbook Details
Entry already synced (operator app) No edit/delete controls for logs
Category marked legal logbook (e.g. ABSA-style) Treated as non-editable (noEdit) — double-check before save/sync

Do not assume “all logbooks are locked forever.” Only legal categories and synced operator views enforce the hard lock; unsynced drafts remain editable until sync.

Email notifications
  • Immediate Acknowledgement Emails in your user profile — email when something needs your acknowledgement.
  • Scheduled acknowledgement emails — configured in your email schedule settings.
Online report

With permission, Reports → Logbook Report shows online logbook history (separate from the offline lists).

Tips & recommendations
  • Create entries when the event happens, then sync so acknowledgers see them.
  • Use the right Logbook Category — it drives filters and legal/non-editable behavior.
  • Prefer Acknowledge Logbook promptly; safety and org-wide notices can block attention for many people.
  • Use Active Safety Concerns / Unacknowledged filters on the dashboard before leaving a site.
  • Call support before clearing cache if you have unsynced logbook drafts.