Constraint-based scheduling compares possible plans against explicit rules. Required rules define what is workable; planning priorities help choose a better plan. Chrona searches those choices and returns a proposal to your Dataverse board.

Start with what must hold

A shift may require a skill. A person may be unavailable or need enough rest before the next shift. These are boundaries on an assignment, not small preferences that can be traded away for a tidier roster.

The rule needs a precise meaning. For example, does an availability window have to cover the whole shift? Does a fixed assignment stay with the same person? If a rule is vague in the application, the solver cannot resolve the ambiguity for you.

Search the whole plan

Assignments affect one another. Giving one person a shift changes who can cover the next one. Chrona evaluates candidate schedules across the selected period, including work that has no assignee yet. It scores the candidates against the supported rules and keeps the strongest plan found during the run.

This search is mathematical optimization. It does not predict a roster from past schedules or generate one from learned patterns. The strongest plan found is a proposal, not a promise that every goal can be met or that no better plan exists.

Then compare the trade-offs

Two workable plans can still be very different. One may cover more work. Another may respect more personal preferences, spread hours more evenly or cost less. Decide which measures matter, over what period, and how those goals should be balanced.

“Balance workload” also needs a definition. You might mean hours, shift counts or another measure. A clear objective lets a planner understand why one proposal scored better than another.

Set the scope of workplace rules

Awards, workplace agreements and regulations can impose scheduling requirements such as rest periods or working-time limits. Chrona checks the supported rules that are configured for your case. It does not interpret an entire award or agreement, and it does not calculate pay. A person with domain expertise must define and test the rules that apply.

Make room for an impossible problem

There may not be enough qualified, available people to cover every shift while respecting all required conditions. Leaving work visibly unassigned can be more useful than silently weakening a requirement. The right response depends on your operating model and should be an explicit decision.

Review the proposal in context

Chrona returns proposed changes to the same Dataverse board. You can compare the current and proposed plans, keep or drop individual changes, and select Apply only when the result is ready. The people who own the rules still own the decision.

The Chrona board in Power Apps shows proposed changes and a list of changes to review before Apply.
A proposal on the board, ready for the planner to review.
How Auto Schedule uses these rules
What constraint-based scheduling means, in the glossary