Policy management software with a policy assistant
Policy management software is where a company writes, publishes and updates its rules, so staff can find the current version. Policies stop being useful the moment nobody can find them. In PeopleMuster each one is published with a category, a summary and its own link, and HashBot answers questions from the text.
HR writes and publishes. Every document gets a category, a short summary and a stable slug, so a link sent in January still opens the right page in July. The last editor and the time of the edit sit on the record.
Employees browse by category. Workplace conduct in one place, leave and attendance rules in another, pay and benefits in a third. Five or six categories cover most companies.
On publish, the document is split into chunks and indexed. That index is what the assistant searches, which is why a newly published policy becomes answerable rather than waiting for anything to be retrained.
The assistant takes a plain question and answers from the corpus. How many sick days do I get. What is the working-from-home rule. Most policy questions are one of about twenty, asked repeatedly.
Suggested questions sit under the box, because people who do not know what a policy library contains do not know what to ask it. Two or three examples are usually enough to show the shape of a useful question.
The reason for indexing on publish rather than on a schedule is simple: a rule that changed this morning has to be findable this morning. A policy library that lags behind the decision it records is the thing people stop trusting first.
Writing remains the hard part. A library of twelve clear documents beats forty vague ones, and no amount of search makes an unclear policy answerable. What the module can do is make sure the clear ones are never the ones nobody could find.
The support desk sits next to this on purpose. A question the library does not cover becomes a ticket in the official policies category, where a person picks it up.
What it does
- Categorised library
- Documents grouped the way people look for them, each with a one-line summary.
- Stable links per policy
- Every document has its own slug, so a link in an old message still works.
- Chunked and indexed on publish
- New text becomes searchable as soon as it goes live.
- Beta question assistant
- Ask in plain words and get an answer drawn from the published documents.
- Edit trail
- Who changed a policy, and when, shown on the record.
What it needs before it works
- Your policies written by HR. The module publishes and indexes whatever HR writes.
- Categories agreed, because that is how people navigate.
- The OpenAI integration connected, for the assistant. Browsing and reading work without it.
Questions people ask
What does policy management software do for HR?
It keeps every policy in one library with a category, a summary, a stable link and an edit trail. PeopleMuster also chunks and indexes each policy on publish, so HashBot, the beta assistant, can answer staff questions from it the same day.
How should people use the assistant's answers?
As a fast first answer. The policy document stays the official source, and anything that matters is read there.
Does a new policy become searchable straight away?
Yes. Publishing chunks and indexes the text, and the record shows the chunk count once it is done.
Who can edit a policy?
HR and admins, through the authoring screen. Each record shows its last editor and the time of the edit, and staff see only the published version.
What powers the assistant?
The OpenAI integration, connected per company with your own key. The library itself works on its own: people browse and read by category.
What if the library does not cover a question?
Raise a ticket under the official policies category on the support desk. A person picks it up, and a gap the library should have covered becomes visible.