**In short:** A brief turns into a game of telephone when the request travels by call, audio and chat with nothing written down. Each hand-off loses context and the work comes back wrong. The way out is one written brief in one place: objective, audience, deadline, named approvers, success criteria.

The request is born in a phone call. The client explains without rushing, gives context, mentions a campaign they saw and liked. On the other end, account management writes down what it can.

Then the call becomes a two-minute voice message in the coordinator's WhatsApp. The voice message becomes two lines in the creative team's chat. Creative does what can be done with two lines.

v1 comes back wrong. v2 fixes the wrong problem. On v3, somebody calls the client and finds out the original request was something else. Nobody lied at any stage. The request was just never written down.

## The cost has a measurement, the habit does not

The BetterBriefs Project, presented at the IPA's EffWorks Global in October 2021, found that respondents estimate roughly a third of the marketing budget goes to waste on poor briefs and misdirected work. The same study measured the distance between the two ends: 80% of marketers think they write good briefs and only 10% of creative agencies agree.

And the volume at stake keeps growing. Advertising agencies in Brazil put R$ 5.58 billion into media in the first quarter of 2026, up 18.4%, according to the Cenp-Meios panel released by CENP on July 14, 2026. More money running through the same old process.

Rework became an accepted cost for one simple reason: it shows up in no report. A delay has a date, a time and a client chasing it, as we covered when writing about [delivery delays putting an agency at risk](https://blog.wikimee.com/en/atrasos-na-entrega/). Rework does not. It keeps getting paid for as if it were a natural part of the creative craft. It is not.

That pattern shows up in almost every operational diagnosis. When we listed [the five most common operational problems in agencies](https://blog.wikimee.com/en/problemas-operacionais/), several of them traced back to the same origin: information lost between whoever asks and whoever executes.

## Five fields stop the game of telephone

No three-page form needed. Five fields are enough:

1. The objective of the job in one sentence.
2. Audience and single message.
3. Deadline with date and time.
4. Named approvers.
5. Success criteria.

Success criteria is the only one that needs explaining: it defines how everyone will know the work is right before the work exists. That is what prevents the fourth version.

Just as important as the fields is where they live. A brief written across five different channels is still a game of telephone, only in writing. The request has to come in through one path, visible to whoever asks and whoever executes. At Academee, Wikimee's education arm, the Central de Demandas sem Ruído track, inside the [Demand and Productivity journey](https://academee.ai/jornadas/demandas-produtividade/), covers exactly this single point of intake, in Portuguese.

Peter Carloni argues that a brief is a contract of expectations, not bureaucracy. Whoever treats the brief as a formality pays its price in versions.

## Frequently asked questions

**Does a written brief make the process slower?**

Writing the five fields is minutes of work. The round of rework they prevent is measured in days and lost ROI. The process gets faster overall, even though intake takes one step longer.

**Who should write the brief, the client or the agency?**

Whoever asks writes, whoever executes confirms. The safest format is for the request to come in through required fields and for the agency to send back its reading of it before producing. Written confirmation is what kills ambiguity.

**Can a WhatsApp voice message be a brief?**

It can be the start of one. The problem is not the audio, it is the audio as the final record. If the information is not transcribed to a place where everyone reads the same thing, each person will remember a different version of the same request.

## Where this stops being theory

An operation that takes requests through a form with required fields, routes them to the right queue and records who approved what removes the game of telephone at intake. Wikimee is the creative operations platform that brings demand, production, approval and assets together in a single, integrable environment, and the practical effect is this: a request that comes in written goes out traceable. The conversation with the client stays human. It is the record that stops depending on everyone's memory. To see it up close, the path is to [look at the platform and book a conversation](https://www.wikimee.com/en/produtos/).