HR & RECRUITING

Stalled provisioning task escalation before start date

Scans open provisioning tasks daily and escalates any that are overdue or unstarted as the start date approaches, nudging owners and alerting HR when a day-one blocker is at risk.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule scans open provisioning tasks
  • ActionPull open tasks with due dates from AsanaAsanaAsana
  • LogicClassify tasks by urgency and status
  • ActionComment reminders on at-risk Asana tasksAsanaAsana
  • OutputSlack-alert HR on critical day-one blockersSlack

What it does

Watches the provisioning tasks you already created and makes sure none silently stall. As a hire's start date gets closer, it escalates incomplete tasks with increasing urgency so day one is not derailed by a missing laptop or unactivated badge.

When to use it

Use it once you fan out provisioning work and need a safety net. It is for HR teams who have been burned by a task sitting untouched until the morning someone shows up.

How it works

  1. 1A daily schedule pulls all open provisioning tasks from Asana with their due dates and start-date tags.
  2. 2Logic classifies each task by days remaining and whether it is unstarted or overdue.
  3. 3Tasks more than five days out get a gentle owner reminder; tasks inside three days that are still open get flagged critical.
  4. 4It comments on each at-risk Asana task tagging the owner.
  5. 5For any critical day-one blocker it sends a direct Slack alert to the HR coordinator with the hire name and the missing item.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AsanaTasks, projects, milestones — everywhere.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.