Coordinate employee onboarding

This example coordinates onboarding work across People Operations, IT, and the hiring manager while keeping sensitive information out of unnecessary context.

Outcome

For each new hire, the team wants to:

choose the correct onboarding path;
prepare a role-specific checklist;
assign owners and due dates;
identify blocked tasks;
give the hiring manager a clear status view.

Add the business context

Create a People Operations Project and add:

the onboarding handbook and role guides as Sources;
reviewed Knowledge pages for standard, manager, and contractor onboarding;
an Onboarding Cases table;
a Tasks table if individual tasks need structured updates.

Store only the information required for coordination. Do not upload identity documents, medical information, compensation details, or credentials to a general onboarding Project.

Prompt to try

Attach the relevant role guide and provide the non-sensitive case details:

Prepare an onboarding plan for a new Customer Success Manager starting on
September 14.

Use our onboarding Knowledge and return:
- the applicable onboarding path;
- tasks grouped by People Operations, IT, hiring manager, and new hire;
- an owner and due date for each task;
- dependencies and blocked tasks;
- policy citations for required steps;
- the questions we still need to answer.

Do not create tasks until I approve the plan.

Review the plan

Confirm that:

the correct employment type and role path were selected;
owners are current Workspace members;
dates account for task dependencies;
optional guidance is not presented as mandatory policy;
sensitive information is not copied into task descriptions.

After approval, create the onboarding case and task records.

Create a Process Skill

Generate Prepare an onboarding plan from the reviewed onboarding Knowledge. Include the questions Cromo must ask when employment type, location, role, or start date is missing.

Create the Workflow

Create a workflow named New hire onboarding.

When an approved Onboarding Case is created:
1. select the correct onboarding path;
2. create the approved task set with owners and due dates;
3. flag tasks whose owner is missing;
4. prepare a welcome checklist for the hiring manager;
5. produce a weekly summary of blocked and overdue tasks.

Do not send invitations or provision accounts automatically.

Test employee, manager, contractor, remote, and missing-owner cases before activation.

Dashboard example

Publish a Dashboard with:

active onboarding cases;
completion percentage by start date;
overdue tasks by owner;
cases blocked by missing information;
the next seven days of onboarding activity.

Expected result

Asset	Purpose
Knowledge	Current onboarding rules and role paths
Data	Cases and task progress
Process Skill	Prepare an onboarding plan
Workflow	New hire onboarding
Dashboard	Readiness, blockers, and ownership

Safety checks

Apply data minimization to every field and attachment.
Keep account provisioning and invitations behind human review.
Remove access when a case is cancelled.
Re-test the Workflow after onboarding policy changes.

Getting Started

Concepts

Guides

Examples

Reference

Coordinate employee onboarding

Outcome

Add the business context

Prompt to try

Review the plan

Create a Process Skill

Create the Workflow

Dashboard example

Expected result

Safety checks

​Outcome

​Add the business context

​Prompt to try

​Review the plan

​Create a Process Skill

​Create the Workflow

​Dashboard example

​Expected result

​Safety checks

Outcome

Add the business context

Prompt to try

Review the plan

Create a Process Skill

Create the Workflow

Dashboard example

Expected result

Safety checks