The team for this work
Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.
✦ Guide · Intermediate
AI for HR teams
Onboarding plans from the handbook, interview preparation from the role description, handbook questions answered from the approved documents and a weekly hiring pipeline as a team of flexible workers.
Start guideYOUR OUTCOME
You will run an HR pod that builds each starter's plan from the handbook and role, drafts role-specific interview questions with a scoring guide, answers handbook questions from the approved documents and reports the hiring pipeline every week.
Onboarding is built from your handbook, the role and the start date Interview questions and a scoring guide come from the role description The pipeline report names what is waiting on you and what has stalled
4 min
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
The team and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
What each lesson covers
The guide, lesson by lesson.
The team for this work
Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.
Start from the work, not the tool: Onboarding plans from the handbook, interview preparation from the role description, handbook questions answered from the approved documents and a weekly hiring pipeline as a team of flexible workers. The team is Ona · Onboarding (Team onboarding), Kai · Hiring (Hiring and interview preparation), Handbook (Document and policy Q&A), Pipeline (Weekly status reporting). Each starts from a Marketplace template, imported as your own copy, renamed and re-goaled on the setup card; nothing personal and no creator credentials come with a template.
Practice. Open Marketplace, Worker templates, and read the Instructions and Integrations of each template on this list before you import anything. Note which sources each one will ask you for.
Marketplace → Worker templates → open Team onboarding. Read Instructions, then Integrations.
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
Import worker creates your copy as a flexible worker and opens the setup card. Rename it, replace the goal with yours, and choose When to work. Onboarding is the first hire because a starter's first week is the most visible thing HR produces, and it must come from your handbook, not a generic checklist.
Practice. Import Team onboarding, rename it Ona · Onboarding, and paste your goal on the setup card. Choose Now, once, and Continue. Check its first deliverable in Doc Manager before the next hire.
Name: Ona · Onboarding. Goal: Using the attached handbook and the attached role description, build a first-30-days onboarding plan for a new account manager starting Monday 5 October: week-by-week goals, the people to meet, the policies to read with their handbook section, and the checkpoints. Use nothing outside the attached documents. When to work: Now, once.
The team and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
Click New team, name it People pod, add Ona · Onboarding, and post what the team is for. Then hire the second wave with goals that start by reading the first wave's document. @Name directs one member, @everyone the room, and Work in the member row opens what that member did in the team. Interview prep drafts from the role description; the handbook worker answers only from approved documents; the pipeline worker reports from the tracker.
Practice. Create People pod, add each hire as it joins, and ask every member to post what it made and the one thing it would flag.
@everyone Welcome to the people pod. Ona's onboarding plan is in the workspace. Kai: draft interview questions and a scoring guide for the attached role description. Handbook: answer the attached staff questions from the approved documents only, and say when they are not covered. Pipeline: report each open role from the tracker.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
A hiring pipeline stalls between meetings; a weekly report names the stalls before they cost a candidate. Each run shows on its worker's Runs tab. Close each cycle with a status round, "@everyone one line each", and a grade against the acceptance checks each worker wrote first.
Practice. Add the time in When it runs, use Run now to get today's first report, then run one status round in People pod.
When it runs → Add a time. Name: Weekly hiring pipeline. What should it do? Read the hiring tracker and this week's updates and report each open role's stage, the candidates waiting on someone in the team with who, and anything unchanged for more than seven days. Read only the tracker and the updates. Repeats: Every week, Friday, 16:00.
Keep going
Make the learning stick
Start with one real piece of work.
Open Oppermind beside the lesson, apply each step, and leave with something you can use.