What's new in the Permit to Work module — every change that makes your day easier, in plain language, not developer-speak.
The permit list now shows 50 rows first; the rest come with the “Show more” or “Show all” button — the list is usable at once, on tablets and slower computers too. Opening a permit loads the data it needs in parallel, and the page no longer downloads data just because the mouse rests over a row. When you return to a requested permit from another window, it refreshes once and does not get in the way of the Back button.
An item recording who is responsible is now a single row instead of two full Yes/No selectors: the issuer has already done it, or the requester has to. A shorter, clearer page that follows the familiar paper logic.
The pre-work on-site risk check (LMRA) can be set per site: in the app, on site on paper, or not at all. The coordinator can be made mandatory up to issue. After-the-fact (paper fallback) recording can be switched on or off — when off, the option is not even shown.
Issuing is blocked when the headcount is below the minimum: at least 2 people on hot work, at least 3 for confined-space entry, including 2 attendants. The factory templates are set this way; deviating takes a reasoned change to the template.
When extending, the gas test must be valid at the start of the new time window. The extension can go on a separate sheet, the team can change meanwhile, and the work can continue under a new permit.
The new “Expiring documents” tab of the Person register shows in one place what has expired and what expires within 30/90 days. An alert block can go on the home page. The email digest is switched at organisation level (off by default, weekly or daily), and users can unsubscribe personally. An expired document already blocked issuing — now you are told before it expires.
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 permit number pattern can be set for the company, site and plant, with a live preview — so an existing paper series can be continued, plant prefixes included. The starting value can only be moved forward, with a reason. The default pattern is unchanged.
All 16 branches in Annex 1 of Hungarian Ministry of Interior Decree 45/2011 can be recorded as documents and used as permit competences; the decree is a source in the rule pack.
The shift log is now a switchable module: an organisation can run on Permit to Work and Analytics alone. The shared master data — site, plant, shift type, functional location — is always there, whichever modules are on.
Photos are downsized on the device before upload — less mobile data, faster uploads, and an oversized original is no longer rejected. The size follows what the server keeps anyway, so quality does not drop.
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.
In the Printing group of the policy you can choose to leave unticked items off the paper. Also: tighter line spacing, a two-line header and fewer redundant sentences — with no loss of content.
A closed log shows the permits issued in that shift, in their end-of-shift state, and the maintenance planned for the shift’s day; the log PDF can include this block too. Every occurrence of a task is visible in the archive as well.
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.
At issue and at the start of work, live isolation points must be applied or removed — in off, warn or block mode. A second person can also check an applied point. The no-sign-in live status page summarises the points. Every new capability is off by default.
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.
A template can prescribe photo points (per step, with a minimum count, optionally mandatory); the added photos are stored separately and the signature chain stays untouched. Notes can also be written on the permit from request to hand-back.
The Permit to Work rule set — risk assessment, policy, legal sources — is updated through expert editing and approval. A legal correction reaches every organisation; a panel on the Standard tab shows what changed and why, and adopting it does not take away your own changes.
Analytics now answers for several sites at once. On the Overview, the “Site” filter chooses which sites a view combines, and the built-in “Sites overview” puts them side by side. You can build dashboards for yourself — a personal dashboard is visible only to you, a shared one to the team. The permit report’s setup can be saved under a name, with a relative period (“previous month”) too, and a saved view can go on a dashboard as a tile: as a table, bar chart or heatmap, also in the PDF and the scheduled email. The settings pages moved into one “Settings” menu, and an “Analyze” button on the Permit-to-Work list opens the report.
A once-prepared, approved assessment can be picked when creating a permit. The policy knows four modes: none, step 0, pre-prepared selectable, pre-prepared mandatory. Assessments can also be bulk-loaded from an xlsx template, under your own rights.
Permit data now answers questions instead of just listing permits. The export’s columns and grain (one row = a permit, a person on a permit, a signature, a gas test…) are yours to choose, and the setup can be saved as a template. The permits’ PDFs come in one ZIP, with a verifiable manifest. In Analytics, the permit pivot breaks permits down by two dimensions — company, plant, type, month… — and behind most numbers is the list of permits (the ones that cannot be opened are marked with an asterisk). The company and person cards bring one contractor’s or one worker’s permits, hours, problems and expiring competences into one place.
The QR code on a printed permit is now a link to your organisation’s own address. Scanned with a phone, the permit’s live status opens without signing in, and its first sentence is the verdict: work may proceed, or do not work — and why (suspended, expired, closed…). So the site guard, the fire watch and contractors can check too, without an account.
The fingerprint of new signatures now includes the previous signature’s, the sequence number and the signing time. Altering a signature afterwards therefore breaks every later one too, and the signing time cannot be changed unnoticed either. Earlier signatures keep being verified by their own rule.
Permits are organised into four main types: general, hot work, confined space and explosive (ATEX) atmosphere. The work’s main hazard decides the type; further hazards do not open separate permits but are added to the same permit as supplementary boxes, with their own gates. The risk assessment starts from the main hazard too.
The policy starts with three ready profiles: Lenient, OPEREX recommended (the default for new organisations) and Strict. If you set something looser than OPEREX recommended, the system asks for a reason and records it — tightening is free. The policy can also be set for the whole company at once, with site-level exceptions.
Nine lifecycle steps (for example acceptance, on-site handover or hand-back before closing) can be switched in the policy — all on by default, and the settings page draws the resulting flow. The status bar at the top of the permit tells you in advance which gate blocks or warns about the next step.
If a request arrives on paper or verbally, the issuer can issue the permit from the draft in one step, without a requester. It is a policy switch: off by default, it can only be turned on with a reason, and the signature chain and the PDF state that it was a single-person issue.
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.
16 step-by-step articles in Hungarian and English, with screenshots: requesting, issuing, risk assessment, preparation, printing, paper check, templates, policy gates, troubleshooting. On the permit screens in the app, the help icon takes you straight to the matching article.
The printed permit carries a QR code in its header. Scan it, paste it into the Paper check page, and you see whether the paper still shows the current state — and if not, what happened since (suspension, hand-back, closure), with names and times. The Evidence check page verifies the signature chain of every permit at once.
A typical permit now prints on 3 pages instead of 6. When downloading you can pick a view: Compact (the authoritative paper), Spacious or Landscape; paper size and orientation are set by your organisation.
A permit can now start with a risk assessment. From a company-specific question set and a job-step table (JSA), the system states which permit(s) are needed under which conditions, and opens the drafts pre-filled. A prescribed item cannot be removed, only tightened; the integrity of an approved assessment can be verified.
Nine landscape pages in Hungarian and English: a permit’s path from request to closure, including the checkpoints. A one-page summary is available alongside it.
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.
Before issuing, the issuer can prescribe preparation steps. They land among the shift’s tasks with a "Permit" label, and if your organisation configures it, the permit cannot be issued until the required ones are done.
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.
With the third phase, Permit to Work data flows into Operations Analytics: permits issued, gate-blocked attempts and throughput by type — broken down by site, plant and period. The data sits where the decision is: you can see which checkpoint stops work, and where.
The second phase is live: the pre-issue checkpoints are now real gates. A competence gate with expiry (person and document master, xlsx/csv import), isolation points (LOTO / blind-flange reference numbers), time-valid gas testing with a re-test on extension, a worker lock (one person on one open permit at a time), SIMOPS along the technical-location tree, and a last-minute risk assessment (LMRA). All off / warn / block, per site and per type.
The Permit to Work module has started, and its first phase is now live. Risky work now runs through a controlled permit lifecycle — from request to a two-sided hand-back — with every step recorded by an append-only, hash-chained signature that visibly breaks if anyone edits the permit afterwards. The permit shows up where the shift works: open permits appear in the log and the shift handover, and it is gated to the maintenance work order. This is the first phase; the further phases follow in their own entries.
No entries in this view.
New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.