To learn how to write a project brief that handles change, start with the agreed plan. A brief is the compact record for one task: the work, who can approve it and how you will check it. The case below is an illustration, not a real client. This is educational planning only, not legal advice.
The same worked example runs through this guide. Mina is the client's founder. Her decisions are due by week 3. Jon leads the supplier's team and estimates the work. A developer checks the technical work but cannot bind either party. The client board decides above Mina's cap. All roles and figures here are made up. They are not recommended limits or a market quote.
How to write a project brief around the real need?
UK public-service design practice says needs should come from evidence about actual users, with the problem distinguished from a proposed solution. (Government Digital Service, 2017) Customer research still does not prove demand or remove bias in whoever gathers it.
In this illustration, a small advisory practice wants qualified enquiries. The visitor's task is deciding whether the service fits them. The current one-page site explains the service poorly. This case has no actual research behind it; the need and the goal are simply stated.
What belongs inside the scope?
Australian official contractor guidance suggests addressing scope, acceptance, payment, disputes and changes, with any variation carrying agreed effects on work, price and time. (business.gov.au, n.d.) That guidance is Australian, so its scope may not match your jurisdiction, and whether a brief forms or varies a contract depends on the circumstances and applicable law. Treat it as a practical record and seek qualified local legal review.
In this invented plan, header version 1.0 means the listed scope is agreed. Pending copy and form details must be settled before the affected work begins. Mina decides them by week 3.
| Baseline element, version 1.0 | Detail |
|---|---|
| Visitor task | Decide whether the advisory service fits their situation |
| Practice goal | Qualified enquiries from referred visitors who currently misunderstand the service |
| In scope, fixed | Five pages: Home, About, Services, Approach, Contact |
| Draft copy pending | Final wording for all five pages. Decision owner: Mina. Deadline: week 3 |
| Form fields pending | Which fields the contact form collects. Decision owner: Mina, on Jon's advice. Deadline: week 3 |
| Out of scope | Booking or scheduling, payment collection, paid media, ongoing content |
| Assumptions | Client supplies source material by the agreed date |
| Baseline budget | AED 12,000. Mina's illustrative total project cap is AED 15,000, not an extra allowance; the client board decides above it |
| Dates, illustrative and relative | Brief approved week 1, copy freeze week 4, build weeks 5 to 8 |
| Acceptance evidence | The five agreed pages load, and the form submits to the agreed address, confirmed in writing against this checklist. A separate proposed purpose check is described below the table |
| Dependencies | Hosting access; a decision on the form tool. These are access and tool checks, not guarantees |
How will you check acceptance?
The functional checks are the five agreed pages loading and the form submitting to the agreed address. The practice also proposes a purpose check for the Services page. A referred visitor reads the page, then explains what help is offered, who it suits and the next step. Mina and Jon would agree the wording, the participants and the acceptance conditions before anyone uses the check. A correct answer is not proof of conversion, and one visitor is not a representative customer study. The parties follow the process they actually agreed; where the agreement requires explicit consent, record it. If the legal effect of silence or a no-objection clause is unclear, get qualified local advice.
Who can approve each decision?
In this example, Jon assesses work and can agree the supplier's scope and dates. Mina can commit up to AED 15,000 for the whole project. The baseline budget is AED 12,000. Her AED 15,000 cap is not an extra allowance. The client board decides above that cap. Suppose a change brings the total to AED 16,000. The board must approve it, and Jon must agree for the supplier. Mina alone cannot commit. This is a worked example, not a quote for the pending booking request.
How should you assess a change request?
Professional project-management guidance describes a proposed baseline change being captured, evaluated and then approved, rejected or deferred, with the consequences assessed before the plan is updated. (Association for Project Management, n.d.) That guidance is organisational practice, not contract law, so an assessment still reflects your actual permissions and obligations.
For the booking request, the practice first needs to know whether the tool can schedule at all, what it costs, and whether either date or price would move. The table is a proposed working aid, not a tested tool.
| Change record | Detail |
|---|---|
| Change ID | CR-001, scheduling only, payment collection explicitly excluded |
| Proposal vs baseline | Baseline version 1.0 is the agreed plan. CR-001 is a separate proposal that is still pending |
| Requested difference | Add an appointment scheduling page to the five agreed pages |
| Cost and date effects | Not yet assumed; no fee or date is fixed until estimates are checked |
| Proposed test, not yet agreed | A booking made in the chosen timezone lands in an agreed slot for the agreed duration, handles an occupied slot as specified, sends the agreed confirmation, and shows what happens after a deliberately failed booking |
| Test owner | Jon carries out and Mina reviews; a developer checks technical work but cannot bind either party |
| Evidence needed | Whether the platform supports scheduling; test-environment access; security and privacy review. These are dependencies, not guarantees |
| Next information needed | Whether the platform supports scheduling; a cost figure for Jon to check |
| Decision owner | Mina decides within her cap; the board decides above it; Jon must agree for the supplier |
| Review date | Relative week 3, before the copy freeze |
| Status | Pending |
What should the revised record contain?
In this example, suggested labels are scope1.0 for the agreed plan and CR-001 proposal-revision2 for the booking request. A new proposal revision can record newly learned facts, while the agreed scope stays scope1.0 until a decision is made. No decision to add the page has been made.
CR-001 leaves the effort, cost and access unknown. Jon proposes the tests. Mina confirms the tool. Two concrete alternatives exist, and neither is yet approved. The first is to leave booking out of this release. The second is to assess deferring the Approach page to make room for booking. That second path is only an option to investigate. It is not proof of equal effort, and it is not proof that the deadline stays unchanged. Before choosing it, check whether the four remaining pages still let a visitor assess service fit. If they do not, that trade is unsuitable.
You can also discuss advisory fit for help thinking through a project plan. The business and life insights hub has more related reading.
Key takeaways
- State the visitor's task and the practice's goal side by side, and mark the need as unproven in this case.
- Settle copy and form decisions before the affected work begins.
- Use a proposed purpose check for the Services page, not only a functional page check.
- Keep the proposal label separate from the agreed baseline label while a request is pending.
- Name the information still needed and the person who decides next.
Frequently asked questions
References
- Association for Project Management. (n.d.). What is change control?.
- Government Digital Service. (2017). Learning about users and their needs.
- business.gov.au. (n.d.). Prepare a contract.
This article is for informational and educational purposes only and does not constitute financial, legal, tax, medical, or professional advice. Individual results vary.