An employee arriving with no user account, no permissions and nobody assigned loses a week. What to build once so that day one happens by itself.
Key takeaways
- Most of what day one needs is known two weeks ahead, so it can be prepared.
- A fixed list matters more than a tool - the same list, every time.
- It should all start on the day the contract is signed, not the day they arrive.
- Every new employee needs a named buddy, not "the team".
- Offboarding is the same list in reverse, and that is what prevents open access.
In a small business onboarding is almost always improvised: somebody remembers to create a user account, somebody else looks for a spare laptop, and the new employee sits for two hours waiting. That is tolerable for one hire a year, and it accumulates into a lost working week across three - and above all it is the first impression the employee forms about how the business is run.
It starts at signature, not at arrival
Once the date is known the whole chain can run: create the user, order equipment, book the first week's meetings, and send the employee what they need to bring. There is no reason for any of it to happen on Sunday morning.
The one thing worth confirming before starting is that the date is firm. Full preparation for somebody who pushed their start by two weeks does no harm, but it does require somebody to remember to update it - so the date is best held in one place everything else derives from.
The list that gets created automatically
| What | When | Who |
|---|---|---|
| User and email | At signature | Whoever runs systems |
| Permissions by role | At signature | From a role template |
| Equipment | At signature | Purchasing |
| First-week meetings | At signature | The line manager |
| Onboarding documents | At signature | Whoever runs payroll |
| Access to core systems | The day before | Whoever runs systems |
The second row saves the most argument. Permissions from a role template - "a salesperson gets X, Y, Z" - remove the recurring question of what each person should have, and they also prevent the common state where a new employee gets a copy of an existing employee's permissions, including things they should never have received.
What the employee needs before day one
- Where to go and when, including parking and who to ask for.
- What to bring - documents, bank details, certificates.
- What the first week looks like, for at least the first two days.
- One name to contact with any question.
- What they are not expected to know yet - to lower the pressure.
That last point looks odd and is useful. A new employee assumes they need to understand everything immediately, and one sentence saying "in the first two weeks we do not expect you to handle X" changes how they start.
What almost always gets forgotten
Three things missing from standard lists that produce day-one frustration: access to shared folders rather than only email, being added to the internal groups and channels where the work actually happens, and permissions in third-party systems the business uses - a courier, invoicing software, a customer's system.
The third is the worst because it depends on an external party. Access requiring a request to a vendor can take days, and if it is requested on arrival day, the employee sits for a week unable to do the main part of their job.
So it is worth marking on the list what depends on an external party and starting with exactly those. It also connects directly to the connections-and-access list described in automation security for business owners - the same list serves both needs.
Day one: what actually matters
Not full training. A good first day is: meeting who does what, getting access that works, doing one small real task, and knowing what tomorrow holds. One real task - even a simple one - is worth more than a full day of introductions.
What ruins a first day is waiting. An employee sitting for an hour with no access draws a conclusion about the business, and that conclusion sticks. That is why the whole list above happens beforehand rather than on the day.
Two weeks in: what to check
Onboarding is judged successful not on day one but after two weeks, and it is worth having a fixed checkpoint. Three questions for the manager and three for the employee, in a fifteen-minute conversation.
For the manager: is the employee doing what they should be at this stage, what is still missing, and what was not ready in time. For the employee: what was most confusing, what was missing on day one, and who they actually go to with a question.
That last question usually reveals the gap between plan and reality. When it turns out the employee goes to somebody other than the assigned buddy, that is not a problem - it is an indication that the right buddy is a different person, and the list is worth updating for next time.
A buddy, not "the team"
Every new employee needs one named person responsible for the first two weeks: the one they ask the silly questions, and the one who checks at the end of each day how it went. Without a name the responsibility disperses and everyone assumes somebody else is asking.
It is also what produces the only feedback worth anything at this stage: what was unclear. A new employee sees your processes for the first time, and everything that confuses them confuses customers too - and that window closes after a month, once they have adapted.
What is worth automating, and what is not
Automate: creating users and permissions by role, sending the onboarding documents, creating the manager's tasks, and booking the meetings. These are identical for every hire.
Do not automate: the content of the training and the introductions. Automation that replaces a conversation produces an employee who can log in and does not know who to ask - and the logic of the training itself is in training your team on a new system.
Why is offboarding the same list?
Because every line on the onboarding list is an access that was opened, and therefore a line that has to be closed. Businesses that build an onboarding list and no offboarding list discover after two years that they have active accounts for people who left, the exposure described in automation security for business owners.
The simple approach is to build both together: the same table, two columns - opened and closed. When somebody leaves, you walk the column and mark it off. That takes ten minutes, and it also covers the connections and access nobody would have remembered unaided.
Sources
Frequently asked questions
Do you need an HR system for this?
Not in a small business. One list and a few simple automations cover most of what is needed up to a few dozen employees. A system becomes necessary once attendance, leave and complex payroll enter the picture.
What about an employee starting remotely?
The same list, with one material change: equipment and access must be ready the day before rather than on the day, because there is nobody at the next desk to solve a problem in five minutes.
How long should onboarding take?
Until the employee does their job without asking about the process itself. In simple roles that is a week, in complex ones a month - and what matters is that somebody checks at the end of the period rather than assuming.
Who owns this with no HR department?
The line manager, with a list. What does not work is responsibility belonging to "everyone", which is exactly why day one starts with no user account.
Keep reading
Related service
Business Automation
I build custom automations that remove repetitive work end to end.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.