Staff handbook review checklist

A handbook review should identify which instructions managers and staff actually use, whether they match contracts and whether the correct UK jurisdiction is covered. Updating the cover date alone does not bring an old policy into line with current law.

Check policy ownership and contractual effect

List each policy, its owner, review date and links from employment contracts. Distinguish contractual promises from guidance the employer intends to amend through an appropriate process. Acas explains the significance of contractual terms and incorporated documents. ^[1]

Resolve contradictions, such as different sickness reporting times, notice periods or holiday approval rules across the contract, intranet and handbook. Remove broken references to departed managers or unavailable reporting channels.

Test policies against real cases

Walk through a grievance against the line manager, a disability-related absence and an urgent family leave request. Can a worker find the right recipient, understand what to provide and obtain a decision? A policy that works only when the usual manager is available needs revision.

Prioritise family leave rules and harassment prevention where legal changes or practical risk require attention. Record what changed, when it applies and how staff and managers will be informed. Preserve earlier versions for decisions taken under them.

Build an inventory of the documents people actually use List the handbook, intranet policies, onboarding attachments and manager guidance currently in circulation. Record the owner and version of each, together with links from contracts. Ask a sample of managers where they look for instructions, because an obsolete shared-drive copy may be used more often than the officially current handbook. The review should locate the practical sources of decisions, not merely the document bearing the newest cover date. Preserve earlier versions where they explain decisions already taken or commitments previously communicated.

Identify contradictions by topic. Compare reporting deadlines, approval routes, benefits and appeal contacts across the documents. A policy directing staff to a departed HR manager or a form they cannot access is not operationally complete. Where wording differs, establish the intended rule and whether a contractual promise is involved before replacing it. Acas explains that terms can arise through different sources and incorporation. ^[1] A general non-contractual label on the handbook does not settle the effect of an individual promise or establish which procedure a proposed change requires.

Prioritise amendments by their practical consequence Separate an inaccurate legal requirement from unclear drafting and an internal process that no longer works. Address errors likely to affect live requests or decisions first. In 2026, family leave, sick pay, holiday records and forthcoming employment reforms deserve a dated check against official commencement information. [2] Mark future changes as future until they apply. A policy should tell a manager what to do for the relevant event date, rather than mixing enacted legislation, current duties and planned reforms in one undifferentiated paragraph.

Check the jurisdictions covered. A UK-wide workforce may require separate Northern Ireland provisions and clear routing for local questions. Avoid changing an Acas reference to a generic national body name while leaving Great Britain rules embedded in the text. Identify which benefits are company-wide promises and which statements describe statutory rights. Where the business deliberately offers more than the minimum, preserve that decision explicitly. A legal update should not inadvertently remove an enhancement or create a new promise through an ambiguous attempt to summarise the law.

Test the policy with awkward but realistic cases Walk through a grievance against the normal recipient, a manager absent during an urgent request and a worker unable to use the standard form. Check whether the document identifies an alternative contact and a meaningful next step. For an absence or adjustment request, ask what information is needed and who should receive it. Policies should be usable without forcing staff to disclose sensitive details to a general mailbox or requiring a legal label before the employer recognises a problem that needs attention.

Test the manager's side as well. Can they identify who makes the decision, what records to retain and when specialist advice is required? A policy containing only employee obligations may leave managers inventing their own response process. Review forms and system fields against the revised procedure so they request the necessary information without adding unsupported conditions. If the handbook promises an appeal or review, confirm who can carry it out impartially. The operational route must exist, particularly in a small business where several roles are held by one person.

Implement changes through a controlled release Keep a change log explaining what was revised, why, the effective date and any consultation or agreement required. Obtain appropriate approval before issuing a change to contractual terms. Communicate substantive amendments in plain language and provide access to the full policy. Train managers on decisions affected by the update instead of relying only on an email asking them to read the attachment. Remove superseded versions from ordinary use while retaining an archive, so staff can find the current instruction without losing the history relevant to earlier events.

Set a review owner and trigger for each significant policy. Legal developments, a workplace incident, a system change or repeated staff confusion may justify review before the next annual date. Monitor whether the revised process works by checking actual requests and outcomes, not by counting acknowledgements alone. Where a problem persists, identify whether the wording, training or implementation needs correction. A useful handbook is a maintained set of instructions connected to contracts and daily decisions, with enough version history to explain which rule applied when a particular case was handled.