Policy Update Email Template — Terms Change Notice
A sober all-type notice: plain title, an effective-date line set off by rules, a summary, and a text link. Deliberately undecorated.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- An email is a top-to-bottom stack of blocks — the recipe follows that order.
- A
[layout]step becomes a single image (great for heroes); everything else stays live text and links. - Theme the footer to match — the recipe's last step does exactly that.
Want this exact email? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share zH4AzMrcBfyWfKPhd2vQR and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
A terms-change notice that looks marketed reads as evasive. No hero image, no accent band, no button — a plain title, the effective date fenced by two rules so the eye cannot miss it, and a link to the full document. The restraint is the message: we are telling you, not selling you.
Snapshot
- Goal: notify clearly, date the change unambiguously, and make the full text one click away.
- Audience & tone: every account holder. Sober, precise, unhedged — the register of a letter from a regulator, minus the jargon.
- Palette: page
#e5e6e7· container#f8f9f9· text#0c0f12/#66686a(muted) · accent#3a4a5a - Font:
Georgia, serif - Artwork: none — fully native blocks.
Build recipe
Each step is one block in the flat stack, top to bottom.
[native]= a real email block.[layout]= a free-form layout embedded as a single image.
- [native] Kicker 1 — text. “Terms of Service”, fontSize: 14, color
#3a4a5a, left, uppercase. - [native] Headline — text. “We are changing our terms on 1 May 2026”, fontSize: 28, color
#0c0f12, left. - [native] Body copy 1 — text. “A summary of what changes and what you need to do is below.”, fontSize: 16, color
#0c0f12, left. - [native] Kicker 2 — text. “What is Changing”, fontSize: 14, color
#3a4a5a, left, uppercase. - [native] Body copy 2 — text. “Section 4: dispute resolution moves from arbitration to the courts of England and Wales.”, fontSize: 16, color
#0c0f12, left. - [native] Body copy 3 — text. “Section 9: we now name the sub-processors that handle your data, with 30 days notice before adding one.”, fontSize: 16, color
#0c0f12, left. - [native] Body copy 4 — text. “Section 12: the notice period to close an account drops from 30 days to 7.”, fontSize: 16, color
#0c0f12, left. - [native] Story title — text. “What you need to do”, fontSize: 20, color
#0c0f12, left. - [native] Body copy 5 — text. “Nothing, if you are happy with the changes — they apply automatically on 1 May. If not, close your account before then at no cost.”, fontSize: 16, color
#0c0f12, left. - [native] Primary CTA — button. Label “Read the full updated terms”, fill
#3a4a5a, color#ffffff, shapeStyle: ‘0_1’, left. - [native] Body copy 6 — text. “Questions about any of this? Reply to this email and a person will answer.”, fontSize: 16, color
#66686a, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#3a4a5a, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#66686a, address.fontFamilyGeorgia, serif, center.
Make it yours
- Summarise the actual changes in plain sentences with section numbers. “We have updated our terms” is not notice.
- State what the reader must do, including “nothing”. Notices without that line generate the most support contacts.
- Resist adding a button, a hero image, or an accent band. Every one of them makes the notice less credible.
About announcements email templates
An announcement earns its own send when it's time-sensitive or significant enough to need full attention on its own subject line — a launch, a leadership change, a funding round, or a policy update, rather than one more line in the next newsletter issue.
See all announcements templates →What kind of news deserves a standalone announcement email instead of a newsletter mention?
Anything time-sensitive or significant enough to need its own subject line and full attention — a launch, a leadership change, a funding round, or a policy update that changes how customers use your product.
How long should a product-update announcement be?
Long enough to explain what shipped and why it matters, short enough to read in under a minute — the templates below separate a short "what's new" summary from optional deeper detail below it.
How do I announce a leadership change without it feeling like a press release?
The new-CEO and leadership templates below lead with a short, human bio and a direct quote rather than a formal title-and-tenure rundown.
Should an announcement email include a call to action?
Not always — a policy update or leadership announcement can stand on its own, while a product-launch announcement should point to one clear next step, like trying the feature or booking a demo.