Build an Onboarding Tracker That Drives Your Flows
A SharePoint tracker and five Power Automate flows that turn one new-hire row into per-step status, tasks, reminders, and failure alerts.
Use this brief to create the first safe version yourself, or paste the handoff into ChatGPT, Claude, Codex, Cursor, or another builder.
Ready to use this Blueprint?
The AI prompt checks connectors, limits, permissions, and failure paths first.
View build detailsOutput, tool, checks
You will create
V1 builds an onboarding tracker in SharePoint Lists and Power Automate for an HR coordinator that takes one new-hire row, creates one step row per onboarding task, and shows a per-hire status board with automated email, Planner task, overdue reminder, and failed-step alert flows.
Use it to
Build an automation
Included
Scope, inputs, and proof checks
Create a trigger/action workflow with retries, logs, and approval gates.
Reviewed by Mark JonesAt a glance
The shortest useful answer to what you will create, who it helps, why it matters, and how V1 proves it works.
What you are building
V1 builds an onboarding tracker in SharePoint Lists and Power Automate for an HR coordinator that takes one new-hire row, creates one step row per onboarding task, and shows a per-hire status board with automated email, Planner task, overdue reminder, and failed-step alert flows.
Who it helps
An HR coordinator or operations lead in a Microsoft 365 company who can build simple cloud flows but does not want onboarding to become a custom app project.
Problem it removes
The coordinator can picture the checklist, owners, and apps, but the current checklist does not give Power Automate one stable tracker to read from, update, and recover when a step fails.
V1 proof
A fictional hire is added, the spawner creates step rows, one email step reaches done, one Planner task step reaches done, one manual task remains pending, and one overdue pending task fires a visible reminder.
Show extra contextOpenClose
Working title
Build an Onboarding Tracker That Drives Your Flows
Why this exists
Multi-owner onboarding becomes unreliable when every flow tries to remember the process on its own instead of reading from a shared step tracker.
Not in V1
Leaver or mover processes, IT provisioning execution, HRIS integration, Power BI reporting, Forms intake, premium connectors, Dataverse, custom Power Apps screens, adaptive-card approvals, AI Builder, or automated access changes in Entra ID.
Naming note
This is a descriptive working title, not a final brand. Do not rename it without checking domain, trademark, competitor, and Space naming fit.
Build Guide
Open one section at a time, then copy the part you need.
Product Intent
Defines the user, painful moment, V1 input, output, first proof, proof boundary, and not-V1 scope.
Blueprint Sources
Sources used in this Blueprint
Reference material used during the research and import process. Treat implementation details as assumptions until tested in your own environment.
Blueprint published by Collab365 Spaces, reviewed by Mark Jones on . Cite as "Build an Onboarding Tracker That Drives Your Flows", Collab365 Spaces. 16 sources referenced.