Brief routing is the decision layer between "client approved the brief" and "work begins": who leads it, who executes it, and what queue it enters. In most studios this happens by availability and habit — whoever's free, whoever did the last one for this client. Sometimes that's fine. Often it's how a brand campaign lands on a production generalist while the senior team polishes a resize.
Why routing is a creative decision, not an admin one
The same brief produces radically different work depending on who receives it. That's obvious. What's less obvious is that routing also shapes the brief itself: a routed-to-senior brief can stay at the level of intent, while a routed-to-junior brief needs more explicit constraints. Routing determines how much direction you have to write down — and how much you can leave to judgment.
Poor routing shows up downstream as quality variance, revision churn, and utilization problems. If your seniors spend a third of their time on work a mid-level could do, that's a routing failure before it's a team utilization failure.
The four inputs to a routing decision
- Complexity class. Not all briefs are equal. A useful taxonomy: origination (new campaign, new look), adaptation (existing look, new formats), and production (resizes, versions, localization). Each class maps to a different experience band.
- Skills match. Motion, stills, copy, look development, 3D. Obvious, but only if you actually track skills per person rather than relying on memory.
- Client history. Who knows this client's taste, veto patterns, and politics? Client fluency is a real productivity multiplier — the argument of client memory software applied to staffing.
- Capacity and sequencing. Real availability, including what's about to land. Routing a job to someone who becomes free in week two of a three-week job is a delay you chose on day one.
A simple routing matrix
| Brief class | Lead | Support | Notes |
|---|---|---|---|
| Origination — new campaign / new client | Senior creative | Strategist, mid designer | Brief needs stakeholder alignment before kickoff |
| Origination — existing client, new campaign | Senior or strong mid | Mid/junior pair | Lean on client history; check veto list first |
| Adaptation — new formats, known look | Mid creative | Production artist | Brief must include locked look references |
| Production — versions, resizes, localization | Production queue | — | Candidate for AI-assisted pipeline with QA gate |
The matrix isn't bureaucracy; it's a way to stop re-deciding the same question every Monday. It also protects seniors for the work that actually needs them, which is where margin lives — see where agency margin leaks hide.
Routing the brief with the context attached
Here's where routing usually breaks: the right person gets the job, but the context doesn't travel with it. The brief goes out as a PDF; the client's feedback history stays in the account lead's head; the look references live in last quarter's drive folder. The routed designer spends two days reconstructing context instead of designing.
This is the problem a memory-based studio solves structurally. In Etch, every brief is attached to the client's Brain — voice, product, look, and feedback profile — and the Creative Director turns the brief into a visible plan that routes into the Canvas pipeline. Whoever picks up the work inherits the context, not just the document. The handoff problem stops being a tax on every assignment.
A good routing decision with no context transfer is just a slower bad routing decision.
Where AI fits in routing
AI is well suited to the classification half of routing: reading an incoming brief, classing it (origination vs. adaptation vs. production), extracting the skills required, and flagging the client-history considerations. It's poorly suited to the judgment half: who needs growth opportunities, whose plate is politically complicated, which client relationship needs a senior face this quarter. Keep the human on the judgment; give them the classification for free. That division of labor runs through everything in creative operations platforms.
Two practical starting moves: tag every completed job with its class and who worked on it (three months of this and you have a real dataset), and write the routing rule down when you deviate from the matrix, so exceptions become policy instead of lore.
Common routing mistakes
Four patterns account for most routing failures:
- The comfort route. Every brief for a client goes to whoever did the last one. Client fluency is real, but mono-routing creates single points of failure and burns out your best people on work a mid could grow into.
- The prestige route. Seniors grab the visible work and juniors inherit production forever, so nobody develops and every departure is a crisis. Route at least one stretch job per quarter per person.
- The availability route. Assigning by who's free this week, regardless of class match. Availability matters, but as the last filter, not the first.
- The context-free route. Right person, no history. The designer spends two days excavating what the account lead already knows. Fix the handoff, not the hire.
Each of these is a policy failure, not a people failure — which is good news, because policy is cheap to change.
The payoff
Good brief routing compounds. Work matches skill, so revision rounds shrink. Seniors concentrate on origination, so the studio's ceiling rises. Juniors get production work with real constraints, so they grow. And because context travels with the brief, every routing decision costs less to execute. It's unglamorous operational work that shows up, unmistakably, in the work itself.