A client breaches your contract the moment they fail to fulfill a specific term they agreed to. Non-payment is the clearest version, but scope rejection without basis, unilateral changes to deliverables mid-project, and refusal to provide contracted materials or access all qualify. Knowing what constitutes a breach, and what doesn’t, is the starting point for deciding what to do about it.

Not every difficult client situation is a breach. Slow feedback, vague approvals, scope creep requests, these are annoying, and they may violate the spirit of your working agreement, but they’re not breaches unless your contract specifically addresses them. A breach is a failure to fulfill a specific, written term. If you’re unsure what terms are worth including, the clauses that protect you in a freelance contract covers the ones that matter most.

What Constitutes a Breach

The most common breaches in freelance work: payment not received by the agreed date, demand for work outside the contracted scope without additional compensation, rejection of work that meets the agreed specifications without a contractually supported basis, and, in longer engagements, unilateral termination without following the termination clause.

The key phrase is “agreed specifications.” A client who genuinely dislikes your work isn’t necessarily in breach, depending on how your contract defines approval and acceptance. If the contract says the client has final approval rights with no conditions, they can reject work they dislike even if it’s objectively good. If the contract says “client approval shall not be unreasonably withheld” or defines acceptance criteria, then refusing to approve work that meets those criteria is a breach.

This is why specific contract language matters more than most freelancers realize. A vague approval clause gives the client unlimited subjective discretion. A specific one ties approval to defined standards, and makes rejection without basis a breach.

What Remedies Are Available

When a client breaches a contract, you generally have three options: request they remedy the breach, pursue damages, or terminate the contract and pursue payment for work already done.

Remedying the breach means asking them to do what they agreed to, pay the invoice, stop requesting out-of-scope work, follow the termination procedure. This is the first step in almost every case, and it needs to be in writing. Send a clear notice specifying which term was breached, what they need to do to remedy it, and by when. Seven to fourteen business days is a typical notice period. Keep the language factual and direct.

Damages for a contract breach are typically the amount you’re owed under the contract terms. In a non-payment situation, that’s the invoice amount, plus any late payment interest specified in your contract. In a wrongful termination situation, it may include the kill fee or the remaining project fee depending on your contract terms. Courts generally don’t award punitive damages for contract disputes, only compensation for what you were owed.

Terminating the contract and pursuing payment for completed work is the realistic outcome when the client relationship is beyond repair. You stop work, you send a final invoice for work delivered, and you pursue that invoice through whatever mechanism your contract provides for.

How to Document a Breach

Documentation is what separates a dispute you can resolve in your favor from one that goes nowhere. Start collecting evidence the moment you recognize something might be going wrong, before you raise the issue with the client.

For a payment breach: gather the contract or written agreement, the invoice with the due date, all follow-up communications, and any client responses. If the client has acknowledged the invoice in writing, even to ask for more time, you have strong evidence the debt exists. If they’ve gone silent, document when you sent each communication and what response you received.

For a scope breach: pull the original scope definition from the contract, the client’s request that falls outside it, your communication noting that the request is out of scope, and their response. The trail shows that you identified the breach, communicated it clearly, and gave them the opportunity to pull back. Without that trail, a scope dispute looks like a misunderstanding rather than a breach.

Screenshot everything that lives in a browser or app, client portals, project management tools, messaging platforms. If your working relationship moved off email onto Slack or a similar platform, export or screenshot the relevant threads. Digital evidence disappears when accounts are closed or subscriptions lapse.

Whether Pursuing a Freelance Contract Breach Is Worth the Cost

This is the question most freelancers avoid until they’re already in it. The honest answer: it depends on the amount, the jurisdiction, your documentation, and your tolerance for the process.

Small claims court (in the jurisdictions where freelancers most commonly work) costs $30–$100 to file, requires no lawyer, and typically involves one or two appearances. The ceiling is usually $5,000–$25,000 depending on the jurisdiction. For disputes in that range with strong documentation, small claims is often worth pursuing, not just for the money, but because leaving a breach uncontested sets a pattern.

For amounts below $1,000–$1,500, the honest calculation often doesn’t favor litigation. Filing fees, preparation time, appearance time, and any follow-up collection work add up. A collections agency is a lower-effort alternative for amounts in this range, they take 25–40% of collected amounts, but they handle the process.

For amounts above the small claims ceiling, you’re into civil court territory, which means legal costs and a longer process. In most freelance disputes, the amounts involved don’t justify this, but knowing your local small claims limit clarifies your options before you’re in the middle of a dispute.

Most breach situations resolve before legal action, if you handle the early stages correctly. The sequence matters.

First: document the breach internally. Gather your evidence before you say anything to the client.

Second: send a written breach notice. Specific, factual, no emotional language. State the term that was breached, what’s owed, and the deadline for remedy. This creates a legal record and often prompts resolution.

Third: if no response or no remedy by the deadline, escalate in writing. Inform the client that you’re proceeding with formal enforcement and specify what that means, a collections referral, a small claims filing, whatever is accurate.

Many clients pay at this stage. The threat of a formal record, a judgment against their business, a collections notation, is often more motivating than the amount itself. Clients who were testing how far they could push become cooperative once they realize the freelancer is prepared to follow through.

The clients who don’t respond to any of this are telling you the cost-benefit calculation on legal action. If they have no assets, no stable business address, and no concern about a judgment, enforcement becomes a matter of principle rather than recovery. Knowing this going in helps you decide early whether to pursue or write off and move on. A client who refuses to honor the contract is also one worth understanding in retrospect — spotting client red flags earlier can help you avoid reaching this point again.

What You’re Entitled to Claim

Beyond the unpaid invoice, your contract may entitle you to additional amounts. Late payment interest, if your contract specifies a rate (common in professional services contracts, typically 1.5–2% per month or a flat statutory rate in some jurisdictions). Legal costs, in some small claims jurisdictions, if you win. The kill fee amount, if the termination violated the contract’s termination clause.

Document these amounts separately and clearly. A claim that says “I am owed $4,200 for the completed project plus $126 in late payment interest per the contract’s interest clause” is cleaner and more credible than a general demand. Courts appreciate specificity, and it signals that you know what you’re owed and why.

The breach itself is one event. What you do in the hours and days after it matters as much as the breach documentation for determining what outcome you can realistically expect. If non-payment is the specific breach you’re dealing with, what to do when a freelance client refuses to pay walks through the escalation steps in more detail.