Most frustration that follows a policy change has little to do with the policy itself. It comes from the gaps around it: the change appears, nobody explains why, the effective date is buried in paragraph four, and half the team cannot tell whether it applies to them. A policy change memo closes those gaps. Done well, it lets you announce something unpopular and still keep people's trust.
What the memo has to do
A policy change memo has five jobs, and it should manage all of them within a page or two:
- state the change and its effective date in plain words
- give the reason, in a form a colleague could repeat accurately
- describe what is different in day-to-day work
- say who it applies to — and who it does not
- set out the steps each reader must take, and by when
The memo is not the policy itself. The policy lives in your handbook or policy library, where it can be version-controlled and updated. The memo is the announcement: dated, shorter, and written for someone skimming it on a phone between meetings. Keep it to 300–500 words unless the change is genuinely complex.
Structure, section by section
Header and subject line
Use the standard header — To, From, Date, Subject — and let the subject carry the decision. "Policy change: expense claims — effective 1 March" tells the reader everything they need to decide whether to read on. "Important update" tells them nothing and gets archived unread.
Opening: the decision
Lead with the change, in two sentences at most.
From 1 March, all expense claims must be submitted within 30 days of the transaction date. Claims older than 30 days will only be reimbursed with written approval from a director.
No background, no apologies, no paragraph about the journey the organisation has been on. Those can come later, if at all.
Rationale: why now
Give a reason that stands on its own. "Claims currently arrive in batches, often two or three months after the spend, which makes them hard to reconcile against budget and slow to repay." That is a fact the reader can weigh. If a consultation or staff survey led to the change, say so and say what it showed. If the driver is cost, say that too — people handle an honest constraint better than a vague one.
Do not dress a decision up as something it is not. Readers spot it, and the next memo you send will be read with more suspicion than this one deserved.
What changes in practice
This is where most memos lose people. Policy language becomes real behaviour only when you show the difference, and a short before-and-after list beats prose.
- Previously: claims could be submitted at any point. Now: within 30 days of the transaction.
- Previously: paper receipts went to Finance in envelopes. Now: a photo of each receipt is uploaded with the claim.
- Previously: manager approval whenever it happened. Now: manager approval within five working days.
Name the system, the form, the inbox and the deadline. Anything a reader has to interpret is a reader who will get it wrong.
Impact and compliance steps
Spell out who is affected — "everyone who claims expenses, including contractors working through the agency" — then give the actions as a numbered list in the order the reader will do them, with dates attached. If there is a transition period, say exactly how the old and new rules overlap and which one applies to work already in progress. It also helps to say what happens if someone misses the deadline: uncertainty is what people fill with worry.
Questions and sign-off
Point to a role and a route, not just "HR". "Questions to the Finance team inbox, or come to the 20-minute drop-in in the week beginning 24 February." Give a date by which questions should reach you, so you have time to answer before the change takes effect. Close with one practical line: "If this creates a real problem in your team, tell us before 1 March rather than after."
A worked example
To: All staff, UK sites
From: Head of Finance
Date: 10 February
Subject: Policy change — expense claims must be submitted within 30 days, effective 1 March
From 1 March, all expense claims must be submitted within 30 days of the transaction date. Claims older than 30 days will only be reimbursed with written approval from a director.
Why. Claims currently arrive in batches, often two or three months after the spend. That makes them difficult to reconcile against budget and slows repayment for the people who claim on time. A tighter window brings the process into line with monthly accounting and gets money back to you sooner.
What changes.
- Claims must be submitted within 30 days of the transaction, not at any time.
- Each claim must include a photo of the receipt, uploaded to the expense system.
- Managers must approve within five working days of submission.
- Claims over £500 also need director approval.
Who it affects. Everyone who spends company money or claims back their own, including contractors working through the agency. Travel booked through the central travel account is unaffected.
What you need to do.
- Upload any outstanding receipts this week.
- Submit claims dated before 1 March by 15 March; the old rules still apply to them.
- Check the updated expense policy in the policy library — the section on receipts has changed.
- Bookmark the expense system on your phone so receipts can be photographed as you go.
Questions. Email the Finance team inbox or come to the drop-in session in the week beginning 24 February. Please send questions by 26 February so we can answer them before the change takes effect.
If this creates a practical problem in your team, tell us before 1 March and we will look at it.
Common mistakes
- Burying the effective date. It belongs in the subject line and the first sentence, not a footnote.
- Defensive rationale. If the reason reads like an argument you expect to lose, rewrite it until it reads as a straightforward explanation.
- No next step. "Please ensure compliance" is not an instruction. Say what to do, where, and by when.
- Sending it to everyone. Broad distribution is fine, but if the change affects one group only, say so early, or half the company will spend ten minutes working out that it does not concern them.
- No review date. If the policy may need adjusting, say when it will be reviewed. It buys goodwill and gives you an exit if the change misfires.
Tone, length and timing
Write in the voice you would use explaining the change to a colleague in the lift. Short sentences, active verbs, no jargon. Avoid blame: a memo that reads as a response to a few people's behaviour makes everyone defensive.
Timing matters as much as wording. Send the memo far enough ahead that people can adjust, and further ahead for anything that alters pay, hours, approval routes or working patterns. If a change touches contractual terms, holiday, pay or anything agreed with staff representatives, treat the memo as the last step rather than the first: check the wording with HR or an employment law adviser, and take advice on whether consultation is required before you announce. Getting that sequence wrong is expensive to undo.
Checklist before you send
- Does the subject line name the change and the effective date?
- Is the decision in the first two sentences?
- Could a reader explain the reason to someone else?
- Have you described what changes in practice, not just what the policy says?
- Is it clear who is affected, and who is not?
- Are the required actions numbered, dated and specific?
- Is there a named route for questions, with a deadline?
A memo that answers those seven questions will not make an unpopular change popular. It will make it understood, which is the part you can control.
Photo: fill / Pixabay
