Build a set of email assets that look like one brand

Create a consistent set of email templates that work across platforms and prevent brand drift in every campaign.

For anyone whose emails all look slightly different · 8 steps · 7 min

How it works today.

You build each campaign by copying the last one that looked decent, then tweaking colours, fonts, and layout until it feels right. Headers end up different heights, call-to-action buttons shift from blue to green to orange, and your footer contact info says three different things depending on which template someone grabbed.

When a new person joins the team, they create their own version because they cannot find the 'right' template. Your brand guidelines exist as a PDF somewhere, but translating them into actual email code means starting from scratch every time. Nothing is reusable, and every send looks like it came from a different company.

Before you start.

All of it has to be true, or step one fails in a way that is annoying to debug.

Access to your current email platform's template editor or HTML export function
Your brand guidelines document with specific hex codes, fonts, and spacing rules
A folder of your last 5-10 email campaigns to audit for inconsistencies
Write access to wherever your team stores shared templates

The steps.

Audit your existing email variations
Open your last 10 campaigns and screenshot the headers, buttons, and footers. Look for differences in font sizes, colours, spacing, and messaging. Note which elements work well and which create confusion.

Extract your brand requirements into email specs

Convert your brand guidelines into specific email requirements: exact hex codes, font families with web-safe fallbacks, button dimensions, and spacing measurements. If your guidelines say 'friendly tone', write actual subject line and body copy examples.

Paste this

Based on these brand guidelines: [paste your brand guidelines], create specific email template requirements including: exact hex codes for primary and secondary colours, font families with web-safe fallbacks, button styling (padding, border-radius, font-size), header and footer specifications, spacing rules between sections, and 3 example subject lines that match our brand voice.

Design your template structure options

Create wireframes for 3-4 template types you actually send: newsletter, promotion, announcement, and transactional. Each should specify where images go, how many text blocks you need, and whether the call-to-action is a button or link.

Paste this

Design 4 email template wireframes for these types: [newsletter, promotion, announcement, transactional]. For each template, specify: header section (logo placement and height), main content areas (number of text blocks and image placements), call-to-action section (button vs link and positioning), footer section (required legal text and contact info). Make them work for both desktop and mobile viewing.

Generate the HTML and CSS code

Use your wireframes and brand specs to create actual email HTML. Email HTML is different from web HTML - it needs inline CSS and table-based layouts for older email clients. Test that your code renders correctly in a preview tool.

Paste this

Create email-compatible HTML templates using these specifications: [paste your brand specs and wireframes]. Use inline CSS and table-based layouts for maximum email client compatibility. Include media queries for mobile responsiveness. Generate separate HTML files for each template type, with placeholder text and image areas clearly marked with comments.

Build platform-specific versions
Import your HTML into your email platform and adjust for its specific requirements. Some platforms need custom merge tags, others require specific class names. Create a version that works with your platform's drag-and-drop editor if you have non-technical users.
Test across email clients and devices
Send test emails to Gmail, Outlook, Apple Mail, and at least one mobile client. Check that fonts fall back correctly, images load, and buttons are clickable. Fix any rendering issues before finalizing the templates.
Create your template library structure
Save each template with clear naming conventions in your platform's template library. Include usage notes for each template type: when to use it, which sections are required vs optional, and character limits for subject lines and preview text.

Document the template system

Write a one-page guide showing which template to use for which campaign type, how to customize without breaking the design, and who to ask when you need a new template variation. Include screenshots of the correct vs incorrect usage.

Paste this

Create a template usage guide that includes: when to use each template type, step-by-step instructions for customizing content without breaking the design, character limits for subject lines and preview text, examples of correct vs incorrect template usage, and escalation process for requesting new template variations. Make it scannable with clear headings and bullet points.

What you keep.

Automating the typing does not move the accountability. These stay with a person.

Final approval of each template before it gets saved as a master version
Deciding which template type fits each campaign you send
Reviewing template usage across your team to catch brand drift before it spreads
Updating templates when your brand guidelines change