What's new in the Shift Scheduler module — every change that makes your day easier, in plain language, not developer-speak.
A sign-in lasts 8 hours by default, but your organisation’s administrator can set it between 4 and 13 hours — so it covers a 12-hour shift plus handover without signing out mid-shift. Nothing changes for existing organisations until they change it.
The first tab of Control panel → Settings shows, across 19 steps, what is done, missing or blocked — one click to the exact setting. It names, for example, what a scheduled report still lacks to be sent, so it does not silently fail to go out.
If an invitation cannot be delivered (the email bounced), the list flags it with a badge. An expired link also shows on the list, with a clear error message. An invitation link is valid for at most 7 days.
The organisation’s language applies even before sign-in; the invitation email and factory role names arrive in English, and the Permit to Work factory texts display in English — on existing permits too.
Five pages for auditors and procurement: how the system shows that a signed permit or a recorded action was changed afterwards — the chained fingerprint, the daily external anchor and the QR code on paper. It also states the limits: what we do NOT claim.
Over the past weeks we kept strengthening the supplier side. Two-factor sign-in is available to every user, and your organisation can make it mandatory; the person affected gets an email when their two-factor is turned off or reset. Our internal security policies became controlled documents, with versions and change history, their content re-checked against the running system.
Until now a sign-in expired roughly every hour during a shift — the "Keep me signed in" box did not change that. From now on a sign-in lasts a full shift, 8 hours, so the box has been removed from the sign-in page. At the end of the shift the session expires; on a shared computer, still sign out when you are done.
When you change or reset your password, every OTHER browser and device is signed out immediately — the session is revoked on the server, not left to expire on its own. A forgotten or compromised sign-in ends on its next click. On top of that, a per-tenant fingerprint of the audit trail is taken every day, chained and stored off-server: a later change to an already anchored day — even one made with owner rights inside the database — can be detected.
If your organisation falls under NIS2 (in Hungary, Act LXIX of 2024), you have to assess your suppliers too — and until now that work meant extracting the facts from us one question at a time. We now hand it over ready-made: a public page and a downloadable supplier data sheet that map the ten Article 21(2) measure groups onto what the system actually does. In an incident we notify you within 24 hours — that figure exists so your own 24/72-hour reporting deadlines stay achievable. Important: this is not a certification and it does not make you compliant; NIS2 applies to your organisation, what we do is make the supplier side verifiable. Our limits are stated on the same page.
A supplier is easy to choose when it is easy to leave. Your full data set can now be handed over: EVERY data table in machine-readable (NDJSON) and spreadsheet-openable (CSV) form, with an inventory of stored files and a SHA-256 checksum per file, so you can verify the package is intact. The package also names whatever is deliberately left out of it, and why. If you then ask for deletion, we issue a certificate: what was deleted, the result of the post-deletion check, and the fingerprint of the export we handed over first. Data leaves the backups with the rotation, within 90 days at the latest — we say that plainly, because backups are taken of the whole database.
A backup is worth what has been restored from it — so we did it. From the off-site backup (every 6 hours, to EU storage) we restored the entire database into a separate instance and counted: every table, every row and every user account came back intact. We checked the canonical shift-log PDFs separately: every one of them has its backed-up file, byte-for-byte identical to the original. The data itself restores in seconds. The full recovery time — which includes rebuilding a machine — is still being measured, and we will only state it once we can back it with a number.
The planner now sees how much leave each person has left — right where the decision is made. Payroll sets the quota once a year, in hours; usage comes from the roster itself: a leave day costs what the person would have worked that day (12 hours on a 12-hour shift). The remainder is shown in days, with exact hours on hover; if someone has no quota recorded, the screen says so instead of showing zero.
The monthly roster can now be downloaded the way it goes up on the wall: the full table grouped by crew, with daily shift headcount and per-person monthly totals, as a landscape PDF (day header repeated on every page) or Excel. There is also a new search view: pick a shift symbol and get every day of the year it occurs — per person, including whether it came from the rotation or was entered by hand, and why.
You can now track who can work which post (a 0–3 proficiency matrix) and which required exams (e.g. a medical) each worker holds, with expiries. If a required exam is missing or expired, the roster view flags it, and a dedicated view shows who has what expiring within 30/60/90 days. The system flags; it does not block — the call stays with the lead.
The module went through a comprehensive, multi-dimensional security and reliability review. No critical issue surfaced; the items found were fixed and hardened per good practice.
Every manual change to the roster — plan overrides and attendance corrections alike — gets an immutable log: when, who, which person, which day, the old and new value, and an optional reason. The log is searchable and filterable (person, date, editor, free text), exports to Excel and CSV, and hovering a matrix cell shows that cell’s history right away. It cannot be edited from the UI — which is exactly what makes it evidence.
Weekly hours are averaged over the working-time frame (Hungarian Labour Code §§ 93–94). The report now also computes the per-person balance for the whole frame (worked minus required hours) and flags anyone above the obligation at frame end. The frame start is configurable per site (calendar Jan 1 by default). It signals and justifies — it does not guarantee.
Keep a per-person register of courses and certifications: the course name, the obtained and expiry dates, and a note. The interface flags expired and soon-to-expire (within 30 days) certificates so re-training happens in time. Editing is permission-gated; anyone with access to the module can view it.
The reports are organised into tabs and expanded: a per-crew quarterly summary, plus simple charts of vacation taken and average daily coverage. So alongside the monthly figures you get the quarterly and the visual picture in one place.
From the reports you can download each colleague’s FULL annual roster — day by day, past (actual) and future (plan) — as a PDF (landscape, printable) and Excel, just like the familiar year sheet. Statistics now break out flex days (CS) and holiday-rest days (Üp) alongside vacation, together with the working-time-frame balance.
The engine behind the Shift Scheduler module has started: a deterministic rostering generator for continuous operations with labour-law compliance checks and statute references — it signals and justifies, it does not guarantee. It generates any shift rotation for any date range, handles crews separately, and supports mixed 8h/12h systems. It will also be available as a standalone developer API (headless engine).
No entries in this view.
New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.