Automation library
>
Planning
>
Clean up planning cards

Clean up planning cards

Cleans up future planning cards per team according to set rules, or notifies the team via email.

Overview

Planning cards for future days require consistent handling for each team. This automation applies each team's specific rule—either deleting a card or sending the team a notification email—and only for teams that have reached their activation date. Administrators receive a full log of all actions taken.

What has changed

  • Planners spend less time manually cleaning up cards
  • Each team's rule is applied consistently every night
  • Every action is logged and traceable

At a glance

SECTOR:
VVT
System:
PUUR planning module, email
RUNS:
Daily at 01:00
Technique:
Rule-based

In één oogopslag

SECTOR:
VVT
Systeem:
PUUR planning module, email
RUNS:
Daily at 01:00
Techniek:
Rule-based

Overzicht

Planning cards for future days require consistent handling for each team. This automation applies each team's specific rule—either deleting a card or sending the team a notification email—and only for teams that have reached their activation date. Administrators receive a full log of all actions taken.

Wat er verandert

  • Planners spend less time manually cleaning up cards
  • Each team's rule is applied consistently every night
  • Every action is logged and traceable

How it works.

PUUR planning future tickets
Team Northdone
Team Eastdone
Team Westrunning
Routes and statuses loaded
01:00 every day
Y
Yara applies
the team rules
Per team rule cleaned up
Ticket 4812deleted
Ticket 4815deleted
Ticket 4820signal email
1 team skipped · not yet active
Team contacts get the ticket IDs and dates.

What it does per team

  1. Logs into PUUR and loads the teams to be processed
  2. Skips teams that have not yet reached their activation date
  3. Retrieves routes and planning statuses for the target dates
  4. Deletes cards or marks them for a notification email, per team rule
  5. Emails the team contact person with the relevant card IDs and dates
  6. Emails the consolidated log to the administrators

Rules

Each team has its own configuration rules: depending on these, a card is either deleted or the team receives a notification email. A team is only processed once its activation date has been reached. 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.