Skip to main contentSkip to navigation

A domain track

Claude & AI for HR

HR, recruiting and people-ops teams who already use AI to polish a job post or an email, but still build onboarding and dig through headcount data by hand. This track puts Claude to work on your existing people data and documents, so every new hire gets a real onboarding path and a policy question gets answered on the spot.

24 topics

Ask an HR team what is open on their desk and the answer is usually a pile of documents. Job descriptions at different stages, a leave policy last touched before the hybrid-work agreement, and an onboarding checklist that gets copied, renamed and half-corrected for every new hire. Nothing in the pile is hard. There is just a lot of it, and all of it has to sound like the same company.

The fear in this department is a mistake with a person's name on it. A policy answer that contradicts the contract, or a salary band that lands in a file it never should have touched. So the first hour goes to the data itself. The team walks through its own files column by column, decides which columns are dropped and which are swapped for an employee ID, and only then does Claude see anything. Every policy answer it gives has to quote the clause it rests on, and a reply with no clause behind it goes back to HR instead of out to the employee.

The session runs on what you already hold: last quarter's job description, the onboarding kit for one role, the parental leave policy, a headcount export with start and leave dates, and the most recent employee announcement. Participants turn the policy into a plain message and a set of answers, build a first-week plan for a role, and cut attrition by team from the export. Each person leaves having run at least one of these on a file of their own, with the prompt or Skill that did the work.

Online course

Start online, at your own pace

The material we teach in the room, recorded slide by slide. You go through it when it suits you, from any screen.

Claude & AI for HR: the online course is on its way

Leave your email and we'll write once, the day it opens.

What happens to your details

Giving us these details is your choice, and no law requires it. Without the fields marked required, though, we can't finish what you came here to do.

What for: To email you once, the day the online course for your role opens. Nothing else.

Who gets it: Wider Group only. Your address sits with our infrastructure providers, Supabase and Vercel. Our email provider, Resend, sends us a note when you sign up. All three run servers outside Israel.

You can ask to see what we hold on you, correct it, or have it deleted, any time. Write to shahar@wider-group.com and we answer within 30 days. The full detail is in the Privacy Policy.

Rather do it live? See the live workshops

Today's challenges

  • Every open role needs a fresh job description, and they pile up fast
  • Policy and procedures lag behind reality, and comms to employees stay scattered
  • The same onboarding process gets rebuilt almost from scratch for every new hire

Example use cases

  • A job description and ad ready in minutes, in the company's own voice
  • Dense policy turned into a clear document and an employee message people can understand in one read
  • An interactive onboarding kit ready for a new hire on day one, not week two
  • A hiring and retention dashboard built from the data already sitting in your files, no extra manual spreadsheet
  • An onboarding journey tailored to each role, with clear tasks and checkpoints for the first weeks
  • Instant, consistent answers to employee questions about policy and benefits, no waiting on HR to reply

What we teach here

Intro

A live opening session built to shift the room, not lecture it: real demos of what Claude can already do inside your workflows, run in front of the group. Participants leave with a working sense of where AI helps and where it doesn't, and enough curiosity to start using it that afternoon.

AI & LLM Basics

What tokens, context windows and hallucinations mean, explained without the math and without the hand-waving. Once a team understands why a model sometimes gets things wrong, it stops either trusting it blindly or dismissing it after one bad answer. Every other module in the program builds on this one.

Claude Intro

A new AI tool comes out every week, and you don't need to chase them. We map the main ones and what each does best, then explain why we spend the day in Claude. After that we set it up together: privacy settings, the one capability to switch on, and a tour of the screen. Face to face it is a live demo; in the online course it is a recorded tour.

Claude Skills

Claude Skills turn a procedure your team already does well into something Claude can repeat on its own: the same checklist, the same tone, the same edge cases covered every time. You build it once with the person who actually knows the process, and from then on every teammate gets that expertise on demand. For teams where quality depends on one or two people, this is how that stops being a bottleneck.

Prompt Engineering

Structure, context and role framing: the craft of asking in a way that gets a usable result on the first try instead of the fifth. Participants practice on real prompts from their own work, not toy examples, so what they take home already fits the job. Every other module assumes this fluency, which is why it comes early.

Claude Projects

Claude Projects hold your documents and instructions in one persistent workspace, so every conversation starts already knowing your company, your terminology and your rules. Teams that set this up once save the ten minutes of re-explaining context at the start of every session, every day. For anyone running the same kind of task repeatedly, this alone changes the math.

Design systems: your brand inside Claude

Without a design system, Claude decides how everything looks, and it comes out different every time. The session shows what a design system holds, how every slide, dashboard and app is built on it, how to make one from your website and a deck you already have, and how to keep several and switch between them.

Artifacts: from answer to deliverable

The difference between an answer and a deliverable. The session covers when something should become an artifact, every kind there is today, how they all come out on your design system, the four ways to change one, and what you do with it: connect it to apps, connect it to files, share it as a live place, or export a snapshot.

Agentic AI vs. Chat

The shift from asking Claude a question to handing it a multi-step task it completes on its own, checking in only where it matters. Participants learn what actually counts as an agent, when handing over work beats doing it turn by turn, and how supervision needs to change once Claude is running unattended. Get this wrong and you either babysit an agent that didn't need it or trust one that did.

Agentic workflows in the Claude chat

In the Claude chat you can hand over a whole job instead of asking a question. Claude plans the steps, searches the web, reads your files, runs code and hands back a finished document, spreadsheet or deck. On a big task it can split the work between several sub-agents running at once. Participants learn which work is worth handing over and how to brief it the way they'd brief a colleague, then practice staying in control while Claude works. They finish by turning a weekly chore into a scheduled task that runs on its own.

Claude Across Office

A full pass across the Office suite: drafting and redlining in Word, tables and analysis in Excel, decks in PowerPoint, and inbox triage in Outlook, taught as one connected workflow rather than four separate tricks. Every exercise uses documents close to what participants actually produce at work. It's the broadest module in the program, and the one most teams come back to most after training.

Routines in Claude

Tasks Claude runs on its own, on a schedule: a morning brief from your calendar and inbox, a weekly report, a competitor watch. Participants learn to tell a routine from its schedule, connect only the connectors it needs, and test every routine before it runs alone. They leave with one routine that works from the next morning.

Connectors & MCP

Connecting Claude to the systems your team actually runs on: drives, CRMs, databases, through connectors and MCP, with the permission boundaries covered before the connection ever gets made. Participants leave knowing exactly what to expose and what to keep out of reach. This is the module that turns Claude from a smart typewriter into something acting on real, current data.

CLAUDE.md

CLAUDE.md is a plain text file Claude Code reads at the start of every session, so whatever you'd explain to a new hire on day one, you write there once. Participants learn what goes in it and what stays out, when it's read, and where it lives: the organization, you, the project and a subfolder, all loading together. They leave with a draft from /init and one rule for growing it: what you corrected twice goes in the file.

Agents for non-engineers

How to build an agent without writing code: it gets a job description, a badge that limits what it can touch, and a bottom line it hands back. Participants see why the work goes to a separate room, take an agent file apart, and fill in the one-page charter that turns into the agent's file. They learn to hire for a role, not a task, and to tell when a job needs an agent rather than a skill. They leave knowing the hard part is the charter, and that the charter is their own expertise, written down.

Plugins: the department in a box

A plugin carries the agents, skills and hooks a team built, so another team installs the same department instead of rebuilding it. Participants see what goes in the box and what stays home: CLAUDE.md and the permission rules belong to each team. Then they ask Claude to build one, try it in a fresh session, and share it through a marketplace.

Context Management

How context windows, memory and cost interact, and what to do about it before a long working session starts drifting or the bill surprises someone. Participants learn to spot when Claude is still hauling a task that should have been closed an hour ago, and how to reset without losing what mattered. A short module with an outsized effect on both output quality and the invoice.

Safe AI at Work

The rules every employee needs before their first real session: what data is safe to share, what isn't, and what org-level guardrails should exist so individual judgment isn't the only safeguard. This module is usually the one legal and IT ask for by name. It replaces vague anxiety about compliance with a clear, specific policy people can actually follow.

Human in the Loop

Where people belong in an AI-assisted workflow: which steps need a review gate, which need an approval, and how to calibrate trust so oversight isn't either everywhere or nowhere. This pilot module gives teams a concrete framework instead of a gut feeling about what to check. Get the calibration right and quality goes up without slowing anything down.

Security & Privacy

Permissions, prompt injection and data boundaries: what makes an agent that can act also one that can go wrong, and how to run it anyway without carrying the risk. This pilot module is built for organizations moving agents past read-only demos into things that write, send and change data. It's the module security teams should sit in on.

Claude for Word

Claude inside Word for text-heavy roles: drafting from a brief, redlining a contract, controlling tone across a document, and automating the parts of writing that are really just formatting. This pilot module is aimed at HR, legal, marketing and sales, where documents are the daily output. It's the module that turns a quick-draft request into a five-minute job.

Claude for PowerPoint & Decks

Claude for PowerPoint is a side panel inside PowerPoint. It reads your template, builds new slides on your own layouts and makes charts and tables you can still edit. The session works on one deck that four people touched: put it back on the master, rebuild a chart that was pasted in as a picture, and check every number against the source before anyone presents it.

Claude in Slack & Teams

Coming soon

Coming soon: bringing Claude into Slack and Teams so summaries, answers and actions happen where the team already talks, instead of a separate tool people forget to open. This syllabus item covers both the setup and the etiquette of an agent inside a shared channel. Built for teams whose real workflow lives in chat, not in a dedicated app.

AI Policy & Governance

Coming soon

Coming soon: writing the AI policy an organization actually needs, usage rules, risk tiers and rollout governance, instead of a generic template nobody follows. This syllabus item is for leadership and compliance stakeholders shaping how AI gets adopted company-wide. Built to produce a document teams can point to, not a discussion that goes nowhere.

Four documents HR stops rewriting

Each starts from a file you already have, and a person signs it off before any employee sees it.

A job description in your voice

A job description and posting drafted from a short brief, in the tone of your last good ad. The recruiter and the hiring manager edit, and the requirements list is checked against the actual role before it is published.

Policy answers with the clause

A set of answers to the questions employees ask most, each quoting the clause and the policy version it came from. Whatever the policy does not cover is routed to a person, not guessed.

An onboarding kit per role

A day-one and first-month plan for a single role, with tasks, owners and checkpoints. It is built once and reused for the next hire in that role. The manager adapts it, and HR keeps the master version.

An attrition read by team

A cut of leavers by team and tenure from the headcount export you already keep, in a dashboard that refreshes from the file. It shows where to look. What it means and what to do about it stays with whoever supports that team in HR.

From the blog

4 min read

Build your own Claude course for HR

Your handbook contradicts itself in two places and you've never had a day to find where. That's the first thing to hand Claude, and it beats the job-post demo everyone else starts with.

Read the post

3 min read

What HR Teams Actually Do With Claude

Bring real job descriptions, a policy document and an actual hiring spreadsheet into one Claude workshop, and here's what comes out: a job post in minutes, an onboarding kit ready for day one, and an instant answer to every policy question.

Read the post

Questions people ask

Is there a Claude course for HR teams in Hebrew?

Yes. Wider Group's online course comes in Hebrew and English, is self-paced, and you pick HR as your role to get exercises built for it. It is not open for purchase yet, and there is a waitlist. For a whole HR team working on its own files, Wider Group also runs a workshop, quoted per team.

Is it safe to put employee data into Claude?

Not without rules, and Wider Group sets them with you before anything is uploaded. The HR workshop goes through your own files column by column, decides which columns are dropped and which are swapped for an employee ID, and only then does Claude see anything. A policy answer without a clause behind it goes back to HR, not out to the employee.

Can Claude write job descriptions and onboarding plans in our company's voice?

Yes. In Wider Group's HR workshop a job description and posting are drafted from a short brief, in the tone of your last good ad, and an onboarding plan for one role is built once and reused for the next hire. The recruiter and the hiring manager edit, and a person signs off before any employee sees it.

Your people files

Tailoring starts with a short call about which files exist and which are off limits. The onboarding kit, policy and headcount export in the session are yours, so the plan gets built for a role you are really hiring this quarter. We set the masking rules for each file with you before the day itself. Tell us the team size and the role you're hiring for, and a quote follows.