Skill certification that actually gates the work, not just a spreadsheet that tracks it

Skill certification records

Each certification names the operator, the skill, the ILUO level achieved, who certified it and when, and — where the skill requires recertification — an expiry computed automatically from the skill's recertification interval. A grant can also carry a future valid-fromdate, so a certification earned today does not silently activate early. One record per operator per skill is current at a time; requalifying an operator updates that record rather than appending to a history log.

Certification types and training records

Certification types carry an issuing authority, an optional validity period, and a flag for whether the certification is regulatory in nature. Individual training events — course title, completion date, duration, score, pass/fail, and the ILUO level achieved — are recorded as immutable entries naming the supervisor who signed off, giving you a defensible training history independent of the current certification snapshot.

Skill-gated execution: a hard block, not a suggestion

The gate lives at the edge station, in three layers. First, a server-side hard block: when an operator submits a step completion for a step that names a required skill and minimum level, the edge API re-validates the gate and rejects the event with a 403 if it fails — the step completion is never written. This runs even if a client were tampered with to skip the UI check, which is exactly the threat it is designed against. Second, an advisory banner in the work instruction runner warns the operator before they get there. Third, an offline staleness check: a cached skill grant older than four hours is treated as unverified and denies the gate, rather than trusting a cache that might be out of date on a station that has lost its connection.

Supervisor override, e-signature grade

When a gate needs to be bypassed — a newly transferred operator on their first shift on a line, say — a supervisor can issue a single-use override. The override requires a written reason of at least twenty characters and three words; a vague justification is rejected outright. The override is consumed exactly once, on the specific execution it was issued for, and both the issuance and the consumption write an explicit audit event. There is no such thing as a standing override that quietly lives on past the shift it was meant for.

Skills matrix and training dashboard

A cross-tab of every operator against every skill they hold or that a route step or piece of equipment requires, showing current level, whether it has expired, and whether the requirement is met — exposed on GraphQL and rendered at /mes/skills-matrix and/mes/training-dashboard. Skill overrides and gate health have their own dedicated views at /compliance/skill-overrides and/admin/skill-gate-health, with breakdowns by skill, operator, and supervisor and counts of certifications expiring in the next 30, 60, and 90 days.

Regulatory mapping

Qontiv is designed for compatibility with these standards and supplies the certification and audit records an auditor asks for. Your certification body audits you, not us.

Scope — what this does and does not do

• No requalification workflow. Recertifying an operator is an update to the same certification record — there is no renewal queue, reminder sequence, or approval chain around it.
• No email or push alerting on expiry today. Expiry dates are computed and enforced by the gate at the moment of execution; a proactive notification to a supervisor before that moment is not yet built.
• Completing a certification does not auto-grant skills. Certification types and skills are separate records; if a course should also grant a skill, that grant is entered explicitly.

Availability

Worker training and competency, including the ILUO skill matrix, is included inProfessional. See pricing for the full tier ladder, or request a demo to see the gate reject a step in real time.