Forty Word documents with the same name
Your consultancy has a good handbook template. Every new client gets a copy, adjusted for their sick pay scheme, their holiday year, their company car rules and whatever else makes them different. Two years later there are forty copies. Some have the old disciplinary procedure. Some have the new one with a client's own edits pasted in. One has a paragraph about a benefit the client stopped offering last year.
Then your advisers decide a policy needs updating across the board. Somebody opens each document, finds the section, checks whether the client has changed it, and edits carefully. It takes days and nobody enjoys it.
Why copies always drift
The problem is the unit of work. A handbook is treated as one document per client, so every change is a manual edit in forty places. The differences between clients are real and legitimate, but they are buried in prose, so you cannot tell at a glance which client has which variation.
Version control is usually a filename: 'Handbook v7 FINAL client edits'. That tells you nothing about which policies changed.
Clients add to the problem without meaning to. Their office manager edits the Word file you sent, adds a paragraph about parking, and emails it back six months later asking you to 'update the handbook'. Now there is a version you did not write, and it has become the one the client thinks is current.
The cost of drift
- Consultants give advice based on the template while the client's own handbook says something else.
- Policy updates take days of careful copying, so they get delayed.
- Nobody can answer 'which clients still have the old version of this policy?'.
- Client edits get overwritten when a new version is pasted over the top.
- New consultants cannot tell what is standard and what is client-specific.
There is a commercial cost too. Keeping handbooks current is part of what a retainer client pays for, and it is hard to show them that you have.
How we build the handbook system
- We break your template into policy sections, each with its own version history: absence, holiday, conduct, grievance, flexible working and so on.
- Client differences become settings and approved variant paragraphs rather than edits in prose, for example sick pay terms, holiday year start, notice periods or enhanced benefits.
- Existing client handbooks are compared with the template so each client's current deviations are listed for a consultant to confirm, rather than guessed.
- When your advisers approve a new version of a policy, the system lists every client using it and shows which have a variation that needs a person to look at.
- New client versions are generated as Word and PDF in the client's branding, with a change summary for the client.
- Each client's approval is tracked, with reminders, and the approved version is filed to their folder in SharePoint or your document store.
| Question | Before | After |
|---|---|---|
| Which clients have the old grievance policy? | Open every file | One filtered list |
| What is unusual about this client's handbook? | Read it | Variations listed as settings |
| Has the client approved the update? | Search email | Status on the client record |
The content of every policy stays with your advisers. The system manages versions and variations. It does not write employment policy.
Day to day afterwards
A policy update becomes a review of the flagged exceptions and a batch of generated documents, rather than forty manual edits. Consultants can see what each client's handbook actually says when they give advice. Clients receive a clear note of what changed and why it matters to them, which is a visible part of the service they pay for.
Is your handbook library like this?
- Every client handbook is a separate Word document edited by hand.
- Filenames are your version control.
- Policy updates across clients take days and get postponed.
- You are not sure which clients have approved the last update.
- Consultants sometimes advise from the template, not the client's version.