Home · Solutions · HR & people
Solution · HR & peopleOn day one everything waits ready: the account, the access, the equipment and the induction plan
Employee onboarding in a small firm
The robot receives a start date and sets off down the checklist: it creates the Microsoft 365 account and access, distributes deadlined tasks, watches check-ups and training, and on day one the new person receives a working set and a first-week plan. At a departure the same list runs in reverse, down to the last access.
Executive summary
Onboarding in a small firm is a list in the owner’s head: the account gets created on Tuesday, access on Wednesday, the check-ups “this week”, and the new person spends the first days on someone else’s login at half capacity.
The start date triggers the checklist: the account and access create themselves by role, tasks go to the right people with deadlines, check-ups and training carry reminders, and gaps escalate before the start date, not after it.
Day one makes a first impression instead of a first grind, nobody works on borrowed logins, and at a departure the access disappears down to the last item, the same day.
the checklist in SharePoint; Microsoft 365 accounts and access; deadlined tasks in Teams; check-up and training reminders
Business problem
Day one on somebody else’s login
A small firm’s hiring ends with a handshake and begins with chaos: by Monday the account must exist, access must be granted, equipment prepared, check-ups arranged, workplace training booked, and someone must be found to look after the new person. There is no list; there is the owner’s memory and the experience that “it always somehow worked out”.
It works out halfway. The account appears on Tuesday, drive access on Wednesday after two requests, the terminal on Friday. The new person, full of first-days energy, spends them waiting and working on a colleague’s login, which is both demotivating and simply untidy. The check-ups and trainings, remembered separately, can surface past their deadline, at the worst possible moment.
Each such induction also costs hours of whoever runs it: a dozen small tasks, each with a different person, each needing watching. At a few hires a year that is an invisible fractional job, and the outcome still depends on whether the week happened to be calm.
Departures are the mirror image, only more dangerous: the account stays active for weeks after the person leaves, drive and system access remains, the entry card lies in a drawer. Nobody does this out of bad will; the list that did not exist at the entrance exists even less at the exit.
How it works today
Below is what the work looks like before anything is automated.
- PersonA hire triggers a list in the owner’s head; every item sits with someone else
- WaitingThe account on Tuesday, access on Wednesday, equipment on Friday; the new person waits
- Risk of errorDays of work on a borrowed login: demotivating and untidy
- Risk of errorCheck-ups and training remembered separately; they can surface past the deadline
- PersonA dozen small tasks to watch at every hire
- Risk of errorAt a departure the access stays for weeks; the card lies in a drawer
Why the current process costs more than it appears
The bill that never shows up in a budget.
- First days spent waiting burn the new person’s enthusiasm and delay the moment she starts earning her keep.
- The hours of running each induction are a hidden fractional job of the owner or the office.
- A check-up or training past its date is a risk that surfaces at the worst moment.
- An active account after a departure is an open door nobody remembers.
Cost of inaction
The first two rows you can count after your last hire: how many hours the running took, and on which day the new person truly had the full set. The third row has no figure until it materialises; then it has them all.
The model assumes a firm on Microsoft 365, where the account and access can be created automatically by role; that is the typical situation and the shortest implementation path.
A model organisation with realistic proportions – the numbers exist so you can run the same maths on your own data; they are not a client result.
A services firm of 25 people: Microsoft 365, a team drive, two industry systems, several to a dozen hires and departures a year, inductions run by the owner and the office.
No onboarding list; every hire is an improvisation from memory; the full set tends to be ready Wednesday to Friday.
Check-ups and training watched in separate notes; slips have happened.
After the last departure, the former employee’s account stayed active for three weeks; nobody noticed.
Recruitment ends with an entry: role, start date, manager; the robot launches the role’s checklist: the Microsoft 365 account and groups create themselves, tasks (equipment, check-ups, training, a buddy) go to the right people with deadlines counted from the start date, gaps escalate two days before the start; on day one the new person receives a welcome email with the week’s plan; a departure launches the mirror list with access withdrawn the same day.
In the modelled case the full set is ready on the start date, and departures close access within hours. Model numbers, not the firm’s records.
Proposed solution
We start by writing the checklist that does not exist today: what must be ready for the start date, per role. The account, groups and licences, system access, equipment, check-ups, trainings, the first week’s buddy, the induction plan. Written once, the list is versioned and grows with the firm; a second, mirrored one we write for departures.
The hiring entry (role, start date, manager) sets the machine off: the robot creates the Microsoft 365 account with the right groups and licence; the human tasks, ordering equipment, arranging check-ups, booking training, go to the right people with deadlines counted backwards from the start date. The robot reminds, and whatever is unticked two days before the start escalates to the owner. On day one the new person logs into her own account and finds the week’s plan in her inbox.
A departure works the other way, and the same day: the account blocked, access withdrawn, the licence recovered, the equipment and card on a return list, the mailbox and files handed over by your rule. After every entry and exit a protocol remains: what, when, who ticked it. Nobody has to remember any more, because the list remembers.
UiPath Orchestrator: date-triggered checklists, the task queue, reminders, escalations and an audit trail; UiPath Integration Service connectors for Microsoft Teams, Outlook 365 and Microsoft Entra
Versioned role checklists for entries and exits, automatic accounts and access, deadlined tasks, pre-start escalations and protocols after every process
Accounts and groups in Microsoft 365 / Entra; checklists and protocols in SharePoint; tasks and reminders in Teams; industry systems per their interfaces
How the automated process works
- SystemA hire is an entry: role, start date, manager; the checklist sets off by itself
- AutomationThe Microsoft 365 account, groups and licence create themselves by role
- AutomationHuman tasks go to the right people with deadlines counted from the start date
- AutomationGaps escalate to the owner two days before the start, not after it
- PersonOn day one the new person logs into her own account and has the week’s plan
- SystemA departure launches the mirror list: access disappears the same day, with a protocol
Human-in-the-loop model
Automation handles
- Accounts, groups and licences by role, and watching the whole checklist
- Deadlined tasks, reminders and pre-start escalations
- The departures’ mirror list and both processes’ protocols
People decide
- The substantive induction: the conversations, the learning, the first week’s care
- The physical tasks on the list: equipment, check-ups, training; the list watches, a human does
- The role checklists and their changes as the firm changes
Before and after
Systems and integrations
The stack is short on purpose: one engine, one execution layer, one place where a person decides.
Inputs
- the hiring entry: role, start date, manager
- role checklists with tasks and deadlines
- the role catalogue in Microsoft 365 / Entra
- the departure notice
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- the account, groups and licences ready for the start date
- ticked tasks with history
- entry and exit protocols in SharePoint
Human touchpoints: tasks and reminders in Teams; pre-start escalations; a protocol after every process; a checklist review quarterly
Technologies used
date triggering, the task queue, reminders, a trail of every step
Aautomatic accounts, groups and licences by role
Atasks, reminders, escalations, the welcome email
Arole checklists, protocols and process history
Aaccess via their interfaces where they have them; otherwise a deadlined human task
BIllustrative economic model
Numbers you can check against your own data.
The model counts the hours and the ramp-up days; it does not count the risk closed at departures, which is the main reason firms adopt this process, or the new person’s first impression. Volumes belong to the scenario; your own numbers go into the calculator alongside.
Run the maths on your data
An illustrative estimate based on your inputs. It models freed capacity, not promised savings.
Business benefits
- Day one makes a first impression: everything works, the plan waits in the inbox
- Nobody works on borrowed logins; order from the first hour
- Check-ups and training carry deadlines and reminders instead of separate notes
- Departures close access the same day, down to the last item, with a protocol
- The owner stops being the checklist; welcoming the human remains
The management view
- Inductions stop depending on a calm week; they are the same at the third hire and the thirtieth
- Entry and exit protocols are order that shows at every audit and dispute
- A role checklist is the firm’s knowledge written down, which stays as people change
Board-level KPIs
the set ready on the start date · time from departure to access closure · tasks ticked before deadline · check-up and training slips · running hours per process
Security and governance
The automation has exactly the permissions it needs. Not one more.
- Access granted by role from the checklist, not discretionally; every grant has a record
- A departure withdraws access in mirror, down to the last item, with a protocol
- Personal data in the process limited to the necessary; HR documents stay in their places
- Escalations and protocols are visible to the owner and those he designates
- Data stays in your Microsoft 365 tenant; the robots run in the EU region of UiPath Automation Cloud
Why now
The labour market forgives weak first days no longer: the new person compares you with her last employer from Monday morning.
Systems and access multiply in every firm; granting and revoking by hand has stopped being safe.
Former employees’ access is now among the commonest incident sources in small firms; the mirror list costs pennies by comparison.
Relevant executive roles
Welcomes the human instead of running the list; sleeps calmly at departures
Gets deadlined tasks instead of remembering everything at once
Logs into her own account on day one and knows what the week holds
Common questions and objections
The process is priced not by the number of hires but by the cost of one bad one: burned enthusiasm, weeks of ramp-up, and open accounts at departures. The checklist works the same at three processes a year and at thirty, and its greatest value, order at departures, does not depend on scale at all.
Which is why the checklists are per role: reception, technician, office, each with its own set of access, equipment and training. A new role is a copy of the nearest one plus fifteen minutes of edits. The variety of roles is the argument for lists, not against them; it is precisely what memory cannot hold.
And those stay in the process as human tasks: with a deadline, a reminder and a box to tick. The robot automates what can be automated (Microsoft 365 usually in full) and watches the rest. The watching is worth more here than the clicking itself.
When this is not the right solution
- A three-person firm hiring once every two years: a sheet of paper and care suffice
- An environment with no central accounts (each system separate, no directory): first order in identity, then the automation
- Expecting the automation to do the substantive induction: the firm teaches, the list only secures the conditions
A question for the next management meeting
How many former employees’ accounts are active in our systems right now? Who knows the answer without checking?
Implementation approach
Scope without ambiguity, before anything is signed.
We deliver
- Role checklists for entries and exits, written and versioned
- Automatic accounts, groups and licences in Microsoft 365 by role
- Deadlined tasks, reminders and pre-start escalations
- The departures’ mirror list with same-day access withdrawal
- Process protocols and two supervised pilot runs
We need from you
- The role checklists written together in one meeting (two hours)
- Administrative permissions to Microsoft 365 for the robot
- The industry systems list and how access is granted in them
Stages
Discovery
How induction looks today, the recent slips, the systems and access
Checklists
Roles, tasks, deadlines, owners; the departures’ mirror list
Build
Automatic accounts, tasks, reminders, escalations, protocols
Pilot
The next two processes under supervision; checklist corrections
Go-live
Every entry and exit on the list; a review after the quarter
A quick win. Microsoft 365 accounts and access automate in full; the rest is writing down lists that should exist anyway.
Monday, 8:55: the new person waits at a desk with no computer. The owner hunts for whoever was to order the laptop. On Thursday it turns out the check-ups were not booked either.
Describe your last hire: what was ready on the start date, and what trickled in during the week. We return a checklist design for your roles and the list of what would create itself.
Check what your last first day looked likeThe neighbouring process usually has the same problem
Sick leave at 6:40, patients from 8:00, and the manager hunts for cover down a phone chain.
See the solution HR & peopleInstructor payouts without the spreadsheetThree rates, four contracts, hours from memory. Payday ends in a discussion every month.
See the solution Legal & complianceCompany deadlines watched: policies, inspections, check-upsThe autoclave, the extinguishers, the liability policy and staff check-ups expire in different calendars.
See the solutionIndustries where we deploy this most oftenSmall business & services