Why exceptions must be treated as a process
An exception without a record is simply a pass issued on trust. After a few weeks nobody remembers who let a person in outside the roster and why, and the schedule stops meaning anything. A good practice is an exception that has an owner, a reason and an expiry date.
The working time module in InnerWeb has supervisor exception queues: missing exit, late arrival, work outside the roster, exceeded norm and rest violation. The thresholds for an uncertain exit (89 minutes) and for a reminder call (34 minutes) are settings, so the plant adjusts them to its shifts.
Rule 1: the supervisor approves, not security
Security does not know the production roster, so it should not decide whether overtime is justified. The shift manager or another supervisor named in the procedure approves, and security carries out the decision. Separating the decision from its execution reduces the pressure on the gate guard at three in the morning.
Minimum rest under the Labour Code
Rule 2: an exception has a scope and a time
An exception for one person and one shift is good practice. An exception for a whole agency for a whole month is already a new schedule and must be introduced as a change of the rule in the access control system, with the planner and the IT department involved.
In practice it is worth adopting thresholds: up to one day as a supervisor exception, above one day as a schedule change. The thresholds are a recommendation that the plant records in its procedure.
Rule 3: rest and night hours under control
Overtime and replacements most easily break rest. The Labour Code guarantees 11 hours of daily rest (art. 132) and 35 hours of weekly rest (art. 133). The working time module warns about daily rest below 11 hours and weekly rest below 35 hours, and counts minutes worked in night hours from 22:00 to 06:00.
Before approving an exception the supervisor should see whether the person would break their rest. It is worth noting that the roster screens and the ERP export are at the preview stage with demo data, and the working time module was piloted on one installation. We therefore describe them as an option in development, not as a finished standard.
Rule 4: settle exceptions every week
Once a week the supervisor and the planner review the list of exceptions. Repeated exceptions for the same person or agency point to a planning error, not to an unusual situation. The conclusion of the review is usually a correction of the roster, not another approval.
The entry verdict in the security panel has four components: no missing trainings, no missing qualifications for dangerous work, a permit or visit for today, and an active account. An exception from the schedule does not release from any of them, so a person without training does not enter even with an approved exception.
Register: what to record for each exception
The first scan with a green verdict records an entry, the second an exit, and a scan with a red verdict records a refusal. For an exception the record should combine the refusal or the entry outside the window with the supervisor's decision.
- Who approved and at what time
- For whom and for which shift
- Reason in one sentence
- Whether the daily rest was checked
- When the exception expires
Checklist
Video
Frequently asked questions
Does an exception release from training?
No. The entry verdict still checks trainings, qualifications, the permit or visit, and an active account.
Can the thresholds of 89 and 34 minutes be changed?
Yes. The uncertain exit threshold and the reminder call threshold are settings of the working time module.
Are the roster and the ERP export ready?
These screens are at the preview stage with demo data, so we describe them as an option in development.
Sources
Let's put exceptions in order on the shifts
We will show the supervisor exception queues and go through the threshold settings with your shift managers.
Let's talk