Onboarding Runner
Joiner and leaver checklists that record who did each step and when, with proof attached, ending in a sealed evidence pack.
What it does
- Two checklists ready to edit: standard onboarding (accounts, hardware, access, policy acknowledgements, first day) and standard offboarding (access revoked per system, hardware returned, data transferred, handover, exit interview).
- Each step can have an owner, a due date counted from the start or leaving date, and a requirement for an attached file before it can be ticked.
- A run applies a checklist to one person. Every step is marked done with a note, skipped with a reason, or annotated, and every action records who and when.
- Overdue steps are flagged on the home page.
- Export an evidence PDF at any time. When the last step is settled the run is sealed with a fingerprint over its facts, printed on the pack, so a copy in a folder can be checked against the record years later.
A person stays in control
Ticking a step is a statement that something was done, so only a signed-in person can do it. Automation can start a run and add notes; it can never tick a box.
For you as a consultant
The leaver record is the product. When a client is asked, months later, whether a departed employee's access was really revoked, the answer is a document rather than a memory. It is the kind of compliance and cyber-insurance evidence small businesses cannot otherwise produce.
Works with your systems
Start runs and read them from the API or MCP server; get a signed webhook or a Slack or Teams message when a step is completed, skipped or overdue, and a weekday morning digest of what is waiting on someone.
Not yet
- It does not create or close accounts in other systems. It records that a person did.
- Emailed reminders to step owners.