A Brief is the structured artifact that anchors a Campaign. It captures the inputs that the Composer and the rendering layer need to produce work that is both on-brand and on-target: goal, key message, audience, KPI, channel mix, deadline, mandatories, things to avoid, target keywords, search intent, and the deliverables list with volumes.
Why structured, not free-text
A free-text creative brief is fine for a human reading it. It is not enough for a rendering layer that needs to make decisions about copy length, image aspect ratio, voice register, and mandatory inclusions across 40 variations in parallel. The Brandflux brief is structured so each field maps cleanly to a rendering input. The brief author writes prose where prose belongs (goal, key message) and picks from constrained options where the system needs a clean answer (channel mix, deliverables).
What gets approved together
The brief is approved as part of the Plan macro, alongside references and named Directions. The approval unit is the plan, not the brief in isolation. There is no per-step “Lock brief” gate. This matters because briefs read differently once the Directions are visible: a goal that sounded right in the abstract sometimes needs a small edit once the team sees what it produces visually.
Editing after approval
A brief can be edited mid-campaign. The system tracks the edit, the renders downstream pick up the new fields on the next regenerate, and the approval state resets if the edit changes a field that the plan-level approval depended on. Edits that change tactical fields (channel mix additions, deliverable volume adjustments) don’t require re-approval. Edits that change strategic fields (goal, key message, audience) do.
Related on this site
- /glossary/campaign is the container the brief lives inside.
- /glossary/direction is the next artifact in the plan.
- /glossary/plan-make-ship is the approval boundary.