Claude for HR: Two Ways to Speed Up the Hiring Paperwork
I teach a lot of HR people, and the same two piles of work come up in almost every class. The first is writing — job postings, offer letters, policy updates, the careful paragraph in a performance review. The second is answering the same handful of handbook questions over and over, usually from people who already have the handbook. Neither pile is hard. Both eat the morning. That is the gap where Claude for HR work actually earns its keep, and it is narrower and more practical than most of the hype suggests.
I want to be clear about what I am not saying. I am not saying let an AI write your policy. The useful version is the opposite: you hand Claude the material you already own — your past postings, your actual handbook — and make it work inside those boundaries instead of inventing from a blank page. That is the difference between a draft you have to rewrite and a draft you can send.
Here are the two I would set up first. Each takes about ten minutes.
1. Use Claude for HR Job Postings That Match the Ones You Already Wrote
The problem with a posting written from scratch is that it never sounds like your other postings. Different headings, different tone, different idea of what “requirements” means. Fix that by giving Claude your back catalog once.
In Claude, click Projects in the left sidebar, then New Project. Call it something like “Job Postings.” Inside the project you will see Project knowledge on the right — paste in three or four of your best recent postings, or drop in the files. That knowledge stays attached to every chat you start inside that project, so you only do it once.
Then start a chat in that project and type something close to this:
Using the postings in project knowledge as the model for structure, tone, and section order, draft a posting for a Payroll Specialist reporting to the Controller. Hybrid, two days on site in Cherry Hill. Match the heading style of the attached postings exactly. Anything I have not told you — salary, benefits, years required — leave as [TO CONFIRM] rather than guessing.
That last sentence is the whole trick. Without it, Claude will cheerfully produce a salary band, a benefits list, and a “5+ years required” line that came from nowhere. With it, you get a clean draft with obvious blanks you can fill in from the real req.
The gotcha: project knowledge is sticky, which is the point, but it also means stale postings keep influencing new drafts. When you change your EEO statement or your benefits boilerplate, go back into project knowledge and replace the old files. Otherwise you will be generating last year’s language all year.
2. Turn Your Handbook Into an Answer Desk — With the Section Number Attached
This is the one that saves the most hours, and almost nobody sets it up. Make a second project — call it “Handbook” — and upload the current employee handbook PDF into project knowledge. Add the PTO policy, the remote work policy, and anything else people ask about weekly.
Now, instead of hunting through a 60-page PDF every time someone asks about carryover, you ask:
Answer only from the documents in project knowledge. An employee transferring from part-time to full-time in October asks how their accrued PTO carries over. Quote the exact section text you relied on and give me the section number. If the documents do not cover this, say so plainly instead of reasoning it out.
Two things make that prompt work. “Quote the exact section text and give me the section number” means you can verify the answer in about five seconds instead of trusting it — and you can paste that quote straight into your reply to the employee. “If the documents do not cover this, say so plainly” is what stops the confident-sounding guess, which is the real risk in HR. A wrong PTO answer with a fake section number is worse than no answer.
The gotcha: watch your effective dates. If last year’s handbook is still sitting in that project alongside this year’s, Claude has no reliable way to know which one governs, and you will get answers that blend the two. Keep exactly one current version in the project, and put the year in the file name so you can see at a glance what is in there.
Plenty more on the calendar
If you want to see both of these built live, with real HR documents and the mistakes that happen along the way, I am running Using Claude to Be More Productive as an HR Professional on Wednesday, October 21. We cover job postings, handbook lookups, policy drafting, and review language, with time for your own questions at the end.
If that date does not work, the full current schedule is on the front page of PCWebinars.com, with new dates going up as they are confirmed. Register for this one, or browse the rest and find something that fits your week.
About your trainer
I’m Tom Fragale. I’ve been a computer trainer and consultant for more than 30 years, and I’ve taught well over 30,000 people how to get more out of the software they already own — Excel, Access, Power BI, Word, Outlook, and now the AI tools that sit on top of all of it: Claude, ChatGPT, and Microsoft Copilot. My background is applied, not theoretical. Alongside teaching, I build real databases and reporting systems for clients in Excel, Access, and Power BI, so the examples I use in class are the problems I ran into last week, not textbook exercises. I also publish free tutorials on YouTube and longer courses online.
Come see the full list of upcoming live sessions, recordings, and custom training options at PCWebinars.com.
