P2 · Trying to get paid
The Clauses Every Freelance Contract Needs
Build a freelance contract around scope, acceptance, deposits, due dates, suspension, IP timing, revision limits, change orders, termination, liability, and governing law.
Scope should identify deliverables, exclusions, client responsibilities, and acceptance. 'Website design' is an invitation to argue; 'five-page responsive marketing site with two revision rounds' is a starting boundary. Payment terms should state deposit or retainer, milestone triggers, invoice due dates, acceptable payment methods, and what happens if payment is late. A late-fee clause must comply with applicable law to be enforceable.
Trace the whole commercial path before counting clauses
The contract should make the commercial path from kickoff to final handoff traceable. Start with scope, deliverables, exclusions, client responsibilities, acceptance, price, deposit or milestone triggers, invoice dates, and any right to suspend for nonpayment. Then align intellectual-property language with the payment and delivery process.
If ownership transfers only after full payment, the contract and the actual file-release workflow should say the same thing. Revision language also needs a definition of what counts as a revision versus fixing work that failed the agreed acceptance criteria.
Connect IP transfer to payment and the actual work product
Tie intellectual-property transfer or license rights to payment in language that fits the work. Copyright ownership, pre-existing tools, third-party assets, and portfolio rights are different questions and deserve explicit treatment.
Contract review before kickoff
- Name deliverables and exclusions.
- Set deposit, due dates, and suspension rights.
- Define revision rounds and change orders.
- Address IP timing and pre-existing materials.
- Have state-specific legal clauses reviewed when the stakes justify it.
A revision limit needs a definition of changed scope
Revision limits work only if change requests can be distinguished from defects or incomplete delivery. Define a round and explain how new scope is priced and approved.
A cancellation rule should price reserved capacity clearly
A kill fee or cancellation structure can compensate reserved capacity when a client stops a project after you have turned away other work. It should be understandable, proportionate, and consistent with local law.
Termination language should describe the operational exit
Termination language should explain notice, amounts due, work product handoff, access revocation, and what obligations survive. Ending the relationship is operationally easier when the contract already describes the exit.
Freelance contract clause map
Name deliverables, exclusions, client dependencies, revision limits, acceptance method, and schedule assumptions. Vague scope makes it difficult to distinguish a correction from a new request.
State deposit or milestone timing, due dates, suspension rights, reimbursable costs, and what happens to licenses or ownership before and after payment. Make any pre-existing tools, templates, or portfolio rights explicit rather than assuming “IP transfer” answers everything.
Define how extra work is quoted and approved, what happens when the client delays, how either side can terminate, what fees are earned or refundable, and what files or access must be handed over at exit.
Review confidentiality, independent-contractor language, indemnity, limitation of liability, governing law, dispute process, and insurance requirements with the actual jurisdiction and risk in mind. These are the clauses most likely to justify attorney review instead of copy-paste language.
How commercial clauses work together
The clauses that deserve the most caution are usually the ones that look like boilerplate: indemnity, limitation of liability, governing law, venue, arbitration, confidentiality, data-security promises, insurance obligations, and termination rights. A solo operator can accidentally accept uncapped exposure in exchange for a modest project fee. Bonsai's contract guidance reflects the market expectation that scope, payment, ownership, revisions, and termination should be explicit, but a template is only a starting document, not legal advice for your jurisdiction. For material contracts, have an attorney review the risky clauses rather than treating a copied freelancer template as universally safe.
Draft the contract around the points most likely to be remembered differently six weeks later. Define the deliverable, what is explicitly excluded, the client inputs required, the number and type of revisions, the acceptance process, and what happens when feedback is late. The payment clause should identify deposit or milestone amounts, invoice dates, due dates, approved payment methods, any lawful late charge, and whether work pauses for nonpayment. Intellectual-property language should say what is transferred, when the transfer occurs, and what pre-existing tools or portfolio rights remain with the freelancer. A sentence saying ‘all work belongs to client’ can create confusion if the project uses templates, licensed stock, open-source components, or a pre-existing framework. Align the contract with the actual delivery model rather than copying a broad clause from another profession.
Then add the exit and risk mechanics. State how either side can terminate, what work and fees become due at termination, whether a kill fee applies, how confidential information is handled, and how credentials/files are returned. Identify governing law and dispute process only after considering where the parties are located and whether the clause is practical; boilerplate from another state may create more questions than it solves. Indemnity, limitation-of-liability, warranty, and insurance language can shift meaningful risk and deserves legal review for larger engagements. Most importantly, add a written change-order process. When the client asks for an extra landing page, new integration, or fourth revision, the contract should make the next action obvious: describe the change, price it, show schedule impact, and obtain approval before starting. That operating habit prevents more disputes than an elegant contract nobody follows.
Version control matters too. Save the final signed agreement and every approved amendment in one project folder, and label drafts so nobody mistakes ‘contract-final-v3’ for the executed version. If the client’s purchase order or master services agreement conflicts with your proposal, resolve the conflict before work starts; an order-of-precedence clause can matter in larger arrangements. For recurring work, schedule a contract review before renewal to update price, scope, insurance, data-security obligations, and contacts. A contract is not a museum document. Its value is highest when the project manager can use it during a change, delay, payment issue, or exit without searching through old email threads to learn what the parties actually agreed.
Trace one client engagement from kickoff to exit
Clause map: put scope and acceptance near the commercial terms; put payment and suspension together; place change control next to revisions; then group IP, confidentiality, liability, termination, and disputes. A client should be able to trace what happens from kickoff through final payment and exit without guessing.
Contract questions to settle before work starts
Which contract clause prevents the most scope arguments?
No single clause does it alone, but a precise scope paired with acceptance criteria, revision limits, and a written change process does most of the practical work. The contract should make it possible to point to the promised deliverable and show what changed. Payment, schedule, and IP terms then need to respond consistently when that scope changes.
When should IP ownership transfer?
That depends on the agreement and type of work, but many freelancers align transfer or license grants with full payment while carving out pre-existing tools or portfolio rights as needed. U.S. copyright ownership and work-made-for-hire rules are technical, so important IP language deserves legal review.
How should revisions be written?
Define what counts as a revision, how many rounds are included, who consolidates feedback, and what happens when the client requests a new deliverable or direction. A change-order mechanism is more useful than a vague promise of 'reasonable revisions.'
Do I need a lawyer for every freelance contract?
Not necessarily for every routine job, but state-specific terms such as indemnity, liability caps, governing law, restrictive covenants, late fees, and IP can carry real consequences. A lawyer can review a reusable base agreement, after which you still need to adapt scope and commercial terms per project.
What if a client purchase order conflicts with the signed freelance agreement?
Do not assume the documents automatically reconcile themselves. Compare payment terms, scope, acceptance, intellectual-property language, liability provisions, and any order-of-precedence clause before work starts. Procurement paperwork can introduce terms you did not price. If the conflict is material, get the documents aligned in writing and use legal advice for high-value or high-risk agreements.