All posts
11 min read

Policy questions every week? Four ways to get them off HR's desk, compared

By the Redstone HR team · Published

Subscribe to our newsletter

Read about our privacy policy.

If the same policy questions about holiday balances, carryover and public holidays land on your desk every week, the cause is usually scattered records rather than unclear policy. Of the four common fixes (a shared FAQ document, an intranet page, a dedicated HR inbox and a self-service assistant), only one that answers from the same record holding each person's live balance and each site's rules cuts the questions as you grow. Below, each option is scored on accuracy across locations, upkeep effort and how often a question still reaches you.

This guide is for HR managers at 15–150 person, multi-site companies. If you were looking for policy interview questions and answers, this is a different topic: it is about the leave questions your own staff ask.

Why the same policy questions land on your desk every week

The same policy questions keep coming because no single place gives staff a complete answer. Balances live in a holiday spreadsheet, approvals sit in email threads and the rules are in a policy document. None of these answers the question on its own, so people ask HR.

The questions that come up most are familiar:

  • How much holiday do I have left?
  • Can I carry days over into next year?
  • Which public holidays apply at my site?
  • What do I do when I call in sick?
  • Who else is off that week?

Each new site or region adds its own public holidays, entitlements and carryover rules. That means the number of questions grows with the number of locations, not just with headcount. One spreadsheet trying to hold every site's rules is also where mistakes and compliance exposure start.

The pressure is not unique to your team. According to Human Resources Director (hcamag.com), a survey of US employers found most are expanding leave programmes, but far fewer have the resources to administer them correctly. The report puts the gap down to under-resourcing, not a lack of policy, and notes that it hits small businesses without dedicated HR staff hardest.

What a good answer to a policy question actually needs

A good answer to a leave question passes four tests: it is personal, current, consistent and available at the moment of asking. These four tests are the scoring criteria for every fix that follows.

  • Specific to the person. The answer reflects their own balance and their location's rules, not a general rule they then have to work out.
  • Current. The answer takes account of approvals already made and the current carryover position.
  • Consistent. The same question gets the same answer at every site.
  • There when the question is asked. Ideally the answer appears where the person is already booking time off.

The policy itself still has to be sound before any of this works. If you are reviewing it, see how to set fair and compliant holiday and time off policies.

Option 1: a shared FAQ document

A shared FAQ document is quick to start and costs nothing, but it cannot answer the most common question: how much holiday someone has left. It suits general rules, such as how much notice to give when booking holiday.

The weakness is that a FAQ document is static. Balance questions still come to HR because the document has no link to anyone's record. When a rule changes, the document goes out of date until someone remembers to update it. Keeping a separate version for each site multiplies the upkeep and the chance that a member of staff reads the wrong one.

Score: low accuracy across locations, medium upkeep, and many questions still reach you.

Option 2: an intranet or HR policy page

An intranet or HR policy page is a better official home for written policy, but it still leaves staff to interpret the rules themselves. It is the right place to publish the policies you are required to have; for a reminder of what essential HR policy documentation should cover, see the glossary.

In practice, an intranet page usually holds the whole policy, so staff read it, are not quite sure how it applies to them and email HR to confirm. Per-location detail, such as a site's public holidays or a different carryover rule, is often buried or missing. Like the FAQ document, an intranet page has no link to live balances.

Score: medium accuracy, medium upkeep, and a steady flow of "just checking" questions.

Option 3: a dedicated HR inbox

A dedicated HR inbox gives accurate, personal answers because a person checks the spreadsheet and the policy before replying. But a dedicated HR inbox does not reduce the work; it puts the work in a queue.

The same hours of checking and replying fall on someone who already has a full job. Answers also depend on who replies, so consistency between sites drifts over time, especially as you add locations and new team members handle the inbox. Tidier spreadsheets and more reconciliation behind the inbox move the effort around rather than removing it.

Score: high accuracy, high upkeep, and every question still reaches HR, just in one place.

Option 4: a self-service assistant that answers from your own policies

A self-service assistant works when employees can ask their own questions and get answers based on their own balance and their site's configured rules. Done well, it passes all four tests: personal, current, consistent and available when the question is asked.

A self-service assistant has limits. It is only as good as the policies set up behind it, so the rules for each location need to be configured correctly first. HR should keep exceptions and sensitive cases.

The assistant works best when it sits inside the same record as requests, approvals and balances. A separate chatbot bolted on top of a spreadsheet can quote the policy, but it cannot see that someone's holiday was approved yesterday.

Score: high accuracy once rules are set per location, low upkeep after set-up, and only genuine exceptions reach you.

Side-by-side: accuracy across locations, upkeep and questions that still reach HR

Only the options tied to a single record of balances and local rules reduce policy questions as you grow; the others add to them with every new site.

Option Accuracy across locations Upkeep effort Questions that still reach HR When a new site opens Shared FAQ document Low Medium Many, including all balance questions Another version to write and maintain Intranet or HR policy page Medium Medium Steady "just checking" questions More detail to add and keep current Dedicated HR inbox High, but depends on who replies High All of them, in one queue More questions in the same queue Self-service assistant on a single record High once rules are set per location Low after set-up Genuine exceptions only Rules set once for that location

The pattern is clear: documents and inboxes scale with effort, while a single record scales with configuration. If your team is multi-site and growing, the last row is the one that keeps the workload flat. For multi-site teams that also run hybrid working, the same principle applies to setting clear policies for hybrid teams across sites.

Which policy questions should still come to HR?

Exceptions, sensitive requests and conversations about patterns of sickness absence should still come to HR, whichever fix you choose. Self-service handles the routine; people handle the judgement.

  • Compassionate leave and other sensitive requests. These need a person, not a lookup. See handling compassionate leave requests with care.
  • Unpaid leave and requests outside normal entitlement. These involve discretion and sometimes pay implications; see the rights and considerations for unpaid leave.
  • Patterns of short-term sickness absence. An assistant can answer "how many sick days do I have left?", but the return-to-work conversation stays with a manager or HR.

Consistent scoring makes those absence conversations happen sooner and more fairly. When Bradford Factor scores are surfaced as absence is recorded, you see repeated short absences before they disrupt shifts and cost you in cover, and every employee is measured the same way.

How Redstone HR handles policy questions across multiple sites

Redstone HR answers policy questions from one record that holds each person's balance, their approvals and their site's rules, which is the approach scored highest above. Here is what that looks like for a multi-site HR team.

  • Rules per location. Leave policies, public holidays and carryover rules are configured per location and applied consistently, so opening a new site means setting its rules once rather than starting another spreadsheet.
  • Employees answer their own questions. Staff ask the AI Policy Assistant balance and policy questions in the app, such as "How many sick days do I have left?" or "Can I carry over holiday?", and see their remaining balance before submitting a request.
  • Coverage is checked at approval. Managers see who else is out that week and get coverage warnings before approving. Approved time off appears on the team calendar and syncs to Google Calendar or Outlook.
  • Patterns are surfaced early. Repeated short absences, Monday and Friday patterns and Bradford Factor scores are surfaced so managers can have the conversation early.
  • Records and reports. Balances, approvals and history are stored centrally and kept audit-ready. Scheduled reports and payroll-ready exports arrive in your inbox as CSV, Excel or PDF. Direct payroll integrations are planned but not yet available, so today the route to payroll is the export.

On cost, the AI Policy Assistant is included in every plan, and Redstone HR is priced as a flat monthly fee by headcount band, not per user. More questions, or one more hire, do not change the bill. That matters because, according to Hypeless, some recruitment software vendors are now adding AI usage-based charges on top of per-seat pricing, so costs can rise even when headcount stays the same.

To be clear about scope: Redstone HR is a web app used in any browser, and it is not a full HR suite. It does not run payroll or benefits administration.

Switching from a spreadsheet or your current leave tool: what to check

Switching goes smoothly when opening balances and each site's rules are agreed before you move, so the first answers staff get are correct. Our view is that set-up should be quick, in about 15 minutes, with rules set once per location rather than rebuilt for each team.

  • Agree opening balances. Reconcile each person's holiday balance and carryover from the spreadsheet or current tool, and get sign-off before go-live.
  • List each site's rules. Public holidays, entitlements and carryover limits for every location, written down in one place.
  • Decide approvers. Confirm who approves for each team and site.
  • Plan the first export. Check that the payroll-ready export gives your payroll provider what it needs before the first month-end.

Whichever tool you assess, put these data security and GDPR questions to the vendor:

  • Where is our data held?
  • Who can see absence and sickness records, and can access be restricted by role?
  • How are changes to records logged for audit?
  • How do we export or delete our data if we leave?

Self-assessment: how many policy questions should you still be answering?

Score your current set-up by answering yes or no to five questions. Mostly "no" answers suggest the questions come from scattered records, not from unclear policy.

  • Can staff see their own live holiday balance without asking anyone?
  • Are the rules for each site applied automatically, rather than looked up by hand?
  • Can you open a new site without creating new documents to maintain?
  • Are fewer than a handful of messages a week "just checking"?
  • Can managers see coverage before they approve time off?

If you answered "no" to three or more, compare your answers with the side-by-side table above to see which option closes your biggest gap. If balances and site rules are the gap, see how a single record with per-location rules and the AI Policy Assistant works for multi-site teams at redstonehr.com, or talk your situation through via the contact page there.

Frequently asked questions

Why do staff keep asking HR the same policy questions about holiday?

Staff keep asking because balances, approvals and rules sit in different places (a spreadsheet, email threads and a policy document), and none of them gives a complete, personal answer on its own.

Is a shared FAQ document or intranet page enough to cut policy questions?

A FAQ document or intranet page can explain general rules, but neither can tell someone their own live holiday balance, so balance and "just checking" questions still reach HR.

Which leave questions should still come to HR after introducing self-service?

Exceptions, compassionate leave and other sensitive requests, unpaid leave and conversations about patterns of short-term sickness absence should still be handled by a manager or HR.

Does Redstone HR connect directly to payroll?

Not yet: direct payroll integrations are planned, so today Redstone HR provides scheduled, payroll-ready exports in CSV, Excel or PDF.

Does using the AI Policy Assistant cost extra in Redstone HR?

No. The AI Policy Assistant is included in every Redstone HR plan, which is priced as a flat monthly fee by headcount band rather than per user.