Guide, 10 Nov 2026, read 10 Nov 2026
Policy questions stop reaching the People team when the answer is easier to find than the person
Count the questions before you fix anything
For two to four weeks, log every policy question that reaches the People team, with the topic, the channel, who asked and the page that should have answered it. A shared spreadsheet is enough. At the end, sort by topic. The top ten usually account for more than half of the volume, and they are almost always time off, sick pay, expenses, benefits and working hours.
Look at the pattern by asker as well. If managers ask the same question again and again, the problem is a missing manager guide. If new starters ask, the problem is onboarding.
Rewrite the page, not the reply
For each frequent question, find the policy page that should answer it and fix the page. Put the answer in the first two lines. Use the real numbers: how many days, who approves, how long it takes. Add two or three worked examples, such as a part-time employee booking a day in a bank holiday week.
Add a 'questions we get' section at the bottom of the page and link to the form or system where the action happens. Where a UK or US rule is the answer, link to the GOV.UK, Acas, Department of Labor or EEOC page that sets it out.
Give managers a short guide
Managers are the first line of every policy question. Give them a one-page guide per topic, covering what they can decide, what they must refer, the three questions to ask before referring and the page to send. Make it clear what they must never do: promise an exception, discuss another person's case or give a medical opinion.
Run a 20-minute session each quarter on the top five questions of the period. It costs less than the replies it prevents.
Keep a route for judgment
Some questions need a person: accommodation, a complaint, a leave request that touches several laws. State on the page which these are and how to reach the right person. A 'raise a question' form with a topic list sends each request to the owner of the policy rather than the whole team.
Set a response time and keep to it. A published target of two working days for a policy question reduces the repeated chasing that also fills the inbox.
Measure and keep improving
Report the numbers to the head of People each quarter. When a question repeats after the page is fixed, check whether the page is findable, and whether the rule itself is the problem.
- Volume of questions by topic each month.
- Share answered by the page or by a link, with no reply needed.
- Time to first answer for the questions that need a person.
- Pages changed because of a question, and the volume of that question afterwards.
- Questions that revealed a gap in the policy rather than in the page.
A page that answers its own questions
Take a page on sick pay. Open with the answer: what you are paid, from which day, and who to tell. Then give the steps for reporting an absence, the point at which a fit note or a doctor's note is needed, and what happens if absence continues. Finish with three questions that always come up, such as what happens over a bank holiday, and link to the system where the absence is recorded. Done well, a page like this removes most of the sick pay questions the team gets.
Sources
- Overtime, Acas, read 10 Nov 2026
- Holiday entitlement, GOV.UK, read 10 Nov 2026
- Family and Medical Leave Act, U.S. Department of Labor, read 10 Nov 2026
- Reasonable accommodation and undue hardship, EEOC, read 10 Nov 2026
Last reviewed 10 Nov 2026.