An Onboarding Automation Checklist, From Accepted Offer to the End of Month One

Picture a new operations coordinator arriving at 9am on her first day. HR knew she was starting. IT got the request on Friday afternoon. Her laptop is still in a box at reception, nobody has created her email account, and her manager is in meetings until lunch. Every person involved did their part. Nobody owned the sequence.

Most onboarding problems look like this. The tasks are spread across HR, IT, payroll and the hiring manager, and nothing ties them to a single trigger. Onboarding automation fixes the coordination: one event (the accepted offer) starts every task, each task has an owner, and anything that stalls gets chased without someone having to notice. What it shouldn't do is take over the parts of onboarding that only work when a person does them.

This is the checklist we use as a starting point. Adjust it for your roles, locations and contract types.

When the offer is accepted

Start here, not on day one. Two or three weeks of notice is the difference between a laptop that's ready and a laptop in a box.

• Create the employee record from the candidate profile so nobody types the details in again
• Tell HR, IT and the hiring manager the start date, in the channel they actually read
• Assign an onboarding buddy and let them know
• Send the new hire a short note on what happens next and anything they need to do

The manager should also call or message the new hire before the start date. It takes ten minutes and settles a lot of nerves. The workflow can remind the manager to do it. It shouldn't send the message on their behalf.

Contracts and documents

• Generate the employment contract from the approved template and the agreed terms
• Send it for signature, with automatic reminders until it's signed
• Collect identity, right-to-work, bank and emergency contact details through a secure form
• Check that the required documents are complete and flag gaps to HR
• File everything in the employee record, visible only to the people who need it

Most contract errors at this stage are copying errors. The offer letter said a three-month notice period and the contract says one, because someone started from last year's template. Generating the contract from the same data as the approved offer removes that whole class of mistake. Collect only the personal data you need, and follow the data protection rules for the country the person will work in.

Accounts and equipment

• Raise IT requests for email, chat and the systems the role uses
• Order equipment from the role template, timed to arrive before the start date
• Arrange building access or remote access
• Two days before the start, confirm everything is done and escalate whatever isn't

Role templates save the most time here. A field technician, a software engineer and an HR coordinator each need a predictable set of systems and kit, and the workflow can request the whole set in one go.

The first week

• Book first-week sessions into the calendars of the new hire and everyone they'll meet
• Put a one-to-one with the manager on day one
• Assign required training and policy sign-offs with realistic deadlines
• Announce the new starter in the team's Slack or Microsoft Teams channel

The calendar can be automated. The conversation in that first one-to-one, about priorities, what good looks like at three months and how the role fits the team, can't.

Leave, attendance and timesheets

These tend to be forgotten until the first leave request or the first payroll run, when someone discovers the new hire has no leave balance at all.

• Create leave balances from the policy and start date, pro-rated where needed
• Assign the right working pattern, location and public holiday calendar
• Set up attendance tracking if it applies to the role
• Turn on timesheets and assign projects or cost codes
• Check approval chains so requests reach the right manager

When these records are live on day one, the new employee can use self-service straight away and the manager isn't caught out by missing data.

The first month

• Schedule check-ins at the end of week one, week two and month one
• Send the manager a short prompt before each one, with a few suggested questions
• Send the new hire an optional pulse survey of two or three questions
• Flag any onboarding tasks that are still open to HR
• Close the onboarding workflow and hand over to everyday HR processes

The workflow makes sure the check-ins happen. The manager makes them worth having.

What usually goes wrong

Starting on day one is the most common mistake. The second is using one checklist for everyone. A contractor in another country and a full-time hire at head office need different steps, so build templates with conditional steps rather than one long list. Every automated task also needs a named owner for when it stalls; otherwise "the system" owns it and nobody chases. And don't automate the welcome. A templated note signed "HR Team" isn't the same as a message from the person you'll be working for.

Onboarding should have a clear end, too. Without one, tasks linger and nobody can say whether a person is still onboarding in month four.

Checking whether it works

You don't need a dashboard to start. After each group of new hires, ask four questions. Were accounts and equipment ready on day one? How many tasks did someone have to chase? Did the first-week sessions happen as planned? What did new hires say about clarity and help in their check-ins? Change the templates based on the answers.

Onboarding goes much more smoothly when candidate data flows straight in from hiring, and our end-to-end recruitment automation guide covers that hand-off. In DataPoint HR, onboarding, contracts, leave, attendance and timesheets sit in the same system as recruitment, with notifications through Slack, Microsoft Teams, Gmail and Outlook. You can look at the HRMS or at our approach to employee lifecycle automation. If your onboarding runs across several separate systems, our introduction to AI workflow automation explains how they can be connected.