·
Steeve Elgui
Email Design Principles That Hold Up on Every Screen
A practical guide to email design for UK brands: components, live-text hierarchy, phone-first layout, consent and a checklist before every send.

You're between meetings, phone in one hand, and a restock note from a skincare brand has just landed. The images haven't loaded. The headline is a picture. So is the button. You can't see the size, the price, or what a tap will do.
That pause is the brief. Email design here means a small interface with states: images blocked, enlarged text, dark mode, a narrow column. We set hierarchy first, type second, decoration last. A model can draft a layout in seconds. Someone still has to read it with one thumb, in a gap, before the next stop.
Email Design Parts at a Glance
A lifecycle email has six parts. Each has a job, a rule, and a way it fails. Read it as a fixed order, not a page to fill.
Part | Job for the reader | Design rule | What breaks it |
|---|---|---|---|
Preheader | Previews the message beside the subject line | Short, distinct line that adds information | Empty, or a repeat of the headline |
Header and logo | Identifies the sender at a glance | Logo as live HTML with alt text | Logo as the only content when images are blocked |
Hero | States the single message | One headline, one image, one button | Competing headlines above the fold |
Body modules | Carries detail in a clear order | Single column, built once and reused | Fixed desktop widths on a phone |
Call to action | Tells the reader what happens next | Live button with a text label and a tap target of at least 44 by 44 pixels | Button baked into an image |
Footer | Shows who sent it and how to stop receiving it | Visible text unsubscribe link with company details | Opt-out hidden in an image or below a long scroll |
The preheader sits beside the subject in the inbox. It should add a fact the subject doesn't carry, such as the shade or the delivery window. An empty line, or a copy of the headline, wastes the only sentence some people see.
The header and logo answer who sent this. Keep the name in live HTML, with alt text on the mark. If the logo is the only content and images are blocked, the message opens as a blank strip.
The hero holds one message, one image and one button. Two headlines above the fold split the glance, and the reader stops.
Body modules repeat across sends, so we build them once. A single column keeps the order. Fixed desktop widths on a phone push the text off the edge.
The call to action says what happens next, as a live button with a text label and a tap target of at least 44 by 44 pixels. A button drawn into an image vanishes when images are off.
The footer names the sender and the way out. A visible text unsubscribe link, with company details, stays findable. An opt-out inside an image, or after a long scroll of extras, fails the person who wants to stop.
Every part has to work with images switched off and on a phone 320 pixels wide. The SendX guide to email design is a clear walk through how those parts sit in a template, especially the space between headline, image and action.
Read any draft top to bottom with images off. Then check that the headline, the main button and the unsubscribe link can each be found in under ten seconds. If they can, the structure holds. If they can't, the breaks are in the parts above.
Why Email Design Is a Service Interface
The Office for National Statistics reported that 86% of adults in Great Britain used email in 2019, the most common internet activity in that release. The same dataset found that 84% of adults had used the internet on the go through a mobile phone, smartphone, laptop, tablet or handheld device.
People open these messages in the gaps. A delivery update. A booking confirmation. A password reset. A monthly note from a bank. A restock notice from a skincare brand. Each one is a service task, and the reader expects the same clarity they get from a careful app screen.

Treat the message as a screen with states: loading, images blocked, dark mode, enlarged text, a narrow column. Each state needs a decision, not luck.
A message that still reads as plain text survives the client that strips the rest.
We draw the information order before any colour or type mood, because the plain version is the one that has to hold. A designer moves through parts, live text, the phone, consent, shared modules, then a send test. The first pass is the parts table. If the headline, the next step and the way out aren't obvious there, no surface treatment will repair the screen.
Building Hierarchy in Live Text, Not Pictures

A restock email for a serum has a fixed job. The reader needs a headline, a product name, a size, a price, a stock note and a button. Each of those is content in the document, not a picture of content.
The headline is the top-level heading: "Your serum is back." The product name is the next heading: "Repair serum, 30 ml." Size and price sit in a real list, so a screen reader can announce the items. A styled line that only looks like a list does not do that. The button is live HTML. Its label says what happens, Shop the serum. "Click here" names the gesture, not the product.
The UK Home Office design guidance recommends a plain-text version and an HTML version where possible, with heading structures, left-aligned text, lists, meaningful link labels and alternative text. It advises against screenshots of text, decorative images standing in for words, colour as the only signal, and styling that depends on bold or italics being recognised by assistive technology. Run a screen reader over the HTML before the send.
What the picture is allowed to say
A product photo gets a short description of what is shown and its colour: "Amber glass bottle of repair serum, 30 ml." A purely decorative divider gets empty alt text, so a screen reader skips it. "Sold out" and "sale" are written as words. Red alone does not carry the state.
Tokens that match the document
Define heading sizes, weights and spacing once in Figma, then map each token to a real heading level in the HTML. The visual stack and the document stack should be the same stack. If the serum name looks like a heading but is a bold paragraph, the structure is a costume. Those sizes should already live in the brand guidelines, so the email does not invent a second type system for one send.
Treat the email as a small interface built from the same components as a page: one heading component, one product block, one price token, one button. Hierarchy comes from that order, not from a flattened graphic of the layout.
Failures that still show up in drafts
One image for the whole message: Nothing remains when images are blocked, and nothing scales when text is enlarged.
A bold line made of an image: The emphasis cannot be read, copied or restyled.
Alt text that says image1: The reader hears a file name, not a product.
Colour as the only cue: A sale price in red, with no word "sale," disappears for anyone who does not see that red.
Switch images and colour off. The message should still read, in order, as a sentence: the serum is back, it is 30 ml, it costs what the list says, and the link shops it.
Build the plain-text version from the same content. Same headline, same sentences, same link labels, same order. Write the button as a labelled link line. Keep HTML and plain text in one template so a copy change hits both. If they drift, the client that shows only plain text shows last month's product.
Designing for the Phone Before the Desktop
The failure we keep correcting is a desktop page squeezed until it fits. Text doesn't reflow, it gets trapped. The UK Government design guidance on layout and typography treats responsive type as a reflow problem. It recommends design for different screen sizes and orientations, readable type, clear headings and line breaks, and relative units such as em and percentages instead of fixed pixels. Relative units let text resize around the reader. Fixed units restrict that.

On a narrow screen the layout is one column. The container is fluid, and on a wide screen it stops at about 600 pixels. That cap keeps line length readable without pretending the phone is a monitor.
What jumps, clips or misses the thumb
Images set without dimensions shove the layout down when they arrive. Give each image the full container width and set its dimensions so the space is reserved.
Body text in fixed pixels ignores the reader's text-size setting. Set type and spacing in relative units, from tokens, so a larger preference reflows the column instead of overflowing it.
Buttons that sit tight against neighbouring links get mis-taps. Keep the control at least 44 by 44 pixels, with clear space between adjacent links.
A three-column product grid on a phone becomes a sideways scroll or a crushed label. Collapse it to one stacked column, and keep the price beside the product name so the pair doesn't split across the stack.
Long headings and enlarged text
Take a product name of about twenty characters, a longer translation, and a shade name with a slash. Each should wrap inside the column. None should break the button or push the layout sideways. Then set text to 200 per cent. No line should be cut off, and no button should keep a fixed pixel height that clips the label. These two checks belong in the send test. The build rule is what makes them pass: flexible tokens, no locked heights, wrapping allowed.
Dark mode as an extra, not a guess
Dark mode is progressive enhancement. A logo on a transparent background can vanish on a dark client. Give it a light panel where the mark needs one. White-background product photos need a visible edge, or they melt into the inverted canvas. Don't rely on a thin dark outline. It is the first thing to disappear.
A rendering contract per component
Write a short spec on each component: the desktop art direction, and the mobile behaviour. A developer should be able to build from that without guessing which column collapses, which image is optional, and which text must stay live. If the spec only shows the wide frame, the phone version gets invented in the inbox.
Consent and Unsubscribe as Interface Elements
Consent is part of the interface. It isn't a footer sentence someone adds after the layout is signed off.
Regulation 22(2) of the Privacy and Electronic Communications Regulations prohibits businesses from sending marketing emails without the recipient's prior consent, subject to the relevant legal exceptions, as set out in the government marketing guidance. Consent has to be an active, positive choice. Silence, or a failure to opt out, doesn't qualify. When those emails go out, Regulation 23 requires a valid address for an opt-out request.
The sign-up, before any module exists
The checkbox starts unticked. The wording names what the person is agreeing to and how often they'll hear from you. "Updates" is too vague to be a choice. "A monthly note on new shades, and nothing else" is a choice. The practical GDPR guide for SaaS marketers is a useful cross-check on how that wording and the record behind it should sit together.
Store the consent state with a timestamp and the source of the sign-up, so it can be shown later. A checkbox that isn't stored is a picture of consent, not consent.
The way out, on every send
Every marketing email carries an unsubscribe link in live text, one tap away, with no image and no login in the way. Separate the preference centre from that link. Leaving one topic shouldn't remove service messages the person still needs, such as an order or a password reset.
A booking confirmation stays a service message. A "you might also like" block turns it into something that needs consent.
Make the consent state a field the template checks before any promotional module renders. If the field isn't there, the module doesn't appear. Confirm the exact wording with your legal adviser. The words matter as much as the layout around them, and a designer shouldn't invent the legal line.
Reusable Modules Across Klaviyo and Mailchimp
Build the library once, in Figma, with a named owner and a version number. A file nobody owns drifts on the second campaign.
A lifecycle programme needs a small set:
Hero: One message, so later editors don't stack three offers into the top.
Product grid: Detail in order, collapsing to a single column on a narrow screen.
Editorial block: A short story in live text, not a poster.
Shade or size table: Options as real text. The swatch is decoration only.
Review quote: A sentence someone can hear, with the product named in the words.
Benefit row: A few facts in a list, not icons that carry the meaning alone.
Footer: Sender and unsubscribe, unchanged unless the legal line changes.
For each module, design the states you will ship: default, sold out, sale, images blocked, long heading, dark mode. A Klaviyo block or a Mailchimp section should carry the same heading levels, alt text rules and spacing tokens as the Figma component. A new send then inherits the structure instead of rebuilding it. The same discipline sits behind a design system: one source, many surfaces, no quiet forks.
Some builders strip classes and rewrite styles. Inline the critical styles, and test the output after each change. What you see in Figma isn't what the client sends until you've opened that send.
How a change gets out
A designer changes the module and records it in a changelog.
A copy review checks reading order and link labels.
An accessibility check runs against the checklist inside the module.
A test send confirms the output in a real inbox.

A shade table in a beauty email shows why this is operational, not decorative. Shade name, size and stock have to be text in a table or a list. The colour chip can sit beside the name. It can't replace the name. Many public guides list contrast, alt text and headings, and stop before several editors, an approval chain and a recurring send. That's where regressions happen: someone pastes a poster into a "flexible" block, and next week's replenishment inherits the poster.
No campaign edits the base module. A campaign changes content inside it. If a send needs a new pattern, that pattern becomes a versioned module, or it doesn't ship.
How to Test Each Email Before It Sends
Run the checks in order. The first three decide whether this send goes. The later ones decide whether the base module is still trustworthy.

Switch images off and confirm the headline, the main button and the order still read as a sentence. Plenty of people on a phone start here, whether they mean to or not. The usual slip is one full-width banner that holds all the copy.
Set the text size to 200 per cent and check that nothing is clipped or overlapping. People enlarge type because the default is too small for them, not to stress your file. The usual slip is a fixed pixel height on a button.
Read the email with a screen reader and check the order and the link labels. This is how you hear the document you built. The usual slip is "Read more" repeated five times, with no product name.
Tab through every link and button and confirm the focus indicator is visible. Keyboard users need to see where they are. The usual slip is a button with no visible state, so focus lands in empty space.
Check the alt text on each image, including product photos and shade swatches. Decorative images get empty alt text. The usual slip is a file name left in the attribute.
Render the email in dark mode and in the clients your readers use most, including the main mobile apps and webmail in the UK. The usual slip is a logo with a thin dark outline that vanishes on a dark background.
Send to a test list, click every link, and confirm the unsubscribe works and the consent state is correct. A pretty file with a dead link is a broken task. The usual slip is a link still pointing at a staging address.
Log the results, name the reviewer and sign off before the send. A test nobody owns gets skipped on the busy week. The log is what the next editor reads.
Anything that fails in steps 1 to 3 blocks the send. Failures in steps 4 to 6 get logged and fixed in the base module before the next send, not patched inside one campaign and forgotten. The same care you give a product screen in UX and UI work belongs here: states, focus, labels, and a person who signs the file.
Run Your Next Send Through the Checklist
Pick the one recurring email with the highest volume. That's usually a welcome, a restock notice or an order update. Run it through the parts table and the testing checklist. Write down every failure, with the step where it showed up.
Fix each failure in the base module, not in that single email, so the next send inherits the repair. Check the consent and unsubscribe wording with your legal adviser. The exact words matter as much as the layout around them.
Bring the module list and the failure log to the first review. Agree one deliverable before anything else: one base module, and one tested send. If the programme has many recurring emails and no shared modules, the work is a system, not a pile of files. That's the point to bring in outside help.
Wecomeet's CRM Email Design service creates lifecycle email design systems that are built and tested for Klaviyo and Mailchimp. Wecomeet turns Figma designs into responsive email templates for Klaviyo and Mailchimp, supporting retail, fashion, beauty and fintech programmes.
Put a date on the first test send, and put that date in the calendar. A checklist without a send date stays a note.
Wecomeet designs and builds those lifecycle systems in Figma, then tests the templates in Klaviyo and Mailchimp for retail, fashion, beauty and fintech programmes. If your recurring emails still break when images are off or the column gets narrow, that's the work. Visit Wecomeet to talk through one base module and one tested send.