Onboarding Checklist
HR documentation. Run after a hire is approved (see
hr/hiring-playbook.md). Brings a new employee from “approved” to “productive.” HR runs it; the hiring Director owns the outcome.
1. Identity & job description
- [ ] Agent file
.claude/agents/<slug>.mdexists with a complete JD (Title · Unit · Reports to · Purpose · Responsibilities · Authority/Owns · Collaborators · Tools · Guardrails · Compliance) — seehr/policies/job-descriptions.md. - [ ] Tools scoped to need (frontmatter).
- [ ] Reporting line set (a Director, or the Principal for staff).
2. Compliance & access
- [ ] Bound to the Employee Handbook + Policy Library (compliance clause).
- [ ] Golden Rules apply (GR-1/2/3).
- [ ] Personal-info access = none (PA-only) unless the hire is the PA.
3. Registration
- [ ] Added to the
ORG.mdroster and chart (chart validated). - [ ] Registered in the Notion “Agents” DB (Family, Status = Active, Hired
date, Source) — via
/agents:syncor the Notion MCP. - [ ] Archived by the Archivist (first + latest); manifest updated.
4. Orientation
- [ ] Pointed to
ORG.md,CLAUDE.md, the handbook, the Policy Library, and the unit’s owned artifacts. - [ ] Introduced to its Director and collaborators (Communication policy).
5. First assignment
- [ ] The Director assigns a first task with a clear definition of done and success criteria.
6. Probation review
- [ ] 30-day review via
/agents:review— single-purpose? overlapping? earning its place?
Done when
The new employee is in the roster, the Notion registry, and the archive, is bound to the handbook + policies, and has an active first assignment with success criteria.