The Questions That Come Back: A Lightweight Register for Better Induction

Every manager knows the pattern. A team member asks how to raise a purchase order, where to find the holiday form, who approves a credit note or what to do when a delivery arrives damaged. The answer is given, often patiently. A week later, the same question returns, sometimes from the same person and sometimes from someone new.

These interruptions are easy to treat as noise. In practice, they are diagnostic. A question that keeps coming back usually points to a gap in induction, handover or written guidance. The response does not need to be a new software platform or a formal knowledge-management project. A shared register, a short weekly review and a simple rule for turning recurring questions into one-page answers can remove a surprising amount of friction.

Treat repeated questions as evidence

The first step is a change of framing. A repeated question is not necessarily a sign that someone was not listening. It may be a sign that the answer is buried in a long document, that the process has changed, that different people give different answers, or that the question naturally arises at a point when the person cannot easily search for help.

That framing matters because it shifts the manager's attention from the individual to the system. The aim is not to discourage questions. It is to make the most common ones easier to answer consistently, so that the team's time is spent on work rather than on repeated explanations.

Start with a shared register, not a new system

The register can be a simple spreadsheet on an existing shared drive, a page in a team workspace, or even a notebook kept in a central location. The point is that it is shared, easy to add to and reviewed regularly. A complicated form will not be used during a busy shift.

Keep the fields few. A workable register might record the date, the question as it was asked, who asked, who answered, roughly how often it has come up, whether an existing document already covers it, and the action agreed. The last field is the important one. The register is not a diary of interruptions; it is a queue of small improvements.

Not every question needs to be logged. Capture the ones that recur, take time to answer, or reveal a process gap. A manager might ask team members to add a line when they find themselves giving the same explanation for the second time in a month. That is a modest ask and keeps the register focused.

Review weekly for fifteen minutes

A weekly review is enough for most teams. Fifteen minutes, held at the same time each week, gives the register a routine. The reviewer sorts entries into four simple categories: answer directly and close, point to an existing document, create or update a one-page answer, or escalate a process problem that cannot be solved by guidance alone.

This is not a meeting that needs minutes. A short note of decisions is sufficient. The value comes from the regularity and from the fact that someone is looking across the questions rather than answering them one at a time. Patterns become visible quickly. Several questions about the same form, for example, may indicate that the form itself is confusing rather than that the team needs more training.

Apply a conversion rule

The register only improves induction if recurring questions are converted into durable guidance. A simple rule helps: when the same question appears three times in a quarter, or twice within a month, it earns a one-page answer. The thresholds are not sacred. The principle is that repetition triggers a written response rather than another verbal explanation.

The one-page answer should be short enough to read in a few minutes. Put the question at the top, answer it in the first sentence or two, then add the steps, the owner, the relevant link or location, and a review date. Avoid turning it into a comprehensive procedure. If the topic genuinely needs a full procedure, link to it and keep the one-pager as a signpost.

Feed the answers back into induction

A collection of one-page answers is useful, but it becomes more valuable when it is built into induction and handover. Add the most common questions to the first-week checklist. Include them in handover notes for shift changes or parental leave cover. Use them as discussion prompts in team meetings rather than as documents that are sent once and forgotten.

This is particularly important in hybrid and shift-based teams, where informal knowledge is harder to pick up by overhearing. A new starter may not know whom to ask, or may ask at a time when the usual expert is unavailable. A short, current answer reduces that dependency without removing the human support that induction should provide.

Keep it from becoming bureaucracy

The risk is obvious. A register can become another compliance artefact, updated diligently but never used. Avoid that by keeping the register small, reviewing it in a standing slot and retiring guidance that is no longer accurate. A one-page answer with no review date will eventually mislead. A review date and a named owner keep it honest.

It also helps to measure lightly. The aim is not a dashboard. A manager might simply note whether the same questions are still appearing, whether new starters settle faster, or whether handover has fewer gaps. Those observations are enough to show whether the method is working.

A small habit with a long reach

The repeat question register is not a grand initiative. It is a habit of paying attention to the questions that keep returning and turning the best answers into something the whole team can use. For UK managers dealing with tight resources and busy schedules, that restraint is part of its appeal. It requires no procurement, no new platform and no lengthy training programme.

Start with one shared page and one weekly review. Capture the questions that come back, convert the most persistent ones into short guidance, and build that guidance into induction and handover. Over time, the interruptions reduce, the answers become more consistent and the team spends less time rediscovering what it already knows.