In an agency, almost no brief arrives in writing and complete. It arrives in an hour-long meeting, in a video call that gets cut short, in three WhatsApp voice notes and in an "I'll explain it better over the phone". The creative team gets going with whatever someone jotted down, and two weeks later the client sees the first proposal and says that isn't what they asked for. The rework doesn't come from a bad idea. It comes from a brief that never became a document.
Transcribing the brief with AI closes that gap with very little effort. You record the conversation, upload it and within minutes you have the full text, a summary by topic and a list of requests and tasks. This guide explains how to do it, what to pull out of the transcript and how to turn it into a scope document the client signs off on before anyone opens a design file.
Why spoken briefs lead to rework
The brief is the conversation where the client explains what they want, and it is also the conversation that gets documented worst. That happens for very specific reasons:
- The client doesn't know what they want yet. They work it out as they talk, contradict themselves and refine along the way. Whoever is taking notes writes down the first version and misses the last one.
- Wishes get mixed up with requirements. "I'd like something fresh" and "it has to be in three languages" come out in the same sentence, but they don't carry the same weight.
- Nobody writes down what's left out. The client mentions in passing that "another vendor handles the website", and that sentence never reaches the team.
- The person listening isn't the person doing the work. The account manager takes the brief; the designer or copywriter gets a second-hand summary.
With a transcript, the team doing the work can read the client's exact words. And when the proposal drifts, instead of arguing over memories you re-read the moment each thing was asked for. It's the same logic we apply when transcribing a new client's kickoff meeting, just one step earlier: here the job itself is still being defined.
What to extract from a transcribed brief
A useful brief fits on one page. The transcript is the raw material; the scope document is what comes out of it. This table sums up what to look for in the text and where each item ends up:
| Block | What to look for in the transcript | Where it goes |
|---|---|---|
| Objective | What the campaign or piece is for, in the client's own words | First line of the scope document |
| Audience | Who it's aimed at and who it isn't | Audience block |
| Deliverables | Which pieces, in which formats, for which channels | Closed list of deliverables |
| Constraints | Brand, tone, colours, languages, legal, deadlines | Mandatory requirements |
| References | What they like and, above all, what they don't want | References appendix |
| Out of scope | Anything they mentioned that another vendor handles or that's left for a later phase | Explicit exclusions section |
| Open items | Materials the client has to send, with dates | Task list with owners |
The exclusions section is the one most agencies skip and the one that prevents the most rework. A client who sees in writing that "social media adaptations are out of scope for this phase" argues about it now, not once everything has been laid out.
How to transcribe the brief step by step
- Give notice and record. Say at the start that you're recording so you can send an accurate summary; clients usually see it as a safeguard, not a nuisance. On a video call, use the native recording; in person, leave your phone on the table. If you have legal doubts, our guide on when it is legal to record meetings and calls in Spain sums it up.
- Walk through the blocks in the table. You don't need a rigid script, but before wrapping up, ask explicitly about deliverables, deadlines and what's out of scope. What gets said out loud is what the AI turns into a task.
- Include the loose voice notes. If the client sent WhatsApp voice notes before or after the meeting, transcribe those too: they are part of the brief. Our guide to transcribing voice notes from your phone explains how to get them off the device.
- Upload the file. The MP4 from the video call works, as does any MP3, M4A or WAV. In a few minutes you have the full text, a summary by topic and the list of tasks and key points.
- Check names, figures and dates. Brands, products and deadlines are the only things worth going over by hand before you write the document.
The whole process takes less time than an internal meeting to "align on what the client said". If you want to try it on your latest brief, VOCAP gives you free minutes when you sign up and one-time packs after that, with no subscription.
From transcript to a scope document the client signs off on
The transcript is for the team; what the client receives is the scope document. Send it the same day or the next, while the conversation is still fresh, with this structure:
- The objective in one sentence, quoting the client's own words if that helps. If they recognise themselves in it, that's the best sign the brief has been understood.
- Numbered deliverables, with format and channel. No "social media assets": how many, for which network and in what size.
- Mandatory requirements: languages, brand guidelines, legal constraints, delivery date.
- Out of scope, as a short, explicit list.
- What we need from you: materials, access and approvals, each with a date.
- Open questions: the contradictions the transcript reveals. Better to ask them now than to resolve them in the design.
Close by asking for a written "OK". That sign-off, together with the archived transcript, is what turns a mid-project change of mind into a scope extension rather than free rework. When the brief includes an ideas session with the client, the same approach makes sure nothing gets lost: in our guide on transcribing brainstorming sessions we explain how to separate ideas from decisions.
How it fits into the agency's day-to-day
The value of transcribing briefs grows when it becomes a habit rather than an exception. A few practices that work in small and mid-sized teams:
- One folder per client and project with dated transcripts. When the client comes back six months later asking for "something like last year's", the original brief is one click away.
- The creative team reads the transcript, not just the summary. A copywriter who reads the client saying "I don't want to sound like a bank" writes differently from one who gets "friendly tone" on a brief sheet.
- Compare brief and proposal before presenting. With the transcript in front of you, go through every deliverable and every requirement. It's the cheapest review there is.
- Transcribe the feedback rounds too. The changes requested when you present the proposal are a second brief, and they usually get documented even worse than the first.
- Update the scope document with every round. Note the date of the session where something changed. When it's time to invoice, the history explains every extension on its own.
With this habit, the agency stops depending on the account manager's memory and gains something clients value a great deal: the feeling that they've been listened to precisely.
Common mistakes and best practices
- Sending the client the full transcript. It contains doubts, internal comments and half-finished sentences. Send the scope document; the transcript is your backup.
- Recording without saying so. Always ask for permission and respect a no. If you can't record, record a voice note on your way out with everything you remember and transcribe that: it preserves most of the value.
- Treating WhatsApp voice notes as casual chat. Very often they are the real brief. Transcribe them and file them with everything else.
- Not asking what's out of scope. If the client doesn't say it, it won't show up in the transcript. It's the question you should always ask before hanging up.
- Trusting the summary without reading. The automatic summary and tasks save a lot of time, but figures, deadlines and brand names are worth verifying in the text.
With these rules, the brief stops being a conversation everyone remembers their own way and becomes the document that protects the project, the agency and the client alike.
FAQ
Can I record a brief with a client?
With their permission, yes. Let them know at the start and explain that it's so you can send an accurate summary. If they'd rather you didn't, take notes and record a voice note with what you remember as soon as the meeting ends.
What's the difference between transcribing the brief and the kickoff?
The brief defines what's going to be done and happens before the proposal; the kickoff starts the project once it's approved and sets deadlines and owners. It's worth transcribing both, but the brief is the one that prevents the most rework.
Does the AI separate the requests from the rest of the conversation?
Yes. Besides the full text you get a summary by topic and a list of tasks and key points. It works best if, when closing the meeting, you run through deliverables, deadlines and what's out of scope out loud.
Does it work for the WhatsApp voice notes the client sends?
Yes. Just export the audio from your phone and upload it like any other file. Those voice notes often contain part of the brief and are worth filing alongside the meeting transcript.
What should I send the client after the brief?
A one-page scope document: objective, numbered deliverables, requirements, what's out of scope, what you need from the client and open questions. Ask for a written OK and keep the transcript as backup.