Mandatories are the must-include elements on every relevant asset. They live in two places: as a brand-wide field on the Brand DNA (the brand always carries them) and as a per-Campaign field on the Brief (this specific campaign also needs these). Composer stamps them on every variation automatically.
Two flavors
- Brand mandatories. Logos, lockups, signature taglines, brand-required imagery elements. Configured once on the Brand DNA; carried on every campaign for that brand forever.
- Mandatory legal copy. Regulator-required text: pharma claims, financial disclaimers, gambling fine print, alcohol responsibility lines, country-specific compliance. Configured on the DNA (brand-wide) or the brief (per-campaign). Per-campaign mandatories stack on top of brand-wide; both fire automatically.
Why this is a hard constraint, not a guideline
Mandatories are the field where “the designer forgot to include it” is a compliance event, not a typo. A pharma asset shipped without the required risk disclosure is a regulatory issue. A financial ad without the fee disclaimer is a CASL or SEC issue depending on jurisdiction. Brandflux treats mandatories as render-time constraints rather than checklist items. Composer stamps them, asset preparation validates them, and regulated campaigns block at export if a required mandatory is missing.
The agency advantage
For agencies running regulated-vertical clients (fintech, health, alcohol, gambling), mandatories on the Brand DNA mean the legal review converges on a configuration once, then every variation produced for that brand inherits the configuration. The legal team stops being a per-asset checkpoint and becomes a per-DNA-revision checkpoint. The throughput math changes substantially.
Related on this site
- /glossary/brand-dna holds the brand-wide mandatories.
- /glossary/brief holds the per-campaign mandatories.
- /glossary/composer does the auto-stamping.
- /use-cases/paid-social-variations is the canonical regulated-vertical scenario.