Define the parties, project, and scope
Start by identifying who is making the agreement. Use each party's legal name, address, and contact details, not only a brand name or social media handle. If your client is a company, confirm that the person signing has authority to hire you. State the effective date and give the project a recognizable name.
The scope of work is the center of the contract. Describe the deliverables, formats, quantities, deadlines, and responsibilities in concrete terms. Instead of promising website design, specify the number of page designs, included breakpoints, file format, and whether development is excluded. List what the client must provide, such as copy, access credentials, feedback, or source files, and explain how client delays affect the schedule.
Add an exclusions section for common assumptions that are not included. Examples might be printing, stock licenses, ongoing maintenance, extra meetings, or migration work. A clear boundary helps both sides price new requests fairly instead of arguing about whether they were implied.
Set payment, deposit, and expense terms
State the project fee or hourly rate, currency, invoicing schedule, due dates, and accepted payment methods. If the work is hourly, explain how time is recorded and whether there is an estimate, minimum, or maximum. If it is fixed-price, connect payments to dates or milestones that can be objectively recognized.
A deposit reduces the risk of reserving time for a project that never begins. Specify the deposit amount, whether it is refundable, and when work will start. For a longer engagement, milestone billing can keep the unpaid balance manageable. Also explain which project expenses need client approval and whether processing, transfer, travel, or third-party costs are passed through.
Include the consequences of late payment. These may include a reasonable late fee where lawful, pausing work, delaying delivery, or withholding a license until payment is complete. The contract should make those consequences predictable rather than punitive. Your invoice can repeat the terms, but the signed agreement is where the client should first accept them.
Control revisions and change requests
Unlimited revisions can quietly turn a profitable project into unpaid work. Define how many revision rounds are included, what counts as a round, and how quickly the client must provide consolidated feedback. Clarify that a revision adjusts an agreed deliverable; it does not replace the brief, add a deliverable, or restart approved work.
Create a simple change-request process. When the client asks for work outside the scope, describe the change, price, schedule impact, and approval method before doing it. Written approval by email may be enough for a small change, while a larger change may need a signed addendum. The important point is that silence or informal discussion does not automatically expand the original fee.
For hourly changes, track the time consistently so you can explain the added charge. A free time tracker provides a practical record for work that sits outside the original fixed scope.
Address ownership, confidentiality, and portfolio use
The intellectual-property clause should explain who owns the final work and when ownership transfers. A common arrangement transfers specifically identified final deliverables after full payment while the freelancer keeps ownership of pre-existing tools, templates, methods, drafts, and unused concepts. If the client receives a license instead of ownership, define the permitted uses, territory, duration, and exclusivity.
Do not promise rights you do not control. Identify third-party assets such as fonts, stock media, software, or open-source components and state that they remain subject to their own licenses. Also decide whether you may display the completed work in your portfolio and when that permission begins.
A confidentiality clause should define confidential information, permitted use, reasonable safeguards, and sensible exclusions such as public or independently developed information. If highly sensitive data is involved, confirm whether the client's required security practices are realistic for your workflow before signing.
Plan for cancellation, risk, and disputes
A cancellation or termination clause explains how either party can end the engagement. State the notice method, what happens to completed work, and when final payment is due. A kill fee compensates the freelancer when a booked project is canceled before completion. It can be a fixed amount, a percentage, or payment for work completed plus a cancellation charge. Make the formula clear.
Confirm that you are an independent contractor rather than an employee, and explain that you control how the services are performed subject to agreed outcomes. Liability and indemnity clauses allocate financial risk, so read them carefully. Avoid accepting unlimited liability for a modest project fee. Any cap, warranty, or indemnity should reflect the work and risks involved, and legal advice is worthwhile when a clause is broad or unclear.
Include governing law and a dispute process appropriate to both parties' locations. The agreement should also cover notices, amendments, and what happens if one clause is unenforceable. Finally, create signature blocks with names, roles, dates, and a clear statement of agreement. Electronic signatures may be valid in many places, but local rules vary.
Turn the checklist into a usable agreement
A checklist helps you spot omissions, but each clause still needs to match the actual project and local law. Start with the free freelance contract tool to organize the core terms, then review every field with the client before signing. For high-value, unusual, or legally complex work, have a qualified local lawyer review the agreement.
Do it now with ProposalPro — free
Offline, no sign-up, nothing uploaded. Pay once only if you want the Pro version.
Open ProposalPro free → Get Pro On PayhipFAQ
- What should every freelance contract include?
- It should identify the parties, define scope and deliverables, set payment and revision terms, address ownership and confidentiality, explain cancellation, allocate risk, and include signatures.
- How many revisions should a freelance contract allow?
- There is no universal number. Choose a limited number that fits the project, define what a revision round means, and price changes that alter the approved scope separately.
- When should intellectual property transfer to the client?
- Many freelancers transfer ownership of specified final deliverables only after full payment while retaining pre-existing tools, methods, templates, drafts, and unused concepts.
- What is a kill fee in a freelance contract?
- A kill fee is compensation owed when a client cancels a booked project before completion. The contract should clearly state the amount or calculation method.
- Does a freelance contract need a signature?
- A clear signature or other legally recognized acceptance helps prove that both parties agreed to the terms. Electronic-signature rules and enforceability vary by location.
Related free tools
This article is general information for freelancers, not legal, tax or financial advice. Rules vary by country — confirm specifics with a qualified professional.