Creative brief vorlage

DACH marketing teams (Germany, Austria, German-speaking Switzerland) frequently inherit US creative-brief templates and translate them - badly. The translation problem isn't linguistic; it's structural. A US brief assumes US regulatory context (no GDPR-by-default, looser advertising claims, broader competitive-comparison freedom). A DACH brief has to bake in different defaults: GDPR-compliant data assumptions, HWG (Heilmittelwerbegesetz) constraints for health-adjacent products, UWG (Unlauterer Wettbewerb) constraints for comparative advertising, and Swiss-specific rules in CH.

The template above is structured for DACH-market realities. Bilingual section headers (German primary, English in brackets) so it works in mixed teams - common in DACH agencies and startups where Slack defaults to English but creative briefs are written by German-first marketers. Field examples calibrated to the regulatory and cultural defaults of the region.

The three filled-in examples each take a DACH-specific category: bio FMCG (Heimwerk Foods - Bavaria), B2B SaaS targeting GDPR-conscious Mittelstand (Datentor - Frankfurt), and Swiss-German fashion (Berghaus Zürich - Ticino). Each shows how the brief structure adapts to the region without losing the load-bearing discipline (behavioral audience, single-sentence angle, explicit don'ts).

Three regulatory defaults to bake in. First, HWG (Heilmittelwerbegesetz) restricts health and supplement claims aggressively in Germany - far stricter than FDA equivalents in the US. Any wellness, supplement, or food brand brief in DACH needs HWG-aware don'ts. Second, UWG (Gesetz gegen den unlauteren Wettbewerb) limits comparative advertising in Germany and Austria; direct competitor-naming requires legal review. Third, GDPR for retargeting and lookalike audiences changes the data-collection and tracking section of any brief targeting DACH users.

Cultural defaults to consider. German-speaking audiences tend to respond worse to high-emotion, low-information ad copy than US audiences. The 'transformation' archetype that works in US DTC often reads as untrustworthy in DACH; problem-solution and demo archetypes typically outperform. Founder-to-camera works if the founder speaks the audience's language register (Hochdeutsch for cross-DACH, regional dialects only for region-specific campaigns).

Localization is not translation. A US ad localized to German via direct translation almost always underperforms. The brief should specify whether the campaign is translated (cheap, fast, weaker performance), localized (re-shot with German creators, German cultural references), or DACH-native (concept developed for DACH from the start). The third tier costs more and performs better; the brief should be explicit about which tier is being commissioned.

Germany (DE) uses Hochdeutsch, accepts more formal address ('Sie' for most B2B; 'Du' increasingly common in DTC for younger audiences). Austria (AT) uses Hochdeutsch with Austrian vocabulary swaps (Jänner not Januar; Erdäpfel not Kartoffeln); the brief should flag whether creative copy needs AT-specific adaptation. Switzerland (CH) uses Swiss High German in written form but Schweizerdeutsch in spoken/video creative; pricing in CHF, payment methods include PostFinance and TWINT.

If you're running a pan-DACH campaign, the brief should specify whether creative is shared across all three markets or adapted per market. Shared creative cuts cost; adapted creative cuts CAC. The right answer depends on the category - regulated categories (financial services, health) almost always need per-market adaptation; lifestyle categories often run shared creative successfully.

Internal links: for the English-only version, see creative brief template. For German-equivalent examples, see creative brief examples.

Download the markdown file from the template card above. The structure converts cleanly into the three formats common in DACH agencies: Word (still dominant in larger German corporates), Google Docs (common in startups and agencies), and Notion (rising fast in DACH product teams).

For Word: paste markdown content; Word will treat headers as styled text. Manually apply heading styles if you need a table of contents. For Google Docs: paste with 'Strg+Shift+V' (keep source formatting off), then apply heading styles - Docs renders markdown headings as plain text otherwise. For Notion: paste directly; Notion auto-converts markdown to native blocks.

If your team operates in Confluence (common in Mittelstand IT-led orgs), import the markdown via the Confluence markdown macro. The structure preserves; the formatting needs one cleanup pass.