How to Evaluate Brand Consistency in AI-Generated Emails

Approve an AI-generated email only when it matches a dated brand reference across nine areas and leaves evidence for every score. Use the rubric below to decide whether the exact email version is ready, needs revision, or should be rejected.

Use this method to evaluate one email artifact. Platform and model remain out of scope. A brand kit records inputs; review determines whether the output follows them.

This is an original operational rubric, not a validated scientific scale or product benchmark. Thresholds make team decisions consistent; they do not predict campaign performance or prove one tool better than another.

Affiliation disclosure: Marketing Wiki maintainers and contributors include people affiliated with Migma. Migma receives no score, ranking, or claim of superiority.

Build the review packet first#

Freeze the material the reviewer will compare. A useful packet contains:

final HTML and rendered screenshots tied to an immutable version or content hash;
campaign brief, audience, primary message, and intended action;
current brand guide with version date and owner;
approved voice examples and prohibited terms;
exact color, typography, spacing, button, and footer tokens;
approved logo files, image treatments, and example campaigns;
desktop, mobile, light-mode, dark-mode, and image-blocked renders where relevant.

Do not guess a missing brand rule. Mark that category NE for not evaluable, name the missing evidence, and return the review to the brand owner. Missing evidence blocks approval.

Score each category from 0 to 2#

Scroll table →

Score	Meaning	Reviewer action
2	Output matches approved reference, or a documented exception is intentional.	Record evidence and keep.
1	Localized drift can be corrected without changing campaign concept.	Request a specific revision and score again.
0	Material mismatch affects identity, meaning, usability, or trust.	Reject this version.
NE	Approved reference or test evidence is missing.	Pause approval and request evidence.

Any blocking defect overrides the total score.

Nine-part brand consistency rubric#

Scroll table →

Category	Score 2: match	Score 1: revise	Score 0: reject	Evidence required
Voice	Vocabulary, tone, formality, point of view, sentence shape, product names, and approved CTA language match the voice guide and reference copy. Prohibited terms are absent.	A few phrases drift in tone or terminology, but the message and position remain correct.	Copy uses the wrong persona, changes positioning, invents brand language, or conflicts with a named voice rule.	Voice-guide version, two approved samples, and annotated copy showing each checked passage.
Color	Every visible color maps to an approved token and its allowed role. Background, text, link, accent, and state colors stay within the palette.	One or two local values are wrong, duplicated, or used in the wrong role.	Dominant palette belongs to another identity, obscures key content, or cannot be mapped to approved tokens.	Token list with exact values, rendered screenshots, and sampled color report.
Typography	Heading, body, label, and CTA styles use approved font stacks, fallbacks, weights, sizes, line heights, and casing.	A local size, weight, line height, or fallback differs from the type scale.	Main type system is replaced, hierarchy collapses, or unsupported fonts leave no acceptable fallback.	Typography tokens, fallback stack, and rendered type samples from target inboxes.
Spacing	Margins, padding, section rhythm, alignment, and density follow approved tokens or reference modules. Repeated elements use the same interval.	One section is too tight, loose, or misaligned, while the larger rhythm remains intact.	Layout density and alignment no longer resemble the brand system or make the message hard to scan.	Spacing tokens, annotated render with measured gaps, and approved module reference.
Imagery	Logo variant, photography, illustration, crop, color treatment, product imagery, and icon style follow the guide. Asset source and usage approval are recorded.	One crop, treatment, or icon family needs a local change.	Wrong logo or product appears, imagery contradicts brand direction, or asset source and permission cannot be established.	Asset URL or file ID, approval or license record, image-treatment rule, and final crop.
Hierarchy	First screen, section order, headline, supporting proof, and visual emphasis serve the brief. One primary message is easy to find.	One competing element or weak transition interrupts an otherwise clear reading order.	Wrong message dominates, essential context is buried, or structure points readers toward a different campaign goal.	Campaign brief and annotated desktop and mobile reading order.
CTA	Primary CTA label, visual style, prominence, destination, and surrounding promise match the approved campaign action. Secondary actions remain subordinate.	CTA wording or styling drifts, but destination and offer remain correct.	CTA points to the wrong place, changes the offer, hides the intended action, or creates competing primary actions.	Approved action, final destination URL, button tokens, and received-email click test.
Footer	Approved footer module uses the correct entity, address, links, preference or unsubscribe controls, social accounts, and visual treatment for the program.	Required elements work, but a local spacing, color, copy, or social-link treatment has drifted.	Wrong sender entity appears, a required element is absent, or an unsubscribe or identity link fails.	Approved footer reference, program requirements, received-email screenshot, and completed link tests.
Accessibility	Content follows the program's chosen accessibility baseline. Text contrast, alternatives for informative images, reading order, descriptive links, and non-color cues are verified in final output.	One isolated issue is fixable and does not prevent the intended action.	A recipient cannot understand or complete the main action because of contrast, image-only meaning, broken reading order, or inaccessible link treatment.	Contrast report, alternative-text review, structure or reading-order check, and final rendered test.

For a WCAG 2.2 Level AA baseline, normal text needs at least 4.5:1 contrast and large text needs at least 3:1. WCAG also covers text alternatives and information conveyed through color. Treat these as selected checks, not proof of full WCAG conformance or legal compliance. See the W3C Recommendation.

Footer requirements depend on message type, sender, recipients, and jurisdiction. For US commercial email, the FTC CAN-SPAM compliance guide covers accurate sender information, a valid postal address, and a working opt-out method. A qualified owner must define the rules for each email program.

Decide: approve, revise, or reject#

Add the nine numeric scores only after every category has evidence.

Approve

Approve when all conditions are true:

total is 16 to 18;
no category is 0 or NE;
footer and accessibility both score 2;
every exception is named, intentional, and approved;
reviewer signs the exact email version.

Revise

Request revision when:

total is 10 to 15 with no score of 0;
any category is NE;
footer or accessibility scores 1;
defects can be corrected without replacing campaign concept.

List each change as a testable instruction. “Make it more on brand” cannot be reviewed. “Replace #2367E8 with approved primary blue #1D4ED8 on both CTA buttons” can.

Reject

Reject the version when:

total is 9 or lower;
any category scores 0;
wrong brand, sender entity, offer, product, or CTA destination appears;
primary action is not usable;
resolving drift requires a new concept or broad structural rewrite.

Record rejection against the email version. Save the evidence so a new version can be tested against the same packet. Tool-level conclusions require repeated tests.

Copyable review record#

email_version: "sha256 or immutable version ID"
brief_version: "brief ID and date"
brand_guide_version: "guide ID and date"
reviewed_at: "ISO-8601 timestamp"
reviewer: "named human"

scores:
  voice: { score: 2, evidence: [], notes: "" }
  color: { score: 2, evidence: [], notes: "" }
  typography: { score: 2, evidence: [], notes: "" }
  spacing: { score: 2, evidence: [], notes: "" }
  imagery: { score: 2, evidence: [], notes: "" }
  hierarchy: { score: 2, evidence: [], notes: "" }
  cta: { score: 2, evidence: [], notes: "" }
  footer: { score: 2, evidence: [], notes: "" }
  accessibility: { score: 2, evidence: [], notes: "" }

total: 18
decision: "approve | revise | reject"
blocking_findings: []
required_changes: []

Any edit to copy, assets, colors, layout, CTA, footer, or generated HTML invalidates affected scores. Re-run those categories against the new version.

Use rubric for product comparison only with controlled evidence#

Brand kits and website import describe inputs, not output quality. A defensible platform comparison would give each product same source packet and campaign brief, generate repeated outputs, hide product identity from trained reviewers, publish raw category scores, and report reviewer disagreements. Until that test exists, score emails rather than vendors.

Build source packet with website-to-on-brand-email method. Use AI email capability matrix for vendor documentation, then pre-send review checklist for final campaign gate.