Tools

Tell us your constraints. We will tell you what we do not cover.

Most vendor conversations start from a features list and work backwards to your requirements. This works the other way round. Describe your unit below and see, rule by rule, which of the 133 named rules already match, which need only a number from you, and which are not in the catalogue at all.

Constraint match

verified

Which of your rules do we already have?

Describe your own unit below, headcount, rest floor, whether you roster on a fixed pattern, and so on. Every field is optional. Whatever you fill in is checked against the 133 named rules in SkyRoster's compiled catalogue and sorted into three groups: rules we already have, rules where your number becomes the setting, and constraints the catalogue does not model at all. The third group is the one worth reading closely.

Nothing you enter is sent anywhere. The match runs in this browser tab only, and your answers are kept in this browser's local storage so the page remembers them if you come back. Clear them at any time below.

Turn on JavaScript to change these answers. The worked example below already shows a typical 96-controller area control centre.

Your unit

HeadcountNumber of teams

Operating hours

Around the clock, 24/7Limited operating hours

How you roster

Pattern

A fixed rotating patternNo fixed pattern, planned individually

Limits you already enforce

Leave any of these blank if you don't have a fixed number.

Minimum rest between duties (hours)Maximum consecutive duty daysMaximum consecutive night dutiesMaximum hours per duty period

Qualification families you roster against

Multiple ratings, ranked by priorityA main qualification, separate from secondary onesRatings that expire and need revalidationSuspension or graduation status can block an assignmentA probation or support period before full currencyInstructor or OJTI capacity limits

You filled in 12 of 12 fields. That is enough to find 14 rules that already cover part of your setup, 1 rule where your own number becomes the configured threshold, and 7 constraints the catalogue does not model.

Maps to rules we already have

A named rule in the catalogue already checks this, as is.

Number of teams
People are rostered with their own team
You said you roster in 4 teams. This rule keeps assignments inside each employee's own team.
Number of teams
Assignments stay inside a person's own unit
You said you roster in 4 teams. This rule keeps assignments inside each employee's own team.
Fixed pattern or none
A run of duties is long enough to be worth it
You roster on a fixed rotating pattern. SkyRoster validates the pattern itself against this rule when it builds the roster, on top of whatever the pattern already encodes.
Fixed pattern or none
Nobody is given two shifts on the same day
You roster on a fixed rotating pattern. SkyRoster validates the pattern itself against this rule when it builds the roster, on top of whatever the pattern already encodes.
Trainees on position
Trainees do not stay on position too long at a stretch
You run trainees on position. At the real-time position-allocation layer, this rule checks it independently of whatever the strategic roster says.
Trainees on position
Trainees get their own minimum rest before position
You run trainees on position. At the real-time position-allocation layer, this rule checks it independently of whatever the strategic roster says.
Bank of working hours
A swap of banked-hours shifts needs the hours to cover it
You use a bank of working hours. When a shift built from banked hours is swapped, this rule blocks the swap if the bank does not cover it.
Self-service shift swaps
A swap cannot cut anybody below minimum rest
You said swaps are self-service today. When someone requests a swap, this check re-runs your rest floor against the trade before it is allowed.
Self-service shift swaps
A swap cannot put anyone on an unrated position
You said swaps are self-service today. The swap is refused if either side would end up on a shift they are not qualified for.
Self-service shift swaps
A swap cannot move anyone outside their own unit
You said swaps are self-service today. The swap is refused if it would move someone into a unit they do not belong to.
Self-service shift swaps
A swap cannot push anyone past their overtime limit
You said swaps are self-service today. The swap is refused if it would push either employee past their overtime limit.
Self-service shift swaps
A swap cannot collide with approved leave or duty
You said swaps are self-service today. The swap is refused if it collides with approved leave or another duty request.
Qualification families
The higher-priority rating is used first
You said your people hold multiple ratings, ranked by priority. This rule lets the solver prefer a higher-priority qualification when more than one would satisfy the same shift.
Qualification families
An expired rating cannot cover a shift
You said ratings expire and need revalidation. This rule stops an assignment from standing on a qualification that is no longer valid.

Supported, but the threshold is yours to set

The rule exists and is configurable. The number you typed is not a default we ship, it becomes the configuration.

Minimum rest between duties
Rest before going on position is checked on the day
Your value: 12 hours
Your 12-hour minimum becomes this rule's configured floor, at the real-time position-allocation layer rather than the strategic roster.

No corresponding rule

The catalogue does not model this. Said plainly, not papered over.

Headcount
Headcount on its own is not a rule input in the catalogue. It changes how much the fairness-and-distribution and coverage-and-demand families have to balance across your 96 people, but no rule reads total headcount as its configured number.
Minimum rest between duties
You roster on a fixed pattern. The compiled catalogue (compiled on 12 September 2026) has no strategic-layer rule applying a minimum rest floor to a pattern-based roster, only to a roster without one (8 rules in the rest and recovery family, none written for a pattern). A fixed pattern already fixes that by construction, its shape sets the gaps and run lengths, but the catalogue does not separately enforce a minimum rest floor as an adjustable rule on top of it. If you need it enforced independently of the pattern, bring that to a working session.
Maximum consecutive duty days
You roster on a fixed pattern. The compiled catalogue (compiled on 12 September 2026) has no strategic-layer rule applying a cap on consecutive duty days to a pattern-based roster, only to a roster without one (8 rules in the rest and recovery family, none written for a pattern). A fixed pattern already fixes that by construction, its shape sets the gaps and run lengths, but the catalogue does not separately enforce a cap on consecutive duty days as an adjustable rule on top of it. If you need it enforced independently of the pattern, bring that to a working session.
Maximum consecutive night duties
You roster on a fixed pattern. The compiled catalogue (compiled on 12 September 2026) has no strategic-layer rule applying a cap on consecutive night duties to a pattern-based roster, only to a roster without one (3 rules in the night work family, none written for a pattern). A fixed pattern already fixes that by construction, its shape sets the gaps and run lengths, but the catalogue does not separately enforce a cap on consecutive night duties as an adjustable rule on top of it. If you need it enforced independently of the pattern, bring that to a working session.
Maximum hours per duty period
You roster on a fixed pattern. The compiled catalogue (compiled on 12 September 2026) has no strategic-layer rule applying an hours-per-duty ceiling to a pattern-based roster, only to a roster without one (9 rules in the working time limits family, none written for a pattern). A fixed pattern already fixes that by construction, its shape sets the gaps and run lengths, but the catalogue does not separately enforce an hours-per-duty ceiling as an adjustable rule on top of it. If you need it enforced independently of the pattern, bring that to a working session. The nearest thing that still applies is a separate, narrower rule capping continuous time on a single console position, which is not the same as a duty-period ceiling.
Trainees on position
You roster on a fixed pattern. The compiled catalogue (compiled on 12 September 2026) has no strategic-layer rule applying an instructor-to-trainee ratio to a pattern-based roster, only to a roster without one (1 rule in the training and supervision family, none written for a pattern). A fixed pattern already fixes that by construction, its shape sets the gaps and run lengths, but the catalogue does not separately enforce an instructor-to-trainee ratio as an adjustable rule on top of it. If you need it enforced independently of the pattern, bring that to a working session.
Hours of operation
Whether you run around the clock or a limited window is not itself a rule. It shapes your demand calendar; the 10 coverage-and-demand rules then fill whatever that calendar asks for and flag both gaps and over-staffing, the same way regardless of the hours it covers.

The 96-controller unit above is a worked example, not a customer. No customer data appears anywhere on this site.

How to read the third column

A gap is not a no

"No corresponding rule" means the compiled catalogue does not have a named rule for that exact constraint today. It does not mean the requirement is impossible, it means it has not been built, or it is handled differently than you described. Bring it to a working session and we will tell you which.

A fixed pattern changes the picture

Answer "a fixed rotating pattern" and several limits move into the third column. A pattern fixes its own rest gaps and run lengths by construction, so the catalogue does not separately enforce them as adjustable rules on top of it. Roster without a pattern and those same limits reappear in the first two columns.

The catalogue moves

This match is read from the same compiled source as the rule explorer, at the same build. A rule added to the engine appears here on the next build, not by us editing this page by hand.

Bring us the constraint that did not match.

A working session is 45 minutes with your own numbers on screen. If the third column named something real, that is exactly what we should spend it on.

Book a working session Send a question instead