Lyron
HR

Automated Employee Onboarding Workflows

Everything around a new starter hangs off one date: the first working day. The workflow schedules every task backwards from there – from the laptop with ten days of lead time to the account that only goes live at seven in the morning – and flags what is still open three days before.

Context

Onboarding rarely fails because of the checklist

Almost every company has an onboarding checklist. It sits in the HR folder as a Word file, it is two years old, and it gets opened in the week the new starter arrives. The problem is not that nobody knows what to do. The problem is that the items on that list have wildly different lead times and belong to different departments.

A laptop takes ten working days at the reseller, a mailbox takes ten minutes, a safety briefing needs a slot with someone who has customer appointments of their own. All of it hangs off a date only HR knows at first – and that date moves when the notice period at the previous employer turns out to be three months after all. Work the list two days ahead and half the items can no longer be done in time. Not through carelessness, but because the lead time ran out weeks ago.

On top of that, nobody owns the whole chain. HR hands over to IT, IT hands over to the department, the department hands over to the line manager. Every handover is an email that slides down the inbox, and nobody notices until Monday morning, when the access to the stock system is missing. So we do not build a prettier checklist. We build a countdown: every task scheduled backwards from the first working day, owned by a role, with an alert that arrives before the start rather than after it.

Use cases

Which staff changes are worth automating

We start with the change that happens most often at your company. Every further case later shares the same role profiles and the same scheduling logic.

Most common starting point

New hire with a confirmed start date

The most common case: contract signed, date fixed, and from then on device, account, training and induction all race the same clock.

Start dateRole profileAccountsEquipment

Field staff and apprentices

More hangs on the person than a laptop: protective equipment in the right size, tools, vehicle assignment, a briefing before the first job.

Protective kitToolsBriefingTime recording

Change of role or department

The case that most often stays half finished: new rights are granted, the old ones stay in place, and the reporting line changes in no system at all.

New roleRevoke rightsNew manager

Leavers and the last working day

The same countdown in reverse: block accounts instead of creating them, collect devices and keys, forward the mailbox for an agreed period.

Account blockDevice returnMailbox cover

Seasonal intakes and several starters at once

When six people start on the same March morning, a checklist turns into scheduling – including time-limited access with an expiry date.

Group intakeFixed termExpiry date

Mandatory training and evidence

Health and safety, data protection, hygiene or machine instruction: deadlines, reminders and a record you can produce when it matters.

DeadlineReminderRecordRefresher
Example

One run, three days before the first working day

Every task for one new starter, counted backwards from the first working day: what is done, what waits for an approval and what escalates today.

Role profile: field service engineer, Kassel site First working day: Monday 3 August · today: T-3
  1. T-14
    Signed contract comes back

    Start date, role and site are recorded in the HR system. From here every deadline counts backwards.

    Trigger · HR
    done
  2. T-12
    Equipment package ordered

    Laptop, work phone and tool case per role profile – ten working days of lead time at the supplier.

    IT · procurement
    done
  3. T-8
    Accounts created, still disabled

    Mailbox, groups and licence are ready. Activation is scheduled for the first working day.

    IT · directory
    done
  4. T-5
    Access to the stock system

    Beyond the standard profile. Who may see purchase prices is the manager's decision, not the workflow's.

    Line manager · open for 1 day
    approval
  5. T-3
    Supplier reports the laptop is late

    The workflow asks for a spare unit from stock today – not at eight on Monday, in front of an empty desk.

    Escalated to IT lead and manager
    open
  6. T-1
    Welcome note to the private address

    Start time, directions, first contact, shape of day one. The line manager receives the same summary.

    Automatic · email
    scheduled
  7. Day 1
    07:00 – accounts go live

    Mailbox, groups and time recording unlock. Keys and protective equipment are signed for.

    The countdown ends, the people part begins
    start
  8. T+3
    Mandatory briefings with a deadline

    Health and safety, data protection. The reminder repeats until the record is on file.

    Automatic · record to HR
    scheduled
  9. T+30
    Handover to the line manager

    Review conversation with a guide, plus whatever the countdown left open along the way.

    Meeting booked · the conversation is human
    human
done a person decides open, escalated scheduled

The line that matters is T-3. No workflow stops a device arriving late – but whether you hear about it three days ahead or on Monday morning decides the first impression.

Illustrative run, shortened: a role profile covers twelve to twenty tasks depending on the site. T is the first working day; the numbers are working days before and after it.

How it works

From start date to the meeting after 30 days

  • The start date becomes the trigger

    A confirmed start date in your HR system – or in a maintained list – starts the run. Every task is scheduled backwards from that day, not from the moment somebody opens the checklist.

  • The role profile sets the scope

    Each role has a package behind it: device type, groups, licences, keys, protective equipment, mandatory training. Somebody starting in field service gets a different set of tasks from somebody in accounts.

  • Tasks go to a role, not to a person

    IT receives its tasks where it already works – Planner, Jira or a ticket by email with a confirmation link. If somebody is away, the task stays with the role instead of sitting in a holiday mailbox.

  • Prepare accounts, activate them on day one

    Mailbox, groups and licences are created days ahead but stay disabled; activation is scheduled for the morning of the first working day. Anything beyond the standard profile goes to the line manager as an approval.

  • Escalate before day one, not after it

    Whatever is still open three days before the start is reported to the responsible lead, naming the specific missing item. After day one the run continues with training deadlines, a check-in and the end-of-probation meeting.

Impact

What changes day to day

Today

  • The checklist gets opened when the start date is already close
  • HR sends IT an email and hopes somebody picks it up
  • The laptop is ordered once the new colleague has arrived
  • Access to the core system is missing on the first morning
  • Nobody is quite sure whether the safety briefing happened

With a countdown

  • Every task carries a deadline counted from the first working day
  • IT gets the task in its own system instead of by email
  • The order goes out twelve days before the first working day
  • Accounts are prepared and unlock on the first morning
  • Missing records keep reminding until they are on file
Limits

Where a countdown is not the answer

Four points we raise before quoting – two of them are reasons to postpone the project or to leave it alone:

  • Below roughly one new starter a month it does not pay for itself. If you hire two or three people a year, you will not recover €1,490 in saved hours. An honestly maintained checklist with one clearly named owner is the better tool then, and we will say so in the intro call.
  • Role profiles have to be created first. If access rights are handed out today on the pattern of give her the same as Sarah, somebody has to decide what a role may do by default and what it may not. That work is organisational, not technical, and it costs your time rather than ours. We facilitate it and write down the result – we cannot take it off your hands.
  • Lead times stay lead times. The workflow orders earlier, reminds and escalates, but if the device is stuck at the reseller, it is not there. What changes is when you find out – and whether there is still time to arrange a loan unit.
  • Day one itself stays human work. The welcome, the tour, the introductions, a buddy for the first few weeks: software can schedule and remind, but it cannot stand in. If onboarding fails at your company because nobody has time for new colleagues, the workflow will not fix that. It will make it visible, which can be uncomfortable.
Systems

Fits your systems

PersonioBambooHRMicrosoft 365Entra IDMicrosoft TeamsPlannerGoogle WorkspaceJira Service Managementn8n
Scope and price

Scope and price

The entry price covers one role profile with the full countdown, from the equipment order to the meeting after 30 days. What moves the price, we say before the quote.

from €1,490 one-off
  • Connection to your HR system or a maintained list of starters
  • One role profile with tasks, deadlines and owners
  • A backwards-scheduled run from T-14 to T+30
  • Accounts, groups and licences in Microsoft 365 or Google Workspace
  • Tasks in Planner, Jira or by email with confirmation
  • Escalation of open items before the first working day
  • Documentation, handover session and 30 days of support

What increases the price

  • Several role profiles with different packages
  • An HR system without an open interface or with its own export route
  • Device and licence ordering through a procurement system
  • Leavers as a separate run with returns and blocking periods
  • Several sites with their own rules, keys or languages

Several role profiles with a leaver run and a connection to a procurement system typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.

All prices excl. VAT · operation and further development optionally via a support package

Included

What you get

  • A production onboarding run

    Set up from start date to the meeting after 30 days and signed off with a real new starter

  • A documented role profile

    Which role gets which device, groups and training – changeable later without us

  • Escalation rules before day one

    Who hears when that something is open, and which specific item is missing

  • Handover for HR and IT

    How a moved start date is handled and what happens when somebody cancels before joining

Questions & answers

Frequently asked questions about automated onboarding

Every task hangs off the start date rather than fixed calendar days. Change the date in the leading source and all open deadlines move with it, while completed steps stay completed. Orders already placed with a supplier cannot be pulled back by the workflow – it flags them for review. If the new starter cancels altogether, the run stops and the prepared accounts are removed again.
Created yes, active no. Mailbox, groups and permissions are prepared but disabled, and activation is scheduled for the morning of the first working day. That way everything is ready on day one without a usable account existing for days with no person behind it. Chargeable licences can be assigned only at activation if you prefer.
No. A maintained list in SharePoint or Excel works as a trigger, as long as there is exactly one source for start date and role. It becomes difficult when the date lives in three files and two of them disagree. We settle that question before building, not afterwards.
In the system it already works in: Planner, Jira Service Management, an internal ticket tool or an email with a confirmation link. Each task carries a due date and an owning role rather than a named person, so annual leave does not stall the run. We deliberately avoid one bulk email with all the items, because nobody feels responsible for those.
IT receives only name, role, site and start date – no contract details and no salary. The workflow logs the status of tasks, not the behaviour of employees. In companies with a works council we still recommend involving it early: systems that make people's tasks and deadlines visible are usually subject to co-determination in Germany. Allow a few weeks for that before the first run goes live.
Yes, as a countdown to the last working day. Instead of creating accounts it blocks them, requests devices and keys back and forwards the mailbox for an agreed period. We usually build the leaver run as a second step, because it reuses the same role profiles and is therefore considerably cheaper than the first one.

What is regularly missing on your first days?

In the free intro call we walk through your last new starter: which tasks came up, who owned them and which arrived too late. Afterwards you know whether a countdown pays off at your hiring volume or whether a good checklist is enough.

Book a free intro call
Practical guide

Where employee onboarding workflows creates value in everyday work

HR, IT, managers and new employees receive complete tasks, information and access at the right time.

Three concrete operating scenarios to compare with your own process.
01

Prepare before day one

Hardware, account, workplace and welcome information are initiated on time.

02

Coordinate tasks

HR, IT and the business team see their steps, deadlines and dependencies.

03

Make progress visible

Missing access or overdue tasks are escalated before the start date.

A strong fit when …

People-related tasks repeat, several teams are involved, and deadlines or access rights must be coordinated transparently.

  • You handle recurring onboarding tasks using repeatable rules.
  • The intake, target system and accountable business role can be named clearly.
  • Exceptions are allowed to remain visible and move to people deliberately.
Transparent potential estimate

Estimate time savings with your own volume

The calculator uses 15 minutes today and 4 minutes after automation as fixed example assumptions. It does not replace process analysis.

Illustrative estimate based on the visible assumptions — not a guarantee.

22Hours per month
264Hours per year
Additional measures after launch Completed tasks Cycle time Overdue steps
Frequently asked questions

What decision-makers should know before starting

How does employee onboarding workflows work in practice?
A signed employment contract or confirmed start date is recorded in the HR system. The workflow then validates the required data, runs approved steps and routes exceptions to the responsible person with context.
Which systems can be connected?
Typical integrations include Microsoft 365, HR-System, Entra ID, Teams, Planner. The decisive factors are a stable interface and clearly defined ownership of each data field, not a specific tool.
Which tasks deliberately stay with the team?
High-risk permissions, individual contract questions and personal support remain with authorised people.
How is the automation introduced?
HR, IT and the business team define required steps, owners and sensitive data fields together before a limited pilot starts. A tightly scoped first process typically takes 2–5 weeks; scope, interfaces and approvals determine the actual plan.
How can the benefit be measured?
Before implementation we record volume and current handling time. After launch we also compare Completed tasks, Cycle time, Overdue steps. The calculator on this page is a transparent estimate, not a promise.
Content reviewed on 26 July 2026 About Lyron AI