Funding correction in the schedule
Automatically adds ZVW time to planning entries with more than one funding source in PUUR.
Overview
Some entries in tomorrow's schedule have more than one funding source. They appear as yellow rows, and each row requires the correct time under ZVW to ensure the scheduled hours are properly funded. The automation reviews each team's schedule every evening, including day and night shifts, so that the next day begins with the funding already in order.
What has changed
- Planners no longer need to manually correct these entries, allowing them to focus on the planning itself
- Funding is recorded consistently across every team each evening
- Reduced risk of missed or incorrectly funded entries in tomorrow's schedule
At a glance
In één oogopslag
Overzicht
Some entries in tomorrow's schedule have more than one funding source. They appear as yellow rows, and each row requires the correct time under ZVW to ensure the scheduled hours are properly funded. The automation reviews each team's schedule every evening, including day and night shifts, so that the next day begins with the funding already in order.
Wat er verandert
- Planners no longer need to manually correct these entries, allowing them to focus on the planning itself
- Funding is recorded consistently across every team each evening
- Reduced risk of missed or incorrectly funded entries in tomorrow's schedule
How it works.
What it does per team
- Logs in and opens the team's PUUR schedule
- Sets the calendar to tomorrow and verifies the date
- Reviews all employees, including those on day and night shifts
- Identifies entries with more than one funding source
- Adds the correct time to ZVW for those entries
- Emails the processing log to the team
Rules
If an entry has more than one funding source, the correct time is added to ZVW; otherwise, the entry remains unchanged. The planning date is verified before any changes are made. The same input always leads to the same outcome, and every run generates a log 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.