Why write it down
Verbal agreements are easy to make and easy to remember differently. Two reasonable people can finish a conversation each believing they agreed to something slightly different. A written agreement turns those private assumptions into shared, visible terms. That helps the client, who knows what they will receive and when, and it helps you, because you know what you are being paid for.
A written agreement also makes it easier to be friendly. When a request goes beyond what was agreed, you can point to the page rather than argue about memories.
Scope and contract: what is the difference?
People use the terms loosely, but they are different things.
- A scope agreement (or scope of work) describes the project itself: what will be delivered, how, by when and what is excluded.
- A contract is a broader legal agreement that includes the scope and also sets out legal terms such as payment, ownership, confidentiality and what happens if things go wrong.
For small projects, the two are often combined in a short document. For larger or riskier work, a fuller contract is common.
What a scope usually covers
A clear scope answers the practical questions:
- Deliverables. What exactly will you hand over? Include quantities, formats and any specifications. “Three page designs delivered as image files” beats “website design.”
- Activities. The main steps you will take, if that helps the client understand the work.
- Timeline. Start date, key milestones and delivery date, plus what the client must provide and when, such as content, access or feedback.
- Revisions. How many rounds are included and what counts as a round. This supports good client expectations.
- Exclusions. What is not included. This is where many disputes are avoided, since unstated extras are the usual cause of scope creep.
- Assumptions. Things you are relying on, for example that the client supplies final text, or that the project does not need integration with other systems.
- Change process. How extra requests are handled: written, estimated, approved before work starts.
- Acceptance. How the client confirms the work is complete, and how long they have to raise issues.
If you have already written a client proposal, much of the scope can be taken from it. A well-defined service offering also makes the scope easier to write, since the deliverables are already described.
Other clauses commonly found in simple contracts
The exact content varies by place and by project. These are topics that often appear, described in general terms only.
Fees and payment. Price, deposit, milestones, due dates and any late payment terms. See the invoicing basics for common payment arrangements.
Ownership of the work. Who owns the final deliverables, and when does ownership pass, for example only after full payment? Whether you may show the work in your portfolio is another point worth stating.
Confidentiality. Whether either side must keep certain information private.
Third-party materials. Who is responsible for licenses for fonts, images or other materials used in the work.
Termination. How either side can end the agreement, with what notice, and what is owed for work done up to that point. This matters if you ever need to step back from a client, as discussed in handling difficult clients.
Liability. Limits on what each side is responsible for if something goes wrong. This is a technical area where the wording matters.
Governing law. Which place’s laws apply and where disputes would be handled.
Entire agreement and changes. A statement that the document is the full agreement, and that changes must be made in writing.
Keep it readable
A contract that nobody understands protects nobody. Use plain language, short sentences and headings. Avoid copying long passages of legal text you do not understand, because you may be agreeing to things you did not intend. A good test is whether the client could explain the key terms back to you.
Templates and professional advice
Many freelancers start from a template. A template can be a helpful outline, but it may not suit your location, your type of work or the specific project, and some terms may not be enforceable in some places. This article is general information and not legal advice. For anything substantial, unusual or risky, such as large fees, ownership of important intellectual property or international clients, consider having a qualified professional review your standard agreement. A one-off review of a reusable template is often a sensible investment.
Putting it into practice
- Agree the main points in conversation or in a proposal first.
- Write the scope and terms in a short document.
- Ask the client to read it and raise questions.
- Have both sides confirm acceptance, using whichever method is valid where you live, which may include a signature or an email confirmation. Check local rules.
- Store the signed copy with your project files and records.
- Refer to it when changes come up, and update it in writing if the project changes.
Keep it a living document
If a project evolves, update the agreement rather than relying on informal changes. A short written amendment stating the new deliverable, price and date is enough in many cases. The goal is not to be rigid. It is to make sure that when something changes, both sides are changing it knowingly.
Even the best agreement cannot prevent every problem, and it does not replace good communication. But it gives you a shared reference point, and that often turns tense moments into routine ones.