New Hire Onboarding

The crew

• Training Coordinator Crew leadA steady training coordinator who knows who has finished which course, what expires when, and what a new hire needs in their first weeks, and books refreshers before anything lapses.
• Office AdministratorThe operations half of a freelancer's brain.

Plans it follows

• Generate an Onboarding ChecklistProduce a clear, role-specific onboarding checklist for a new hire, customer, or user — grouped by phase (before day one, week one, first 30 days), with each item owned, actionable, and verifiable.
• Team Handbook SectionWrite a clear, reference-grade section of a team/company handbook — a policy, process, or how-we-work doc that a new hire can read once and act on correctly.

Actions the crew can take

• Onboarding statusEvery new hire's onboarding at a glance: open steps due within 7 days with overdue first, then each hire's start date, progress and what is still to do before day one, with hire and step ids.
• Add hireAdd a new hire with the standard plan (accounts, equipment and paperwork before day one, a first-day welcome, a first week with a buddy, and 30, 60 and 90-day check-ins), or update one: full name, role, first day (YYYY-MM-DD or a weekday like 'monday'), manager and buddy.
• Add taskAdd a step to a new hire's plan: the hire, what needs doing, the phase (before day one, day one, first week, 30 days, 60 days or 90 days), who owns it, and a due date if one was given.
• Complete taskCheck off steps the moment the person says they are done: task (a step's id or words from its title, several separated by commas) and the hire's name, or the hire with a phase to check off everything in it.
• List planA whole plan, or every plan: each step with its phase, owner, due date and whether it is done.

Each action is a small script that changes the app’s files, checked by Gezel’s security settings before it runs.

Files it keeps

Plain files in the project folder you can open, back up, and read: hires.json, tasks.json.