Explaining the process, checking someone’s status and taking an action are three different requests with three different scopes. Each needs its own information and permissions, and its own tests.
Two useful ideas, with different requirements.
In one practitioner discussion, a commenter suggested using AI to handle repeated HR questions and to keep onboarding tasks from slipping through the cracks. Both are worth doing, but they are separate jobs. Knowing the process doesn’t tell you what a particular new hire has completed.
1. Explain the process: “What do I need to do?”
Information needed. The approved onboarding guidance for the relevant role, site or employee group.
A useful response explains the steps, references the source and names the person who can help.
The boundary. Don’t infer that an individual has completed anything from a general checklist.
Practical check: This is guidance, not a readiness decision.
2. Check the status: “What am I still missing?”
Information needed. Authorized access to the employee’s current task record, and what each status means.
A useful response shows the outstanding items on record, and when the record was last updated.
The boundary. A missing record isn’t proof the work was never done. Flag the uncertainty.
Practical check: Access to status is a separate capability to scope and test.
3. Take a defined action: “Can you follow up?”
Information needed. The outstanding task, the person responsible and the agreed follow-up rules.
Permission needed. Define the recipient, the content, the timing and any approval required before sending.
Confirm the outcome. Record whether it was delivered. Prevent duplicates, and stop reminders when the status changes.
Practical check: A message sent is not the same as a task completed.
An exception: the start date changes.
One date changes. What else does it affect?
Verify the approved new date in the designated source of record.
Prepare a list of the affected tasks, with proposed changes to deadlines or communications.
Review and act. Get the approvals required, apply the authorized updates and confirm the actual result.
Practical check: Don’t invent a new deadline or change one silently.
Test across all three scopes.
Guidance. Is it current, and does it apply to this employee’s situation?
Status and access. Is the record current, and can each person see only what they are authorized to see?
Action and responsibility. Is the follow-up permitted and traceable? Who decides when onboarding is complete?
Practical check: Task status alone must not declare someone fit for work or ready for site.
Explain, check, act: scope each one.
Start with the capability that solves the problem. Name the information and permissions it needs, and keep the exceptions with an accountable person. These are distinct scopes, not a ladder you have to climb.
Read more: Are You Prompting AI or Running an HR Workflow? · HR Knowledge Agent