A new hire’s first day depends on work that starts well before they arrive. HR needs complete hire details. IT needs equipment and access requirements. Payroll needs the right information. The hiring manager needs a plan for welcoming the employee.
Sano is a Business Operating System that connects organizational structure with everyday work. This illustrative example shows how Roles, Responsibilities, Workflows, and Active Work can support onboarding coordination.
Start with ownership
Identify the participating Teams and Roles, then connect each Role to its ongoing Responsibilities. HR might coordinate onboarding, IT might own access preparation, payroll might own payroll setup, and the hiring manager might own first-week readiness. These are example assignments: choose owners and decision-making authority that match your organization.
Build a repeatable workflow
Define the meaningful stages, responsible Roles, required information, completion requirements, and timing. A simple example could follow this path:
Confirm hire details — HR. Confirm the start date, role, manager, and location.
Prepare equipment and access — IT. Review the requirements, perform setup in the appropriate systems, and record completion.
Complete payroll preparation — Payroll. Complete payroll-related work in the payroll system and record readiness.
Prepare the first week — Hiring manager. Confirm introductions, initial expectations, training arrangements, and the welcome plan.
Review completion — HR. Check the agreed requirements and coordinate outstanding follow-up.
The sequence is illustrative. Configure the workflow around your organization’s process and the workflow behavior available in Sano.
Connect the workflow to active work
Use the defined workflow for an individual onboarding. Sano carries the process structure into execution through current-stage guidance, ownership, due dates, requirements, and progress visibility.
The workflow is the repeatable process. Active work represents the specific onboarding moving through it. That distinction helps teams reuse the process while keeping each new hire’s progress separate.
Support people and specialized systems
Sano coordinates operational ownership and execution. IT still provisions accounts in the appropriate systems, payroll still completes payroll setup, and managers still make the decisions their responsibilities require.
This example does not imply automatic account provisioning, payroll integration, document signing, or automated approval decisions. It illustrates how the work around those activities can be organized.
Keep sensitive employee records in your approved HR and payroll systems. Coordination does not require putting passwords, identity documents, or bank details into workflow notes.
Make handoffs clear
Agree on what information each stage needs before work reaches it. A useful handoff explains what is ready, what remains outstanding, and who owns the next action. If the start date changes or a prerequisite is missing, clarify who will coordinate the next decision.
For employees, clearer coordination can support a more organized welcome. For the people preparing it, clear ownership provides a stronger starting point for working independently.
Start with one process
Choose a common hiring scenario. Map its Roles, Responsibilities, workflow stages, and handoff requirements. Test with fictional data and review the example with the people who will use it. Refine the process as you learn where coordination becomes difficult.
Explore Sano for your organization
Explore the product, review plans, or request a demonstration to discuss how Sano could fit your onboarding process.