How to Turn a Vague Client Email Into a Clear Brief in 6 Steps

To turn a client email into a brief, pin down the ask, list what's missing, send one round of questions, collect files and a real deadline, write the brief in a fixed template, and get the client to confirm it. It takes about 20 minutes of your time plus the client's reply.

This guide is for agencies, studios, consultants and freelancers who get fuzzy emails from clients and want to start work with confidence. It's beginner level, and you'll finish with a reusable brief template and a copy-paste follow-up message.

Before you start

Before you start, gather five things: the original email, one place to store the brief, the approver's name, the client's files, and your usual turnaround time. None of it takes long, and each piece saves you a scramble later.

• The original client email, saved as-is. You'll want to quote it later, especially if the scope drifts.
• One place to store the finished brief. Stripo advises formalizing a brief into one document instead of leaving details scattered across chats and client emails. Pick the spot now.
• The name of the client's approver. If you don't know who says yes, you can't get a yes.
• Logo, brand and file links, or where to find them. If the client keeps assets in a shared drive, note the link.
• Your usual turnaround time. You'll need it to offer a realistic date instead of a guess.

The point of the routine: a brief isn't a document you write at the start. It's what's left after you've gathered the missing pieces.

Step 1: Read the email for the ask

Start by writing down what the client is actually asking for, in one sentence, before you try to solve anything. Vague emails tend to ask for a quick update, a more modern website or a simple campaign, with too little context to scope or price the work, as VocalJet's guide to vague client emails points out.

This is the first move in good client request management: know the ask before you do anything else.

Here's how to do it:

1. Read the email twice. The first pass is for the feel, the second is for details.
2. Underline the verb and the thing. "Freshen up" is the verb. "Homepage" is the thing.
3. Split what they say from the goal behind it. "We need a new landing page" is a stated want. "We need more webinar sign-ups" is the goal. Note both, even if the goal is only a guess for now.
4. Write the ask in one sentence, and mark anything you're guessing with a question mark.

Example. A client writes: "Can you freshen up the homepage before the launch?"

Your one-sentence ask becomes: "Refresh homepage hero and top sections ahead of a launch (date unknown)."

That sentence already shows you what you don't know: which launch, when, and what "freshen up" means.

The usual mistake: starting to solve it, or replying with a quote, before the ask is pinned down. A quote built on a fuzzy ask is a quote built on assumptions. Park the price until the brief exists.

Step 2: List what's missing

Check the email against a short list of what every brief needs, and mark only the gaps that block the work. Gaps you find now are cheap. Gaps you find mid-project are rework.

Use this as your base. The first five are the focused questions VocalJet recommends asking, and the rest cover the practical details that stall a job:

1. Outcome: what should this create?
2. Why now: why does it matter at this moment?
3. Audience: who is the primary audience?
4. Deliverables: what exactly do they expect to receive?
5. Examples and references: anything they like, or want to avoid?
6. Deadline: a real date, not a mood.
7. Approver: who signs off?
8. Files: logos, copy, links, access.

Brief-writing advice, such as Indeed's how-to, starts with goals and motivations, including background. That's why outcome and why-now come first on the list.

Example. Check the homepage email against the list. There's no goal, no date, no approver and no files. The deliverable is only half there, since "freshen up" could mean new photos or a full redesign.

The usual mistake: listing everything a perfect brief could hold, instead of only what blocks the work. If you can start without it, leave it off the list. For a deeper look at what clients will actually fill in, see our guide to a creative brief clients will fill in.

Step 3: Send one question round

One written round of questions beats repeated calls and half-answers. VocalJet notes that answering too quickly risks building a proposal around assumptions, while scheduling another call every time makes intake slow and expensive. A single written round is quicker for both sides, and it leaves a record you can point back to.

So don't hop on a call, and don't fire questions one a day. Send one tight message.

How to build it:

1. Pick the 3 to 5 gaps that block the work most. Usually that's outcome, deadline, approver and files.
2. Put the answer you can already give first, such as "Happy to help with the refresh."
3. Use short paragraphs and bullets. LinkedIn's tips on clear client emails say to keep it short, make the point in the first few lines, and use short paragraphs or bullet points.
4. Make replies easy: yes/no, multiple choice, or "reply with a date."
5. Say what happens next: "Once I have these, I'll send a one-page brief to confirm."

Here's a copy-paste follow-up message. Swap the bracketed bits:

Subject: Quick questions on the [homepage refresh]

Hi [Name],

Happy to help with the [homepage refresh]. Four quick questions
so I can write it up properly:

1. What should the new homepage do? (e.g. more demo requests,
   a cleaner look for the launch, something else)
2. When is the launch, and when would you like to see a first draft?
3. Who on your side signs off on the final version?
4. Can you send the logo, any new photos or copy, and a link to
   one or two sites you like?

Reply right under each question, short answers are perfect.
Once I have them, I'll send a one-page brief for you to confirm
before we start.

Thanks,
[Your name]

The usual mistake: ten questions, or one question every day. Ten questions feel like homework and get ignored. Daily drips make the client feel interrogated. Stay with your top few.

If you're doing this by hand, it's a chore worth automating. An AI account manager like Dora's asks for what's missing for you, and with Dora you can turn client emails into requests so clients keep writing the way they already do.

Step 4: Fill in files and the deadline

Files and dates are what most often stall a job, so close them out as soon as answers come in. If the client sent replies but left gaps, chase just those two things.

Here's the routine:

1. Collect logos, copy, links and examples into the folder or request where the brief will live. If any came as email attachments, move them out of the thread.
2. Check for brand guidelines, or at least fonts and colors. If the client has them, link them. If they don't, say so in the brief.
3. Put the real date near the top. Email on Acid advises placing the deadline near the top of a brief and making it reflect the actual date.
4. Note budget and timeline fields. A demo tutorial that turns an email into a structured brief includes sections for the ask, budget, deliverables and timeline, so it's worth leaving room for each, even if budget is just "fixed by quote."

Dora keeps client files together in a brand library, so logos and guidelines stop living in old threads.

Example. The client replies: launch is 14 March. That's the launch date, not your delivery date. State both: "Launch: 14 March. First draft due: 3 March. Feedback due: 7 March." Working back from the launch gives the client time to react.

The usual mistake: writing "ASAP" or "soon" as the deadline. Those words mean something different to every person who reads them. If the client says ASAP, reply with a date you can meet and ask them to confirm it.

Step 5: Write the brief

Write the brief by copying the client's answers into a fixed nine-section template. A brief is the shared source of truth for goals, deliverables, constraints, risks and next steps, as VocalJet frames it. Teamwork calls a client brief a foundational guide for the entire project.

Start with goals and background, then fill the rest. Rock's client brief template describes nine sections and where each piece of information comes from, such as a questionnaire or sales notes. Here's a reusable template built the same way, with nine sections:

BRIEF: [Project name]
Client: [Name]   Prepared: [Date]

1. SUMMARY
[One sentence: what we're making and why.]

2. BACKGROUND
[Two or three sentences on the client and what led to this.]

3. GOAL
[The one outcome that tells us this worked.]

4. AUDIENCE
[Who the work speaks to.]

5. DELIVERABLES
- [Item 1]
- [Item 2]
- Out of scope: [what's not included]

6. DEADLINE AND MILESTONES
Final due: [Date]
First draft: [Date]
Feedback due: [Date]

7. FILES AND REFERENCES
- [Logo / brand guide link]
- [Copy / photos link]
- [Examples they like]

8. CONSTRAINTS AND BUDGET
[Technical limits, brand rules, budget or quote.]

9. APPROVER AND NEXT STEPS
Approver: [Name]
Next: [What happens after they confirm]

Filled-in example (homepage refresh):

BRIEF: Homepage refresh
Client: Maple & Co   Prepared: 21 February

1. SUMMARY
Refresh the homepage hero and top three sections so the site
looks current for the product launch.

2. BACKGROUND
Maple & Co launches a new product line on 14 March. The current
homepage still shows last year's range.

3. GOAL
More demo requests during launch month.

4. AUDIENCE
Operations managers at mid-sized retailers.

5. DELIVERABLES
- New hero (headline, image, button)
- Updated top three sections
- Out of scope: new pages, blog changes

6. DEADLINE AND MILESTONES
Launch: 14 March
First draft: 3 March
Feedback due: 7 March

7. FILES AND REFERENCES
- Logo and brand guide: shared folder link
- New product photos: shared folder link
- Reference: two sites the client likes

8. CONSTRAINTS AND BUDGET
Keep current navigation. Fixed quote.

9. APPROVER AND NEXT STEPS
Approver: Priya (marketing lead)
Next: client confirms this brief, then design starts.

The usual mistake: copying the client's vague wording into the brief. "Make it pop" is not a deliverable. Translate it into something checkable, like "new hero image and headline." And keep one document: update this one rather than starting a second in a chat thread.

This is also where running clients from your inbox shows its cracks, because the brief ends up buried under the next ten emails. Dora writes the brief from the email for you and keeps it with the request.

Step 6: Get a quick confirm

Send the brief back and ask for a yes. Briefs aim to improve alignment and reduce revisions, as NLC puts it, and a yes before kickoff protects your scope. If the client later says "I meant a full redesign," you have something to point to.

How to do it:

1. Send the brief with a one-line ask: "Does this capture it? Reply 'confirmed' or tell me what to change."
2. Offer a reply-by date, so silence has a clock on it.
3. Make approving one click or one reply. Nobody should have to write a paragraph to say yes.
4. Agree on what happens if they go quiet: a friendly nudge, then an auto-approval window.

Copy-paste confirm message:

Subject: Brief for [homepage refresh]: please confirm

Hi [Name],

Here's the one-page brief for the [homepage refresh]:
[link or pasted brief]

Key points:
- Goal: [more demo requests during launch month]
- First draft: [3 March]. Final: [14 March]
- Approver: [Priya]

If it looks right, just reply "confirmed." If anything's off,
tell me what to change.

Could you reply by [Friday 24 Feb]? That lets us start in time
for your launch.

Thanks,
[Your name]

In Dora, the brief sits on the request where the client can see it, and Dora follows up with clients who leave a question unanswered. When the work itself is ready, one-click approvals handle sign-off, with auto-approval after the days you choose. If you're doing it by hand, our client approval process guide covers how to keep sign-off from stalling.

The usual mistake: treating silence as a yes without saying so. If you plan to proceed after a set number of days, say that in the message: "If I don't hear back by Friday, I'll take that as a go."

Common mistakes

The most common mistakes are answering too fast, asking too many questions, and skipping the confirm. Here's what to watch for:

Requests also arrive in more than one place. If yours come by email, chat and DMs, our answer on clients sending requests in different channels shows how to bring them into one flow before you start Step 1.

How to tell it's working. We don't have a client case to quote, so measure your own. For your next 10 inbound client emails, note how many go through more than one round of questions, and how many get revised after first delivery because of a missed detail. Then run the six steps and the template on the following 10. Compare rounds of questions per request, revisions caused by missing info, and time from email to confirmed brief. Four weeks of normal intake is enough to see a difference.

Checklist

Here are the six steps in short form. Keep this next to your inbox:

1. Read the email for the ask. Underline the verb and the thing, and write the ask in one sentence.
2. List what's missing. Check outcome, why now, audience, deliverables, deadline, approver, references and files, and note only what blocks the work.
3. Send one question round. Ask 3 to 5 short questions in a single message, answer first, bullets after.
4. Fill in files and the deadline. Collect assets, put the real date near the top, and state both launch and draft dates.
5. Write the brief. Fill the template with checkable wording, and keep it as one document in one place.
6. Get a quick confirm. Send it back with a reply-by date, one-reply approval, and a clear note on what silence means.

Or let Dora ask the client for what's missing and write the brief for you: try Dora free, your first client is free, forever.

Frequently asked questions

How do you turn a client email into a brief?

Pin down the ask, list what's missing, send one round of questions, collect files and a real deadline, write the brief in a fixed template, and get the client to confirm it. It takes about 20 minutes of your time plus the client's reply.

What should a client brief include?

A summary, background, goal, audience, deliverables (including what's out of scope), deadline and milestones, files and references, constraints and budget, and the approver with next steps. Start with the goal and background, then fill the rest.

How many questions should I ask about a vague client request?

Three to five, in one written message. Pick the gaps that block the work most, usually outcome, deadline, approver and files. Ten questions feel like homework and get ignored.