AI
AI for Employee Onboarding
AI for HR turns approved company rules into a clear first-day guide. An HR coordinator feeds the documents to the AI and gets a plain-language answer to a new hire's question. This article shows a complete example: two documents, a system access question, a correct and a wrong answer with error breakdown, a copyable prompt, and a line-by-line check.
Two training documents
The AI builds the guide only from the documents you give it. If the prompt sets this limit, it does not invent timelines or add rules of its own.
Every role, time, and procedure in the documents below was made up for this example.
Document 1. "First Day," training version 1, dated 04.10.2026.
"At 09:00 the coordinator runs an intro meeting and hands over an approved read-only copy of the catalog. At 10:30 there is a planned solo session in the CRM, a customer relationship management system that tracks client interactions. Solo work happens only after access is confirmed. If access is not yet confirmed, read the catalog copy you were given; the coordinator will reschedule the CRM session once access lands. The schedule shown does not guarantee access by 10:30."
Document 2. "CRM Access," training version 1, dated 04.10.2026.
"Submit a request to the IT support desk. The CRM owner approves access; after approval the IT desk creates your personal account. You may work in the CRM only under that account. Using a colleague's account is forbidden. Access is confirmed by a successful login to your personal account with the correct permissions. No processing time is set here. The coordinator asks the IT support desk what is blocking access; the coordinator cannot approve access personally."
How does AI answer a new hire's question - and where does it go wrong?
The new hire writes to the coordinator: "CRM won't open. My schedule says 10:30, and a colleague is offering to let me log in under their account. Can I do that, and when will I have my own access?"
The correct answer, drawn only from the two documents:
"You cannot log in under someone else's account. Document 2 says using a colleague's account is forbidden. To get access, submit a request to the IT support desk. The CRM owner approves the request, then the IT desk creates your personal account. Access is confirmed by a successful login to that account with the right permissions. I cannot promise a specific time: Document 2 sets no processing deadline. While you wait, read the catalog copy you were handed. The coordinator will reschedule the CRM session after access is confirmed."
Now here is a deliberately wrong answer to the same question: "Log in under your colleague's account so you make the 10:30 slot. Your access will arrive after lunch."
This answer has two errors.
Error 1: "log in under your colleague's account." Document 2 forbids using a colleague's account outright. The schedule condition does not override that ban - Document 1 itself warns that the schedule does not guarantee access by 10:30.
Error 2: "after lunch." Document 2 sets no processing time for the request. Any specific clock reference - "after lunch," "by evening," "tomorrow morning" - has no support in the text.
The fix: delete both phrases. Keep the request route, the owner approval, the personal account, the login check, and the instruction to read the catalog while waiting for access.
How to write the prompt and check every line of the result
Below is the text you can paste into an AI tool as-is. Both documents appear verbatim.
You are preparing an answer for a new hire based on two documents. Answer only from these documents. Do not add contacts, timelines, SLAs (service-level agreements, promised response windows), or rules that do not appear in the text.
Document 1. "First Day," training version 1, dated 04.10.2026. "At 09:00 the coordinator runs an intro meeting and hands over an approved read-only copy of the catalog. At 10:30 there is a planned solo session in the CRM, a customer relationship management system that tracks client interactions. Solo work happens only after access is confirmed. If access is not yet confirmed, read the catalog copy you were given; the coordinator will reschedule the CRM session once access lands. The schedule shown does not guarantee access by 10:30."
Document 2. "CRM Access," training version 1, dated 04.10.2026. "Submit a request to the IT support desk. The CRM owner approves access; after approval the IT desk creates your personal account. You may work in the CRM only under that account. Using a colleague's account is forbidden. Access is confirmed by a successful login to your personal account with the correct permissions. No processing time is set here. The coordinator asks the IT support desk what is blocking access; the coordinator cannot approve access personally."
New hire's question: "CRM won't open. My schedule says 10:30, and a colleague is offering to let me log in under their account. Can I do that, and when will I have my own access?"
Answer the new hire in plain words. Cover: whether a colleague's account is allowed, the request route, who approves, what confirms access, whether a time can be promised, what to do while waiting, who reschedules the session.
This prompt is for training purposes. The reference answer below was written by the authors of this example.
The reference answer
"Logging in under someone else's account is forbidden. Document 2 says so directly. To get access, submit a request to the IT support desk. The CRM owner approves the request, then the IT desk creates your personal account. You may work in the CRM only under that account. Access is confirmed by a successful login to your personal account with the correct permissions. Document 2 sets no processing time, so I cannot promise a specific moment. While you wait, read the catalog copy you were handed. The coordinator will reschedule the CRM session after access is confirmed."
How to check every phrase against the source lines
Verification works line by line, not by impression. For each key claim in the answer, find the source line in the document.
| Phrase in the answer | Document | Source line |
|---|---|---|
| Colleague's account forbidden | Document 2 | "Using a colleague's account is forbidden" |
| Submit to IT support desk | Document 2 | "Submit a request to the IT support desk" |
| CRM owner approves | Document 2 | "The CRM owner approves access" |
| Successful login with correct permissions | Document 2 | "Access is confirmed by a successful login to your personal account with the correct permissions" |
| No processing time set | Document 2 | "No processing time is set here" |
| Read the catalog copy | Document 1 | "read the catalog copy you were given" |
| Coordinator reschedules the session | Document 1 | "the coordinator will reschedule the CRM session once access lands" |
If the AI wrote "access will arrive after lunch" or named a specific person, no line in either document would support it. That phrase gets cut. AI tools fill gaps with plausible detail, and a prompt narrows the problem but does not eliminate it. Line-by-line checking is required before you hand any guide to a new hire.
What does GitLab's handbook say about HR onboarding?
The GitLab handbook splits onboarding into a general task set and role-specific task sets. People Operations - the company's HR department - owns the checklist template. IT handles access requests, and employees reach them through the #it-help channel. This is an open source; licensed CC BY-SA 4.0, usage terms.
One detail matters for HR: a checkbox in the onboarding checklist can mean "completed" or "marked as not applicable." A tick does not prove the person actually logged into the system.
A separate handbook page on Access Requests names a different route. There, the Corporate Security Helpdesk, the company's security support team, processes requests, while People Connect - the employee services team - handles onboarding and offboarding. The difference in wording between the two pages does not mean one is outdated. The route and approver for any specific system must be confirmed with the responsible owner.
Practical takeaways for the HR coordinator:
- A new hire waiting on access can study approved materials. A technical failure is not a sign of weak skills.
- Do not include personal data, performance reviews, or resumes in the documents you pass to the AI for this exercise.
- Collect feedback on the guide text on a voluntary basis. A small group that responds is not automatically anonymous.
The training documents in this article are not GitLab rules. GitLab shows how another company's process is structured, not a norm for your organization.
The first-day guide, a note to the coordinator, and updating it
The first-day guide has two parts: the schedule from Document 1 and the access instructions from Document 2. Below is a training sample.
First Day. Training version 1, dated 04.10.2026.
09:00 - intro meeting with the coordinator. An approved read-only catalog copy is handed over.
10:30 - solo session in the CRM (customer relationship management system). The session starts only after access is confirmed.
If access is not yet confirmed: read the catalog copy you were given. The coordinator reschedules the CRM session after access lands. The schedule does not guarantee access by 10:30.
CRM Access. Training version 1, dated 04.10.2026.
Submit a request to the IT support desk. The CRM owner approves access. After approval the IT desk creates your personal account. You may work in the CRM only under that account. Using a colleague's account is forbidden. Access is confirmed by a successful login to your personal account with the correct permissions. No processing time is set. The coordinator asks the IT support desk what blocks access; the coordinator cannot approve personally.
Note to the coordinator
Verified in the text: colleague-account ban, request route via IT support, owner approval, personal account, login confirmation with correct permissions, no processing deadline, catalog reading while waiting, coordinator rescheduling the session.
What was not verified: a real login. Text checking confirms the documents agree, but it does not prove a specific new hire has actually entered the CRM. Open question for IT support: what exactly blocks access for this account, and when will it be resolved.
When the document gets a version 2
Suppose Document 2 gets a version 2. One thing changes: instead of "submit a request to the IT support desk," the text now reads "submit a request through the CRM owner's form." The approving owner stays the same. The coordinator still checks with IT support about what blocks access and still cannot approve personally.
What to update in the guide and FAQ:
- In the "how to get access" section, replace the IT-support-desk phrase with the CRM-owner-form phrase.
- In the FAQ answer to "Where do I go if the CRM won't open?" swap in the same updated route.
Everything else stays the same: the colleague-account ban, the personal account, the login check, no processing deadline.
Without confirmation from the person responsible for the document that version 2 supersedes version 1, the priority is not established. You need a named person who says: "From this point, the route is this."
How do you train the HR team to catch AI errors?
Steps for preparing a training exercise:
- Pick the role and its first work task.
- Find the official company rules.
- Confirm the source and your right to share the text with the AI.
- Write the guide using only those rules.
- Test the difficult scenario: the system won't open, the new hire is stuck.
- Hand the guide to the responsible person.
- Collect voluntary feedback on the wording.
For the exercise, give staff the wrong answer from this article: "Log in under your colleague's account so you make the 10:30 slot. Your access will arrive after lunch." Ask them to find two errors and support each one with a specific line from the document.
First error: "log in under your colleague's account" - Document 2 forbids using someone else's account. Second error: "after lunch" - Document 2 sets no processing time for the request.
The correct guide has no errors. The wrong answer has no third error either.
Then move the skill to the version 2 document with the changed route. Ask staff to identify exactly what changed and update only that. One correct answer under the new condition shows attentiveness, but does not prove the skill is locked in.
Three tasks - three different levels of work
| Task | What you need | Role of AI |
|---|---|---|
| Guide and FAQ from existing rules | Approved documents, right to share the text | Reformats into readable language |
| Maintained knowledge base | Document owner, versioning policy | - |
| LMS or HRIS integration | IT project with tickets, testing, and data migration | Drafts a spec or first-pass instruction |
LMS (Learning Management System) is a platform that stores courses and completion records. HRIS (Human Resource Information System) is an HR platform that holds employee data and access permissions. Connecting an LMS or HRIS is a separate IT project with tickets, testing, and data migration.
Frequently asked questions
Can I ask the AI to "do it like GitLab"?
No. The GitLab handbook describes one company's processes, not a universal onboarding standard. You cannot copy their timelines, roles, or contact channels into your company's guide: your organization has different rules and different systems. AI for HR works only from the documents you provide - those become the source of answers for the new hire.
What if the AI adds a contact or a deadline that does not exist in the documents?
Delete that phrase and check the entire answer against the document text line by line. Every claim must have a source line. AI tools fill gaps, and a prompt reduces the problem but does not eliminate it. Line-by-line checking is required before you hand any guide to a new hire.
Should the first-day guide go to a lawyer?
No legal review was performed in this example and none is claimed here. If the guide enters a real HR process, a review of employment law and data protection rules is a separate step. This matters especially if the company operates in multiple jurisdictions or if the guide touches on employee rights. AI helps with the text, not the legal review.
How often should the guide be updated?
The update cycle depends on your company's policy, not a fixed calendar. In this example, changes were made when the request route changed - that is, when version 2 of the document appeared. If the document has not changed, leave the guide alone. Without an approved update policy, do not set arbitrary deadlines like "same day" or "within a week."
Can a new hire borrow a colleague's account in the CRM "for one day"?
No. Document 2 forbids using a colleague's account with no exception for duration. There is no "one day" exception in the document. The approved action while waiting is to read the handed-over catalog copy until personal access is confirmed. A schedule deadline or convenience does not make the violation acceptable.
What does "access confirmed" mean, and why is it not enough to evaluate a new hire?
Access confirmed means a successful login to a personal account with the correct permissions. This proves the system opened for that specific person - nothing more. It does not measure competence. Professional readiness is assessed separately, for example through a supervised test task with real data under a mentor's observation.
How do you train HR staff to find errors in AI answers?
Show a deliberately wrong answer and ask staff to find errors by citing specific document lines. The explanation must be grounded in the text, not in general impression. One correct answer does not prove the skill is locked in. Make the exercise harder: give a changed version of the document and ask what exactly shifted and what to update in the guide.
How to bring AI for HR into real onboarding
AI for HR helps make the onboarding process clearer - it turns approved rules into readable text. The coordinator provides the documents, the AI writes the guide, and a person checks the result line by line.
If you want to see how exercises like these fit into team training, check out the AI training section. Questions: hello@majento.ai, Telegram: https://t.me/shimaoz.