Automatic shift scheduling from your needs and rules
What to prepare before a run
The system plans the schedule from the team and rules you set for the period.
People and skills
Who is active, and which roles they can fill.
Staffing demand
How many people each role needs, on a shift or in a time window.
Shifts or opening hours
Fixed shifts, or limits for creating shifts from demand.
Availability and absences
What employees submitted, and who is away in the period.
Rules
Rest between shifts, hour caps and preferences you set. This is not a claim that every Israeli labor rule is encoded automatically.
Example: a restaurant with about 25 people
Illustration only
Lunch needs service and kitchen cover. Dinner raises demand at the bar. One employee asked not to work lunch. The proposal should honor what you marked as required, and weigh the request by preference weight.
| Role | Lunch | Dinner |
|---|---|---|
| Service | 4 | 6 |
| Kitchen | 3 | 3 |
| Bar | 1 | 2 |
The same headcount covers lunch and dinner differently, based on the demand you set for each role.
What must hold, and what is only preferred
You set what must not break and what may be weighed. The run tries to satisfy both together.
Hard limits
For example an approved absence, a role the person does not hold, or minimum rest between shifts. If those cannot be met, that situation has no valid assignment.
Preferences
A shift request, a fairer split of hours, or lower cost. They are weighed, and they do not guarantee a given result on every run.
Run mode
You can choose what to favor when more than one feasible plan exists.
Balanced
Balance payroll cost with a fairer split of shifts.
Keep labor cost down
Favor lower payroll, even if hours are split less evenly.
Spread hours fairly
Favor spreading hours, even if payroll rises a little.
Choosing the run mode is available depending on your plan. Pricing
Fixed shifts and dynamic shifts
A fixed shift is a template with known hours. A dynamic shift is created from demand, inside the opening hours and length you set. Dynamic shift creation is in every plan. Run count is limited separately.
Run, wait, draft and publish
The run happens in a separate process. You can follow it in the run list while a proposal is built.
Send a run
Choose a unit, a range and a setup, then send it.
Wait for the result
Status updates when the proposal is ready, or when the run failed.
Edit and keep a draft
The proposal is not opened to the team. You can change assignments before approval.
Publish
Only after approval do the shifts appear for employees.
The full working sequence, from collecting availability to publishing, is on the shift management page. Shift management system
When there is no solution
Not every mix of demand, availability and rules can be solved. If a valid schedule cannot be built, the run does not end with a proposal, and you adjust availability, demand or rules and run again.
Checking the result
Before publishing, check the proposal against coverage requirements, availability and rules, and edit what you need. After shifts are worked, you can compare the hours that were planned with the hours that were reported.
