Why Certification Is Checked When You Schedule, Not When You Punch

EDGEBIC by User Solutions checks operator certification when it builds the schedule, never when someone taps a button at the terminal, and that split is deliberate. Certification enforcement scheduling works this way because the plan is the only place in the system that can enforce anything about people, and the terminal is the one place that structurally cannot.

That sentence tends to worry people on first hearing, particularly in regulated shops. It should not, once you see what each side is actually capable of. The plan can guarantee that a job requiring a certified welder is only ever placed where a certified welder exists and has hours. The terminal can guarantee that whoever ran the job is named on the record forever. Neither can do the other's job, and pretending otherwise would produce a control that looks strong and is not.

Where the Gate Actually Sits

A routing step can carry a Required Skill. When it does, the scheduler adds a second question to the one it always asked. The machine question is unchanged: does this work center have free hours? The new question is whether a person who holds that certification, is rostered on that shift, is not on recorded time off, and still has hours left in their day is available in the same window.

If the answer is no, the step does not go there. It slides to the next window where the answer is yes. The machine can be sitting with eight free hours and the step will still move, because for that step an unstaffed shift is unusable capacity. See how operator skills gate work center assignment.

Certification is data with a life of its own inside that check. A certification row carries a Certified On date, an optional Expires On date, and an Active flag. A blank expiry means it never expires; a date that has passed stops qualifying the person on the next scheduling run; unticking Active suspends the certification without destroying its history. See skill expiry and recertification.

So the gate is not a warning and not a prompt. It is a constraint on where work is allowed to be placed, applied every time the schedule is built.

Why the Terminal Cannot Hold This Gate

The kiosk has no login, no PIN, and no badge scan. The Operator box is a free-text name that gets stamped onto every punch. See why the kiosk has no login.

That single fact settles the question. A certification check at the terminal would compare a required skill against a typed string. Anyone who mistyped their name, used a nickname, or was covering for a colleague would be blocked from reporting real work, and anyone who wanted to bypass the check would type a certified colleague's name. The check would obstruct honest operators and fail dishonest ones, which is the worst possible ratio for a control.

There is a second reason, and it matters more in practice. A gate at the terminal would put the software between an operator and the act of reporting what happened. Every design choice in the kiosk points the other way: fewer taps, no authentication ritual, nothing that gives anyone a reason to stop punching. Data that is easy to capture gets captured. A terminal that sometimes refuses to record reality is a terminal that trains people to record nothing.

Two Records, Kept Apart On Purpose

EDGEBIC keeps these two apart rather than reconciling them automatically, and that is the design's most useful property for anyone who has to answer questions later. The plan says who should have done it and is guaranteed to name only qualified people. The floor says who did. Agreement is your evidence; disagreement is an exception you can see. Merge them and the exception disappears, taking the useful signal with it. See planned crew versus who actually worked.

What This Means for a Regulated Shop

The honest statement to give an auditor has three parts, and it is stronger than it sounds.

First, the assignment was constrained. Every scheduling run refused to place this operation anywhere a person holding an unexpired certification was not available. That is a systemic control, applied without anyone remembering to apply it, and it is visible in the plan.

Second, the assignment was communicated as a named instruction. The crew plan reaches the floor as a read-only list grouped by operator and date, with shift, job, work center, window, and hours. The supervisor handing out work on a skill-gated step is handing out the certified assignment, not guessing. See how supervisors use the dispatch view.

Third, execution was attributed permanently. Every punch carries a typed name and a timestamp taken when the tap landed, corrections require a reason, and nothing is ever erased. See reading the kiosk punch history drawer.

What the software does not claim is that it authenticated the person at the machine. If your quality system needs a verified signature, that step still belongs to your quality system. The scheduling software's contribution is that the certified answer is now the default one, produced automatically and printed on the sheet, instead of depending on a supervisor's memory of who holds what ticket.

What the Gate Quietly Depends On

Because the check happens in the plan rather than at the machine, it inherits the plan's data dependencies, and one of them surprises people.

Operators are rostered onto global shifts, and the roster is a weekly pattern of shift by weekday. A work center whose calendar is derived from a global shift automatically inherits that shift's roster, so certifying and rostering a person once covers every machine mirroring the shift. But a work center shift that is not derived from any global shift can never be staffed, because no roster row can ever match it. Skill-gated steps routed there will visibly fail to schedule, and the cause is a calendar decision rather than a certification one. See how the shift operator roster works.

The second dependency is timing. Certifying someone, renewing an expiry, rostering a new shift, or recording time off changes nothing until the next scheduling run. Nothing replans on its own. So a newly certified welder does not become available the moment you tick the box; they become available the next time the schedule is built. That is worth telling supervisors explicitly, because the gap between entering data and seeing it honored is where people conclude the feature is not working.

The Pin Is the Strongest Control Available

When the identity of the person is genuinely a requirement rather than a preference, the plan has a stronger setting than the skill gate: pinning the step to one named, qualified operator.

A pin is hard on purpose. The step schedules only when that person has hours, and the rest of the qualified pool is never used as a fallback. If the pinned person is on vacation, the step slides through their absence to their first day back rather than quietly moving to a colleague. That visible slip is the feature working: a named person's absence becomes schedule movement you can see and decide about. See how the operator pin pins a person to a job.

Use it sparingly. Letting the system pick from the whole qualified pool load-balances the work and gives the scheduler room to hold dates. Every pin trades that flexibility for certainty about who, so spend pins where the certainty is worth the dates: customer sign-off requirements, a regulated inspection, the one setter who can run a particular fixture.

One caveat is worth internalizing. Reassigning a step by dragging it onto another operator's lane on the Gantt checks qualification and accepts the drop, but it does not check that person's remaining hours. You can knowingly overload someone; the next scheduling run books hours honestly and slides the step if they cannot cover it. That is the same trust model as dragging an operation to a different machine.

The Failure Mode to Design Against

The one way this model goes wrong is a shop that believes the terminal is a gate.

The symptom is a supervisor who stops checking the dispatch list because they assume the software will refuse a wrong assignment. The terminal will not refuse. It will record an uncertified person's name against a skill-gated job without complaint, and the plan will be perfectly correct while the floor quietly departs from it. Nothing breaks, and nothing warns you.

Three habits close the gap, and none of them are software features. Hand out the dispatch list rather than the machine queue on skill-gated work. Keep expiry dates real, so a lapse removes someone from the plan automatically instead of surfacing at audit time. And review the punch names against the crew plan periodically on your gated operations, because that comparison is the only place the divergence becomes visible.

The takeaway

Certification is enforced where enforcement is possible: in the plan, on every run, as a constraint on where skill-required work may be placed. The terminal is left frictionless because a free-text name cannot authenticate anyone, and a gate built on one would block honest operators while failing everyone else. Keep the two records apart, use the pin when identity is genuinely a requirement, and remember that the last mile stays a supervisory control. Explore the platform at EDGEBIC, see the upgrade path in RMDB to EDGEBIC, and read on in how the shift operator roster works and how an operator's hours are attributed to a job.