Scope creep starts with a vague brief
How a well-defined brief protects both sides of a support engagement — and a practical checklist to help you write one.
Start with the outcome
Before handing over a task, describe what you need at the end. "An indexed PDF bundle ready for review" gives more direction than "please organise these documents". Include the preferred format and any house-style requirements.
Set out the scope
Identify the material to be included, the work already completed and anything that falls outside the task. A short written brief can prevent assumptions and make it easier to identify questions early.
Make the timing clear
Distinguish a preferred delivery date from a fixed deadline. Allow time for review, corrections and any further instructions. Confirm who should be contacted if a question affects progress.
Agree how information will be shared
Use the document-sharing method agreed for the engagement. Keep versions clearly labelled and identify the source documents. For law-firm work, nominate the practitioner who will direct and review the task.
A useful starting checklist
- The outcome and file format you need.
- The documents and instructions to use.
- The scope, priorities and delivery date.
- The person responsible for questions and review.
- The agreed method for sharing files.
A clear brief does not need to be long. It needs to make the next step understandable.
General information about administrative workflows. This article is not legal advice.