Good supplier management comes down to four habits: a clear brief, a written agreement that names deliverables and ownership, a change process so scope does not drift, and regular reviews against what was agreed. It applies equally to agencies, freelancers and technology vendors. Most disputes trace back to vague scope or unspoken assumptions, not to bad intent.
Write it down before work starts
The Western Australian Small Business Development Corporation’s guidance on contracts and agreements says it is advisable, where possible, to put business arrangements in writing, because verbal agreements are hard to prove. If you cannot get a written contract, it suggests keeping emails, quotes or notes of discussions. It also lists what a contract may cover, including:
- the parties and any subcontracting
- duration, key dates and milestones
- a description of the services and key deliverables
- payment details and dates
- insurance and indemnity
- complaints and dispute resolution
- termination conditions
The same page makes a point that matters for creative work: for something like a logo, the creator usually keeps copyright unless there is an assignment, so include an assignment clause if you need to own the materials. This is general information, not legal advice, so have significant contracts reviewed by a lawyer.
Brief the supplier properly
A brief is the shared reference for the whole engagement. Useful briefs state:
- The business objective, not only the task.
- The audience and where the work will run.
- Required deliverables, formats and specifications.
- Constraints: budget range, timing, brand rules, legal and platform requirements.
- Examples of what you like and dislike, with reasons.
- Approval roles: who gives feedback, who signs off.
- What is out of scope.
Templates help. Our brand brief guide and website brief template show what to include for those project types.
Agree deliverables you can verify
The Australian Government’s contract management guide is written for public sector buyers, but its principles carry over. It advises clearly defining the objectives, deliverables and scope from the outset, regularly monitoring performance against the contract, and managing the working relationship with the supplier. It also covers handling contract variations properly rather than informally.
For private buyers, apply the same idea in plain terms. A deliverable is verifiable if someone else could check it: “three 15 second cutdowns in the agreed formats” is checkable, “engaging video content” is not.
A supplier management cycle
| Stage | What to do | What to keep |
|---|---|---|
| Select | Compare briefs responses on approach, evidence and fit, not only price | Scoring notes |
| Agree | Written scope, milestones, payment, IP, confidentiality | Signed agreement |
| Kick off | Meet, confirm contacts, approval path and schedule | Meeting notes |
| Deliver | Check work at milestones against the brief | Dated feedback |
| Change | Record any scope or timing change and its effect | Written variations |
| Review | Meet briefly at milestones and at the end | Short review notes |
| Close | Confirm final files, handover and ownership | Archive of assets |
Handling changes without drama
Scope changes are normal. The risk is the informal change that nobody priced or recorded. Agree upfront how changes are requested, who approves them and how cost and timing are assessed. Rounds of revisions are a common friction point, so state how many are included and what counts as a revision versus a new request.
Giving feedback that works
- Consolidate feedback from your team into one list before sending.
- Refer to the brief: say what does not meet it, not only what you dislike.
- Be specific about what to change and what to keep.
- Say who has final approval so the supplier is not chasing conflicting opinions.
Reviewing performance fairly
At milestones and project end, review against what was agreed: quality, timeliness, communication, responsiveness and value. Record both sides. Suppliers improve when feedback is specific, and your records help you decide whether to rebook, change scope or move on. Our guide on choosing a web development partner lists criteria that also work for ongoing reviews.
Limits
No template removes the need for judgement. Small engagements may justify lighter documentation, while large or high-risk ones deserve legal review. Government guidance describes good practice, not a legal requirement for private businesses.
Where Radiance Impact fits
Radiance Impact works with businesses on creative production, websites and automation, and values a clear brief. If you are scoping a project or comparing suppliers, read more about us or contact us.
Sources
- Contracts and agreements, Small Business Development Corporation (Western Australia)
- Australian Government Contract Management Guide (August 2025), Department of Finance
