Automation library
>
Planning
>
Weekly call lists

Weekly call lists

Creates and distributes weekly call lists by region from the home care planner.

Overview

Every week, call lists per region are required for the clients in the selected week. This automation selects the week, processes the clients in batches, formats the lists by region, and moves the files to the planning location. The logs for each region are sent via email.

What has changed

  • Less work logging in, selecting the week, and distributing files
  • Call lists are created the same way every week
  • Reduced risk of human error

At a glance

SECTOR:
VVT
System:
Home care planner, Excel, SharePoint, email
RUNS:
Weekly, Tuesday at 02:00
Technique:
Rule-based

In één oogopslag

SECTOR:
VVT
Systeem:
Home care planner, Excel, SharePoint, email
RUNS:
Weekly, Tuesday at 02:00
Techniek:
Rule-based

Overzicht

Every week, call lists per region are required for the clients in the selected week. This automation selects the week, processes the clients in batches, formats the lists by region, and moves the files to the planning location. The logs for each region are sent via email.

Wat er verandert

  • Less work logging in, selecting the week, and distributing files
  • Call lists are created the same way every week
  • Reduced risk of human error

How it works.

Home care planner planning week
Batch 1 of 3done
Batch 2 of 3done
Batch 3 of 3running
Clients processed in batches
02:00 every Tuesday
Y
Yara formats
per region
Planning location call lists ready
Region North.xlsxplaced
Region South.xlsxplaced
Backup copiessaved
3 regions done · 0 errors
Each region gets its own log by email.

What it does per client

  1. Logs into the planner and selects the planning week
  2. Processes clients in batches
  3. Formats the call lists by region
  4. Checks if all batches are complete
  5. Moves the files to the planning location and creates backups
  6. Emails the logs by region

Rules

The planning week is retrieved from a setting or calculated, clients are processed in batches, and the final step only runs once the batch folder confirms that all batches are complete. Every run follows the same logic and is logged for review, leaving no room for guesswork.

Frequently asked questions.

Do we need to change our system?

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.

Who builds and maintains the automation?

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.

Can we see what it did?

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.

What happens if something goes wrong?

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.

Can it work for our process, even if it differs from this example?

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.

Process not found?

Don't see your process listed? Let us know. We'll start with an automation scan to see what can be automated.