Copywriting Brief Questions for Clearer First Drafts
A copywriting brief should explain what the reader needs to understand and do. It also needs the facts the writer can use, the claims someone must verify, and the constraints of the actual placement. ‘Make it punchier’ is feedback; it is not a substitute for those inputs.
Questions that remove guessing
Scroll sideways to read all three columns.
| Ask | A useful answer includes | Writer's decision |
|---|---|---|
| Where will the copy appear? | Page, email or asset type and relevant format limits. | Structure and depth. |
| Who reads it, and what do they already know? | The reader's situation and familiarity with the offer. | What must be explained first. |
| What should the reader do next? | One primary action and its destination. | The main call to action. |
| What might stop them? | A real uncertainty or objection, with evidence if available. | Which questions the copy should answer. |
| Which facts and examples can support the message? | Approved source links and a factual owner. | What can be stated and what needs checking. |
| What must stay consistent? | Names, terminology, voice examples and non-negotiable wording. | The boundaries for expression. |
| Who reviews the draft? | One consolidator and the people checking facts or specialist issues. | A review route and sequence. |
Keep source material separate from instructions
A folder of old presentations may contain useful facts, but it does not tell the writer which version is current. Link to the approved source and identify the owner of anything uncertain. Mark a result or quotation as unverified until the right person confirms it can be used.
Instructions should explain what the new copy must accomplish. If a client supplies a competitor page, ask which aspect is relevant: structure, depth or the way a question is answered. Do not turn ‘we like this’ into a request to reproduce someone else's wording.
Illustrative message brief: software setup service
Scroll sideways to read all three columns.
| Brief element | Working answer | Review implication |
|---|---|---|
| Reader | An operations manager comparing ways to organize a rollout. | Explain the process without assuming implementation expertise. |
| Action | Request a scoping conversation. | Avoid copy implying an instant fixed-price purchase. |
| Main concern | Unclear responsibilities between the service team and the client. | Show the proposed division of work, subject to scope review. |
| Proof | An approved process description; no verified performance claim yet. | Use the process evidence and leave unsupported results out. |
| Review | Service lead checks accuracy, marketing lead consolidates comments. | Resolve factual corrections before polishing the final wording. |
Use acceptance criteria rather than taste alone
Before drafting, agree what the first version needs to demonstrate. In the illustrative service brief, the reader should understand the next step, the information needed for scoping, and the responsibilities still to be agreed. Those criteria let reviewers explain why a passage is missing or misleading.
Keep preference comments, factual corrections and scope changes separate during review. ‘Use our current service name’ is a correction. ‘Add a new industry page’ changes the deliverable. When feedback changes the audience or offer, update the brief before treating the revision as a small wording adjustment.
A practical review sequence
Check the message
Confirm the audience, primary action and overall argument before line-editing every sentence.
Check the evidence
Have source owners review names, descriptions, claims and examples. Record unresolved facts visibly.
Check the final placement
Review the copy in its intended context, including headings, link text and any length limits. Confirm which version is approved.
Before sending the brief
- The main action has a real destination.
- Source links identify current versions.
- Unsupported claims are marked for review.
- Format and delivery constraints are specific.
- One person will consolidate feedback against the agreed purpose.
Put the guide into practice
Brief a writer on the reader, desired action, voice, evidence and review process for a specific deliverable.
Collect one page's copy, image links, approval state and content owner for a website build.
Anchor design feedback to a version, explain the requested change and identify the next reviewer.
Questions people ask
Should I include a word count?
Include a real placement limit when one exists. Otherwise explain the reader's task and required information rather than imposing a length without a reason.
Does a tone-of-voice document replace the brief?
No. It explains how the organization speaks; the project brief still needs the audience, offer, action and source material for this particular piece.
What if the client has no research?
Record what is known and what is assumed. The writer can identify questions to investigate, but should not present invented customer findings as evidence.
Keep reading
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.