Transforming Onboarding with Workflow Automation

The client is a regional healthcare system delivering nationally recognized inpatient and outpatient care through its hospital and network of physician practices, urgent care centers, and imaging centers. Onboarding ran on paper, with no way to track forms as they moved from Human Resources to the Information Technology Department, and new staff members often waited up to 12 days before gaining full access to the hospital’s IT network and applications. i3solutions designed and delivered a paperless Workflow Automation System built on Microsoft SharePoint: electronic forms signed with legally binding IntelliSafe digital signatures, automatic routing to every required touch point, real-time visibility of each request’s status, and automated reminders for pending or overdue actions. The workflow automation behind it, and the systems integration that carries a new hire’s paperwork from Human Resources through to IT provisioning, changed the timeline: instead of taking up to an average of 12 days, new employees’ information is almost immediately uploaded and all necessary system access is fully accessible in a matter of days.

The client, a regional healthcare system, delivers nationally recognized inpatient and outpatient care through its hospital and network of physician practices, urgent care centers, and imaging centers.  Their manual, paper-based system for onboarding new hires proved slow, error-prone, and provided no way to track paperwork as it moved from Human Resources to the Information Technology Department. As a result, new staff members often waited up to 12 days before gaining full access to the hospital’s IT network and applications.

Recognizing that technology could address these inefficiencies, the hospital’s administrators sought an automated solution to streamline the onboarding process, reduce errors, and eliminate misplaced documents. They wanted a system that would replace paper forms with digital ones, provide legally binding electronic signatures, allow staff to track approvals and requests in real time, and decrease the time needed to provision new hires with network resources. By implementing such a solution, the hospital hoped to expedite and standardize the entire hiring process, allowing newly onboarded professionals to engage fully in their roles as quickly as possible.

A new nurse sits through orientation without a working login because IT heard about the hire from a form that arrived late. During the wait described above, the paperwork moved between Human Resources and IT with no way to track it. Look for the lost days in the handoffs before looking inside any one department, and automate the handoff that every later step waits on first: once the HR record, not a form or a ticket, triggers account creation, the paperwork, the account and the day-one access set stop waiting on each other. Below are the three handoffs where the days go, in the order i3solutions recommends taking them, what Microsoft documents for each, and the two cases where that order is wrong.

The paperwork handoff between HR and IT

A signed offer that lives on paper or in an inbox is the first stall: no one can see which signature it is waiting on, so IT cannot plan the account. The fix in this case study was a SharePoint workflow: electronic forms and digital signatures, routed automatically to each approver, with reminders whenever an action sat pending or overdue. Where the forms already live in Microsoft 365, Microsoft documents the same routing pattern in Power Automate; its page “Get started with Power Automate approvals” (last updated April 29, 2026) says: “With the approvals capability in Power Automate, you can automate sign-off requests and combine human decision-making for workflows.” Speed is not the only return from this step. It leaves a complete, signed HR record on a known date, with the status of each signature visible in the workflow tracking, and the next step depends on that record.

The account itself: created from the HR record, not a ticket

When IT creates accounts from tickets, the account waits for the ticket and the ticket waits for someone to notice the hire. The alternative is to let the HR record trigger the account, and Microsoft documents two routes to it. For a cloud HR system, “Plan cloud HR application to Microsoft Entra user provisioning” (last updated July 24, 2025) says: “Microsoft Entra user provisioning service offers integration with cloud-based human resources (HR) applications. Examples of applications include Workday and SuccessFactors.” The same page sets the license: “you require a valid Microsoft Entra ID P1 or P2 license and a license for the cloud HR app, such as Workday or SuccessFactors.” For an HR system outside that list, “API-driven inbound provisioning concepts” (last updated August 20, 2026) says: “With API-driven inbound provisioning, the Microsoft Entra provisioning service now supports integration with any system of record.” The decision rule i3solutions applies: the HR system decides the route, and whichever route it is, the HR record replaces the ticket as the trigger for the account.

Day-one access: what is ready before the first shift

An account with no password, no license and no group memberships still leaves a new clinician waiting on the first day. Microsoft’s “What are lifecycle workflows?” (last updated April 14, 2026) describes the joiner as the point “When an individual enters the scope of needing access” and gives, as an example workflow, “sending a manager an email seven days before the value in the employeeHireDate attribute of new employees”. Its task reference, “Lifecycle Workflows tasks and definitions” (last updated July 29, 2026), lists tasks that include “Generate Temporary Access Pass and send via email to user’s manager”, “Request user access package assignment”, “Assign licenses to user”, “Add user to groups” and “Send onboarding reminder email”, and notes: “The user’s employee hire date is used as the start time for the Temporary Access Pass.” The overview page states: “Using this feature requires Microsoft Entra ID Governance or Microsoft Entra Suite licenses.” For the licensing and audit-evidence side of that decision, see Microsoft Entra ID Governance for Regulated Enterprises: Product Scope, Licensing, and Audit-Defensible Implementation.

When this order is wrong

Two situations reverse it. If hire dates and job codes reach the HR system late or wrong, automating account creation first provisions accounts on bad data, and an account with access no one approved is exactly what an access review is meant to find. In that case the paperwork and data-quality handoff comes first, and the HR record becomes the trigger only once it is right on the day it is entered. And if the delay sits inside one clinical application’s own access process, identity automation alone will not close it: the account can be ready on day one while that application still waits on its own request.

How long did a new hire wait for full system access before the automation?

New staff members often waited up to 12 days before gaining full access to the hospital’s IT network and applications. The onboarding process was manual and paper-based, and it gave nobody a way to track paperwork as it moved from Human Resources to the Information Technology Department.

How long does it take now?

Instead of taking up to an average of 12 days, new employees’ information is almost immediately uploaded and all necessary system access is fully accessible in a matter of days. That lets new employees be fully oriented and working on the first day of their employment.

What does the Workflow Automation System connect?

It is built on Microsoft SharePoint and routes digital forms automatically to every required touch point in the approval chain, from Human Resources through to the Information Technology Department that provisions network access. IntelliSafe and its IntelliSafe Vault provide the digital signatures, so staff create, sign, and securely store legally binding documents in a paperless environment, and SharePoint tracks each request and generates reminders for pending or overdue tasks.

Why does an onboarding delay matter this much in a hospital?

New hires cannot start patient care or other responsibilities until they have access to the IT network and applications those duties require. At the hospital that wait ran up to 12 days on the paper process; with digital workflows the hospital cut the average onboarding cycle from nearly two weeks to just a few days.

Can a new hospital employee sign in on their first day without IT handing over a password?

Yes, where the hospital licenses it. Microsoft documents a Lifecycle Workflows task that generates a Temporary Access Pass and sends it by email to the new employee’s manager, and Microsoft uses the employee hire date as the start time for that pass, so the task setting and the time in the hire date must leave it valid on the first day. Microsoft states that the feature requires Microsoft Entra ID Governance or Microsoft Entra Suite licenses. It depends on a correct hire date in the HR record, which is why the paperwork handoff comes first.

If your new hires wait days or weeks for system access while HR and IT trade tickets and paper forms, the delay usually sits in the handoffs rather than in any one department. A short conversation with the i3solutions team that built this onboarding workflow walks your current process, from signed offer through account provisioning, against what a fully digital and tracked version looks like at your size. You leave with a specific list of the handoffs worth automating first, what electronic signatures and approval routing involve, and the order the work would go in. That is also what you need if you are building the case internally. Start the conversation