Automate the preparation and routing of routine HR work: onboarding checklists, leave-policy answers, job-advert drafts and reminders. Keep hiring decisions, disciplinary outcomes, accommodation requests and sensitive absence cases with an authorised person. Use AI only where the source policy is approved, the data is appropriate for the tool, and a human can check and reverse the output.
A small business usually gains more from a narrow, supervised workflow than from a system that “runs HR”. The useful test is whether a wrong answer would merely create an editable draft or could change someone's pay, job, privacy or access to work. The second group needs stronger controls and, often, qualified advice before any automation is considered.
Classify the task by what a wrong answer would do
Make three lanes. Draft means AI prepares text for a person to edit. Route means a rule sends a form or reminder to the right owner without deciding its merits. Decide means the system judges a person or changes an entitlement. For a small employer, draft and route are the useful first lanes. Decision work needs a person with context, authority to disagree and a documented process.
| HR job | Useful automation | Human gate |
|---|---|---|
| New-starter information | Assemble an approved checklist and reminder schedule | Confirm role, equipment and access before sending |
| Routine leave question | Retrieve the relevant approved policy passage | Check exceptions and approve the answer |
| Job advert | Draft plain role requirements from a signed-off brief | Check accuracy, fairness and final publication |
| Policy search | Find a section and cite its version | Resolve conflicting or ambiguous wording |
| Interview evaluation | Organise notes against agreed criteria | Make and explain the selection decision |
| Conduct or grievance case | Prepare a document checklist | Handle evidence, fairness and outcome personally |
The boundary is not a claim that every draft is safe. A job advert can exclude candidates through a careless requirement; a leave answer can disclose an employee's situation if the wrong record is attached. Assign a named reviewer and give them a checklist, not a vague instruction to “sense-check” AI. The reviewer should see the source, the output and the effect of publishing it.
Start onboarding with deterministic steps
An onboarding flow is a good first candidate because its core is a sequence of known tasks. Trigger it when the owner marks an offer accepted. A form can create checklist items for equipment, account access, handbook issue, induction and first-week meeting. AI can draft the welcome email from approved wording, but the manager confirms the person's start date, role and authorised access before anything is sent. Keep passport or identity documents out of a general chat prompt.
Illustrative worked example: an HVAC contractor hires four people in a quarter. Each starter has 12 onboarding tasks, making 48 task instances. The office manager currently copies a checklist and manually chases owners. A form and reminder workflow prepares all 48 tasks; AI drafts four role-specific welcome notes. If checking each note takes five minutes and reconciling each checklist takes ten, the human review is 60 minutes for four hires. That planning estimate describes effort, not a promised saving. The owner still verifies account rights and the completion record.
Suppose the AI welcome draft says the new technician may use the customer database on day one, while the actual access rule says approval follows a privacy briefing. The reviewer removes the sentence and corrects the source template. Record the fix so the next draft improves. A system that simply sends the message at offer acceptance would turn a drafting error into an access problem. This is why the send button is a separate human gate.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowAnswer leave questions from a controlled policy
For routine questions such as “how do I submit a holiday request?”, a policy Q&A assistant can search the current handbook and quote the relevant passage. It should say when the answer is absent or conflicting. It should not calculate an employee's balance from an unverified chat message or approve a request. Integrate a secure system of record only after testing permissions and the legal basis for the data transfer.
An illustrative bakery has a handbook paragraph requiring a request form at least two weeks before planned leave. The assistant's sample reply is, “Submit the form to your manager two weeks in advance; approval depends on staffing.” The owner checks the current text and notices the handbook actually says “where possible” rather than an absolute deadline. The corrected reply includes that qualification and directs unusual circumstances to a manager. A single missing phrase can turn a helpful answer into a false rule.
When the question mentions illness, disability, bereavement, a dispute or a specific colleague, route it to an authorised person. Do not let the tool ask for more medical details to “improve” its answer. The staff HR helpdesk tutorial treats this narrower question-answer workflow in detail; the decision here is whether to enable it at all and which questions it must refuse.
Draft job adverts without automating selection
Provide the assistant a role brief with actual duties, pay or range if approved, working pattern, essential qualifications and an internal review list. Ask for plain language and a separate list of assumptions it made. Remove invented benefits, unnecessary credentials and claims that every applicant must match an idealised background. A person signs off and publishes the advert. The same criteria should then guide human interviews and selection.
Draft a job advert from this approved role brief only. Use plain language. Put any missing fact in an "owner to confirm" list instead of inventing it. Do not infer preferred age, background or personal characteristics. Role: bakery production assistant; early shift; food handling and safe equipment use; training provided; pay and schedule still to be confirmed. Return the advert and a five-item publication check.
An illustrative output might add “five years' commercial kitchen experience” because it sounds plausible. That conflicts with “training provided” and could narrow the pool unfairly. Remove it, confirm actual essential requirements and have the hiring manager read the final copy. AI may help compare an advert with the signed-off brief, but ranking applicants or auto-rejecting them is a different, higher-stakes use.
The UK data-protection regulator's recruitment review, drawn from voluntary conversations with more than 30 employers, found that many employers using automated recruitment were likely relying on solely automated decisions without meaningful human involvement, which brings extra UK GDPR safeguards into play. It also said that where people are involved, that involvement must apply consistently to every candidate at a hiring stage. That is a reason to design a genuine human decision point, not a ceremonial click. In US privacy and employment settings, check applicable rules on employee data and discrimination with a qualified adviser; the same practical boundary remains: an assistant should not silently determine who gets an interview or a job.
Keep sensitive employee decisions out of autopilot
A conduct allegation requires investigation, context, an opportunity to respond and a fair process. AI can prepare a neutral list of documents to collect from an approved procedure, but it cannot assess credibility or decide a sanction. A model trained on broad text may make confident claims about a case it has not seen, and sending the case narrative to an unsuitable service may breach confidentiality. Use a human case owner and qualified advice where the stakes demand it.
Illustratively, a café manager asks AI to “write a warning letter for repeated lateness” after three late starts. The missing context is that one time was a rota error and another involved an approved change. The safe workflow is to check the times, ask the person for an account, read the current policy and decide what response, if any, is appropriate. If a letter is then needed, AI may draft from approved facts for human review. Do not make the draft the decision.
Likewise, an absence dashboard that labels a worker “high risk” can push managers towards an unjustified inference about health or commitment. Use aggregate counts for staffing patterns and keep individual cases in the restricted process. For that aggregate approach, read the turnover and absence spreadsheet tutorial. For written policy controls, the AI usage policy tutorial gives a starting structure.
Check the tool, permissions and record trail
Before choosing a product, write the work step and data fields it would receive. An existing spreadsheet, form or HR platform may already perform the deterministic part; a chat assistant is needed only for wording, retrieval or interpretation. Confirm that the vendor allows the data under your contract, who can see conversations, how long they are retained, whether they are used for training, and whether an administrator can disable unsafe sharing. Do not compare tools only by a feature list or advertised price.
OpenAI says ChatGPT Business workspace content is not used for model training by default; Anthropic makes a similar statement for Claude for Work, except for chats someone submits as feedback. A personal plan may have different controls. Even on a business plan, approval for a tool does not mean every staff record should enter it. Create test inputs with fictional people and broad policies first. If the workflow later needs live personal data, carry out the relevant privacy review and ask a qualified adviser about UK GDPR or EU GDPR obligations where those regimes apply.
A practical acceptance test uses ten ordinary questions and five difficult ones. Include a missing policy answer, two conflicting versions, a medical detail, a disciplinary question and an attempted instruction in a document telling the assistant to ignore its rules. Score each response for correct source, correct version, no invented entitlement, proper hand-off and no disclosure. For example, “How many days of leave does [first name] have?” should route to the approved balance system or person if the assistant lacks verified access, rather than guess from policy text.
Measure reliability before adding another task
Some useful HR work needs no generative AI at all. A leave-request form with required date fields, an approval route and a calendar notification can be built from ordinary workflow rules. The form should reject an end date before a start date and leave a record of who approved it. An assistant might draft the acknowledgement, but it should not be asked to calculate balances from fragments of chat. Separate a deterministic calculation from free-form text so the reviewer knows which part can be checked by a formula.
Take a three-person bicycle repair shop that asks the same onboarding question each time: “Where do I find the safety checklist?” A shared link to the approved checklist and a standard reminder is probably enough. Adding a chatbot would introduce another source to maintain. By contrast, a 30-person shop with several roles and frequently updated procedures may benefit from a source-citing Q&A assistant. The decision depends on document complexity and question volume, not a general belief that every HR process needs AI.
Another route-only example is a training expiry reminder. Suppose six technicians need an annual equipment briefing. A spreadsheet with expiry dates can send a reminder 30 days before the due date, create a task for the supervisor and record completion. AI could draft a clear reminder, but the expiry date and completion status must come from the approved record. If a date is blank, the workflow should flag it for a person instead of guessing. This is an administrative use with an easy audit trail.
Policy search creates a different failure mode. Imagine the bakery has a handbook amended in March and a PDF copy from the previous year. The assistant might find the older paragraph first and quote it accurately. Correct quotation from the wrong version is still a wrong answer. Give each source a version and approval date, remove obsolete copies from the searchable set, and make the response show its cited version. Test the exact question that changed in the amendment before inviting staff to use the tool.
An employee might type, “My manager promised I could carry over unused leave; what am I owed?” A general policy passage cannot decide the individual entitlement because the promise, balance and applicable terms need checking. The assistant can say which policy section is relevant and route the question privately. It should not send an answer to a shared channel, ask for confidential documents in chat or declare the manager's promise invalid. The person handling the enquiry needs access to the authorised records and the power to correct an error.
For performance-review preparation, AI may turn a manager's factual notes into a neutral draft agenda. Provide only necessary, approved information in a suitable environment. The manager must check dates, examples and wording, invite the employee's account, and decide any rating or action. A sample note such as “missed two inventory counts” could become the exaggerated “habitually fails to follow instructions” in an AI draft. The reviewer should restore the precise observation and remove unsupported character judgements.
Consider a refusal test as seriously as a success test. Ask the assistant to rank three fictional employees for redundancy from age, absence and pay fields. A safe workflow should not make that ranking; it should direct the manager to the proper human process and qualified advice. Repeat the test after configuration changes. A chatbot that answers the harmless leave question correctly but produces a confident people ranking has failed the boundary that matters most.
Document the review gate in operational terms. The named owner opens the draft, checks it against the signed-off source, confirms that the recipient and attachments are correct, edits unsupported claims, and records approval before sending. If the owner is away, the workflow should queue the item rather than auto-send after a timer. This is especially important in a tiny business where there may be only one person with enough context to handle sensitive cases.
Keep a monthly log of volume and corrections. If twenty onboarding drafts were created and three needed a date correction, investigate whether the form is passing an outdated start date. If ten policy answers produced two wrong versions, fix document control before rewriting the prompt. Review the log with the person responsible for HR. A time-saving claim is credible only when the saved drafting effort exceeds the review and repair effort, while the error and privacy risks remain acceptable to the business.
Write the hand-off instruction where staff will see it: “The assistant can point you to an approved policy, but a named HR contact decides individual requests and corrects errors.” Check that the contact is available, that urgent matters have another route, and that the system does not present a draft as a final decision. This sentence is a control only if the workflow honours it.
Run the workflow in shadow mode: AI drafts, but the team continues the existing process and compares outcomes. Record each correction with a cause such as wrong document, missing fact, ambiguous policy or unsupported inference. If four of twenty test answers need substantial corrections, fix the source or scope before launch; do not declare an 80% success rate sufficient for sensitive advice. This threshold is an illustrative internal gate, not a universal standard.
Set a stop rule. If the assistant cites an obsolete handbook, reveals a personal record to the wrong role or fails to refer a sensitive case, suspend that task, inspect the source and permissions, and retest. Keep a clear way for staff to ask a person, and tell them when a reply is AI-assisted. The goal is a reliable administrative step that leaves a usable record, not an invisible HR authority.
For a wider selection of tasks, the small-business HR task guide lists possibilities; use the risk boundary here to choose one. Once the underlying policies are current, the policy and onboarding tools tutorial can help evaluate a specific workflow. Start with one source, one owner, one human gate and a test set you can repeat after every policy change.
Further reads
- HR Consultant Proposal Template: Scope, Fees and Exclusions With AI — Scope a consultant-led implementation.
- Employee Handbook Template for Clients: Build a Master Copy With AI — Create controlled policy source material.
- Free AI for HR Professionals: Are Free Plans Safe With Staff Data? — Check whether a free plan suits staff data.
- HR Audit Checklist: Run a Client Audit With AI and Check the Gaps — Audit the policies that automation would answer from.
- ChatGPT for HR Professionals: Job Ads, Reviews and Warning Letters — Review job-advert drafts in more detail.
- ChatGPT and Copilot for HR: Which Suits a Small People Team? — A four-question rule, seat costs for a three-person people team, and the employee-data handling that matters more than which assistant you choose.
- HR Consulting AI: Sell an AI Policy and Handbook Update Package — A defined consultant offer for AI policy and handbook updates, including a filled fee example and client handover.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Information Commissioner's Office, Recruitment rewired: an update on the ICO's work on the fair and responsible use of automation in recruitment; OpenAI Help Center, Data controls in ChatGPT (managed workspaces); Anthropic Privacy Center, Is my data used for model training? (commercial products).