It works while you sleep.
A schedule of background jobs handles the chores HR used to do by hand: absent detection, auto check-out, long-absence escalation, leave accrual and year-end rollover, alert rules, morning digests, celebration emails, people-ops reminders and subscription reminders. Every job is idempotent — safe to re-run.
- 20:00Absent detectionNo-shows marked Absent — weekends, holidays and approved leave skipped
- 21:00Long-absence escalationDay 1 → managers · day 3 → HR · day 5 → payroll flag
- 23:59Auto check-outOpen sessions closed at shift end
- 02:15Alert-rule scanConsecutive absences, monthly lates, attendance % thresholds
- 02:30Insights scanAnomalies and weekly absence-risk scores
- 07:00CelebrationsBirthday and work-anniversary emails
- 07:30People-opsProbation → active, joining reminders
- 08:00Morning digestPersonal email + Slack / Teams summary
All plans (jobs are enabled by the platform operator).
Automation, in practice.
Scheduled jobs that close sessions, mark absences, accrue leave and send digests.
Nightly attendance maintenance
20:00 absent detection, 21:00 long-absence escalation, 23:59 auto check-out.
Alert rules
Consecutive absences, late entries per month, attendance percentage below a threshold — each rule notifies chosen roles by email, in-app and Slack/Teams.
Leave lifecycle
Monthly accrual on the 1st, Monday/Friday pattern scan on the 2nd, carry-forward and expiry on 31 December.
Morning digest
A personal digest email at 08:00 plus a company summary posted to Slack or Teams.
People-ops reminders
Probation-to-active switches, joining reminders, birthday and work-anniversary emails.
Scheduled announcements and reports
Due announcements publish every five minutes; saved report templates email themselves on schedule.
Step by step.
What happens, in order, from the first action to the last — and where the system takes over from people.
- 1
Configure once
Shifts, holidays, leave policies and alert rules describe how your company works.
- 2
Schedulers enqueue
Cron schedulers hand each job to a queue at the right moment.
- 3
Workers run
Dedicated workers process jobs; every job is idempotent, so a retry never double-counts.
- 4
People are told
Results land as emails, in-app notifications and Slack/Teams messages.
Good to know
The boundaries of this feature, stated plainly.
- Each scheduler is switched on by the platform operator in production; the website lists the jobs the product ships with.
- Attendance jobs run against the company's configured time zone.
Works alongside
Each of these reads from the same record, so what happens here shows up there.
Where it fits
Teams that lean on automation the most.
Ready to get your team started?
Create your workspace in minutes, then choose Basic or Pro when you are ready.