Automation
How do we get a new starter working on their first day?
By Paul Meakin7 min read

Why does a new starter spend the first week waiting?
Because nobody started the setup until they walked in. The laptop is still in its box. The email account exists, but the password went to a manager who is on holiday. The shared drive needs someone to add them, and that someone is in meetings until the afternoon. The training is whoever has time, and nobody does.
None of this is hard. It is stored in one head, usually the office manager's or the owner's, and it happens in whatever order that head remembers it. When that person is off, the new starter reads the staff handbook twice and waits.
A first day like that costs more than a lost day. It shows the new person how the business really runs. First impressions include the login screen.
What has to be ready on the first day?
Two kinds of thing: what the law expects you to hand over, and what the person needs to do the job.
The legal part is short, but it has a deadline. GOV.UK's guide to the written statement of employment particulars says an employer must give employees and workers a document stating the main conditions of employment when they start work. It is precise about timing. The employer must provide the principal statement on the first day of employment and the wider written statement within 2 months of the start of employment. If that document is written from scratch for every starter, it is the first thing to turn into a template.
The working part is accounts and access. The NCSC's guidance on identity and access management says your account management process should include a joiners, movers and leavers policy, so access can be revoked when no longer needed, or changed for movers.
The practical version of that is a list. Write down, by role, what a new person in that role gets. A list that says "sales: email, the sales shared drive, the customer database, the price list" means nobody has to remember it on a Monday morning.
Why not set the account up on the morning they start?
Because the account is where everything else hangs, and it is not always instant. Google's guide to managing users with the Directory API says that if the Google Account has purchased mail licences, a new user account is automatically assigned a mailbox, and that this assignment may take a few minutes to be completed and activated.
A few minutes is nothing on its own. A few minutes with the person sitting beside you, and the groups, the shared drives and every tool outside Google still to add, is how the first morning disappears.
Do not hand them a shared office login in the meantime. Nobody can tell who did what, and when one person leaves, everybody's password has to change.
Where do people get this wrong?
Starting late. The account, the equipment and the paperwork all begin when the person arrives, so the waiting is built in.
Copying a colleague's access. "Give them whatever their predecessor had" is quick, and it hands the new person everything that account picked up over the years, including access nobody needs any more. The NCSC tells organisations to review user accounts and systems for unnecessary privileges on a regular basis. Copying is how those privileges spread.
Keeping the checklist in a person rather than a document. If the steps live only in the office manager's head, the process stops whenever they take a week off.
And forgetting the other end. A starter process with no leaver process means accounts pile up for people who left long ago, some of them still able to open company files.
What does a starter checklist that runs itself look like?
It starts with one form. The manager fills it in once, when the offer is accepted: name, role, start date, line manager and a personal email address for the account details. Everything else follows from that.
In Google Workspace, Apps Script can pick the form up. Google's guide to installable triggers says an installable form submit trigger runs when a user responds to a form. From there, the Admin SDK Directory service allows administrators of Google Workspace domains to manage devices, groups, users, and other entities. Google's own samples include adding a new user and adding a user to an existing group. So a script can create the account, put the person in the groups for their role and send the rest of the checklist to whoever owns each remaining step.
| Step | Started by | Owner | Ready by |
|---|---|---|---|
| Account created | The form | The script | Well before the first day |
| Added to role groups and shared drives | The form | The script | At the same time |
| Written statement prepared from the template | The form | HR or the owner | The first day |
| Equipment ordered and set up | A checklist task | Office manager | Before the first day |
| Training booked | A checklist task | Line manager | The first week |
Groups are what make this manageable. Grant access to a group for each role rather than to each person, and adding someone to the group gives them the lot. Moving roles then becomes a change of group, which covers the movers part of the NCSC's policy as well.
Two warnings. The same triggers guide says installable triggers always run under the account of the person who created them, so build this on an account the business controls. And keep a person approving the request before the script acts. The form should come from a named manager, not from anyone who happens to have the link.
We build this as process automation and, for the Google side, in our Google Apps Script service.
What should happen when someone leaves?
The same list, run backwards, on their last day rather than some weeks later.
Close the access first. The NCSC's point is that access should be revoked when no longer needed, and after someone's last day it is not needed. Block the sign in, then deal with the files.
Move their files before the account goes. Google's Data Transfer API describes a transfer resource that represents the transfer of the ownership of user data between users, which is the step a leaver script calls. Moving ownership is not the same as checking who can open those files, so look at what the leaver shared outside the business as well. Our post on sorting out a messy Google Drive covers that check.
Do not rush the delete. The same Directory API guide says the deleted user can no longer sign in, and that a user deleted in the last 20 days must meet certain conditions before the account can be restored. It also notes that only an account's super administrator can undelete a user account. Delete in a hurry and getting anything back is neither quick nor certain.
And look beyond Google. The NCSC says policies should cover wherever your organisational identities can be used, including the online services staff can create an account on with their work email address. Each of those is another account to close. Where single sign on is available, the NCSC notes it can help revoke access along with someone's work account when they leave the organisation.
When is this not the answer?
When you take on one person every couple of years. A printed checklist and an hour the week before will do, and automating it would cost more than it saves.
Questions about the contract itself are another matter. What goes in the written statement, notice periods and probation terms belong with an HR adviser or an employment solicitor. A template saves typing. It does not make the content right.
When nobody in the business holds the admin rights. The principle still holds, but the first job is getting the business control of its own admin accounts, wherever they sit.
Someone who left on bad terms and may still have access is not a process question either. Block the sign in now, then check what they could reach.
Where do you start?
Write down, for each role, every account, group and folder a new person needs. Then write the leaver version beside it. If you cannot finish that list in an hour, that tells you something.
If the list is long, or half of it lives in someone's head, tell us what's stuck and we'll map the quickest fix. We will tell you straight whether it needs a checklist, a short script or something bigger. Time to talk yet?
Common questions
How far ahead should we set up a new starter's account?
As soon as the offer is accepted and the start date is fixed. The mailbox itself may only take a few minutes, but the groups, shared drives and tools outside Google that hang off the account take longer.
Can we just copy an existing employee's access?
It is quick, but it copies everything that account has built up. Start from the list for the role instead, and review access regularly, as the NCSC recommends.
Should we delete a leaver's account straight away?
Block the sign in first and move their files. Google says a user deleted in the last 20 days can only be restored if certain conditions are met, and only by a super administrator, so a hasty delete is hard to undo.
Does a script that creates accounts need any special setup?
Yes. Google describes the Admin SDK Directory service as an advanced service that has to be enabled in Apps Script and on your domain, and it is for Google Workspace administrators. Run it from an account the business controls.
Sources
- Employment contracts: written statement of employment particulars, GOV.UK
- 10 Steps to Cyber Security: identity and access management, NCSC
- Installable triggers, Apps Script, Google for Developers
- Admin SDK Directory Service, Apps Script, Google for Developers
- Manage user accounts, Directory API, Google for Developers
- REST resource: transfers, Data Transfer API, Google for Developers
Paul Meakin, Founder
Twenty years of fixing businesses from the inside, eighteen of them in recruitment from consultant to national operations, before building the automation, web applications and compliance systems Staxxd runs today.
More about Paul