HR's drill should rehearse a confidentiality failure, where an HR agent does most harm fastest. Use a scenario in which the query agent includes a colleague's sickness details in a reply. In about 90 minutes, HR advisers practise pausing the agent to draft-only, escalating to the HR director and data protection officer, recording decisions and handling the breach.
What does an HR drill rehearse?
HR teams use agents to answer employee questions about policies, leave and benefits, to draft letters for absence management, and to prepare documents for recruitment and onboarding. A query agent may answer policy questions at depth 3 within bounds; letters about individuals are drafted at depth 2 for an HR adviser to approve. Sickness records, disciplinary matters and pay are among the most sensitive data an organisation holds, and health information is special-category data under GDPR.
The HR director owns the drill. A senior HR adviser facilitates. HR advisers, the data protection officer, someone from IT and an employee relations specialist take part. For the format, see what an incident drill is.
The scenario
Tuesday, 10:30. An employee forwards a reply from the HR query agent to her manager, puzzled. She asked how much sick leave she had left. The reply gave her figure correctly, then quoted the absence history of a colleague with a similar name, including the reason for absence. An HR adviser checks: a recent change merged two employee lookup sources, and for employees with matching surnames the agent sometimes retrieved the wrong record. The agent answered about 400 queries since the change.
The drill, step by step
- Person (facilitator): reads the scenario and starts the clock.
- Person (HR adviser receiving the forward): escalates to the HR director and DPO at once. The test is whether the adviser recognises a data breach rather than a typo.
- Person (HR director or delegate): pauses the agent to draft-only. Every reply is held for an HR adviser. The verdicts name the organisation's own limits as the deciding bound.
- Person (IT): reverts or fixes the lookup change and confirms when it went live.
- Person (HR adviser): lists from the record every reply that drew on a record other than the requester's. The agent's sources are logged with each verdict, which makes this possible.
- Person (DPO): assesses the breach. Whose data was disclosed, to whom, how sensitive, and whether notification to the data protection authority or the people affected is required under the rules that apply.
- Person (employee relations specialist): plans conversations. The colleague whose data was disclosed should hear it from a person, privately and soon. The employee who received it is asked not to share it further.
- Person (HR adviser): records each decision with owner and time.
- Person (facilitator): runs the debrief.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Alert | Has answered queries | 3 | Recognising a breach |
| Pause | Holds every reply | Dropped to 2 | Tightening limits |
| Fix | Nothing | 2 | IT revert |
| Scope | Nothing new | 2 | Listing affected replies |
| Assess | Nothing | 2 | DPO's breach assessment |
| Conversations | Nothing | 2 | Employee relations |
| Record | Files verdicts | 2 | People's decisions |
What is specific about HR incidents?
The people affected are colleagues. The employee whose sickness was disclosed works alongside the one who received it. HR must protect both, and the conversations matter as much as the technical fix.
The drill also shows why the agent should never answer about one person using data drawn from another. A useful debrief outcome is a new bound: the agent may only use records that match the requester's verified identity, and any mismatch is refused. That is a change to the agent's bounds, filed in the record like any other change.
Include managers in the scenario. The employee forwarded the reply to her manager, so a third person has now seen the data. HR should brief the manager on confidentiality, and the drill should practise that short conversation.
Which controls does the drill test, and what evidence do they leave?
The pause. Evidence: the limit change in the record, name and time.
Scope from the record. Each verdict records the sources used. Evidence: the list of affected replies.
Breach assessment. Evidence: the DPO's written assessment and any notification, with times.
Conversations. Evidence: a note of each conversation, kept in line with HR's own confidentiality rules.
This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
What should the HR director measure?
- Time from the forwarded email to the pause.
- Time to the DPO's breach assessment.
- Time until the colleague whose data was disclosed was told in person.
- Whether the new identity-matching bound was in place before depth was restored.
Where do HR drills go wrong?
Treating it as an IT issue. IT fixes the lookup; HR owns the breach and the people.
Telling the affected colleague by email. Disclosure of health information deserves a private conversation.
Restoring depth 3 when the lookup is fixed. Add the identity bound first, then check a sample of replies.
HR's neighbours face related risks: the payroll team drill covers pay errors, and the fraud team drill covers adversaries probing bounds. Build your own scenario with the AI agent incident drill script template. The training behind a drill is set out in how to train a team to handle an AI agent incident and training teams for AI agents.
Questions people ask
Should an HR agent answer questions about an individual's records at all?
It can, at depth 3 within strict bounds, once certified and with identity matching. Many organisations keep sensitive categories, such as sickness reasons, at depth 2.
Who tells the employee whose data was disclosed?
An HR adviser or employee relations specialist, in person or by private call. The DPO advises on what must be said.
How often should HR drill?
Once or twice a year, and after any change to employee data sources or the agent's capabilities.