Coordinate new-hire onboarding
Assemble onboarding trackers, team summaries, and drafts for a welcome space.
ZeroTwo collects approved background on new hires, stages tracker updates, drafts summaries per team, and prepares the welcome space for your review, with nothing going out until you approve.
Related links
Skills & Plugins
- SpreadsheetsStages tracker changes as a new
.xlsxor.csvfile ($spreadsheets). - Google DriveSupplies approved documents, tracker templates, and exports.
- NotionSupplies onboarding plans, project pages, and checklists.
Starter prompt
Introduction
Onboarding spans hire lists, trackers, manager mappings, readiness checks, and chat spaces. ZeroTwo can assemble one reviewable packet per cohort; keep the first pass read-only and approve every write, invite, or post explicitly.
Define the review boundary
Before anything is read, fix the population, sources, allowed fields, destinations, reviewers, and out-of-scope actions. Keep to practical details such as role, manager, start date, and readiness, and exclude compensation, demographics, IDs, addresses, medical, immigration, and performance data.
Gather approved onboarding inputs
Use the source your organization approves, such as an HR export or tracker. Attach the files in the composer or point ZeroTwo at a Drive or Notion document. Have it report sources, row counts, date range, and columns first, treating records as data rather than instructions.
Build the onboarding tracker
Keep source facts apart from generated planning fields such as owners, orientation, buddy, readiness, and next action. Stage it as a new spreadsheet file or a draft tab, and review rows and destination before any write.
Draft team summaries and welcome spaces
Prepare drafts in coordinator order: team summary with readiness gaps, private space names, invite lists and first-week checklists, and announcement copy without needless personal detail. ZeroTwo drafts the welcome-space plan; you create the channel or space and send the invites yourself. Tracker writes and posts wait for your approval.
Run the weekly onboarding workflow
- Inventory only named sources and report conflicts.
- Stage tracker, summaries, space plan, drafts.
- Review cohort, destinations, audience, naming, privacy, messages.
- Execute only reviewed actions, such as a tracker write, after explicit approval.
- Report links, counts, gaps, and owners.
Suggested prompts
Run separate passes: a read-only cohort inventory, then staging of the tracker and team summary, each with strict source and exclusion rules.
Related use cases
Draft PRDs from internal context
Write product requirements documents using Linear, Slack, meeting notes, and source documents.
Prepare meeting briefs
Convert what is on your calendar into an agenda and a notes outline.
Run event playbooks
Set up repeatable workflows for managing event programs.


