PRACTICAL GUIDES FOR WORK, STUDY & EVERYDAY LIFE

About   /   Contact

Home  /  Guides

How to Write a Freelance Project Brief That Prevents Scope Creep

A freelance project can start with one small request and become a very different job by the end of the week. The client asks for an extra page, a second design option or another round of changes. You want to be helpful, so you say yes. Eventually the deadline slips, the agreed fee no longer reflects the work and neither side is sure what was included.

A short written project brief can prevent much of this confusion. It sets out the result the client wants, what you will deliver, what they need to supply and how changes will be handled. This guide is for beginners working on writing, design, websites and similar projects. It is practical project-management advice, not a substitute for a contract or legal advice.

What a project brief is — and what it is not

A project brief explains the work in ordinary language. It connects the client’s problem to a particular deliverable and gives both sides the same reference point. Think of it as a shared map: what you are making, who it is for, how you will know it is finished and what happens if the route changes. A good brief may be a page long for a simple task or several pages for a complicated project.

It is not automatically a complete legal contract. Depending on the work, you may also need formal terms covering payment, ownership, confidentiality, cancellation, liability and other matters. The UK’s Small Business Commissioner contract guide recommends writing down what has been agreed clearly, especially to avoid payment disputes.

Start with the client’s actual problem

Before quoting for a deliverable, ask what the client hopes will improve. “I need a website” does not explain whether they want more enquiries, clearer information for existing customers or a way to book appointments. The answer changes the content and level of work involved. Ask who will use the final result, what already exists and what is causing difficulty now.

Record the client’s answer without turning it into a grand marketing promise. A designer cannot promise a particular increase in sales simply by making a new brochure. A more useful objective is “produce a readable, on-brand two-page brochure for the autumn event”. It is observable, modest and within the project’s influence.

Write a specific deliverables list

A deliverable is something the client can receive, review or use. Instead of “website improvements”, write “rewrite copy for the home, about and contact pages, supplied in an editable document”. Instead of “social media help”, write “four square graphics and four caption drafts”. Include file formats, languages and platform requirements when those details affect the work.

List every agreed item as a separate line. Where useful, state quantities: three pages, one illustration, two review rounds. Avoid vague phrases such as “anything needed” or “all revisions” unless you truly intend to include unlimited work. This level of detail makes it easier to provide a fair quote; our freelance pricing guide covers the wider pricing decision.

Say what is out of scope

The easiest way to create confusion is to describe what is included but leave every nearby task open to interpretation. A website copy project might exclude photography, translation, page building and search engine optimisation. A logo project might exclude packaging design and trademark checks. Mention the exclusions most likely to be assumed by the client, not every imaginable service.

Keep the wording calm: “This quote covers the written page copy; publishing it in WordPress is not included.” You are not trying to catch anybody out. You are giving the client a chance to add important work before the quote is accepted. If they need the excluded item, discuss an adjusted brief and fee.

Define what the client must provide

Freelancers often underestimate how much a project depends on receiving material from the client. A writer may need product information, house style and access to a knowledgeable contact. A web designer may need images, brand colours, logins or legal wording that the client has already approved. Put those dependencies in the brief alongside an expected date.

Be precise about responsibility. For example: “Client will provide the current logo files and approved product descriptions by Tuesday.” If the client misses that date, explain how you will agree a revised schedule rather than silently absorbing the delay. Never ask for passwords through an insecure channel; agree an appropriate access method.

Make the schedule realistic, with review points

Split the work into stages you can explain: discovery, first draft, client review, revisions and final handover. Give a target date for each stage and identify which dates depend on feedback or resources. Include a little room for ordinary delays. A seven-day job with no allowance for replies may become impossible if the client goes away for a weekend.

A milestone should have a purpose beyond making the brief look professional. “First draft delivered” tells both sides what they can expect to see. “Client supplies consolidated feedback” tells the client what happens next. If your work changes after feedback, ensure the revised delivery date is written down where everyone can find it.

Agree how feedback and revisions will work

A revision round is easier to manage when everyone knows what it means. One practical definition is a single consolidated list of comments on one delivered version. The client may want small adjustments to wording, spacing or colour. These are different from asking for a new concept or an additional piece of work. Explain the distinction in the brief.

For example: “The fee includes two rounds of corrections to the agreed brochure layout. A new format or additional pages will be quoted separately.” Invite the client to nominate one person who gathers comments when several stakeholders are involved. Clear communication matters as much as the document itself; see our guide to professional client communication.

Include a workable change-request process

Scope creep is not always unreasonable. Projects develop, and a new request may genuinely improve the outcome. The difficulty comes when extra tasks slip into the original fee and timetable without a discussion. Agree a simple rule: when the client wants something beyond the brief, describe the request, estimate the extra work, revise the cost and dates if necessary, and get written agreement before starting.

A friendly message is enough for a small change: “Happy to add a second version. That was outside our agreed two-page brief. It would be an additional £X and take Y working days. Shall I update the project outline?” These amounts are examples to be negotiated, not standard industry rates. The aim is transparency, not confrontation.

Write a clear fee and payment section

State the agreed price, currency and whether the quoted amount includes applicable taxes and expenses. Identify the payment schedule, how invoices are issued and what counts as a completed milestone. If you ask for a deposit, say how it will be treated and what the client receives before the balance is due. Keep the brief and actual contract consistent.

The Small Business Commissioner highlights written payment terms as an important protection for businesses. The rules for late business-to-business payments can depend on the parties and the agreement; see GOV.UK’s explanation of when commercial payments become late if it applies. Do not copy legal wording you do not understand.

Clarify sign-off and what ‘finished’ means

A project can feel finished to the freelancer and unfinished to the client. Define an acceptance point: perhaps the approved copy has been delivered in the agreed file format, all in-scope revision comments have been addressed and the client has received the promised source files. State how the client will confirm acceptance and whom they should contact if something is missing.

Avoid treating silence as approval unless your agreed terms clearly and fairly say how that works. You may choose to send a final handover note listing files, outstanding items and practical next steps. A clear finish protects the relationship and gives you a better basis for requesting a testimonial or adding a permitted example to your freelance portfolio.

Keep project communication in one reliable place

Important decisions can disappear across messaging apps, meeting notes and email threads. Choose one primary place for the latest brief and approved changes. For a very small project, this might be a shared document and a short confirmation email. Larger jobs may need a task board. The system matters less than knowing which version is current.

After a meeting, send a short recap containing decisions, who is responsible and the next deadline. If the client replies with a correction, update the shared brief. A record need not be formal or unfriendly; it prevents two people acting on different memories of the same conversation.

A worked example: a small business brochure

Imagine a café asks a new freelancer for a promotional leaflet. A vague brief says: “Make a lovely flyer for our menu.” A stronger version says: “Create one A5 double-sided print-ready leaflet featuring six menu items, the opening hours supplied by the client, and one approved promotional message. Supply a PDF for printing and an editable design source file.”

Add the practical boundaries: the café supplies copy, prices and approved images by a certain date; the freelancer supplies the first design by the next milestone; two consolidated revision rounds are included; extra sizes or photography require a separate quote. You can now see what the client receives and what either person must do next. This is a fictional teaching example, not a standard contract template.

How to respond when an extra request arrives

Read the new request carefully before saying yes or no. Does it clarify an existing deliverable, fix your own error or genuinely add new work? Correcting a mistake you made against the agreed brief should not automatically be treated as an extra. A completely new page or audience may be different. Ask a neutral question if the boundary is uncertain.

Where it is a change, show options rather than presenting an ultimatum: complete it for an additional fee, replace a lower-priority item, or defer it to a second phase. Record the chosen option, the effect on timing and any revised acceptance criteria. Your client may welcome the clarity because they also need to manage a budget.

Common briefing mistakes worth avoiding

Do not begin from a proposal that promises a result you cannot control. Do not rely on a list of tasks without a definition of completion. Avoid vague revision policies, missing client responsibilities and unrealistic deadlines. Do not hide important restrictions in a separate document the client has not seen. If you change the scope, make sure the written record changes too.

If you work through a freelance platform, check its current terms and dispute process before agreeing to off-platform arrangements. If a project involves sensitive data, intellectual property or regulated work, take specialist advice where appropriate. Acas notes that describing a person as a contractor or freelancer does not by itself settle their actual employment status; see its guidance on self-employment and contracts for services.

A brief template you can adapt

Write the following as short sections in a document: Project name and contacts; problem to solve; target audience; deliverables and file formats; excluded work; client-supplied materials; stages and deadlines; review and revision allowance; change requests; fee and payment schedule; final handover and acceptance. Include the agreed date and a clear version label.

You do not need complicated software to use this structure. Ask the client to read it in full and respond with any missing assumptions. Once it matches the agreement, keep it somewhere both of you can access. Updating one concise brief is usually better than sending lengthy messages about what was supposedly agreed last Tuesday.

Frequently asked questions

Is a freelance project brief legally binding?

A brief may form part of the agreement, but its legal effect depends on the facts and terms. Use an appropriate written contract for obligations that need formal protection and seek qualified advice for significant work.

How many revisions should a beginner include?

There is no universal number. Choose a limited, clearly defined allowance that reflects the type of job and the fee. Explain how feedback should be collected and how additional revisions are priced.

What if the client refuses to sign a brief?

Explain that a written scope protects both sides by reducing confusion. Offer a simpler one-page version if the current document feels heavy. Consider whether proceeding without clear agreement is an acceptable business risk.

Should I charge for every small change?

Not necessarily. Clarifications and corrections to your own in-scope mistakes are different from fresh work. Set expectations fairly and use judgement rather than arguing over every minor request.

Can I use the same brief for every client?

Reuse the headings, not the assumptions. Each project needs its own deliverables, responsibilities, timings and fee. A generic template becomes useful only after you adapt it to the real discussion.

A better start to your next project

A useful brief should make the first client conversation easier, not more bureaucratic. Clarify the result, define the deliverables, make room for feedback and agree what happens when requirements change. The moment you can point to a shared written version, you have a calmer way to discuss price, deadlines and expectations.

Sources and further reading

UK Small Business Commissioner: contract guide; GOV.UK: late commercial payments; Acas: self-employment and contracts for services; Competition and Markets Authority: fair consumer contract terms (relevant where the client is a consumer).

Keep learning

One useful skill leads to another. Choose your next guide from the collection.

Browse all practical guides →