HR, Legal, and People
No department handles more sensitive combinations of documents and people than this one — which is exactly why the boundary must be brightest here: Claude accelerates the document work; qualified people make every judgment about a person or a legal position. Held firmly, that line frees real hours inside document-heavy work that quietly consumes this team.
Workflow patterns
Policies and job descriptions
Draft from approved templates, role evidence, jurisdiction guidance, and inclusive-language standards — with one instruction that changes everything:
Draft the job description from the attached template and role notes.
Where information is missing — salary band, remote policy, travel — do
not fill the gap with typical language. Insert [DECISION NEEDED: owner]
and list all open decisions at the top of the draft.
Generic filler is this department's quiet failure mode: a plausible paragraph nobody decided becomes policy because nobody noticed it needed deciding. Flagged gaps turn the draft into a decision list — which is the actual work.
Contract review assistance
Daniel, Northstar's HR partner, uses Claude to prepare counsel's review, not replace it: extract clauses, compare each against the approved playbook, and produce a deviation list — "clause 7 allows 60-day termination notice; playbook standard is 30" — with open questions attached. Counsel starts from a map instead of a blank read. The sign-off remains theirs; Claude's comparison is preparation, never the organization's legal position.
Onboarding materials
Turn approved policies and process notes into role-specific checklists, guides, and 30-day plans — the classic important-but-never-urgent backlog. Name the source and owner beside every requirement, so when the policy changes, someone can trace which onboarding materials inherit the change instead of discovering the drift a year later.
Sensitive-data protocols
This track's data rules are stricter by default. Employee, candidate, health, compensation, performance, investigation, and legal-matter data: minimize ruthlessly, use only approved enterprise environments, and never widen the audience — if three people may see the investigation file, the Claude workflow that touches it is available to exactly those three. Most drafting tasks work with roles and situations; names and identifying details usually add risk, not quality. Strip them.
Track lab
Choose one low-risk document workflow:
- Draft a job description from approved role inputs
- Compare a sample agreement against a clause playbook
- Build an onboarding guide from current policies
- Rewrite a policy section for clarity without changing meaning
Test deliberately for omissions, unsupported language, bias, confidentiality leaks, and correct escalation. For the policy rewrite, have the owner confirm the meaning survived — "clearer" that shifts an entitlement is a new policy, not a rewrite.
Human sign-off gates
An authorized reviewer approves before: a policy publishes, an employment decision is made or communicated, a legal interpretation leaves the team, or a contractual position is accepted. These gates appear in the workflow design itself — visible steps with named roles, not habits people are trusted to remember.
Definition of done
The output traces to approved sources, open decisions are flagged rather than filled, sensitive data stayed minimal and contained, and the workflow ends at the correct qualified human — by design, not by luck.