Turn a Creative Brief into a Clear Project Scope

Count the outputs and their variants

Write three finished vertical videos, each approximately thirty to forty-five seconds, from client-supplied footage, rather than three social videos. Then name the export format, caption arrangement and delivery location. If the client also wants square versions, clean versions without captions and separate cover images, those are additional variants to count. Small changes across several files create real work. List them before editing so the client can choose which versions they actually need instead of finding the omission at the final export.

Set an input boundary

Describe the accepted source material: for example, up to twenty labelled clips, approved talking points and a folder of permitted brand assets. Explain that the planned schedule begins after these arrive in usable form. A scope based on twenty clips is different from reviewing five hours of unlabelled footage. Ask the client to confirm who supplied the material and whether there are restrictions on its use. Do not accept an unfamiliar shared-folder download or executable just because a message describes it as project footage.

Define completion through observable checks

Useful acceptance checks describe things both people can inspect: the approved headline appears, dialogue is intelligible, the correct logo version is used, captions have been reviewed and exports open. Avoid acceptance wording based entirely on making it viral or exceeding last month's views. Those outcomes depend on factors beyond an editor's deliverables. For an accessible handoff, include the agreed caption and transcript files as actual outputs. W3C encourages planning accessibility early; the scope is a sensible place to assign that work.

Describe exclusions without sounding defensive

Exclusions help a buyer understand adjacent work. Write filming, new voice-over recording, translations and paid media placement are outside this package. Explain how to discuss an addition, rather than listing a wall of prohibitions. Where the boundary is easy to misunderstand, give an example: replacing a supplied sentence is an edit; rebuilding the video around a different offer is a new direction. Keep the explanation close to the included work so it reads as a clear menu of decisions.

Create a small change-request path

Use a short change note containing the request, reason, affected files, extra inputs and effect on timing and cost. For example, adding a second presenter may require a new assembly, captions and another approval. Pause the affected work until the client agrees the revised plan. Never assume a casual message approves an unspecified extra fee. Keep changes visible in a log, including requests you decide to include without charge, so the latest scope remains a reliable picture of what will be delivered.

Make the boundary easy to revisit

Store the scope alongside the brief under a version number and date. At kickoff, ask the client to describe what they expect at handoff; the answer often exposes a missing source file or platform version. At the first draft, reference the agreed objectives and invite a consolidated response. If the project changes substantially, update the scope rather than accumulating exceptions in chat. Good boundaries support collaboration because people can make a deliberate trade-off between an extra idea, a smaller package and a later delivery date.

Your working checklist

Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.

• Confirmed brief
• Deliverables and variants list
• Input inventory
• A simple change-request note

Put it into practice

1. Convert the brief into a countable list of deliverables, variants and file types. Identify any output that is currently implied rather than explicitly named.
2. State the source-material limit and observable completion checks. Ask the client to confirm that these describe a useful finished project before production starts.
3. Write the excluded adjacent tasks and the process for requesting additions. Keep the wording neutral and show one example of an ordinary edit versus a new direction.
4. Maintain a dated scope and change log through delivery. When new work is agreed, update quantities and timing together so the project has one current baseline.

Common questions