A 30-60-90 day plan for every hire, ending in proof they're ready.
One reviewed plan per job role, copied for each new hire. A person is marked ready only when every gate has closed on real evidence, not on ticked boxes.
Onboarding that ends in a decision.
One plan per role, not per person
An AI agent drafts the template from your documents and training, with a reason for every gate. A person reviews and publishes it once.
Gates close only on evidence
A manager's sign-off, work a manager accepted, a passed understanding check or a passed practice conversation. Never on a tick.
Starts on its own
Import new hires with a job role and hire date and their plans start, with due dates counted from day one.
From job role to ready.
Define the role
The skills it needs and the level for each, with its 30-60-90 template beside it.
Each hire gets a copy
Due dates come from their hire date. Editing the template later never rewrites a plan already running.
Managers sign off
One queue of gates waiting on them. "Not yet" needs a reason and puts the plan at risk, visibly.
Recorded from the real app.
Checklists versus evidence.
| Typical onboarding checklist | Ascend | |
|---|---|---|
| What closes an item | Someone ticks it | Gates close only on a sign-off, reviewed work or a passed check |
| What finished means | Every box ticked | Every gate closed on strong evidence; no percentage decides it |
| Promotions | A new checklist, or the old one again | The new role's plan, with skills already proven marked as done |
| What audit can see | A completion date | An evidence pack per person, including what is still missing |
What buyers ask.
Does AI write a separate plan for every new hire?
Can people become ready without a sign-off?
What about promotions and role changes?
Where does the start date come from?
See it working on one of your own job roles.
A 30-minute call. Send two or three documents for one role, and watch Ascend turn them into an onboarding plan, training and a check that people understood it.