Write a project brief that prevents rework

‘We need a brochure’ identifies a format, not a project. A writer still needs to know who will read it, what the reader should understand and why a brochure is the right place for that information. Starting with production details alone often pushes these decisions into the first round of revisions.

Describe the situation behind the request

Explain what prompted the work. Perhaps a service has changed, customers repeatedly ask the same question or a sales conversation needs supporting material. State the problem without assuming the proposed format is the only solution. A shorter page or clearer email may sometimes address it more directly.

Name the reader and the decision the material supports. ‘Raise awareness’ is difficult to use while writing. ‘Help a facilities manager compare the maintenance options before requesting a quote’ gives the draft a more specific job. It also suggests what information the reader needs and which detail may be premature.

Define the output and its limits

Specify the required deliverables, approximate scope and where they will appear. Distinguish a draft from a designed file, a short summary from a full report and a rewrite from proofreading. Ambiguity about the type of work can create more rework than an unclear stylistic preference.

List the facts that must be included and where they can be verified. Mark missing information openly. If pricing is not confirmed, the brief should say so rather than quietly supplying an estimate as final copy. Give the writer access to relevant source material, not an undifferentiated folder containing years of superseded documents.

Explain how the work will be judged

Agree what a successful draft must accomplish. A hypothetical service leaflet might need to distinguish two packages, explain the booking process and avoid implying that emergency support is included. These criteria are more useful during review than a request to make the copy feel more premium.

Identify reviewers and their areas of responsibility. The technical reviewer checks accuracy; the brand reviewer checks consistency; one person resolves the final decision. Include dates that allow for the actual review process. A deadline for publication is not the same as a deadline for the first draft.

Before work begins, ask the writer to summarise the assignment back in a few sentences. Differences between that summary and the intended brief reveal misunderstandings while they are still inexpensive to resolve. Keep the agreed version accessible and note material changes to it. A brief cannot eliminate every revision, but it can stop the project from repeatedly rediscovering its own purpose.