Which Handbook Applies? HR Across Multiple Companies

A growing number of HR teams do not support one company. They support several. A founder owns a main business and a handful of smaller ones, a private equity group rolls up regional firms, or a parent company keeps acquired brands as separate legal entities. On the org chart, HR is one team. In practice, HR is running four or five sets of policies at once, and every question that comes in starts with a hidden first question: which company is this person in, and which handbook applies to them?

The usual response is to build or buy a system. An HRIS gets scoped, a pilot company is chosen, and the plan is to prove it out and roll it to the rest of the group. That is a sensible plan for people data. It does not solve the problem that actually drives most of the confusion.

Why is HR so hard when you support multiple companies?

Because each entity carries its own history. One company was founded with a generous PTO policy and never changed it. Another came through an acquisition with its own benefits carrier. A third has employees in a different state with different leave requirements. A fourth was set up recently and borrowed the parent's handbook with a few edits nobody tracked.

Each of those differences is reasonable on its own. Together they mean that the same question, how much bereavement leave do I get or when does my 401(k) match vest, has four or five different correct answers depending on who is asking. HR staff learn to answer from memory, which works until the person with the memory is out, or until someone answers a question from the wrong company's policy.

Does an HRIS answer employee policy questions?

Mostly, no. An HRIS is a system of record for people data: who works where, in what role, at what pay, with what benefits elections and time off balances. It is essential, and every multi-entity group eventually needs one. But the answers to most policy questions are not fields in a database. They are paragraphs in handbooks, benefits summaries, offer letter templates, state-specific addenda, and email threads where an exception was approved.

Those documents live wherever each company happened to keep them: a SharePoint site for the parent, a Google Drive folder for the acquired firm, attachments in an HR inbox for the newest entity. Gartner found that 47 percent of digital workers struggle to find the information they need to do their jobs, and that the average desk worker now uses 11 applications, up from six in 2019. Multi-entity HR is that problem multiplied by the number of companies in the group.

What goes wrong when employees get the wrong policy?

Most of the time, the cost is friction. An employee reads the parent company's handbook, plans leave around it, and then learns their entity's policy is different. A manager approves a remote work arrangement that one company allows and another does not. New hires at a smaller entity get onboarding materials written for the larger one and spend their first weeks asking which parts apply.

Some of the time, the cost is real exposure. Pay practices, leave entitlements, and benefits eligibility are areas where giving an employee the wrong answer can create a claim. When HR cannot quickly show which policy applied to which employee at which time, every dispute becomes a manual reconstruction from old files and email. That is as much a compliance and audit problem as it is an HR one.

How do you manage HR policies across multiple companies?

Two things have to be true. First, the policies themselves need a clear structure: what is shared across the group, what is entity-specific, and which version is current. Many groups land on a shared core handbook with addenda per company. Second, people need to be able to find the right version without knowing where it is stored or what it is titled.

The second part is where retrieval-augmented generation, or RAG, earns its place. Instead of asking employees to browse folders, it indexes the documents where they already live and lets people ask questions in plain language. A question like "how many days of bereavement leave do I get" returns the passage from the policy that applies to that employee's company, with a citation to the source document so HR can verify it.

How does RetrieveIT help multi-entity HR teams?

RetrieveIT connects to SharePoint, Google Drive, OneDrive, Confluence, Gmail, Outlook, and Microsoft Teams, so each company's handbooks, benefits guides, and policy threads become searchable without moving them. Workspaces let you organize search the way your group is actually structured. Each company can have its own workspace with its own sources and members, and a group-level workspace can give HR teams visibility across all of them. Permissions from each source system are enforced at query time, so an employee at one entity does not see another entity's documents.

Every answer cites the source document, the author, and the date, with a link to the original, which matters when two companies have similar policies with different details. The same setup supports employee onboarding, since new hires can ask questions about their own company instead of reading a handbook written for a different one. RetrieveIT does not replace your HRIS. It answers the questions your HRIS was never designed to answer.

Supporting several companies with one HR team is a growth problem, and a good one to have. It stops being painful when the first question, which handbook applies, gets answered automatically.