Claude Cowork for HR

HR operates on cycles. Hiring cycles. Onboarding cycles. Performance review cycles. Engagement survey cycles. Headcount planning cycles. Every cycle starts the same way — with the same pipeline review, the same pre-calibration prep, the same survey export you’re staring at trying to find the story inside it.

The work is real. The problem is that it’s reactive. Something slips through onboarding because no one checked. A performance calibration runs long because no one did the distribution analysis ahead of time. A pulse score drops and leadership finds out in the all-hands instead of in the HR report.

Cowork threads know your cycles. You seed them once — with your hiring context, your review rubric, your onboarding checklist — and every time that cycle comes back around, the thread already has everything it needs to get you to the analysis fast. The work still happens. Cowork makes sure it happens systematically, not reactively.

This guide sets up five persistent threads for the recurring rhythms HR owns: recruiting pipelines, onboarding readiness, performance review prep, employee pulse, and headcount planning.

---

What You’ll Build

Five persistent threads, each with a job:

1. Recruiting Pipeline Monitor — weekly view of which roles are at risk and what sourcing needs to happen

2. Onboarding Readiness Tracker — weekly flag of what’s not ready before Day 1

3. Performance Review Prep Thread — calibration-ready summaries with distribution analysis and equity flags

4. Employee Pulse Monitor — monthly survey analysis that surfaces what leadership needs to act on

5. Headcount Planning Thread — quarterly scenario modeling against budget and attrition data

---

Step 1: Setup

Claude Cowork runs inside Claude.ai. On desktop, find Projects in the left sidebar — that’s the persistent context layer where threads live. On mobile (iOS and Android), same app, same threads.

Name your threads clearly. You’ll be checking some of these from your phone between meetings:

• HR: Recruiting Pipeline

• HR: Onboarding Readiness

• HR: Performance Review

• HR: Employee Pulse

• HR: Headcount Planning

No integrations required. No API keys. No IT ticket. The threads work from copy-paste — whatever you can pull from your ATS, HRIS, or survey tool, you drop in.

---

Step 2: Recruiting Pipeline Monitor

The weekly recruiting sync happens because someone needs to ask the questions that should already be answered: which roles are behind, where the pipeline is thin, what sourcing isn’t working. It’s a reactive meeting. It doesn’t have to be.

Open your HR: Recruiting Pipeline thread and paste this to seed it:

You are my recruiting pipeline analyst. I'm going to give you context on our open roles,
hiring manager priorities, target start dates, and sourcing channels. Hold this context
across all future updates I give you.

Open roles: [paste your current open req list with department, level, hiring manager,
target start date, sourcing channels active]

For each role, track: stage distribution (applied / screened / interview / offer),
days open, and any sourcing context I give you.

Then each week, paste your pipeline update and use this prompt:

Here's the recruiting pipeline update: [paste — role, stage, count, status]

Produce:
1. Which roles are at risk of missing the target start date and why
2. Where the pipeline is thinning — stages with fewer candidates than needed
3. Recommended sourcing actions for the 2 most critical open roles
4. What I should communicate to hiring managers today

Recruiting updates that used to require a 30-minute weekly sync get to the point in 5 minutes. The thread remembers your roles, your hiring managers, your timelines. You’re not re-explaining context every week — you’re just dropping in new data.

---

Step 3: Your First Result

Before you read further, run the pipeline thread once with a real update.

Paste your current open roles and one week of pipeline data. Review what comes back. You’re looking for the thread to flag the right risks — roles that are old and thin at the top of funnel, or roles where the interview stage has stalled.

The output won’t be perfect on the first pass. Add context where it’s missing: tell the thread which roles have the most pressure, which hiring managers need proactive communication, whether you’re capacity-constrained on the sourcing side. The thread holds all of it.

On mobile, the thread is right where you left it. Before your Monday morning recruiting review, open the app, pull up the thread, check the flags. You walk into the meeting knowing what matters.

That’s the first win. The rest is below the line.

---