Copy roster weekly
Copies the schedule to the coming weeks, team by team, ensuring alternating weekly rosters remain consistent.
Overview
Teams with alternating weekly rosters need next week's schedule repeated two weeks later. This automation copies it team by team using each team's specific settings, after checking the status of the source days and any routes already present on the target days. A log and report show what was copied and what was skipped.
What has changed
- No more manual copying of rosters across weeks
- Alternating weekly rosters remain consistent across teams
- Reduced risk of missed or incorrect transfers
At a glance
In één oogopslag
Overzicht
Teams with alternating weekly rosters need next week's schedule repeated two weeks later. This automation copies it team by team using each team's specific settings, after checking the status of the source days and any routes already present on the target days. A log and report show what was copied and what was skipped.
Wat er verandert
- No more manual copying of rosters across weeks
- Alternating weekly rosters remain consistent across teams
- Reduced risk of missed or incorrect transfers
How it works.
What it does per team
- Logs into PUUR once and loads the teams
- Skips teams that are not yet active
- Applies team-specific settings on top of the defaults
- Checks the status of source days and existing routes on target days
- Copies the schedule from next week to two weeks later
- Writes a log and emails the report
Rules
The schedule is copied from the source days to the target days according to each team's settings, and only after checking the status of the source days and whether any routes are already present on the target days. Teams that are not yet active are skipped. Because the logic is fixed, the same input always yields the same result, and every run is logged.
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.