Publishing an HR policy everyone can find
Policies fail at findability, not at writing. The document is fine. It is in a shared drive, in a folder, under a name that made sense to whoever saved it.
HR writes a policy. Everyone is told. Two months later the same question is asked four times, because nobody can find the answer.
The gap between having a policy and having a findable policy is where most of the support load lives.
In PeopleMuster policies are published into categories with a summary each, and indexed so an assistant can answer questions from them.
Two habits make the difference. Write the summary as though it is the whole policy, because on the list that is what people read. And check the chunk count after publishing, which confirms the text was indexed rather than merely saved. An unpublished policy is invisible to the assistant and therefore invisible to most of the team.
Why one record instead of two
Policy is HR work whose cost is paid by everyone else in interruptions. Making it findable moves the load off people and onto a document. The assistant answers from the published text, and the document stays the official source.
What is switched on
- Policies
- Authoring with a category, a slug, a status and a record of who last edited it.
- Policies
- Publishing chunks and indexes the text, and the authoring screen shows how many chunks are indexed.
- Support desk
- The official policies ticket category shows which questions the policies still do not answer.
- Notifications
- A scheduled Slack announcement is how people learn a policy changed.
- Activity log
- Edits are recorded with author and timestamp, so a version question has an answer.
What the week looks like
Writing
Give it a category and a summary. The summary is what people read on the list, so it does most of the work.
Publishing
Publishing indexes the text. The chunk count confirms it was indexed rather than just saved.
Announcing
A scheduled Slack post reaches people who will not visit the policy list.
Weeks after
Watch the official policies ticket category. Repeat questions point at an unclear policy, not a slow reader.
When it changes
Edit and republish. The last editor and time are recorded on the policy.
Quarterly
Read the list as a list. Contradictions between two policies are obvious side by side and invisible one at a time.
Questions people ask
How do people learn a policy changed?
A scheduled Slack announcement reaches the team, and the policy record shows its last editor and the time of the edit.
How does the assistant know the answer?
Policies are chunked and indexed when published, and the assistant retrieves from that text. Publishing is the step that makes a policy answerable.
Does PeopleMuster supply policy templates?
The product holds and publishes the policies you adopt. Free policy templates live in the templates section of this site, as a starting point for your own wording.