Processing schedule disruptions
Keep employee shifts accurate regarding meetings, contract changes, and corrections by adding, removing, and adjusting shifts.
Overview
When contracts, meetings, or corrections change, employee shifts in SDB Planning must be updated accordingly. This automation compares employee and scheduling data, determines which shifts need to be added, removed, or corrected, and applies them based on meeting categories and contract rules. Cases that cannot be resolved are logged as exceptions, and those involved receive an email on Friday.
What has changed
- Less manual scheduling work
- Reduced risk of missed changes
- Exceptions are recorded and do not get lost
At a glance
In één oogopslag
Overzicht
When contracts, meetings, or corrections change, employee shifts in SDB Planning must be updated accordingly. This automation compares employee and scheduling data, determines which shifts need to be added, removed, or corrected, and applies them based on meeting categories and contract rules. Cases that cannot be resolved are logged as exceptions, and those involved receive an email on Friday.
Wat er verandert
- Less manual scheduling work
- Reduced risk of missed changes
- Exceptions are recorded and do not get lost
How it works.
What it does per schedule change
- Compares current employee data with stored data
- Reads scheduling data (shifts, open shifts, shift codes) from SDB Planning
- Prepares the necessary additions, removals, and corrections
- Executes every change per meeting category and contract rule
- Logs every result and writes exceptions to an error file
- Emails outstanding cases to the relevant parties on Friday
Rules
For each change, the automation looks at the meeting category, whether it is a removal or correction, whether contract hours are above or below 12 hours, and whether the employee is a personal supervisor, and determines which shifts should be added, removed, or corrected based on that. Changes it cannot apply are logged as exceptions. The same input always leads to the same outcome, and every run leaves a logbook that can be audited.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.