Tasks late
4
across 2 starter(s)
Started this quarter
5
12-month hiring shape
Starting soon
1
in the next 14 days
Needs your action
- 4 onboarding task(s) past their due date The oldest is "On-call shadowing arranged" for Ade Bakare, 19 day(s) late. Chase them
- 1 starting in the next two weeks The tasks that run before somebody arrives are the ones that get missed. See who
Live plans
All starters →| Starter | Day | Progress | Late |
|---|---|---|---|
| Priya Raman
Software Engineer |
in 6d |
1/19
|
1 |
| Tom Whitfield
Product Designer |
day 3 |
4/8
|
— |
| Ade Bakare
Software Engineer |
day 34 |
14/18
|
3 |
Overdue tasks
Export →| Task | Late |
|---|---|
| On-call shadowing arranged
Ade Bakare · Rosalind Cheng |
19d |
| 30-day check-in
Ade Bakare · The manager |
3d |
| Probation objectives agreed and written down
Ade Bakare · The manager |
3d |
| Order the laptop and second monitor
Priya Raman · IT |
1d |
Starters, last 12 months
0 in 2025-12Dec
1 in 2026-01Jan
2 in 2026-02Feb
1 in 2026-03Mar
0 in 2026-04Apr
1 in 2026-05May
2 in 2026-06Jun
1 in 2026-07Jul
1 in 2026-08Aug
2 in 2026-09Sep
1 in 2026-10Oct
2 in 2026-11Nov
Busiest month in this window: 2 starter(s).
Your AI can work the list
Onboardora speaks MCP at POST /mcp. Ask it what is late and it
reads the same derived dates this page does. A read-only key can answer that and
cannot change a thing; a full key can tick a task off and hand one to somebody else. Creating a
starter is deliberately not a tool — a plan built from the wrong checklist is worse than no plan.