Skills-based scheduling software

Check who can do the work before deciding who gets it.

Availability does not make two workers interchangeable. Define what the post requires, record who meets it, and use those requirements when building the roster or looking for cover.

Start free Watch the demo

Free to start. No credit card, and nothing reaches your crew until you publish.

Every exclusion has a reason
A preference never beats a requirement
You decide

An engineer at a workbench with instruments and a stripped assembly in front of them.

See it work

Every “no” comes with its reason.

Open any gap and see who was eligible, who was not, and which requirement excluded them.

Recorded in the console with demonstration data: the first 30 seconds of the guide.

The Fivexer console with a reported absence and a Find cover drawer open, stating that nobody based at the site can take the shift and offering the reason each person was ruled out. — Actual Fivexer console on sample data. “Nobody passes every rule for this shift” is a first-class answer, with the reason for each person behind “Ruled out” and “Run one short” recorded as a decision rather than left as a silent gap.

Actual Fivexer console on sample data. “Nobody passes every rule for this shift” is a first-class answer, with the reason for each person behind “Ruled out” and “Run one short” recorded as a decision rather than left as a silent gap.

Ruled out, with the reason shown, so a manager can check the source data.

The short answer

Put the required qualification on the post rather than on the person, keep site permission separate from it, and every staffing decision states who was eligible and which requirement excluded everybody else.

What it checks: Required qualifications on the post, site permission, and availability — each a pass-or-fail condition.
What it does not supply: Independent verification. A recorded skill is what your team entered, not proof of a licence or certificate.
Who decides: You. A preference can order eligible people; it can never make somebody eligible.

Put requirements on the post

A reception post and a maintenance post should not inherit the same requirements simply because they share a building. Describe the qualifications each post needs and keep site permission separate. A worker can have the right skill and still be unable to work at that location.

Post requires: Reception training
Site permission: Northgate

Separate eligibility from preference

A required qualification is a pass-or-fail condition. A preference for a familiar worker is a choice among eligible people. Keep the two separate so a strong preference cannot compensate for missing permission or training.

Requirement: Hard gate
Preference: Orders the eligible

Read exclusions when there is no cover

If everyone is excluded, examine the missing requirement and check the source data. Correct an inaccurate record; do not remove a real requirement to make the roster appear full. An explicit uncovered shift gives the manager a decision to escalate.

The nearest worker is not always eligible

Illustrative example: one post requires reception training and Northgate site permission.

Worker record	Outcome
Reception training; Northgate permitted	Consider alongside availability and working rules
Reception training; Northgate not permitted	Excluded by site eligibility
Northgate permitted; no reception training	Excluded by required qualification

Know the limit. Qualification records are only as reliable as the information maintained by your team. A recorded skill is not independent verification of a licence or certificate.

Read the rostering documentation for setup detail, or return to workforce scheduling software for the whole workflow.