The fictional Germany handbook points employees to the country-specific parental-leave guide and the people-team reviewer for their circumstances. Open that reference before starting a request. This is an invented company-policy example; it does not state German statutory entitlements, determine eligibility or replace advice from the responsible HR team.
Germany policy reference: consult the parental-leave guide for the relevant employment arrangement and contact the people-team reviewer before submitting a request. This fictional handbook does not describe statutory entitlements.
AI for HR should make a policy easier to inspect
People teams answer recurring questions about leave, benefits and onboarding while managing information that should not be available to everyone. Those are different responsibilities. A connected policy collection can support routine questions without treating the entire HR repository as suitable context for every employee.
An HR knowledge base is a maintained collection of policies, procedures and answers with named owners and review dates. Begin with employee-facing guidance approved for sharing, and make clear where people should ask about an exception. An AI HR assistant can help compatible clients consult that collection and inspect the source; it should not decide eligibility, compensation or an employment outcome.
Before considering sensitive employee records, review the live access behavior, processing terms and the organization’s obligations. The restricted examples here use fictional data and demonstrate a visible withheld state. They do not prove that a particular HR deployment protects salaries or personal records, and they are not a reason to import those records without assessment.
Keep the human route prominent. A policy may describe a normal procedure but leave a personal circumstance unresolved. An employee should know who can interpret the guidance and correct outdated information. Use the questions people ask to improve the maintained policy, rather than allowing unreviewed assistant responses to become an unofficial replacement for it.
Connect. Ask. Govern.
From scattered documents to a shared answer
01
Connect approved HR guidance
Choose current policy references, manager guidance and the employee-facing process collection. Name the policy owner and review date. Keep private employee cases outside the starter collection rather than treating every HR file as general guidance.
02
Ask for the policy and its exception
Ask how the published process routes a request and inspect the relevant clause. Bring unclear eligibility, local requirements or personal circumstances to the responsible HR professional instead of turning a generated explanation into a binding determination.
03
Govern confidential personnel knowledge
Separate employee guidance from private case records. Test the actual asker’s scope with synthetic material and review membership when responsibilities change. A limited-access example explains the boundary without requiring real employee data in a pilot.
See the idea in action
ai for hr: questions with evidence
Fictional examples. These interactions do not query your Brain or test real permissions.
The fictional Germany handbook points employees to the country-specific parental-leave guide and the people-team reviewer for their circumstances. Open that reference before starting a request. This is an invented company-policy example; it does not state German statutory entitlements, determine eligibility or replace advice from the responsible HR team.
Fictional Germany employee handbook
Germany policy reference: consult the parental-leave guide for the relevant employment arrangement and contact the people-team reviewer before submitting a request. This fictional handbook does not describe statutory entitlements.
The two fictional policy versions show a process change: the earlier guide allowed receipts to be supplied on request, while the current guide asks for the receipt with the initial claim. Inspect both excerpts before following the current procedure. This example does not approve an expense or establish a real company policy.
Fictional expenses guide · prior version
Prior version: provide the supporting receipt when the expenses reviewer requests it.
Fictional expenses guide · current version
Current version: attach the supporting receipt with the initial expenses claim. The reviewer handles exceptions through the existing process.
The fictional export places the example learning coordinator in the People team and names a people-team owner for review. Its table is illustrative source material, not a ready HRIS connector or a real employee record. Verify supported formats, processing terms and access before considering an actual export; leave personal records outside a general policy pilot.
Fictional HRIS export illustration
Illustrative row: role, Learning coordinator; department, People; review owner, People-team lead. No employee identifiers or salary fields. This is an invented export example, not a live HRIS connection.
The fictional salary planning file belongs to a restricted people-team collection. In limited-access mode, the example displays a withheld notice without its answer or source excerpt. This is a demonstration of a UI state, not a claim that a live HR repository has been tested. Salary information should remain outside a general employee-policy pilot.
Salary planning illustration
Restricted example: salary planning is available only to the authorized people-team group.
Open a question, then inspect its source excerpts.
Brain is a knowledge layer reached through MCP, the Model Context Protocol. Claude, Cursor and Codex are examples of compatible clients in the existing product. Client support and setup differ, so check the current connection instructions rather than assuming every assistant has the same capabilities.
The current public setup describes Google Drive and Notion as connected sources, alongside documents you choose to add. Start with a focused collection and inspect the actual connection screen for availability. A tool appearing in a roadmap or illustration does not mean its connector is ready for your account.
Google Drive
Connect the documents your workspace needs.
Notion
Bring approved pages into a shared knowledge layer.
Your documents
Add a focused set of knowledge you own.
Keep access intentional
Separate policy answers from individual employee cases
An employee-facing policy can have a broad audience while an investigation or personal record remains restricted. Deliberately scope each collection and review the current processing terms before including personal information. Brain helps locate and explain references; the HR owner assesses individual circumstances and approves any employment action through the established process.
Fictional content-blind access record
Actor
Example teammate
Action
Read approved source
Outcome
Allowed within the example workspace
Fictional metadata only. No document content is shown, and this is not a record from your account or proof of live enforcement.
Use the relevant policy context for a practical question
A leave-process question may need the applicable clause, definition and exception rather than the whole employee archive. Compare the answer with the approved policy and measure actual context usage. Include retrieval and output charges in the budget, and never trade away a necessary exception merely to produce a smaller token count.
Provides a human route for personal circumstances, exceptions and employment decisions. Repeated policy-location questions still need maintained guidance and a named owner.
An FAQ-based HR chatbot
Can present a curated set of policy answers. Review how its team updates those answers, shows supporting references and routes questions it cannot resolve; capabilities vary by product.
Pasting the handbook into ChatGPT
May help explain the text supplied in that conversation. ChatGPT for HR still requires approved material, appropriate account terms and current policy versions. Do not paste employee cases or restricted salary records without assessment.
An approved HR knowledge base with Brain
Lets compatible clients consult maintained policy references with citations. The people team owns interpretation, individual cases and employment actions; the fictional examples do not certify a sensitive deployment.
ai for hr: frequently asked questions
Which HR questions are suitable for a knowledge pilot?
Start with questions about locating approved policies, finding onboarding instructions and identifying the owner of a process. Use employee-facing documents that the organization has approved for sharing. Keep personal employee records and employment decisions outside the initial collection. Review answers against their sources and provide a clear route to the people team.
What should HR review before connecting employee data?
Review the data categories, processing terms, access controls and the organization’s legal and privacy requirements. Test the intended boundaries in the actual configuration before importing sensitive records. The illustrations here use fictional information and do not establish live protection. Begin with approved policy material while the responsible owners assess any broader use.
Can employees consult approved HR policies themselves?
An employee-facing collection can help people find a policy and inspect the section behind an answer through a compatible client. Give employees a clear way to ask a human about personal circumstances or exceptions. Keep the original document maintained, and review which sources each employee is permitted to consult in the actual deployment.
Does the salary example prove HR confidentiality?
The salary example is a fictional presentation of a withheld response. It removes the example answer and source from the limited-access view, but it does not test a real backend or establish confidentiality. HR should verify source and workspace access using separate permitted and denied identities before considering any sensitive employee-information workflow.
How does policy knowledge support a new manager?
A maintained collection can make manager guidance, onboarding preparation and routine people processes easier to locate. The manager should inspect the cited source and confirm any role-specific requirements with the people team. Connecting the guidance does not authorize an action or make an employment decision; the responsible people and systems still carry out the process.
How should HR correct an inaccurate policy answer?
Check the cited source first to see whether the policy is outdated, ambiguous or interpreted incorrectly. Ask the policy owner to correct the original document when needed, then repeat a representative question after the update is available. Keep a human escalation route for unresolved cases. An assistant’s fluent wording should never override approved policy.
What is an HR knowledge base?
An HR knowledge base is a maintained collection of approved policies, procedures and reference answers. Each item should have an owner, audience and review date. Brain can help compatible clients consult those references with sources; the people team remains responsible for correcting guidance, handling individual circumstances and approving employment decisions.
Start with the questions in your handbook
Use approved employee-facing guidance for your first knowledge workflow. Keep personal questions and consequential decisions with the people team.
Fictional Germany employee handbook
Fictional expenses guide · prior version