From client chat to clear brief

Who is this guide for?

This guide is for account managers, freelancers, and service providers who receive unstructured briefs, loose chat logs, or raw audio transcriptions from clients and want to convert them into a structured brief draft.

What this guide helps with

The workflow extracts project objectives, deliverables, constraints, and deadlines from unstructured text. Crucially, it highlights omissions and ambiguities that you need to resolve with the client.

How to use this guide

1. Collect the relevant messages and remove personal, confidential and access information.
2. Read the safe-use rules, copy the full prompt and replace the input placeholder with the anonymized conversation.
3. Compare the draft with the original messages. Keep uncertain dates, scope and prices marked for verification.
4. Ask the client the missing questions. Approve the brief and reply yourself before using or sending them.

Example input

Here is an example of an informal client request that you can use as input:

Client: Hey, we need a simple contact page on our site. Needs a map and a form.
Consultant: Sure. Do you want it to save submissions somewhere?
Client: Just email them to us. Need it by next Friday if possible. Oh and we need custom styling, no standard templates.

Short example output

This shortened model output follows all seven sections of the prompt. A requested date remains tentative until confirmed:

1. BRIEF SUMMARY
- Client wants a custom contact page with a map and a form, preferably by next Friday if possible. The delivery date is unconfirmed.

2. CONFIRMED FACTS
- Form submissions sent via email.
- Custom styling required (no standard templates).

3. TO VERIFY
- Which email address should receive submissions?
- What map service is preferred?
- Which calendar date does "next Friday" mean, and is delivery feasible after reviewing the scope and materials?

4. WORKING BRIEF
- Objective: Add a contact page.
- Requested scope: Map, email form submissions and custom styling.
- Deliverables and technical approach: To verify against the existing site.
- Preferences: No standard templates.
- Available materials: Request text only.
- Missing materials: Site details, content, design references and recipient address.

5. PRIORITY QUESTIONS FOR CLIENT
- What email address should receive submissions?
- Do you have a preferred map provider (e.g. Google Maps)?

6. RECOMMENDED NEXT STEP
- Clarify the requested date, site setup and available content before assessing scope or timing.

7. DRAFT REPLY FOR REVIEW
"Hi, thank you for reaching out. I understand you would like a custom contact page with a map and an email form, preferably by next Friday. Before we assess the scope and timing, could you share the site setup, preferred map provider and the exact date you have in mind?"

Before sending, check the facts, tone, scope and all commitments to the client.

What to check in the output

Before sending or utilizing the output from the AI assistant, verify the following:

• Accuracy of facts: Check that the AI correctly captured the client's request details without inventing new features.
• Tone: Ensure the drafted response aligns with your brand voice and sounds natural.
• Scope: Confirm that the working brief only lists requested features.
• Promises and commitments: Ensure that no pricing, strict deadlines, or final delivery commitments are accidentally made or implied.

Related guides

• JMHZ and Czech payroll reporting — AI as a control assistant – How to use AI as a preparation and control assistant for payroll processes.
• From inquiry to next step – Evaluate incoming sales inquiries, assess project fit, and outline response scopes.