Your biggest client just paused the project six weeks in. The deposit covered the first two weeks. The half-finished deliverable sits on your drive, the client is asking for all work in progress, and your invoice from last month is still unpaid — now 45 days past due with no late fee in the contract to point at. Nothing about this situation is unusual. Nearly a third of freelance invoices arrive late, and most disputes between consultants and clients are not about the quality of the work. They are about things the agreement never nailed down: what was actually in scope, who owns the half-built work product, what happens when the project stops early, and how much of the client's losses you are on the hook for.
A consulting agreement is not paperwork you sign to make the client comfortable. It is the operating manual for the engagement — the document that decides who gets paid, who owns what, and who absorbs the damage when something goes wrong. Whether you are a solo freelancer or a small agency, the checklist below covers the clauses that matter most, in the order you should negotiate them.
1. Pick the Right Container: Standalone Contract or MSA Plus SOW
Before any clause, decide what kind of document you are signing.
- A standalone consulting agreement fits a one-time project with a defined deliverable and end date. Everything — scope, fees, ownership, liability — lives in one document.
- A Master Services Agreement (MSA) plus a Statement of Work (SOW) fits ongoing or repeat work. The MSA governs the relationship (payment terms, confidentiality, indemnification, liability caps), and each project gets its own SOW describing the services, who performs them, and the fees. New projects need only a new SOW, not a renegotiated contract.
If a client expects to hire you more than once, push for the MSA structure. Renegotiating indemnification and liability from scratch on every project wastes leverage you already won once. Either way, make sure the term is explicit: a fixed end date far enough out to finish the work, or an open-ended term either party can end with written notice.
2. Scope of Work: Write the Out-of-Scope List First
Scope disputes are the most common consulting fight, and they are almost always preventable. A scope section that says "marketing strategy support" means something different to you and to the client. Be specific about deliverables, milestones, timelines, revision rounds, and who does what — including what the client owes you (data access, feedback within five business days, a single decision-maker).
Then write the mirror image: an explicit out-of-scope list. Implementation support, extra revision rounds, work in tools you did not agree to, rush turnarounds — name them, and state that anything outside scope requires a written change order with additional fees. That one paragraph converts most scope creep from an argument into an invoice.
Two more scope details that save freelancers real money:
- Acceptance criteria. State how the client accepts each deliverable and what happens if they go silent — for example, deliverables are deemed accepted if no written objection arrives within ten business days. Without this, a client can stall acceptance indefinitely and with it your final milestone payment.
- Client dependencies. If your timeline depends on the client delivering inputs, say so, and say the schedule extends day-for-day for client delays. Otherwise their three-week silence becomes your missed deadline.
3. Who Owns the Work Product: Work-for-Hire Language Is Not Enough
This is the clause consultants misunderstand most. Many agreements declare that everything you create is "work made for hire" owned by the client — and many consultants assume that settles it. Under US copyright law, the work-for-hire doctrine covers employees and only narrow categories of specially commissioned works. Most consulting deliverables do not qualify, and courts have repeatedly held that calling something work for hire in a contract does not make it so.
What actually transfers ownership is a written copyright assignment. A solid IP section has three parts:
- Assignment of deliverables. You assign to the client all right, title, and interest in the finished deliverables — ideally upon full payment, which gives a non-paying client a reason to settle up.
- Carve-out for your pre-existing IP. Your frameworks, templates, code libraries, and methods that predated the engagement stay yours. List them or describe the category, and grant the client only a license to use them as embedded in the deliverables. Without this carve-out, a broad assignment can accidentally hand over the reusable toolkit your whole practice runs on.
- License-back for portfolio use. If you want to show the work to future clients, get written permission now. Many clients agree to portfolio use with confidential details removed; almost none agree after the fact.
If you subcontract any of the work, flow these terms down: your subcontractor agreement should assign the subcontractor's work product up the chain to you, or you will promise the client ownership of something you do not own.
4. Payment Terms That Actually Get You Paid
Roughly 29 percent of freelance invoices are paid at least one day late, and cash flow is the top-cited concern for independent workers. Your payment section is where you fight that statistic. Cover each of these explicitly:
- Upfront deposit. Ask for 30 to 50 percent before work begins, non-refundable, credited against the total fee. A client who will not pay a deposit is signaling how the final invoice will go. For long engagements, consider a monthly retainer paid in advance instead.
- Milestone schedule tied to deliverables you control. Break fixed fees into installments invoiced as you complete defined milestones — not a single balloon payment at the end. Each milestone should have the acceptance criteria from section 2 attached.
- Net terms you can live with. Net 30 — payment due within 30 days of invoicing — is the consulting standard, but large clients often impose net 60 or net 90. Know your floor before the negotiation, and price longer terms into the fee if you accept them.
- Late fees and pause rights. A monthly late charge (for example, 1.5 percent per month) sets expectations even when clients negotiate it down. More powerful is the right to pause work if an invoice goes unpaid beyond a defined grace period — it converts your leverage from a future lawsuit into present-tense pressure.
- Payment method and expenses. State how you get paid (ACH or wire, not a credit card that passes processing fees to you), how often you invoice, which expenses are reimbursable, and the receipt and pre-approval process.
One bookkeeping habit belongs right here in the contract discussion: money a client pays you before you earn it is not revenue yet. Record retainers and deposits as a liability — cash received in advance — and move each portion to income only as you complete the milestone. Booking the whole retainer as day-one income overstates your profit, understates what you owe, and makes an early termination far messier to unwind. If you track your practice in Beancount.io, that liability account doubles as a live readout of unearned obligations across every client.
5. Kill Fees and Termination: Price the Cancelled Project
Every engagement ends, and many end early. A termination clause should answer three questions before anyone wants out:
- How much notice? Thirty days is typical for retainers; project work often allows termination at any point with written notice. The notice period is what guarantees a retainer consultant gets paid through a wind-down window instead of losing the income overnight.
- What is owed on exit? You should be paid for all work performed through the termination date, plus expenses incurred, plus — for project work — a kill fee covering the cancelled portion. A common structure: the non-refundable deposit serves as the kill fee, plus payment for completed milestones and wind-down work.
- What changes hands? Spell out that you deliver work in progress upon payment of amounts owed, and that confidentiality obligations survive termination.
Negotiate this clause when everyone is optimistic, because it only gets read when someone is not. A client cancelling for convenience should still make you whole for the time you reserved and turned away other work to protect.
6. Indemnification: Tie It to Bad Acts, Not Everything
Indemnification means one party covers the other's losses — including legal fees — from specified events, usually third-party claims. Clients often present one-sided versions where you indemnify them for any losses "arising from" your services. Read that literally: a client could hand you the bill for their own business losses tangentially connected to your work.
Push for three fixes:
- Tie your indemnity to fault. You indemnify the client for third-party claims caused by your gross negligence, willful misconduct, fraud, or infringement of third-party IP — not for every loss connected to the engagement.
- Make it mutual where fair. If the client supplies data, content, or instructions that trigger a claim, the client should indemnify you. One-way indemnities in either direction deserve a justification.
- Cap it. Your indemnification obligation should be subject to the same liability cap as everything else (see section 7), excluding only what the law in your jurisdiction will not let you cap.
Indemnification without a cap is the clause most likely to bankrupt a freelancer over a single engagement. Never sign an uncapped indemnity to win a project.
7. Cap Your Liability at Fees Paid
The limitation of liability clause sets the maximum you can owe if things go wrong. The standard freelancer position has two halves:
- Exclude consequential damages. Neither party is liable for indirect, incidental, consequential, special, or punitive damages — including lost profits — even if advised they were possible. This is mutual and almost always accepted.
- Cap direct damages at fees paid. Your total liability under the agreement cannot exceed the fees the client actually paid you (some consultants negotiate fees paid in the preceding 12 months for long engagements). A $25,000 project should never be able to produce a $250,000 judgment against you.
Expect carve-outs: breaches of confidentiality, IP infringement, and fraud or willful misconduct are commonly excepted from the cap. That is normal. What is not normal — and worth walking away over — is unlimited liability for ordinary breach, or a cap that applies to you but not to the client. Many clients accept the fees-paid cap once it is framed as proportionality: your exposure should match the size of the engagement, not the size of their company.
8. The Supporting Clauses Worth Reading Twice
The seven items above carry most of the risk. These five close the gaps:
- Confidentiality. Protects the client's non-public information and limits your use of it to performing the services. Check that the definition has standard exceptions (publicly known information, independently developed knowledge, legally compelled disclosure) and that the survival period is reasonable — two to five years, not forever, except for true trade secrets.
- Independent contractor status. States you are a contractor, not an employee: you control your schedule and methods, use your own equipment, serve multiple clients, and handle your own taxes with no withholding. The label alone does not decide worker classification — tax authorities apply multi-factor tests — but its absence invites misclassification trouble.
- Non-compete and non-solicitation. Treat any post-engagement restriction on who you can work for as a major concession, not boilerplate. Narrow the scope, shorten the duration, and charge for it. An unbounded non-compete signed casually can idle your practice for a year.
- Governing law and dispute resolution. Prefer your home state's law; for cross-state engagements, a neutral jurisdiction is a common compromise. Decide between courts and binding arbitration deliberately — arbitration is private and often faster, but harder to appeal and sometimes surprisingly expensive.
- Entire agreement and change control. The written agreement (plus its SOWs) is the whole deal — proposals, emails, and verbal promises do not modify it. Pair this with a requirement that scope or fee changes be in a signed writing, and handshake scope creep loses its power.
9. Pre-Signature Checklist: Read Your Draft Against These Questions
Before you sign — your template or theirs — run through this list:
- Could a stranger tell from the SOW exactly what you will deliver, when, and what is excluded?
- Does the IP section assign deliverables, carve out your pre-existing toolkit, and address portfolio use?
- Is there a deposit or prepaid retainer, milestone invoicing, defined net terms, and a late-fee or pause-work remedy?
- Does termination for convenience pay you for work done plus a kill fee, and define the handover?
- Is your indemnity limited to your bad acts and subject to the liability cap?
- Is your total exposure capped at fees paid, with consequential damages excluded both ways?
- Are confidentiality, contractor status, restrictive covenants, governing law, and change control all addressed?
If the client redlines heavily, concede in this order: governing law venue before liability caps, liability caps before indemnity scope, and indemnity scope before IP ownership of your toolkit. Never trade away the cap or the IP carve-out to close faster — those two clauses are the difference between a bad project and a practice-ending one.
Keep Your Consulting Finances as Clean as Your Contracts
A tight agreement gets you paid; clean books prove what you earned, what clients still owe, and which engagements actually made money once deposits, milestones, and expenses are tracked properly. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and run your practice on books as disciplined as your contracts.
