How to use AI in HR: a practical starting guide for people who already know HR

You are not behind. In SHRM's State of AI in HR 2026 report, 54% of organizations have not adopted any AI in HR and have no plans to this year. Only 39% have adopted it at all, and just 25% say their AI policies are clear and future-proof.

That gap is the opportunity. Learning how to use AI in HR deliberately puts you ahead of most of the field. What makes AI safe in HR is what you already have: judgment. You know when an output is wrong, when a policy claim is off, or when a decision needs a person in the room. AI does the mechanical work underneath that judgment so you can spend your attention where it counts.

This guide walks you through that path in order. Start with low-risk drafting, build a review habit, formalize one workflow, write a short policy, bring in your team, and only then move toward decision-adjacent work with guardrails already in place. Every step keeps AI on preparation and keeps the decision with a person. Step 1 is something you can do this week.

Step 1: Start with low-risk drafting and summarizing

Pick one task you'll do this week anyway, and let AI take the first pass.

A task is safe to start with when it clears three checks: no personal data in the prompt, you're the only one reviewing it, and the result is a draft that still needs your decision. Job descriptions, policy updates, and meeting summaries are all good places to start.

Where to start with AI in HR

• Flag outdated language in a policy. Feed a policy section to AI; get back a list of unclear or outdated phrases to review. Why it's a safe start: No personal data; you review and decide what to change.
• Summarize meeting notes. Paste anonymized notes; get a structured summary. Why it's a safe start: Low stakes if the summary misses a point, easy to catch on read-through.
• Draft internal announcements. Give context and tone; AI writes the first pass. Why it's a safe start: You own the final copy; no compliance exposure.
• Generate a first-draft job description. Provide role details; AI structures the JD. Why it's a safe start: The single most common AI use case in HR, at 66% adoption per SHRM 2026 [1].
• Build a 30-60-90 onboarding checklist. Give role and team context for your new employee; get a structured checklist. Why it's a safe start: Template output; nothing goes live automatically.

Nearly 9 in 10 recruiters using AI for job descriptions report time savings or efficiency gains from it. [2] These are tasks that eat hours and produce something you would have written anyway, so even a first draft that needs some refining can still save you real time.

A simple way to sort these tasks, borrowed from our AI for HR Professionals course, frames it this way: is this a chore, is it thinking work, or is it something you never had the bandwidth for before? Chores like scheduling, routing, and reminders are worth automating outright. Thinking work (a first draft, a rubric, a summary) is where AI augments you as a drafting partner. And the tasks you never had time for at all, like cross-referencing a finalist's skills against your current team's gaps, are where AI extends what you can actually do. Sorting a task into one of those three buckets before you touch a tool keeps you from over-engineering a five-minute chore or under-resourcing a genuinely new capability.

Try this prompt on a real document today:

Summarize the key points of this [policy or handbook section] in clear, professional language under 200 words, suitable for HR business partners to explain to employees.

‍

The same pattern works for exit-interview themes, offer letters, and behavioral interview questions with answer benchmarks. Pick one workflow to improve this week rather than trying to AI-enable everything at once. One good win beats ten half-finished experiments.

Step 2: Review every output like a fact-checker

Treat every AI output as a first draft that needs a human fact-check. Here's what that catches: AI invents employment histories that never happened, rates identical resumes differently based on demographic signals, and cites outdated legal details as settled fact.

AI background-check tools have generated detailed, confident, and entirely false employment histories, including candidates listed as working at companies that had closed years earlier. Bias follows the same pattern: in one randomized study, GPT-3.5 Turbo rated identical resumes 0.45 points higher when the candidate was female. [3] Position matters too: a 2025 study that ran more than 2,000 simulated hiring decisions through ChatGPT found it consistently favored whichever resume appeared first, and some candidates needed a notably stronger resume just to close that gap. [4] The most-cited example of hiring-AI bias is still Amazon's internal screener, which downgraded resumes that included the word "women's"; the tool was retired back in 2018, but it remains the reference case for how bias creeps into automated screening in the first place.

There's a version of this loop already playing out in hiring: candidates increasingly use AI to write applications, employers increasingly use AI to screen them, and in the worst version of that exchange, no human touches the process at either end. That is exactly the failure mode this step exists to prevent.

AI can also hallucinate employment law details with total confidence. Search "parental leave" through a general-purpose model and you may get outdated entitlements stated as a settled fact. A practitioner who knows the current rule catches it in seconds; a general-purpose AI tool has no way to.

Maisha, an instructor in our AI for HR Professionals course, teaches a related three-step model for this exact moment: check, inspect, correct. Check is a fast surface scan (does anything look off or inconsistent at a glance). Inspect is the deeper pass (is this accurate, complete, and right for the audience). Correct is where you make the actual edits, or send the draft back to AI with sharper instructions instead of fixing everything by hand. Her shorthand for the whole habit: "pause before you publish."

Run every output through this check before it touches a person:

• Fact-check every legal or compliance claim against the actual regulation or your attorney
• Scan for biased or coded language (ninja, rockstar, digital native, recent grad)
• Watch for position bias on any ranking. Reorder the inputs and re-run
• Check the tone against your actual culture instead of a generic corporate register
• Confirm no personal data went into the prompt

One tactic worth adding to that list: AI tends to agree with whatever you show it, so if you suspect it is just telling you what you want to hear, assign it a skeptical persona before you ask for feedback. Rather than asking AI to proofread a policy announcement, ask it to review the announcement as an employee who dislikes the change and explain exactly why. That single framing shift turns a compliant editor into a genuine stress test.

The stakes go beyond reputation, into legal liability. Workday's screening tools drew a bias lawsuit alleging they disqualified Black, disabled, and over-40 applicants at disproportionate rates, and you stay legally responsible for an AI-influenced decision even when a vendor's tool produced the recommendation. The durable skill here is knowing when to use AI and how to QA what it gives you, because you own the output regardless of which tool produced it.

Step 3: Keep your employee data safe

Never put identifiable employee data or company information into a public AI tool. That single rule prevents most of the damage.

The risk is already inside most companies. About 1 in 20 employees has pasted confidential data into ChatGPT, [5] roughly 80% of companies have shadow AI use, and only 37% can detect it. [6] It's no surprise that 63% of HR pros name data security as a top concern. [7]

What data to keep out of public AI tools

• Employee names, salaries, or performance reviews. Identifiable; covered by privacy law and most company data policies.
• Disciplinary or grievance notes. Legally sensitive; exposure risk if stored in training data.
• Health, disability, or protected-characteristic information. Covered by HIPAA, ADA, and equivalent laws in most jurisdictions.
• Named candidate notes or background-check results. Identifies individuals; creates liability if data is exposed or retained.

One category that's easy to miss: data from a very small or otherwise identifiable group. A team of three people is functionally identifiable even with names stripped out, and so is a demographic breakdown fine enough that only one person could match it. If aggregating the data still points to one specific person, treat it like you would their name.

Free and consumer tiers of AI tools commonly store your inputs for training by default. ChatGPT's free and Plus tiers are the most-used example of this: even deleted chats can persist. Use the newspaper test: if you wouldn't want the exact prompt to appear in a screenshot, strip more out of it before you send it.

Strip names and identifiers before you start, then work from the anonymized text. For anything involving real HR data, use a secured enterprise tool that doesn't train on your inputs: ChatGPT Enterprise or Team, Microsoft Copilot for M365, or AI built into your HRIS. On the consumer tier, at minimum turn off "Improve the model for everyone" in settings, though for real HR data the enterprise tier is the safer call regardless. This ties straight back to Step 1: scrub names from exit-survey text before you paste it into a summarizer.

Step 4: Turn one task into a repeatable workflow

Pick one recurring task and formalize it, because the gap between a good AI habit and an abandoned one is rarely the tool.

Nearly half of AI initiatives were abandoned in 2025, and 88% of HR tech leaders report no significant ROI from their AI investments so far. [8] The difference between the teams that stick with it and the ones that quietly drop it is whether anyone turned a one-off win into something repeatable.

Formalizing a workflow means writing down four things: which tool you use, what you will never input (your Step 3 list), who reviews the output, and what "good" looks like. Job-description drafting with a bias check is a strong first candidate. Here's the complete two-prompt version:

Draft: Create a job description for a [job title] at a [industry] organization. Include [responsibilities] and [qualifications]. Use inclusive, gender-neutral language.

Bias check: Acting as an expert in HR and employment law compliance, review this job description and flag any language that could be considered biased, discriminatory, or unenforceable. For any potential issues, provide suggestions on how it could be rewritten.

‍

A human reviews both outputs before anything gets posted. That review step is the workflow itself. The prompts repeat well because they follow the same shape every time: role, context, output format, then constraints. Write those four lines down where the next person can find them; an undocumented workflow lives in one head and disappears the day that person leaves.

If your tool supports it, take this a step beyond a written doc: set up a persistent project or custom instructions that bundle your context, reference files, and guardrails once, so every new chat starts from that baseline rather than from scratch. ChatGPT Projects and similar features exist for exactly this. The AI for HR Professionals course builds an entire onboarding communications workflow this way, uploading approved templates once and reusing the same project for every subsequent request.

Teams that succeed spend as much effort preparing their people as their platforms. A few meaningful workflow redesigns a year beats overhauling everything at once, and the workflow your team will actually use every week beats the one that only looks impressive in a deck.

A workflow you can describe in four lines is also a workflow you can write a policy around.

Step 5: Write a one-page AI use policy before you scale

Write a one-page interim policy before you expand AI use past your own desk. Most organizations haven't: only 25% say their AI policies are clear and future-proof, 23% call their own too vague, [9] and 25% have no formal AI governance at all. [10]

The minimum policy fits on one page and covers four things:

• Approved tools and permitted use cases
• The prohibited-inputs list (reuse your Step 3 list directly)
• Mandatory human review before any output is used
• Who owns the final decision, which is never the algorithm

That's enough to expand safely, and it gives your team a clear answer whenever they wonder if a task is allowed, which is most of what shadow AI use comes down to. As you grow the policy, add data classification, a bias-audit cadence, transparency to employees and candidates, an override and appeal process, and a legal-review checkpoint before any new use case launches.

Building an internal AI assistant forces the same thinking in miniature. When the AI for HR Professionals course walks through building a benefits chatbot, the instructor defines exactly what it's allowed to answer, what it must never do (no legal advice, no personal recommendations, no storing personal data), and when it hands a question back to a human. Maggie's framing applies just as well to your one-page policy: "It's here to inform, not to decide."

Review it every 3–6 months, because the tools move faster than annual policy cycles. Write it around principles and inputs rather than specific products, since a policy tied to one vendor goes stale the moment you switch tools. Anything AI-generated should be reviewed by a human before it goes public. A short policy everyone understands is what makes the next step safe: bringing your team in.

Step 6: Roll it out to your team as an experiment

Roll AI out to two or three colleagues first, framed explicitly as an experiment.

The resistance is real and worth naming before you ask anyone to adopt anything. People worry AI means job cuts or that using it makes them look replaceable. There's also a genuine cognitive cost: generative AI use has been linked to memory retention losses of over 80% compared to search engines, along with fading motivation to keep a skill sharp once a tool handles it. [11]

Give a short demo, hand out a one-page cheat sheet of prompts that work, and hold a quick feedback session each week for the first month. The proof this matters: HR teams that follow change-management practices are 2.6x more likely to report a successful rollout. [12]

Keep that feedback loop lightweight rather than building a survey program: a thumbs up or down on individual outputs, one or two short follow-up questions (was this helpful, what felt off), and a quarterly pulse check are usually enough to see whether trust is building or friction is building instead. Track it by task type. If job-description drafts get consistently positive reactions but policy summaries don't, that tells you where to focus the next round of training rather than declaring the whole pilot a win or a loss.

Protect against skill erosion by keeping humans on the judgment work, the same QA habit from Step 2. If a team offloads the thinking along with the typing, it trades short-term speed for long-term capability. Three habits worth building into the rollout: be clear about intent before reaching for AI, stay willing to override it, and keep checking quality on a regular, proactive schedule.

Point people to where the conversation goes after the demo ends. The OpenAI Academy has a tested HR prompt library, SixFifty covers compliance-specific prompts, and r/humanresources is a useful, unfiltered check on what actually works in practice versus what looks good in a vendor pitch.

Step 7: Approach hiring and performance decisions carefully

Save hiring, performance, compensation, and discipline for last, after your review habit and your policy already exist. This is where law and bias risk concentrate, and the legal ground under HR is moving fast: the EEOC's AI hiring guidance came down in early 2026, Illinois amended its Human Rights Act for AI effective January 1, 2026, and Colorado's AI Act takes effect February 1, 2026.

The rule for this tier is firm: AI narrows and informs, it does not decide. Every use here needs a named human reviewer, bias-audit protocols, legal sign-off, and transparency with the affected candidate or employee. You are legally responsible for an AI-influenced decision even when a vendor's tool produced the recommendation.

In practice, "AI narrows and informs" breaks down into three levels of oversight, not one. Some actions need approval: the automation stops and waits for a named person to sign off before anything happens, which is the right call for anything high-stakes or irreversible, like final pay calculations or termination communications. Others only need review: the action goes ahead, but a human checks the results afterward, which is enough for low-risk, easily-reversible tasks like routine reminders. And some need an override option: the process runs normally, but a person can step in when a case doesn't fit the standard pattern. Deciding which level applies, before you automate anything in this category, is most of the work.

The compliance map is already concrete. NYC Local Law 144 mandates annual independent bias audits and candidate notice for automated employment decision tools, with penalties of $500–$1,500 per violation per day. The EU AI Act classes employment tools as high-risk, with penalties up to 40 million euros or 7% of global turnover. Involve legal early and treat transparency as table stakes, because what is optional today may be mandatory in your state next year.

AI uses to avoid in HR decisions

• Final hire, promotion, or termination calls. Legally accountable decision; requires named human ownership.
• Sensitive employee conversations. Empathy and judgment cannot be delegated to a tool; trust is at stake.
• Interpreting local employment law without verification. AI hallucination risk is high; errors are legally consequential.
• Anything touching union or organizing activity. Protected activity; AI involvement creates legal exposure.
• Facial-expression "enthusiasm" analysis. Unreliable science; legally risky and ethically indefensible.

‍