Direction-Selected is the deliverable state name for a Direction the Client has signaled as their pick at concept review. It is the signal that focuses the Make-phase team’s rendering effort on one Direction rather than spreading credits across the unpicked ones.
Naming is deliberate
The state is Direction-Selected, not “directional approval” and not “Directionally-Approved”. The wording matters because Brandflux reserves formal-approval terminology for the Final approval stage. Concept review is the Client expressing preference, not signing off on shipping. Confusing the two states muddles what was actually committed at each gate, which becomes a problem when audit trails come into play six months later.
What Direction-Selected does
- Marks the Direction in the campaign view with the Selected badge so the team knows where to focus.
- Triggers the Hero render tier auto-routing for reels if the Selected Direction was also flagged Recommended by the Lead.
- Tags the unpicked Directions as not-selected. They stay in the archive (visible, not deleted) for reference and possible revival.
What Direction-Selected does not do
- Does not approve any specific Variation for delivery.
- Does not lock the Direction’s notes against further edits.
- Does not commit credits beyond what the Lead chooses to spend on production renders.
- Does not produce a locked master, a DAM entry, or anything the Client can download.
Reversibility
A Direction-Selected state can be changed. The Client can switch picks late in the campaign, the Lead can re-pick on the Client’s behalf with documented authorization, and the unpicked Directions remain available for the swap. The system tracks the change and resets downstream approval state on affected deliverables.
Related on this site
- /glossary/direction is the artifact that carries the state.
- /glossary/final-approval is the formal-approval gate that comes later.
- /glossary/anchor is the Variation that represents a Direction at concept review.