An Operator With the Right Skill Was Not Used: Certification, Roster, Time Off

A qualified operator the scheduler skips is almost always filtered out of the pool for a specific, checkable reason: an expired certification, a missing roster row for that shift and day, or a time-off entry. Certification alone does not put a person in the pool, and the engine tells you which condition failed.

EDGEBIC by User Solutions treats the operator as a second constraint alongside the machine, so a step needing a certified person only schedules when a qualified one is genuinely present. This post covers the case where the person clearly has the skill but was not used; it sits in the EDGEBIC troubleshooting guide and pairs with operator and skill scheduling explained and how EDGEBIC books operator hours.

First, Understand What "Qualified" Means

For a given skill on a given date and shift, the qualified pool is the set of operators who clear all three of these at once: certified and unexpired for the skill, rostered for that shift and day of week, and not on time off. Certification is necessary but not sufficient. If a person misses any one condition, they are not in the pool for that window, and the step either uses someone else or slides to a window where a qualified person exists. Each qualified person contributes only their remaining unbooked hours for that window, so a person who is already fully booked on the shift is in the pool but has nothing left to give, and the step still moves on. The engine books the least-loaded qualified person first, which spreads work across the pool rather than leaning on one name.

Cause 1: The Certification Expired

A certification carries an optional expiry date. Once that date passes, the certification is filtered out entirely when the scheduling data is built, so the operator stops counting as qualified on the next run. The record still exists and looks fine at a glance, which is what makes this easy to miss.

How to tell: open the operator's certifications and check the expiry date against the schedule date. A lapsed renewal is the culprit.

Fix: renew the certification with a current expiry (or set it to never expire if that fits your policy), then re-run scheduling. A suspended certification, one turned inactive pending a re-test, has the same effect and the same fix: reactivate it once the person is cleared.

Cause 2: The Operator Is Not Rostered for That Shift and Day

The roster is a weekly pattern: a person works a given shift on given days of the week. If the operator has no active roster row for the shift and day-of-week the step would run, they are not in that window's pool, and the machine being free does not help.

How to tell: the operator holds a current certification but has no roster row for that shift and day, or the row is inactive.

Fix: add or reactivate a roster row placing the operator on that shift for the relevant days. Note that rosters key to a global shift; if the step runs on a custom machine shift that is not derived from a global shift, no roster row can reference it and the pool reads empty. In that case, align the work center to a global shift the roster can point at.

Cause 3: The Operator Is on Time Off

A time-off range removes the operator from the pool for every date it covers, regardless of certification and roster.

How to tell: the schedule date falls inside a time-off range for that operator.

Fix: if the time off is wrong, correct or remove it and re-run. If it is real, the step correctly waited for a day the person is present; the slide is the system showing you the staffing gap rather than hiding it.

Cause 4: The Wrong Skill Is on the Step

If the step requires a different skill than the one the operator holds, the operator is not qualified for it no matter how present they are.

How to tell: the skill named on the routing step does not match the certification the operator holds.

Fix: set the step's required skill to the one the work actually needs, or certify the operator for the skill the step requires. When no active operator holds the required skill at all, the step fails fast with a message naming the skill, rather than searching fruitlessly.

The Reconciliation, in Order

1. Check certification expiry; an expired cert is filtered out silently.
2. Check the roster for an active row on that shift and day of week.
3. Check time off for the specific date.
4. Confirm the step's required skill matches the certification you expect to use.
5. Confirm the shift is a global shift the roster can key to, not an unreferenced custom shift.
6. Re-run scheduling after any change; the fix applies on the next run, not retroactively.

Prevention

• Track expiry dates actively. A renewal that lapses removes a person quietly on the next run, so review upcoming expiries before they bite.
• Roster to global shifts. Keep the shift a skilled step runs on aligned to a global shift so roster rows can reference it.
• Enter time off before scheduling, so the plan reflects real availability rather than planning against someone who is out.
• Re-run after certification, roster, or time-off edits, because operator changes only take effect on the next scheduling run.

If the problem is that you cannot pin a specific person to a step at all, that is a different question covered in I cannot assign an operator to a step. To set up operators, skills, and rosters from scratch, see how to set up operators, skills, and rosters.