# Every answer needs a named owner

> Jack on why a handbook owned by everyone is owned by no one: give every policy, page and answer one named owner (the person who'd get asked anyway) and a review date, and make owning mean review, answer and retire.

Source: https://forematter.com/notes/every-answer-needs-a-named-owner/
Published: 2026-09-29
Author: Jack Stovell (https://jstov.uk/)

Ask who owns the handbook and you'll usually get a shrug, or "well, HR", or "the team, I guess". Which is the problem, right there. If it belongs to the team, it belongs to nobody.

I've got a simple view on this. Company knowledge rots, and it rots quietly. A page that was correct on the day somebody wrote it drifts as the business changes and the rules change, and nothing on the page tells you. It looks exactly as confident as it did the day it went up. Nobody decided to let it go stale. Everyone just assumed someone else had it.

That's what shared ownership really is: everyone assuming. You spot a mistake, you think "someone will sort that", and you carry on with your day. Fair enough, I'd do the same. But when every reader thinks that, you get a document with plenty of readers and no keeper.

## Why a name matters

Put one name on a page and two things change.

First, it becomes fixable. There's somebody to ask, and that somebody can actually change the page. Without a name, a gap is just a vague feeling that something's missing, and vague feelings don't get fixed.

Second, it becomes trustworthy. An answer with a person behind it is an answer someone is accountable for. That matters more than it sounds, because people can tell when nobody stands behind a page, and they stop relying on it. Then they ask around instead, which is how you end up with three different answers to the same question.

The official guidance already leans this way. For health and safety, HSE says your policy [should clearly say "who does what, when and how"](https://www.hse.gov.uk/simple-health-safety/policy/index.htm), and that you should [list the names, positions and roles of the people with specific responsibility for it](https://www.hse.gov.uk/simple-health-safety/policy/how-to-write-your-policy.htm). The employer or most senior person should sign it and review it regularly. Acas, in its guidance on writing a home and hybrid working policy, puts it plainly: ["You should regularly review your policy."](https://www.acas.org.uk/policies-for-home-and-hybrid-working/how-to-structure-a-policy) It says to decide when or how often that happens, who will be involved, what it will consider, what the outcomes might be and how it will be communicated.

That's guidance on those particular policies, not a rule for every page you have. But I think the habit is sound well beyond them. A name, and a plan to look again.

## Pick the person who'd get asked anyway

Here's where people get nervous, because it sounds like paperwork. It isn't. You don't need a committee, and you definitely don't need a responsibility matrix (I'd rather eat the chart).

The owner is whoever would get asked anyway. Whoever runs payroll owns pay dates. Whoever books the leave owns holiday. You already know who these people are. They're the ones who get the message when somebody's confused. Making it official just means writing their name down.

One name per topic, though. Not a team, not a pair. Two owners is a polite way of having none, and we're back where we started.

Write the role next to the name as well, so not just "Sam" but "Sam, who runs payroll". People move on and change jobs, and a role survives a handover in a way a first name doesn't. When someone leaves, handing over what they owned is part of the handover. Easy to forget, so put it on the list.

## What owning actually means

Owning is three jobs, and none of them is big.

Review it on a date. Pick the date on purpose, rather than "when we get round to it", because we never do. The right gap depends on the page and the business, and I'm not going to invent a number for you.

Answer questions about it. The owner is who people go to, and if the same question keeps coming back, that's the owner's cue to make the page clearer rather than keep answering it by hand.

Retire it when it's wrong or no longer applies. Which brings me to the bit people skip.

## Retiring is part of the job

An out-of-date page that still looks official is worse than a missing page. A missing page makes people ask. A wrong page makes people act, confidently, on something that stopped being true. That's the expensive way to find out.

So retire pages. Delete them, or mark them clearly as no longer current, but don't leave them lying about like old milk in the office fridge. Somebody has to be allowed to make that call, and that's the owner. Another reason you need one.

## Start with a name and a date

That's really all I'm asking for: a name and a review date at the top of each page. Nothing grander.

If you want somewhere to start, the [small business policy checklist](/templates/uk-small-business-policy-checklist/) has Owner and Review date columns ready to fill in, and the guide to [keeping an internal knowledge base people actually use](/guides/internal-knowledge-base/) covers the wider job of keeping it all findable. Forematter, onboarding software for UK companies, shows the owner under every answer. But you don't need software to begin. A list and a pen will do.

Pick a page. Put a name on it.