Start with the result, not a list of activities
A weak brief begins with scattered tasks: research this, redesign that, add several pages and make everything professional. A useful brief begins with the result that must exist when the project is complete.
Describe who will use the final output, what decision or action it should support and which file formats are required. This gives the freelancer a stable direction when individual tasks change.
- Name the final output and its intended user.
- Explain what success looks like in observable terms.
- Separate essential requirements from optional improvements.
Share the source material and its status
Freelancers lose time when they discover late that a logo is outdated, a dataset is incomplete or a document is only an early draft. List the files you have and state whether each is approved, provisional or only a reference.
If something is missing, say so. A clear gap is easier to plan around than an assumption that becomes a surprise.
Define constraints before the deadline
Brand rules, university requirements, software versions, hosting access, word limits and review stages can all change the correct delivery method. Include the real deadline and any earlier review date.
- Required template, platform or software
- Word, page, slide or feature limits
- Reviewers and approval stages
- Confidentiality or access restrictions
Make quality expectations testable
Words such as modern and professional mean different things to different people. Replace them with checks: all links must work, calculations must be traceable, slides must follow the supplied template, or the website must work on mobile and desktop.
A good freelancer should still ask questions. The brief makes that discussion focused and productive.