HR Operations Automation: One Flow for Onboarding, One for Check-Ins
Onboarding was a chain of manual handoffs, and a missed step surfaced on day one. We built a single-form onboarding flow and a cadence-driven check-in process with an access-controlled record.
- Service
- Business Transformation
- Industry
- Professional Services & Staffing
- Region
- United States
- Engagement
- SES (specialist engineers)
Outcomes
- One-form onboarding
- Check-ins on cadence
- Role-controlled HR records
Stack
Power Automate · Microsoft Forms · E-signature · Teams adaptive cards · SharePoint
Written byOriental Nippon Team
A US staffing and recruitment business ran two people-processes that both depended on someone remembering to act: bringing a new hire on board, and holding regular one-to-one check-ins between managers and their reports.
Onboarding was a chain of manual handoffs between HR, IT and the new hire. Check-ins happened when someone remembered, and what was said was not recorded anywhere central.
The problem
Onboarding
- Separate handoffs. Offer letters, policy documents, IT accounts and equipment, with nothing tracking them end to end.
- First-day surprises. A missed step showed up on the new hire's first day, the worst possible time.
- Filing by hand. Compliance retention depended on someone saving the right document in the right place.
Check-ins
- No cadence. Conversations happened irregularly.
- Unstructured feedback. Hard to compare or act on.
- No secure record. Nothing central or access-controlled.
| Before | After | |
|---|---|---|
| Onboarding trigger | Emails and reminders | One form starts the whole flow |
| Offer and policies | Sent manually | E-signature, chained automatically |
| Check-in cadence | Irregular | Scheduled |
| Performance records | Scattered | SharePoint, role-level access |
What we built
An onboarding workflow
One Microsoft Form starts it: tailored offer letter for e-signature, policy documents chained behind it, IT notified for accounts and equipment, everything archived to secure storage.
A check-in workflow
Schedules conversations at a set cadence, sends the self-evaluation form beforehand, delivers the result to the manager as a Teams adaptive card, and archives the final review with restricted access.
An access and retention model
Who may read a performance record, and for how long it is kept.
The onboarding chain, from one form to a filed record:
Technology and the role it played
| Technology | Role in this project |
|---|---|
| Microsoft Forms | Starts onboarding and collects self-evaluations |
| Power Automate | Runs both workflows end to end |
| E-signature integration | Offer letters and policy acknowledgements |
| Teams adaptive cards | Delivers completed check-ins to managers |
| SharePoint | Archive with role-level access control |
How we delivered it
We decided who may see a performance record before automating the creation of any. Our SES specialists treated access control as the first design question, not the last.
- Map both processes. Including the handoffs that were failing, not just the documented steps.
- Design access and retention. Who sees what, for how long, and how that is evidenced.
- Build onboarding. Tested with real hires under supervision before running unattended.
- Build check-ins. Starting with one department.
- Extend. Department by department once the pattern held.
01Process mapping
2 wks
Both flows, including the failing handoffs
02Access and retention design
1–2 wks
Who sees what, for how long, evidenced how
03Onboarding workflow
3–4 wks
Form trigger, e-signature, document chain, IT notification, archiving
04Check-in workflow
3–4 wks
Scheduling, forms, manager delivery, restricted archiving
05Roll-out
2–3 wks
Department by department
Risks and how we handled them
| Risk | How we handled it |
|---|---|
| Sensitive records visible to the wrong people | Access and retention model designed before any automation |
| A broken step on a new hire's first day | Tested with real hires under supervision first |
| Uneven adoption across departments | Check-ins rolled out one department at a time |
Outcome
HR, IT and the new hire now stay in step through one flow instead of a chain of reminders. Check-ins happen on a cadence, with a documented, access-controlled record behind each one.
Performance records are sensitive. Automating their creation before deciding who may read them would have been the wrong order.
What the client keeps
- Workflow definitions
- Document templates
- The access and retention model, documented
- The archive structure
Sources and further reading
- Types of cards in Teams, Microsoft Learn
- Understanding permission levels in SharePoint, Microsoft Learn
- Power Automate documentation, Microsoft Learn
- Understanding employee onboarding, SHRM
Facing something similar? This is the kind of work our Enterprise & Digital Transformation team delivers every day. Talk to us about your stack.
