How to use AI in HR: 7 practical rules for HR teams

AI is everywhere, and the pace can make it feel like everyone else is already ahead. HR teams are still at very different stages of adoption. According to SHRM's State of AI in HR 2026 report, 39% of organizations have adopted AI in HR, while 54% have not adopted it and do not plan to do so this year.

That leaves room to learn deliberately. HR professionals already bring one of the most important skills for using AI responsibly: judgment. You know when an output is wrong, when a policy statement needs verification, and when a decision needs a person in the room.

This guide lays out seven practical operating rules for how to apply your existing judgment as an HR professional using AI as a tool. You do not have to follow them in a perfect sequence. Begin with lower-risk work, build strong review and data habits, and add workflow, governance, and experimentation as your use case expands. Use added caution whenever AI gets closer to a consequential employment decision.

How to use AI in HR

Rule 1: Start with lower-risk tasks

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

A good starting task clears three checks:

• The prompt contains no personal or confidential data.
• The output is a draft, not a decision.
• A person reviews it before anyone relies on it.

Where to start with AI in HR

Job descriptions are a proven place to start. In SHRM's 2025 Talent Trends research, writing job descriptions was the most common recruiting use of AI among adopting organizations, and 89% of HR professionals using AI in recruiting said it saved time or increased efficiency.

A useful way to sort potential tasks is to ask whether AI will automate, augment, or extend the work. Scheduling and reminders are candidates for automation. Drafts and summaries are augmentation: AI prepares material and a person improves it. Cross-referencing structured skills data across a team can extend the analysis HR has time to perform when the data, tool, and use case are appropriate and approved.

For your first use case, stay in the augmentation lane. It gives you a practical way to learn prompting and review without putting AI close to an employment decision.

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. Use only the source text. Mark anything ambiguous or potentially outdated for human review. Do not add policy requirements, legal conclusions, or information that is not in the source.

The same pattern works for approved onboarding content, internal communications, and other lower-risk drafting or summarization tasks. One practical use case is a better starting point than ten disconnected experiments.

[[cta-big]]

Rule 2: Review every output like a fact-checker

Treat every AI output as a first draft. Check it against the source material before it reaches an employee, candidate, manager, or decision-maker. The higher the stakes of the use case, the more rigorous that review should be.

This is important to note because AI can return confident answers that are incomplete, outdated, or influenced by how information is ordered. A 2025 study of ChatGPT as a resume screener found a strong preference for the first resume presented when candidates appeared equally qualified. The researchers ran 2,800 resumes through the model and found that prompt changes reduced one form of position bias but introduced another. That is one reason not to treat an AI comparison, ranking, or recommendation as objective simply because the output looks structured.

Historical recruiting systems show how biased patterns can enter automated recommendations. Amazon abandoned an experimental recruiting tool after finding that it penalized resumes containing terms associated with women, according to Reuters' original reporting.

Use a simple review loop: check, inspect, correct.

• Check: Does anything look inconsistent or implausible?
• Inspect: Is the output accurate, supported by the source, and appropriate for the audience?
• Correct: Edit the draft or send it back with more precise instructions. Then verify the revised output again.

Before an output touches a person:

• Verify legal and compliance claims against current official guidance or counsel.
• Scan for coded or exclusionary language such as "digital native" or "recent graduate."
• For analytical or comparison tasks, test whether changing the order or framing of the inputs materially changes the output.
• Check the tone against your organization's actual voice.
• Confirm that the prompt contained no prohibited data.
• Check names, dates, numbers, citations, policy terms, and other factual claims against the original source.

If the model seems too agreeable, ask for a skeptical review. For example: "Review this announcement from the perspective of an employee who opposes the change. Identify unclear claims, missing context, and likely objections." You can take this a step further by asking it to identify the evidence needed to support claims it cannot verify.

The risk is not theoretical. Mobley v. Workday alleges that automated hiring technology discriminated against Black, disabled, and older applicants; the litigation was still active in 2026, so it should be described as an allegation rather than a finding. Court records show the case and its discrimination claims remain ongoing.

The habit to build early is simple: never let polished output substitute for verification. AI can accelerate the first pass; HR remains responsible for checking what leaves the tool.

Rule 3: Keep employee and candidate data safe

Do not put identifiable employee, candidate, or confidential company data into AI tools unless your organization has explicitly permitted that specific data type and use case in that tool.

Data privacy is already a leading HR concern. In a survey of more than 500 HR professionals, 63% named data privacy and security as a top concern.

What to keep out of AI tools unless explicitly permitted

Anonymization requires more than deleting names. A team of three people may still be identifiable from job titles, location, dates, or demographic details. If the remaining context points to one person, treat the information as identifiable. Use the minimum amount of data necessary for the task, and prefer aggregated, group-level information when individual-level data is not required.

Understand the data settings of the specific tool and plan you use. In personal ChatGPT workspaces, model-improvement sharing is enabled by default but can be turned off. OpenAI says content from ChatGPT Business, Enterprise, Edu, and its API is not used to train models by default. Other vendors have different terms, retention periods, and controls, so be sure to check.

For real HR data, use only an approved business or enterprise environment under your organization's security, retention, access, and contractual requirements. Turning off a training setting in a personal account does not make that account an approved HR system. And an approved enterprise tool does not automatically mean every employee or candidate data type is appropriate to use. Follow your organization's AI policy and rules for the specific data and use case.

Rule 4: Turn one task into a repeatable workflow

Once a task proves useful, document how it works.

The gap between a good experiment and a durable workflow is usually not the AI tool choice. It is whether the team has written down the tool, inputs, review steps, and quality standards. SHRM found that only 16% of HR professionals use their own ROI metric for AI investments, while 56% do not formally measure AI investment success.

Document five things:

1. The approved tool and account type.
2. The trigger or task that starts the workflow.
3. The information that must never be entered.
4. The person responsible for reviewing the output.
5. The definition of a usable result.

If the workflow includes automation, also document where a person must approve, intervene, or handle an exception.

Job description drafting with a second-pass review is a practical example. Instead of asking AI to draft and critique in one prompt, use two separate prompts with two different jobs. The first prompt creates the draft. The second prompt reviews that draft against a defined set of risks and quality standards.

This works because separating creation from critique reduces the chance that the model will simply reinforce its own first answer. It also makes the workflow easier to review: you can see what AI generated first, what it flagged on the second pass, and what a person ultimately changed.

Draft Prompt:

Act as a recruiting manager skilled with writing effective job descriptions. Create a job description for a [role] at a [type of organization] in [industry]. Use only the responsibilities, qualifications, and approved company information below. Do not invent compensation, benefits, or requirements. [Paste approved information.]

Review Prompt:

Check this draft for gendered, exclusionary, unnecessary, or potentially unenforceable language. Explain each concern and suggest a revision. Do not provide legal advice; mark any issue that requires HR or legal review.

The second prompt is not a substitute for human review. It is another quality-control pass before the HR professional checks the source information, evaluates the suggestions, and approves the final version. A person checks both outputs before the job is posted. That review step is part of the workflow, not an optional final polish.

Before scaling the workflow, test it repeatedly and track what still requires correction. A repeatable workflow should produce a consistent enough result that the team knows what to expect, what to review, and when to stop using it.

If your approved tool supports persistent projects or controlled knowledge bases, you can store approved examples and instructions once. Apply the same access and retention rules you would use for any other HR system. Only store content that your organization permits for that specific environment and use case.

Rule 5: Set clear AI use guardrails before you scale

Before AI use spreads beyond a few controlled tasks, document the guardrails employees are expected to follow. If your organization doesn't yet have an approved AI use policy, a one-page interim policy or set of guardrails can be a practical starting point.

According to SHRM's 2026 research, 49% of organizations using or preparing to pilot AI had a workforce AI policy. Among organizations with a policy, only one quarter described it as clear and future-proof; 54% said it was too restrictive and tool-specific, while 23% said it was too broad.

Examples of HR guardrails in practice:

• Recruiting: AI may draft a job description from approved role information, but it may not score, rank, or recommend candidates.
• Performance: AI may organize approved feedback into themes, but it may not determine a performance rating or promotion decision.
• Employee relations: AI may help prepare questions for an investigation or legal consultation, but it may not decide whether misconduct occurred or what discipline should follow.
• Compensation: AI may help HR prepare questions for a pay-equity review, but identifiable compensation data and pay decisions stay within approved systems and qualified human review.
• Employee communications: AI may draft a benefits or policy communication from approved source material, but HR must verify dates, requirements, and legal or policy claims before distribution.

A useful boundary is to keep AI in a support role. It may organize relevant evidence, but it should not independently score, rank, recommend, or make an employment decision. A qualified person should be able to review the underlying evidence, question the AI output, and make an independent decision.

Examples like these make the guardrails concrete. The next step is to capture them in a simple policy that tells employees what is allowed, what requires review, and what is off limits.

A useful one-page interim policy covers:

• Approved tools and permitted use cases.
• Prohibited data and inputs.
• Required human review.
• Named ownership of the final decision.
• A route for questions, corrections, and escalation.
• What employees should do when they are unsure whether a use case is permitted.

As the policy matures, add data classifications, vendor review, bias-testing requirements, employee and candidate notice, recordkeeping, accommodations, an appeal process, and legal review for new high-risk uses.

Keep the first version usable. Employees should be able to tell what they can do, what they cannot do, and when they need help without interpreting a long governance document. Review the policy every three to six months. Write it around data, risk, and decision rights so it survives a change in vendors. Tool names can sit in a separate approved-tools list that is easier to update as technology changes.

Rule 6: Pilot it with a small group and measure what happens

Test the workflow with two or three colleagues, or a small team, before expanding it.

Give a short demonstration, share the approved prompt and review checklist, and collect feedback weekly for the first month. Keep the questions simple: Was the output useful? What was wrong or missing? How much time did the review take? Would you use the workflow again? Also track how much time the workflow saved once review and correction were included.

Some lower-risk HR pilots include:

• Draft a job description from approved role information.
• Create a recurring HR communication from approved facts, dates, and source material.
• Build an onboarding checklist from an existing process or manager guide.
• Summarize an approved policy into plain-language employee guidance.
• Turn approved learning content into a short summary or knowledge-check questions.

These are good first pilots because the source material already exists, the output is easy to verify, and AI is not making an employment decision. When introducing changes to a process or adopting new tools, change management efforts should not be underestimated. Intentional change management strategies have a measurable effect. SHRM reported that organizations following change-management best practices were 2.6x more likely to report successful outcomes.

Protect skill as well as data. A small 2025 MIT preprint on AI-assisted essay writing found lower engagement and recall in some LLM-assisted conditions, but the researchers cautioned against generalizing beyond the study. The useful lesson for HR is narrower: keep people actively involved in reasoning, review, and correction rather than asking them to accept generated work passively. Read the MIT Media Lab study and its limitations.

Define what success looks like before the pilot starts. For a drafting workflow, that might include time saved, number of corrections required, factual accuracy, consistency, and whether reviewers would use the workflow again. Track results by task. If job-description drafts consistently pass review but policy summaries do not, improve or stop the weaker workflow instead of judging the entire pilot as one success or failure.

A pilot should help you decide whether to continue, revise, or stop a specific use case before expanding it.

Rule 7: Approach employment decisions carefully

Use the greatest caution when AI touches hiring, promotion, performance, compensation, discipline, termination, or other consequential employment decisions. These uses can affect a person's livelihood and carry significant legal and bias risk.

In practice, ask how much influence AI has over the employment decision:

• Hiring: AI may organize resume or interview evidence against predefined job criteria, but it should not decide who advances, who is the "best fit," or who should be hired.
• Performance and promotion: AI may summarize approved feedback or organize evidence, but it should not assign a rating, determine readiness for promotion, or recommend an employment action.
• Compensation and employee relations: AI may help prepare questions, summarize approved materials, or identify areas for further review, but pay decisions, investigation findings, discipline, and termination require qualified human judgment and the appropriate HR, legal, or compensation expertise.

For HR, this goes beyond simply whether a human is "in the loop." Ask what the AI tool has already influenced before the person sees the output, whether the reviewer can inspect the underlying evidence, and whether the decision can be made independently of the AI recommendation.

As outlined in the guardrails rule above, AI should not independently score, rank, recommend, or make consequential employment decisions. When AI gets closer to hiring, promotion, performance, compensation, discipline, termination, or other employment decisions, the governance and legal requirements increase.

The legal landscape changes quickly. As of September 2026:

• New York City's Local Law 144 requires covered automated employment decision tools to undergo a bias audit within one year of use, publish audit information, and provide required notices.
• Illinois' amended Human Rights Act has prohibited discriminatory use of AI in employment since January 1, 2026. Illinois Human Rights Commission materials summarize the amendment.
• Colorado replaced its earlier framework with an automated decision-making law that takes effect January 1, 2027. The Colorado Attorney General is developing implementing rules.
• The EU AI Act treats certain employment and worker-management systems as high-risk. The main Annex III high-risk obligations apply from December 2, 2027 under the current implementation timeline. The European Commission explains the scope and dates.
• Federal disability law still matters when employers use AI. The EEOC warns that algorithmic tools can screen out qualified people with disabilities and that employers may need to offer a reasonable accommodation or alternative method. Read the EEOC's current guidance.

Do not rely on a general article for legal conclusions. Confirm the rules for every jurisdiction and use case with current official guidance and counsel. Requirements may depend on where the employer, role, candidate, or employee is located and on how the specific technology is used.

AI uses to avoid in HR decisions

The closer AI gets to influencing a consequential employment decision, the stronger the governance should become. Before using it, ask what role AI is playing, what evidence it is using, what a person can independently review, and what happens when the system is wrong.

FAQs about using AI in HR

Will AI replace HR professionals?

AI can reduce administrative and drafting work, but HR still owns context, empathy, conflict resolution, and accountable decisions. The useful question is not whether AI can produce an output. It is whether the task should be automated, augmented, or kept entirely human.

Is it safe to put employee data into ChatGPT?

Do not put identifiable or sensitive HR data into an AI tool unless your organization has explicitly permitted that specific data type and use case in that environment. Remove direct and indirect identifiers, follow your data-classification rules, and confirm contractual controls for training, retention, access, and deletion. A personal account with training disabled is not automatically an approved HR system.

How do I write better prompts for HR tasks?

Using the CRAFT framework, give the tool context, a role, an action, a required format, and a tone. Add source boundaries and constraints: what information it may use, what it must not infer, and what it should flag for review. Then verify the result against the source material. For recurring work, separate drafting from critique by using a second prompt to review the first output against your quality and risk criteria.

Do we have to tell candidates when we use AI?

Disclosure depends on the tool, use, and jurisdiction. New York City already requires notice for covered automated employment decision tools, and other laws have their own effective dates and requirements. When notice is required, build it into the workflow rather than treating it as an afterthought. Confirm the current requirements for the jurisdictions and use cases involved with official guidance and counsel.

Can AI help make hiring, promotion, performance, or pay decisions?

AI can help organize relevant evidence, but consequential employment decisions require a higher level of scrutiny. Do not rely on AI to independently score, rank, recommend, or make the decision. A qualified person should be able to review the underlying evidence, question the AI output, and make an independent judgment.

Where can I keep learning?

The Ziplines AI for HR Professionals course covers prompting, guardrails, workflow design, and human oversight through practical exercises. SHRM's State of AI in HR 2026 report is a useful benchmark for adoption, governance, and measurement.