Client brief: questions, a template and a post-call example
The client explained in detail what he needed. It remains to turn the conversation into a document on which to discuss the work, timing and source materials.
Each line of the brief has statusSo the wishes do not turn into the promises of the performer
Short response
A brief for the client is a short description of the task and baseline conditions: why you need work, for whom, what should turn out, what are the limitations and who accepts the result. You can fill it together on the call. After the conversation, collect the answers in one document, mark the gaps and send the client for verification. Below are questions, template and example for a small project.
Contents
What should the brief clarify
“We need a modern website,” “want more sales,” “do as a competitor” – good starts to the conversation, but weak initial data for work. Of these, it is unclear who will come to the site, what action he needs to do and what the customer considers the result ready.
The brief helps to clarify these things to a detailed assessment. He doesn't have to be a long questionnaire. If the client is easier to explain the task by voice, conduct an interview and fill out the document yourself. This method of joint filling describes and WEEEK Brief Management.
Share three documents for your intended purpose. The brief collects introductory. The technical task describes in detail what and how it should work. Letter after meeting fixes the nearest agreements and actions. They may refer to each other, but they are not required to repeat the entire text.
What questions to ask the client
Start with the situation and then move on to the requirements. So it is less likely to get a list of functions for which no one remembers the original task.
| What to ask | Working question | If the answer is too general |
|---|---|---|
| Reason for the project | What is happening now and why did you decide to change it now? | Ask to understand one recent case. |
| Result | What should a person do after the completion of the project? | “More convenient” replace with a specific action. |
| Audience | Who will use the result and in what situation? | Select the main scenario if the answer is “all.” |
| Borders | What is necessarily included in the first stage, and what can be postponed? | Ask, without which the launch loses its meaning. |
| The source | What texts, files, accesses and data are ready? | Check the owner and the date of receipt of each. |
| Restrictions | Is there a fixed date, budget range and mandatory rules? | Find out what can be changed if there is a lack of resources. |
| Reception | Who checks the work and on what grounds does the result take? | Ask for an example of an acceptable outcome. |
Do not ask questions that do not change anything in your work. For the cover of the podcast and for the system of harmonization of applications, a different set of introductory is necessary. The general part helps to start a conversation; subject matters are added to a specific project.
Brief Template for Copying
Copy the block to the document. Replace the fields in square brackets with answers. At each controversial requirement, leave the status so that the client can check it.
Project: [name].
Date and version: [date, number].
On the part of the client agrees: [name / role].
1. The original situation
[What's happening now. Example of a problem.]
2. Purpose and Primary User
[For whom we do. What task he should solve.]
3. The result of the first stage
[Specific composition of the result and mandatory scenarios.]
4. Beyond the boundaries of the stage
[What was discussed but not yet included.]
5. Initial materials
[Material — who provides — term — readiness status.]
6. Restrictions
[Date, budget range, formats, technical and brand requirements.]
7. Checking the result
[Who checks — what we demonstrate — how to record the remarks.]
8. Open questions
[Question — who answers — when you need a response — what affects.]
Confirmation:
[What paragraphs have confirmed, by whom and when. Reference to the current discussion.]
Do not hide important restrictions in the Comments field. If the start depends on the catalog of goods, the period of receipt of the catalog should be visible next to the corresponding stage.
Example of a filled brief after a conversation
An educational example: a fictional workshop orders a page for corporate orders. This is not a real case of Transkribator.
The situation. Applications come to the messenger. The manager each time specifies the circulation, date and method of application of the logo.
The goal. To help the representative of the company send the initial data for calculation by one address.
The first stage is confirmed. One page with product examples, process description and request form. In the form: product type, quantity, desired date and contact for response.
Not included, confirmed. Online payment, personal account and automatic price calculation.
Materials. Photos and list of products are provided by the client. The date of transfer has not yet been confirmed.
Limitation. The client wants to show the page at the exhibition on November 20. The possibility of starting by this date is evaluated after receiving materials and agreeing on the volume.
The reception. The client manager sends a test request from the phone and computer. Checks that the application contains completed fields. The texts are agreed by the head of the workshop.
Open question. Can I attach the logo to the application? In the conversation, the function was proposed, but no decision was taken. It is necessary to clarify the permissible formats and storage of files.
There is no promise to “increase sales by 30%.” The document describes the result that can be verified. If the project has a business indicator, fix it separately together with the method of measurement and the factors that the performer influences.
How to collect a brief from a convocation record
- Get the text of the conversation. For the working brief, not all words are important, but the full formulation of requirements and conditions.
- Mark up the answers by section. Goals - to goals, wishes to the interface - to the requirements, the timing of the transfer of sources - to materials.
- Check the numerical data. Relisten to deadlines, quantities, units of measurement, and mention of budget.
- Find the conditions. “We will be able on Friday if we get the texts on Tuesday” cannot be reduced to Friday’s promise.
- Separate your offer from the client’s response. The phrase of the performer “can be added filter” does not mean that the filter is needed and included in the price.
- Gather the missing answers. Send a short list of questions that affect volume or evaluation.
In the inner draft, you can keep the timecodes near complex requirements. In the client version they get only if they help to check the meaning. Sending the customer the entire transcript instead of a brief is usually inconvenient: he will have to do your editorial work again.
Example of conversion. “Well, so that it was beautiful and the applications went” → “We need to clarify: who leaves the application, what data transmits and what path it now prevents him.” The general phrase becomes a question, not a made-up requirement.
How to agree and not lose the current version
Name the document clearly: “Breed – corporate orders – version 1”. In the message, ask to check specific sections: the composition of the first stage, sources and open questions. Indicate what answer is needed to continue the evaluation.
If the client changes the requirement, update the document and briefly list the changes. Do not store three files with the same name “Final” next to you. One current version and the history of important decisions should be available to the responsible for the work.
If you contradict, do not choose a convenient formulation yourself. For example, at the beginning of the meeting, the client excluded payment on the site, and at the end mentioned it as desirable. Write down the question: “Confirm whether online payment is included in the first stage or remains in the plans.” Before the answer, do not consider the amount to be agreed.
- The goal is described through the human task.
- The mandatory requirements are separate from wishes.
- There is a list of what is not included in the stage.
- It is known who provides the materials and will agree on the result.
- Unconfirmed terms and conditions are clearly marked.
- The client received a clear request to check the brief.
Frequently asked questions
What if the client does not want to fill out the questionnaire?
Offer a short conversation and fill the brief on his answers. Then send the document for verification. You don’t have to get a client to re-write everything he’s already explained in voice.
How many questions should be in the brief?
As long as it takes to understand the problem and the next solution. Remove questions “just in case” and add substantive refinements for your service.
Is it possible to evaluate the project on the brief?
On full introductory it is possible to discuss preliminary assessment. If the price or term depends on the unknown requirements, list them and indicate that the estimate will be specified after the answers.
Transkribator itself will agree a brief with the client?
No. transcription helps to restore what is said. The structure of the document, verification of requirements and coordination with the client are performed by you.
Additional material: WEEEK – drafting and aligning the brief. The template and the completed example in this article are editorial.
Keep the introductory from the conversation
Transkribator translates the recording of the call into the text with timecodes. Use transcription to gather requirements, find conditions, and prepare a brief that the customer will be able to check.
Transcribing the conversationCheck the important wording and timecodes for the original record before using the text.