OPEREX · Shift LogLive

Record what happens in your plant — and the work each shift completes

In one auditable place: structured shift handover, event and incident log, and an append-only audit trail. For any shift-based operation — offline and on your own servers, too.

Production Excellence (operations)

Product updatesHelp
The module

Built for the daily rhythm of a multi-shift plant

OPEREX runs the operating rhythm of a multi-shift operation: the right people record the right things, every shift's log opens and closes on schedule, and nothing — an instruction, a recurring task, an event — slips between shifts.

Multi-shift by design

Handles your full rota — continuous or batch, any number of shifts and crews. The system knows which shift is on from the time of day.

Roles you assign

Operator, shift supervisor, plant manager, data steward… — you decide who records, sees and finalises what (role-based access).

Logs open and close on their own

Each shift's log is generated and closed automatically, on schedule — nobody has to remember to open or finalise it.

Standing orders & shift instructions

Push standing orders to the floor; every shift acknowledges what's active — with a trace of who saw what.

Recurring & carried-over tasks

Assign one-off and recurring tasks; unfinished ones carry over to the next shift, recurring ones reappear on schedule.

Events, incidents & audit trail

Capture events and near-misses, escalate to incidents, and keep an append-only audit trail — who recorded what, and when.

Everything the shift log takes care of

One auditable system for the daily rhythm of a shift-based plant — from role to report, in one place.

  • Role assignmentOperator, supervisor, plant manager, data steward — you decide who records, sees and finalises what, with custom roles too.
  • Multiple plantsSeveral plants in one organisation, with quick switching, per-plant log setup and access.
  • Multiple sitesGeographically separate sites under one account — each with its own plants, logs and roster.
  • Automatic log lifecycleThe system opens and closes logs on their own, from your rota and timezone — no manual start.
  • Shift attendanceRecord who worked the shift — from a managed roster, with name and position.
  • Customisable logA drag-and-drop builder and ready templates: text, numbers, lists, tables, images — your log.
  • Operating-mode timelinePlant state on the shift bar: mode, "since", "from previous shift" and a "now" marker — on shifts that cross midnight too, drawn the same way in the PDF.
  • Handover notesThe handover entry (text, dictation, photo) can be its own diary element on request — the same field, switchable both ways without losing data.
  • Midnight stock gridAny field-based diary element can also be shown as a compact grid: a row per item (e.g. a tank), a column per measure (e.g. the midnight stock). The fields and the stored data do not change, and the grid can be switched on and off without losing data; on a phone the item column stays pinned, in the shift PDF it is a table. A total field can add up fields from other elements too — if a term is empty it does not calculate by default, it names the missing one.
  • Instructions and tasksStanding orders and one-off or recurring tasks; unfinished ones carry over to the next shift.
  • Events and incidentsCapture with HSE severity, tied to the log; in the Events report each event is tracked with an ID and a status (new → acknowledged → in progress → investigating → closed).
  • PDF reportA tamper-proof PDF for every closed shift, with every diary element that is switched on — parts that belong together stay on one page. Saved to the server, downloadable and previewable.
  • Automatic deliveryThe end-of-shift report emailed to your contacts on schedule — no login required.
  • Archive and searchFilterable, searchable past logs — by status, date, who finalised, and plant.
  • Data exportAny datapoint into a CSV/Excel report with a point-and-click builder; saved definitions re-run anytime.
  • Audit trailEvery change is recorded (append-only, ISO 45001 §7.5) — nothing can be rewritten silently.
  • EU data residencyYour data is stored in the EU (GDPR); self-hosted or on-premise on request. Transactional email is delivered by a US provider (Resend) under the EU–U.S. Data Privacy Framework.
  • Multilingual interfaceInterface language is configurable per organisation — Hungarian and English today, extendable to more; dates and formats follow the locale.
Add-ins

Extend the log when you need to

Separately orderable paid add-ins — the base log is complete without them. The interface grows as you switch them on.

Data series that roll across shifts

Optional add-in

Continuous recording whose lifetime belongs to the process, not the shift: lab results, in-process sampling, batch tracking. The next shift keeps writing into the same series and sees the history.

Details & pricing

Multilingual reading & reports

Optional add-in

Your shift records in its own language; your foreign colleague reads the log in theirs, with a toggle, right in the app — and the finalized log's report can reach each recipient in their own language too, attached alongside the original PDF. The original document stays unchanged and authoritative — the translation is a marked, non-authoritative layer on top: it renders the intent (not word-for-word), keeps equipment identifiers and names untouched, and flags anything uncertain. English for now; more languages on request.

Details & pricing

Reporter — reporting without an account

Optional add-in

Employees, contractors and visitors can report an event without signing in, from a posted QR code or a link — to a plant, a site or the whole company. The report lands in the plant’s shift log or the Events inbox; the reporter’s details are kept separately, with configurable retention. An optional public tier adds a public reporting page with bot protection and quarantine, plus a secret status link for the reporter.

Details & pricing

Campaign start-up

Optional add-in

For batch production: campaign phases per plant with signed gates, every step recorded in a hash chain. A start-up checklist, a phase indicator in the log, progress against plan and a campaign PDF with QR verification — with Training, also who takes which exam.

Details & pricing

Batch records

Optional add-in

Batch production batch by batch, across shifts: template-based steps or an event log (dosing, measurement, correction), hourly data and lab results on one sheet, with a summary box per vessel, also as a PDF and in analytics. Correction helper: the template formula suggests a correction from the latest measurement; the operator decides. Works without campaigns; it needs the Data series that roll across shifts add-in.

Details & pricing

Production plan

Optional add-in

For continuous production lines: daily plan rows per line (product, grade, quantity, target tank), the running product with changeovers and stops, and an Overview per line. Plan vs actual from the quantities of the shift log's line periods, with a produced-quantity calculation helper (the formula suggests, the operator decides). Start-up on a production line: start-up checklist, signed gates, production gate.

Details & pricing

Quality specifications

Optional add-in

Grades per product with versioned limits, per sampling point: an in-process target range and a release limit. On Batch records it is the target grade (measurements are judged against it; changing it needs a reason), on a Production plan row the planned grade, and on Analytics trends a target range with the share within it.

Details & pricing
Optional add-inLive

Batch records: one sheet for a batch, across shifts

A batch does not end with the shift. The template sets out the steps, the next shift picks up where the last one stopped, and the steps, hourly data and lab results stay on one sheet.

The OPEREX batch record: steps of the reactor section of an open batch with prescribed and actual values, times, crew and operator, and a lab result below.The OPEREX batch record: steps of the reactor section of an open batch with prescribed and actual values, times, crew and operator, and a lab result below.
A real OPEREX screen with test data; the names and product are fictional.
  • Templates without code: sections, steps, hourly columns and lab limits in an editor, versioned once published. Start empty, from a copy or from a built-in sample.
  • Across shifts: prescribed and actual value per step, from–to times that can cross midnight, crew and operator. On batch plants the shift log also offers the next steps due.
  • Lab link: limits and status per sampling point on the sheet, and each sample goes into the same lab data series as on the Data series page. A pending lab result does not block closing; it can arrive afterwards.
  • Checked closing: a list of missing required steps, a content hash on the closed batch, and reopening or voiding only with a reason, in an event chain.
  • Batch PDF in three views (Full, Summary, Traceability), with a content-hash prefix and template version in the footer of a closed batch.
  • Analysis with the Analytics module: cycle and section times, out-of-limit rate, trends batch by batch, gaps stated openly, drill-down to the sheet, CSV export.
  • Event-log mode: events from the template catalogue (dosing, measurement, correction) in one or two clicks, with the measurement type and a summary box per vessel in the diary, the PDF and on the home page.
  • Correction helper: the template formula suggests a correction from the latest measurement, the mass or a manual input; the operator enters the quantity, and the server recalculates and stores only a matching result.

It needs the Data series that roll across shifts add-in. It works without Campaign start-up and can be linked to a campaign. Part of a custom quote.

Optional add-inLive

Production plan and Quality specifications: produce to plan, measure against limits

Two add-ins for continuous production lines. The plan says what should run, the shift log records what ran and how much was made, and Quality specifications set per product what a sample is measured against.

Production plan

Plan rows per production line and day; the shift records the product actually running.

  • Daily plan rows per line: product, grade, quantity per day, target tank. Repeat to the following days, and a change log with restore.
  • Overview: one box per line — running or stopped, the running product and since when, today's plan, the next changeover. Changeover, Start and Stop with the plan's suggestion.
  • Plan vs actual: the actual is the quantity of the shift log's line periods; open periods and periods without a quantity do not count. In the Analytics module, a plan vs actual grid and metrics.
  • Produced-quantity calculation helper: next to a period's quantity, "Calculate" suggests a value from a formula using the period's data (duration, product); taking it over only fills the field, the operator decides.
  • Start-up on a production line: a start-up base checklist per plant, opened from the plan or by hand, two signed gates, "Start production", and a production gate (off, warn, block).

Quality specifications

Grades and their limits per product in one place, versioned — Batch records, the Production plan and Analytics all read from it.

  • Grades per product, limits (min, target, max) per sampling point. Every change is a new version: an older sample is judged with the limits in force at its own time.
  • An in-process target range and a release limit, with separate scopes: the target range for running production, the release limit for release.
  • Target grade on Batch records: a batch opens with a target grade, measurements are judged against it, and a change needs a reason and stays in the chain. The correction helper pre-fills the in-process or the release target.
  • Target range on Analytics trends: the range in force at the sample's time, with "samples outside the target range" and "within target range (share)" views. The grade of a plan row comes from here too.

Both are Shift log add-ins and part of a custom quote: request them on the Add-ins tab of the Control panel, and OPEREX switches them on. Plan vs actual uses per-line recording in the shift log's operating-mode element; the target grade needs Batch records, and the target-range trend and the plan vs actual grid need the Analytics module.

Downloadable materials

Solution briefs, the guide, datasheet and security brief — as PDF, always generated from the latest product information.

All materials

Excel isn't auditable. Paper gets lost.

Same shift, two worlds. Toggle and see the difference.

  • Scattered Excel tabs — everyone on a different version.
  • Handwritten log: “who changed it, and when?”
  • The near-miss gets lost between shifts.
  • At audit time you hunt for evidence for days.
See the full Excel vs. shift-log comparison
Who it's for

Built for any operation that runs in shifts

Continuous or batch, hazardous or not, from a single production unit to large multi-site organisations. Common settings:

  • Chemical & process plants
  • Food production
  • Energy & utilities
  • Pharmaceuticals
  • Manufacturing
  • Oil & gas

Works for a single production unit too — a few shifts, no IT department.

AB50%1 + 1 + 1 − 1 = 2AB100%1 + 1 + 1 + 1 = 4
Where the asset team pulls in one direction

Operations, process technology, maintenance and HSE all see the same log. When goals are aligned the team's rope pulls together (1+1+1+1=4); when they aren't, the effort cancels out (1+1+1−1=2). The shift log is where that daily alignment lives.

One auditable workflow

Shift log

The shift's events and handover in one place.

Event

An entry becomes an incident or near-miss record.

CMMS trigger

A maintenance-relevant event raises a task.

Report

An auditable, finalized shift report.

Try it: the audit trail can't be rewritten after the fact.

The audit log is append-only: you can add a new row, but you can't rewrite or delete an existing one. Click the lock on a row and see.

Immutable log
  1. 06:14B. KovácsShift start, systems in normal operation.
  2. 09:02K. NagyPump P-204 vibration near the upper limit.
  3. 11:37K. NagyGasket leak at the heat exchanger — near-miss, escalated.

The audit trail is the immutable, timestamped history of the shift log and its events: who recorded what, and when. You can only append — never rewrite or delete an existing entry. That's what gives an ISO 45001 §10.2 investigation trustworthy, tamper-evident evidence.

This demo illustrates the idea: in production it's enforced server-side by an append-only database policy (FORCE RLS — inserts only); even the app can't rewrite an existing row.

How can you tell the audit trail was not rewritten afterwards?Digital fingerprints — technical brief

How much time can you free up in a year?

Set your own numbers — the calculator gives a conservative estimate. Illustration, not an offer.

Illustrative estimate
—Documentation hours saved / year
—Audit hours saved / year
—Total hours freed up / year

This freed-up time can go to autonomous maintenance, preventive work, or other value-creating activity — not lost hours, but recovered capacity.

Assumptions (tunable): 40% of documentation time and 50% of audit prep can be saved; documentation time is counted per person per shift. This is an illustration, not a contractual promise.

Frequently asked questions

What is a digital shift log?

A shift log is the official handover document for shift changes at any operation that runs in shifts (continuous or batch): what happened during the shift, and what the next team needs to know. OPEREX digitizes it — with immutable, timestamped entries.

How does OPEREX support the ISO 45001 §10.2 audit?

Every entry and status change gets an append-only audit trail (who, what, when) that cannot be altered afterwards. The shift log and incident handling thus provide auditable evidence.

Which operations is it for?

Any operation that runs in shifts — continuous or batch, hazardous or not, from a single production unit to large multi-site organisations. Common settings include chemical and process plants, food production, energy, utilities and manufacturing — oil & gas among them.

Where is the data stored?

In the EU, under GDPR. On request, a dedicated or on-premise (air-gapped) deployment (Enterprise).

How long does it take to roll out the shift log?

The shift log is the lowest-risk entry point: structured shift handover can go live for one unit within days to weeks via a pilot. We fit the rollout to the team's pace.

Who can access it, and with what role?

Role-based access (RBAC): operator, shift supervisor, plant manager, data steward, etc. — who sees, records and finalises what. Every change leaves an audit trail.

How does the shift log relate to operational excellence?

The shift log is the daily execution layer of operational excellence — its 'last meter'. The top-down OE framework (process safety, reliability, efficiency) becomes a concrete, auditable datapoint here: the KPI fact, the gap to target and the triggered action are recorded shift by shift.

Can it replace the paper shift log book?

Yes — that is usually the first step. What the printed shift log or event log book holds (handover, events, instructions, tasks) becomes structured, searchable entries with an immutable audit trail; the log structure is shaped to the book you use today. Where a printed copy is still needed, the log can be exported to PDF.

Does it handle batch production and batches?

Yes, with the Batch records add-in. The template sets out the steps, shifts carry the same batch sheet forward, hourly data and lab results stay in one place, and the batch can be downloaded as a PDF. The add-in is part of a custom quote, needs the Data series that roll across shifts add-in, and works without campaigns.

Does it help calculate a batch correction?

Yes, with the correction helper of the Batch records add-in. A formula set in the template suggests a correction from the latest measurement, the batch mass or a manual input; two clicks turn it into an event, and the operator enters or overrides the quantity. The server recalculates with the batch's template version and stores only a matching result. It is a suggestion, not automatic dosing — the formula comes from your own process engineers.

Can I compare the production plan with the quantity actually produced?

Yes, with the Production plan add-in. You write plan rows per production line and day (product, grade, quantity, target tank); the actual is the quantity of the shift log's line periods, which the calculation helper can suggest from a formula, with the operator deciding. Open periods and periods without a quantity do not count, and the system says what is missing. Grades and their limits come from the Quality specifications add-in: an in-process target range and a release limit, and the target grade on Batch records. Both are part of a custom quote.

Help

How to use it — step by step

Help describes the product: a concrete task, numbered steps, and what to do when you get stuck. Public, searchable, in Hungarian and English.

A taste of one article: “Log an event in the diary”

From the built-in types (HSE, technical fault, quality deviation, maintenance-requiring, process, material release, other) or your own; plus a subcategory, if there is one.

Near miss, incident or accident. For other types the field does not even appear.

The date comes from the diary — you only enter hours and minutes, and only within the shift window.

Go to Help
Knowledge base

Related reading from the knowledge base

Go deeper into the methodology behind this module.

Open the knowledge base

Let's start a pilot

We'll show you OPEREX on your own operational processes — no strings attached.

Request a demo
Newsletter

Follow how OPEREX evolves

New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.

You can unsubscribe anytime — the link is at the bottom of every email.