How to Write an AI Acceptable Use Policy for HR Teams
An AI acceptable use policy for HR teams should define which AI tools HR staff may use, which employee data may never enter them, which decisions require documented human review, and what notice employees and candidates receive. It differs from a company-wide AI policy because HR handles the most sensitive personal data and makes decisions that carry legal liability.
Key takeaways
- Write a separate HR addendum to any company-wide AI policy, because HR data and decisions carry higher legal risk.
- Classify HR data into tiers and tie each tier to approved tools, not to vague "use good judgment" language.
- Name prohibited uses explicitly, especially AI making or recommending employment decisions without review.
- Build in notice duties: Illinois has required notice of AI use in covered employment decisions since January 1, 2026.
- Assign an owner, a review cycle and a simple process for requesting a new tool.
Why does HR need its own AI acceptable use policy?
Most company AI policies are written for general knowledge work: drafting emails, summarizing documents, writing code. HR work is different in two ways. First, HR handles data that is sensitive by default, including medical leave records, accommodation requests, investigation notes, compensation and immigration documents. Second, HR outputs often become employment decisions, and those decisions are regulated.
A typical failure looks like this: a recruiter pastes a batch of resumes into a consumer chatbot and asks for the "top five." No one intended to automate hiring, but the organization now has an undocumented selection procedure, candidate data in an unapproved tool and no record of how the shortlist was produced. A general policy that says "do not share confidential information" did not prevent it because it never addressed HR-specific scenarios.
If you have already published broad guidance for all employees, as discussed in our piece on giving employees guidance on workplace AI tools, treat the HR policy as an addendum with stricter rules for the people who handle workforce data.
What should an HR AI acceptable use policy include?
Keep the policy short enough to read in ten minutes, with detail moved into appendices. These are the clauses that matter most.
1. Scope and definitions
State who the policy covers (HR, talent acquisition, payroll, HR operations, people analytics, and contractors doing HR work) and define "AI tool" broadly. Illinois Public Act 103-0804 defines artificial intelligence as a machine-based system that infers from inputs how to generate outputs such as predictions, content, recommendations or decisions, and it expressly includes generative AI. Borrowing a statutory definition avoids arguments about whether a feature "counts."
2. Data classification tiers
Tie data sensitivity to tool approval. A simple three-tier model works for most teams:
| Tier | Examples | Allowed in |
|---|---|---|
| Public or general | Published job postings, public policy summaries, generic templates | Any approved AI tool |
| Internal personal data | Names, job titles, schedules, performance goals | Enterprise AI tools with a signed agreement that bars training on your data |
| Restricted | Medical and leave data, accommodations, investigations, compensation, Social Security numbers, immigration records | Only tools specifically approved for that data, or none |
3. Approved tools list
Maintain a list of approved tools and the highest data tier each may receive. Make it a living appendix owned by HR technology so the policy text does not need to change every time a tool is added.
4. Prohibited uses
- Using AI to make or recommend a hiring, promotion, discipline, termination or pay decision without documented human review.
- Entering restricted data into any tool not approved for it, including personal accounts on consumer AI products.
- Using AI to infer protected characteristics, health conditions or union activity.
- Using ZIP codes or similar proxies for protected classes in any model or screening rule.
- Sending AI-generated communications about leave, benefits or pay eligibility without checking them against the source policy.
The ZIP code item is not hypothetical. The Illinois amendment makes it a civil rights violation for an employer to use AI that has the effect of subjecting employees to discrimination, or to use ZIP codes as a proxy for protected classes.
5. Human review and accountability
Specify where a person must review AI output before it is used, who that person is, and how review is recorded. The NIST Generative AI Profile (NIST AI 600-1) identifies confabulation, meaning confident but false output, as a core generative AI risk. For HR, that means a named reviewer for anything that states a policy, a number or an eligibility rule.
6. Notice and transparency
List the situations where employees or candidates must be told AI is in use. Illinois requires notice when AI is used for covered employment decisions such as recruitment, hiring, promotion, discipline and discharge. New York City requires notice before using an automated employment decision tool. Under California's privacy regulations, businesses using automated decisionmaking technology for significant decisions, which include hiring, work allocation, compensation, promotion and termination, must comply with pre-use notice and related requirements by January 1, 2027.
How do you handle AI features inside existing HR systems?
Many AI features arrive through updates to systems you already own: an HRIS that drafts job descriptions, an ATS that ranks applicants, a service desk that suggests answers. These bypass a policy that only governs "new tools." Add a clause requiring HR technology to review AI features before they are switched on, and to document whether the feature influences decisions about people.
The risk is greater when HR builds its own automations. Our article on the compliance gap in HR-built AI agents covers what happens when a no-code workflow starts making employment decisions without anyone classifying it as a selection tool.
Who should own and enforce the policy?
Ownership should sit with the CHRO or a delegate in HR operations, with legal, privacy and security as required reviewers. Practical enforcement depends less on discipline and more on making the approved path easy:
- Provide at least one approved enterprise AI tool so staff are not tempted to use personal accounts.
- Publish a one-page request form for new tools, with a target turnaround time.
- Train HR staff with realistic scenarios, such as summarizing an investigation file or drafting a termination letter.
- Log AI-assisted decisions in the same system of record as the decision itself.
- Review the policy at least annually and whenever a relevant law takes effect.
What mistakes make HR AI policies fail?
- Too abstract. "Use AI responsibly" gives no guidance at 4 p.m. on a busy day. Use examples.
- Ban everything. Blanket bans push usage into personal accounts where you have no visibility.
- No data tiers. Without tiers, staff cannot tell whether a performance note is acceptable to paste.
- Ignoring vendors. The policy should require vendor terms that bar training on HR data and allow deletion.
- Forgetting privacy law. Employee data rights still apply when AI is involved; see our overview of GDPR and employee data privacy in HRMS.
Frequently Asked Questions
Is an HR AI policy different from a company-wide AI policy?
Yes. A company-wide policy sets general rules for all employees. The HR addendum adds stricter data tiers, prohibited decision uses, human review steps and notice duties because HR handles sensitive personal data and makes regulated employment decisions. Both documents should use the same definitions and approved tools list so they do not conflict.
Can HR staff use consumer AI chatbots at work?
Only for public or general information, and only if your organization allows it. Personal or restricted employee data should go only into enterprise tools covered by an agreement that controls retention and prohibits training on your data. Spell this out with examples so staff can decide quickly without escalating every question.
Do employees need to be told when HR uses AI?
In some places, yes. Illinois requires notice when AI is used for covered employment decisions, New York City requires notice before using automated employment decision tools on candidates and employees, and California privacy rules add ADMT notice duties from January 1, 2027. Even where not required, notice builds trust and reduces disputes.
How often should the HR AI policy be updated?
Review it at least once a year and whenever a new law takes effect, a major vendor changes its AI features or you adopt a new category of tool. Keep the approved tools list in an appendix so it can change monthly without re-approving the whole policy.
Practical next steps
- Inventory the AI tools and features HR staff already use, including personal accounts.
- Draft data tiers and the approved tools list first, then the prohibited uses.
- Confirm notice duties for every state and city where you hire.
- Pilot the draft with recruiters and HR business partners and revise based on their questions.
- Publish, train and schedule the annual review. More governance resources are in our AI in HR guides hub.
Last reviewed: October 2026.
Sources
- Public Act 103-0804 (HB 3773), Illinois General Assembly
- Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile (NIST AI 600-1), National Institute of Standards and Technology
- CCPA Updates, Cybersecurity Audits, Risk Assessments, Automated Decisionmaking Technology, and Insurance Companies Regulations, California Privacy Protection Agency
- Automated Employment Decision Tools (AEDT), NYC Department of Consumer and Worker Protection
Comments
Post a Comment