Journey works for everyone who takes part in onboarding
Twelve roles, from the apprentice on a phone to the auditor sampling records. Find yours to see what gets in the way today, what Journey gives you, and two examples of it at work.
Office and hybrid new hires
Coordinators, analysts, engineers and contact-centre agents joining an office or a hybrid team.
What gets in the way
A welcome email, a Word checklist and messages from teams you haven’t met
Not knowing what’s due when, or who you’re waiting on
Sending a form and never hearing whether it arrived
What Journey gives you
Your whole journey in one place, grouped by stream, with due dates
Who each task is waiting on, and a question to the owner on any task
Forms in a private folder, with a reason and a Replace button if one comes back
ExampleDay six, and they know exactly what's next
A new marketing coordinator is in her second week. She has finished the first-week welcome tasks but has a policy to acknowledge, training to finish and an access request with IT.
Without Journey
Her tasks are spread across an HR email, a calendar invite from IT and a note from her manager. She can't tell whether IT has her access request or whether she's holding things up, so she asks her manager, who doesn't know either.
With Journey
My onboarding shows 9 of 22 tasks done, 1 in approval and 1 overdue, grouped by stream with progress for each. The access review task says it's waiting on Priya Sharma from IT. She asks Priya a question on the task and sees the answer under Updates; her due date doesn't change while she waits.
The new hire works from one plan and knows who each step is waiting on, so she spends her second week on her job rather than chasing status.
ExampleA returned form, fixed in two minutes
A new analyst uploads a scan of his photo ID in week one. The expiry date is cut off.
Without Journey
People Ops emails him to send it again. The email sits unread, his file stays incomplete, and payroll set-up waits on it.
With Journey
People Ops returns the file with a reason. My documents shows it as Returned with the quote “The expiry date is cut off. Upload a scan that shows the whole card,” and a Replace button. The new file goes back into his private folder, which only he, his manager and People Ops can see.
Forms are collected once, into a secured folder, with the reason for any return in the same place as the fix.
Field and frontline new hires
Technicians, apprentices and site crews with a phone and a Microsoft 365 account, but no company laptop.
What gets in the way
Safety orientation in a binder at the district office
Paper acknowledgements that never reach head office
Finding out a step is missing when you’re stopped at the site gate
What Journey gives you
The safety stream your location and job role need, assigned by rule
Your journey on a phone-sized screen
Paper acknowledgements recorded by your manager, on the record and with you told
ExampleThe right safety stream, without anyone choosing it
Twelve apprentice line technicians start at the Edmonton district office on the same Monday in April.
Without Journey
Someone in People Ops has to remember which of the twelve need field safety orientation, PPE fitting and a competency sign-off. Last spring two were missed until a supervisor noticed.
With Journey
An assignment rule (Location = Edmonton, assign Site Safety) adds the Site Safety stream to each journey when their Entra ID profile matches. Each apprentice sees Site Safety alongside Company Welcome, IT & Security and HR & Policies, with due dates counted from their start date.
Field-specific onboarding is assigned by rule, so nobody depends on memory for the steps that keep people safe.
ExampleA paper acknowledgement that still counts
A field technician acknowledges the health and safety policy on paper during site induction because she doesn't have a laptop and her phone sign-in isn't set up yet.
Without Journey
The paper form goes in the district office binder. Head office can't see it, so she shows as unsigned in every report, and the audit sample can't find it.
With Journey
Her manager opens her journey from My team and records a paper acknowledgement of the Health & Safety Policy with the scanned form attached. Journey keeps who recorded it, when and why, and tells her it was recorded.
Sign-off from people who can't sign in is still on the record, with the scan and the name of the person who recorded it.
Line managers
Supervisors, team leads and hiring managers with direct reports in Entra ID.
What gets in the way
Finding out someone is behind when they tell you
Approvals for probation and competency arriving as email attachments
New hires with no onboarding plan until someone notices
What Journey gives you
Every direct report’s progress, with overdue items flagged
Remind, extend a due date or record a task, on the record
Approvals with the evidence in front of you, and a colleague to cover while you’re away
Assign a journey to someone who doesn’t have one yet
ExampleThree people behind, seen on Monday morning
A commercial team manager has four people in onboarding, one starting next week and two more with hire dates set in Entra ID but no journey yet.
Without Journey
He tracks them from memory and his inbox. He doesn't know that one is two tasks overdue on site safety, and nobody has told him the two new hires have no onboarding plan.
With Journey
My team lists his direct reports from the Entra ID manager attribute, each with progress, overdue and in-approval counts. He sees Aisha with 2 overdue, reminds her from her journey, extends one due date, and uses Assign a journey for Jordan, who has a hire date but no journey yet. Journey tells each person what he did.
Managers see who's behind before it becomes a problem, and every action they take for someone is on the record and visible to that person.
ExampleA competency sign-off with the evidence in front of him
A field technician has finished her site induction and two supervised visits and submits her safety competency sign-off.
Without Journey
Today it's a paper form signed by the supervisor and posted to the safety office, which signs it weeks later. The dates rarely line up with when she actually started working alone.
With Journey
The sign-off arrives in David's Approvals with what Aisha wrote (induction date, PPE check, supervised visits). The approval shows level 1 is the manager, from Entra ID, and level 2 is the Safety Officers approver list. He approves with a comment; Journey checks before the decision and passes it to level 2.
Multi-level approvals follow the org chart, carry the joiner's own evidence, and keep a dated trail of each decision.
Department heads and second-level approvers
Directors, district managers and senior managers who approve at the second level.
What gets in the way
Probation reviews forwarded after the probation date
Approvals that wait while you’re on holiday
What Journey gives you
Only the levels routed to you, never two levels of one item or your own
Hand your approvals to a colleague while you’re away
Reports filtered to your own people
ExampleApprovals keep moving while the director is away
A district operations manager is away for two weeks during the spring intake, when six probation and competency sign-offs are due.
Without Journey
The approvals sit in his inbox. Supervisors chase People Ops, People Ops chases him, and two probation dates pass without a decision on record.
With Journey
Before he leaves, he uses Away? Hand over your approvals to name a colleague. Approvals routed to him go to the colleague while he's away, with the hand-over on the record. Journey still stops anyone deciding two levels of one item, or their own.
Approvals don't stall on one person's calendar, and the record shows who decided and on whose behalf.
ExampleA probation sign-off with a clear trail
A new hire's three-month probation objectives need sign-off by her manager and then the department head.
Without Journey
The probation form is a Word document emailed between three people. Nobody can say which version was approved or when, and HR files whichever one arrives last.
With Journey
Probation objectives agreed is an approval sign-off task in the HR & Policies stream with two levels: the Entra ID manager, then the department head. Each level sees what the joiner wrote, approves or returns it with a comment, and the item shows where it is: waiting now, next, or decided.
Each level decides once, in order, and HR has a dated record without collecting emails.
The teams that own a part of onboarding
People Ops, IT, safety, facilities and each department own a stream of tasks.
People Ops and onboarding administrators
The HR or People Operations team who design onboarding, assign journeys and check the paperwork.
What gets in the way
Rebuilding the checklist for every hire
Emailing five teams to say someone is starting
Chasing forms one by one and building reports by hand
What Journey gives you
Streams and task collections built once, with due days and approval routes
Rules and group assignment, with a check that names who’s left out
Documents to check, with Accept and Return
Every change shown, with Undo, and an audit log
ExampleBuild a stream once, assign it by rule
People Ops is redesigning onboarding before the spring intake of 60 field and office hires.
Without Journey
Each hire gets a copied checklist that someone edits by hand. Every change to the process has to be made in a dozen places, and the copies drift.
With Journey
In the Management console, People Ops creates the HR & Policies stream with its audience and two approval levels, builds its task collection (forms to upload, policies to acknowledge, the benefits guide to read, probation objectives to approve) with due days counted from the start date, and sets rules so the right streams are assigned automatically. Changes apply to existing journeys straight away; new tasks go to new journeys.
Onboarding is designed once and assigned the same way every time, and changing the process is one edit.
ExampleAssign a whole intake, and see who's left out
Sixty people start in April. Most of them are already in an Entra ID group for the spring intake.
Without Journey
Assigning onboarding one by one takes a day, and People Ops only finds out who was missed when a manager asks.
With Journey
People Ops assigns a journey to the Microsoft 365 group. Before anything is created, Journey's check names each person who will get a journey and who is left out (for example, someone who already has one). Afterwards, Documents to check lists every upload waiting for review, with Accept and Return.
A whole intake is assigned in one step, with the exceptions named before it runs, not discovered later.
IT service desk and identity team
The team who prepare laptops and accounts, and the security lead who reviews access.
What gets in the way
Hearing about new hires from a late ticket, or not at all
Access reviews by email, missing what the new hire actually needs
What Journey gives you
Every new hire against every IT task in one matrix
Laptop and account tasks in Tasks for you as soon as a journey is assigned
Access reviews in your own approvals queue, with what the new hire wrote
ExampleThe laptop is ready on day one
A remote marketing designer starts on Monday. The laptop has to be imaged, licensed and shipped by Friday.
Without Journey
The service desk heard about her from a ticket People Ops raised two days before her start date. The laptop arrives on Wednesday of week one.
With Journey
Laptop and accounts ready is the first task in the IT & Security stream, due on day 0 and owned by the stream owner's team. It appears in IT's Tasks for you as soon as her journey is assigned, which a rule does when she's added to Entra ID, often weeks ahead. The completion matrix shows her row as 0% with the task open.
IT sees new hires as soon as they're assigned, not when someone remembers to raise a ticket.
ExampleAn access review with the joiner's own words
A new coordinator can't open a project workspace and asks whether to include it in her access review.
Without Journey
The question goes to a shared mailbox. The access review is approved without it, and she raises a separate ticket a week later.
With Journey
She asks the question on the Access review confirmation task. It appears in Priya's Questions; Priya answers, and the joiner sees the answer on the task and under Updates. When the review arrives in Priya's Approvals, it shows what the joiner wrote, so she approves the right access once.
Questions and approvals stay on the task they're about, and IT approves access with the joiner's context in front of them.
Health and safety officers
Safety advisers and officers who own field orientation, PPE and competency sign-off.
What gets in the way
A spreadsheet filled in from paper forms posted by district offices
Competency sign-offs approved weeks after the fact
What Journey gives you
The Site Safety stream, assigned by location and job role
Every new field worker against every safety task
Competency sign-offs at your level, after the manager’s, with dates on record
ExampleEvery new field worker, every safety task, one screen
Before the safety certification audit, the safety officer needs to show which new field workers have completed orientation, PPE and competency sign-off.
Without Journey
She spends three days reconciling district binders against the HR new-hire list, and still can't vouch for the dates.
With Journey
The stream monitor's matrix for Site Safety shows each assigned worker against each task, with complete, in progress, awaiting approval, overdue and not-yet-available marked. Overdue items are listed under the matrix. Reports filter the same records by location and start date, and the CSV export lists the filters it used.
Safety completion is visible live, by person and task, without reconciling paper.
ExampleThe second level of a competency sign-off
A field technician's manager has approved her competency sign-off. Safety has to approve it before she works without supervision.
Without Journey
The paper form waits in the safety office in-tray. She keeps working supervised, or worse, unsupervised without a record.
With Journey
Once the manager approves level 1, the sign-off moves to level 2, the Safety Officers approver list, and appears in each officer's Approvals with what the technician wrote and the manager's comment. One officer decides; the trail shows both levels with dates.
Competency decisions are made in order, by the right people, with the evidence and dates kept together.
Department and facilities stream owners
Department leads who own their team’s onboarding, and facilities staff who arrange desks and badges.
What gets in the way
Department onboarding kept in one manager’s notebook
Finding out about a new starter when they arrive at reception
What Journey gives you
A department stream every manager runs the same way
Tasks that link to your existing intranet pages
Your team’s tasks in advance, with start dates
ExampleDepartment onboarding that every manager runs the same way
The marketing director wants every new marketing hire to learn the brand guidelines, the tools and the team rituals in their first month.
Without Journey
Each marketing manager does it differently. Some hires are told about the brand guidelines in week one, some never.
With Journey
The Marketing Team stream, targeted at the Marketing department and the Marketing Team group, adds four tasks to each new marketing hire's journey, including acknowledging the brand guidelines (v2.4). The director edits the collection in My streams; tasks link to the existing intranet pages, so nothing is copied.
Department onboarding is consistent and owned by the department, without HR rebuilding it.
ExampleFacilities knows before the badge is needed
Fourteen people start at head office in the same fortnight.
Without Journey
Facilities hears about most of them from reception on the morning they arrive.
With Journey
A Workplace Ready task with the facilities team as its owner (desk, badge, parking) sits in the Company Welcome stream, due before day one. It appears in facilities' Tasks for you as each journey is assigned, with the start date, and the new hire sees it as waiting on facilities.
Teams outside HR see their onboarding work in advance, with dates, from the same plan.
People who govern, audit and run it
They answer for the program, test it, pay for it or keep it running.
HR director
The head of HR or People who owns the onboarding program and its results.
What gets in the way
Onboarding quality depends on which manager a new hire gets
Two days a month building a spreadsheet for the executive team
What Journey gives you
Completion by stream, manager, department, location and start date
A policy acknowledgement measure, CSV export and Power BI
ExampleA monthly onboarding report in two clicks
The HR director reports to the executive team each month on onboarding during the spring intake.
Without Journey
An HR adviser spends two days a month building a spreadsheet from email, the HR system and the IT queue, and the numbers are out of date by the meeting.
With Journey
Reports, filtered by start date and department, show journeys in scope, tasks complete, overdue, awaiting approval and policies acknowledged, with completion by stream and by person. The CSV export lists the filters used, and Power BI can read the same lists for an executive dashboard.
Onboarding reporting comes from the records themselves, current on the day it's read.
ExampleConsistent onboarding across six districts
Exit interviews show new hires in two districts had a much worse first month than the others.
Without Journey
Each district runs its own version of onboarding, and HR can't see what was done where.
With Journey
Every district uses the same streams, with location-specific streams assigned by rule. Reports filtered by location and manager show where tasks run overdue or approvals wait, so HR can see which districts need help.
HR can compare onboarding across locations and managers from the same data, and fix the process once.
Compliance, audit and legal
Compliance officers, internal auditors and legal counsel.
What gets in the way
Onboarding records spread across personnel files, binders and inboxes
No way to tell who recorded a task, or why
What Journey gives you
Every task in every stream, with who completed it and when
Paper records marked as such, with who recorded them
An audit log that can’t be edited, filtered and exported
ExampleDid every new hire finish orientation?
An internal auditor samples 25 people hired in the last year and asks whether each one finished orientation and the training their role required, and when.
Without Journey
HR pulls 25 personnel files and asks three districts for their binders. Some show a completion date, some an email, and three have nothing.
With Journey
Reports filter by start date, department and location. Each new hire’s journey shows every task in every stream with the date it was done and who did it, including tasks a manager recorded for them. Their policy acknowledgements sit alongside, by version. The audit log filters by person and date and exports.
Onboarding completion is a record for each person, ready for a sample in minutes.
ExampleWho recorded that, and why?
An auditor notices a field worker’s site induction recorded on the same day as three others, by the same manager.
Without Journey
With paper, there's no way to tell who recorded what, or whether the worker was there.
With Journey
The record shows it as recorded by the manager from a paper form, with the scan, the date and the reason. The audit log shows the action alongside every other change, and the worker was told it had been recorded.
Actions taken on someone's behalf are distinguishable from their own, and traceable to a person.
Executive sponsor
COOs, VPs of Operations and CEOs.
What gets in the way
Early turnover with no line of sight to onboarding
A choice between another vendor platform and more spreadsheets
What Journey gives you
Consistent onboarding on the Microsoft 365 you already own
Completion and acknowledgement figures from the records themselves
ExampleA business case without a new platform
The COO has been asked to approve onboarding software after the safety audit finding and a run of early resignations among apprentices.
Without Journey
The options on the table are a new vendor platform with its own login and data outside the tenant, or more spreadsheets.
With Journey
Journey runs on SharePoint, Entra ID and Power Automate in the utility's own tenant, using standard connectors and the Microsoft 365 licences it already has. The business case uses the organization's own hiring volume and early turnover, with Gallup's estimate that replacing an employee can cost one-half to two times their annual salary as the published reference.
The sponsor can approve better onboarding without a new platform, vendor contract for data or extra logins.
ExampleManagers who take part
The executive team agrees that managers should own their new hires' first 90 days.
Without Journey
Managers say they would, if they could see what their people had left to do.
With Journey
My team gives every manager their direct reports' progress on one screen, with overdue items flagged and approvals one click away, and reports show completion by manager.
Manager involvement becomes something the organization can see and support, by manager and team.
IT and Microsoft 365 administrators
Microsoft 365 owners and Power Platform administrators.
What gets in the way
Another vendor cloud to assess and another sign-in to support
Fragile, undocumented list-and-flow builds from past years
What Journey gives you
One deployment package, built for your organization and installed by iomer
Data on a dedicated SharePoint site, people and managers from Entra ID
Standard Power Automate connectors, under a service account you own
One setting for how people are told: in Journey, by email or in Teams
ExampleA security review IT can finish in a meeting
The Microsoft 365 owner has to approve Journey before People Ops can go ahead.
Without Journey
The last onboarding tool needed a vendor security questionnaire, a data processing agreement and a new SSO integration.
With Journey
The architecture view shows each screen's list or library, Entra ID through Microsoft Graph for people and managers, and Power Automate on standard connectors for approvals, reminders, welcome emails and rules. Data stays on a dedicated SharePoint site in the tenant; task records are secured to the joiner, their manager and stream owners, and uploads to a per-joiner folder.
IT reviews a SharePoint site and flows it already knows how to govern, rather than a new vendor.
ExampleNotifications that match what Journey says
IT installs the flows and People Ops wants reminders in Teams rather than email.
Without Journey
In past builds, flows sent duplicate emails after an outage, and nobody knew which messages had actually gone out.
With Journey
Journey always shows updates in the app. Three optional flows, built for the customer's site, deliver them by email or as a Teams message and send welcome emails before the start date. Each flow reads Journey's How people are told setting on every run, skips updates over 24 hours old so a backlog isn't sent, and records any failed delivery.
IT controls how people are told from one setting, and Journey never says a message was sent when it wasn't.
The examples are set in a regional utility of about 1,800 staff. The same patterns apply to construction and field services, municipalities, health organizations, financial services and higher education. Names, figures and screens are illustrative.
Bring the people in your organization who need this
Watch the 40-second tour, then book a walkthrough with someone from HR, a manager, an IT or safety lead and your Microsoft 365 owner. We’ll show each of them the part that matters to them.