Running a pre-launch marketing compliance check, MBA Training, MBA Training
4/4+150 XP
Running a pre-launch marketing compliance check
# Running a pre-launch marketing compliance check
A €2 million launch campaign for a new electric SUV once went live across 14 markets with one wrong number: a WLTP range figure copied from a pre-production prototype. The correction cost more than the media spend, because every asset (web, configurator, dealer emails, paid social) carried the same claim. WLTP, the Worldwide Harmonised Light Vehicles Test Procedure, is the official EU test standard for range and emissions. Get the number wrong and you have a regulatory problem, not just a typo.
This lesson gives you the working checklist to clear a launch before the embargo lifts. An embargo is the agreed date and time before which no campaign asset may be public.
Why automotive marketing is heavily policed
Cars are expensive, safety-critical, and sold on emotion. Regulators know it, so the sector carries some of the strictest advertising rules outside pharma and finance.
Price and finance claims: monthly payments, APR (Annual Percentage Rate, the yearly cost of credit including fees), deposit terms.
Performance and safety claims: acceleration, autonomy features, driver-assistance capability.
Who enforces this?
United States: the Federal Trade Commission (FTC) polices deceptive advertising; the EPA governs fuel-economy and emissions claims; state law adds more. The FTC
set the bar for environmental claims and are being updated, so check the current version.
Europe: the EU Unfair Commercial Practices Directive is the backbone, reinforced by the 2024 Empowering Consumers Directive, which tightens greenwashing rules. In the UK, the Advertising Standards Authority (ASA) enforces the CAP Code, and the Financial Conduct Authority (FCA) governs any consumer-credit promotion.
The point for marketers: a stunning creative concept means nothing if the disclaimer is missing or the approval order was skipped.
The pre-launch sign-off checklist
Think of the check as four passes over every asset. Run them in order. Each pass has a named owner who signs off before the next begins.
Pass 1: Approval order (sequence, not just presence)
The most common launch failure is not a missing approval. It is approvals collected out of order, so a later change invalidates an earlier sign-off.
Correct sequence:
1. Factual accuracy (product/engineering confirms specs are final, not prototype).
2. Legal and compliance (claims, disclaimers, territory).
3. Brand (tone, logo, visual rules).
4. Media/trafficking (final files sent to platforms).
Why order matters: if brand approves a hero image, then engineering changes the confirmed range figure, the on-image disclaimer is now wrong and brand sign-off is stale. Legal must re-clear. Lock facts first.
Practical rule: every asset carries a version stamp and a sign-off log. If any figure changes, the version increments and the affected passes re-run.
Pass 2: Disclaimers and mandatory information
Every claim needs its qualifier, sized and placed so a normal reader actually sees it. "Small print no one can read" is itself a compliance failure under both FTC and ASA guidance.
Check each of these where relevant:
Range and efficiency: state the test standard (WLTP in Europe, EPA estimates in the US) and note that real-world figures vary. Never show a prototype figure.
Charging times: state the conditions (for example "10 to 80 percent on a 150 kW DC fast charger at 20°C"). Charging speed claims without conditions are misleading.
Finance: a representative example is usually mandatory. In the UK the FCA requires it to include APR, deposit, term, and total amount payable, all given equal prominence to the headline monthly figure.
Autonomy and driver assistance: this is the current enforcement hotspot. Language like "self-driving" or "autopilot" attracts scrutiny where the system is actually SAE Level 2 (partial automation requiring a supervising driver). Match the marketing word to the certified capability.
Price: on-the-road versus list price, which options are shown, and whether the pictured car matches the advertised price.
Pass 3: Territory and channel scoping
A single global campaign hits many jurisdictions at once. A claim that is fine in one market can be illegal in the next.
Watch for:
Range figures: WLTP for Europe, EPA for the US. Do not put an EPA number on a European page or vice versa.
Currency and finance: an APR example is jurisdiction-specific. A US "APR" example on a German site is meaningless and non-compliant.
Geo-targeting on social: paid social lets you target by country, so an asset with the wrong figure must be fenced to the correct territory, not run globally.
Configurator logic: the configurator (the online tool where a buyer builds their car) must only show trims, options, and prices available in the visitor's market. A US-only trim appearing on a French configurator is both a customer-experience and a compliance problem.
Pass 4: Fair-treatment and consumer-protection review
Beyond individual claims, regulators ask whether the whole campaign treats consumers fairly. The UK's Consumer Duty (FCA) and the EU's fairness rules both push this "outcomes" test.
Ask:
Would a non-expert understand the total cost, not just the monthly figure?
Are vulnerable consumers considered (for example, high-pressure "offer ends midnight" tactics)?
Does the configurator make the cheapest compliant path clear, or does it hide the base price behind a pre-loaded expensive build?
Is the environmental story honest end to end, or does one green headline oversell a car with a small electric-only range?
🎬 [VIDEO: "How the FTC Green Guides Affect Your Marketing" - youtube.com - plain-language walkthrough of environmental claim rules that mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → directly onto EV range and 'eco' messaging]
A worked example: clearing the configurator
Say the new SUV launches with a WLTP range and a finance offer. Here is a minimal check log you might keep. This is illustrative structure, not a real vehicle's figures.
ASSET: EV-SUV configurator, DE market, v3
------------------------------------------------
CLAIM CHECK STATUS
WLTP range 480 km final spec sheet? PASS (eng v-final)
Test standard shown "WLTP" on page? PASS
"up to" qualifier present + visible? PASS
Charge 10-80% 28 min conditions stated? FAIL -> add kW + temp
APR representative equal prominence? PASS (FCA-style ex.)
Currency EUR only? PASS
Trims shown DE-available only? PASS
Approval order facts->legal->brand? PASS
------------------------------------------------
RESULT: 1 FAIL -> re-run Pass 2, re-legal, re-version to v4
One failed line (charging conditions) forces a re-version and a re-run of the legal pass. That is the discipline: a single fail resets the affected passes, not the whole project, as long as your log tells you exactly what changed.
Knowledge check
1. The opening example of the electric SUV launch with a wrong WLTP figure primarily illustrates which concept about pre-launch compliance?
2. Why does the lesson describe automotive marketing as being 'heavily policed' compared to most other sectors?
3. A team is checking a US campaign that claims a vehicle is 'zero emissions.' Which authority's standards are most directly relevant to validating that environmental claim?
MULTIPLE CHOICE
4. Select ALL correct answers about the claim categories that trigger most compliance trouble in automotive marketing.
Select all the correct answers.
MULTIPLE CHOICE
5. Select ALL correct answers about the European regulatory landscape for automotive marketing described in the lesson.
Select all the correct answers.
Common launch-day failure modes
Even with a checklist, launches slip. The recurring causes:
Copy-paste across markets: the fastest way to spread one wrong figure everywhere. Fix at source, then check each localised version separately.
Prototype figures leaking in: press assets and internal decks use pre-final specs. Never let those feed public copy.
Stale approvals after a late change: the classic. A pricing tweak on launch eve invalidates everything downstream.
Social scheduled ahead of embargo: a scheduled post that fires early breaks the embargo and can void an entire coordinated reveal. Double-check time zones on every scheduler.
Influencer and dealer content: third parties are still your responsibility. In the US the FTC requires clear disclosure of paid partnerships (#ad is not optional), and dealer-run local ads must carry the same disclaimers as national ones.
A note on autonomy claims: this is where 2026 enforcement is most active. Regulators on both sides of the Atlantic have pushed back on driver-assistance marketing that implies more capability than the system is certified for. If engineering says Level 2, marketing says "driver assistance," never "self-driving." Keep the certified capability and the marketing verb in the same sentence during sign-off.
Building the check into your workflow
The checklist only works if it is a gate, not a suggestion. Practical setup:
One shared sign-off log per launch, visible to product, legal, brand, and media.
Version stamps on every asset. No stamp, no traffic.
A named "embargo owner" who holds the go/no-go and controls scheduler access.
A market-by-market matrix so no territory ships an unchecked figure.
Key Takeaways
Lock facts before anything else. Engineering-final specs first, then legal, then brand, then media. Out-of-order approvals are the top launch failure.
Every claim carries its qualifier, visibly. Range needs its test standard (WLTP or EPA), charging needs conditions, finance needs a representative example with equal prominence.
Scope by territory and channel. WLTP for Europe, EPA for the US; fence geo-targeted social; keep the configurator showing only market-available trims and prices.
Match marketing words to certified capability, especially on driver-assistance. "Self-driving" language on a Level 2 system is the current enforcement flashpoint.
One failed check re-versions the asset and re-runs the affected passes. The log tells you exactly what changed, so you fix the line, not the whole campaign.