If you've already decided you're going to respond to a claim — see how to respond to a claim if you haven't worked through that yet — this is where you actually do it. A vague, one-line denial and a specific, well-organized Defence can lead to very different outcomes, even when the underlying facts are the same. If you'd like a structured way to sort out the specifics before you start writing, the being sued wizard walks through the same questions in order.
What a Defence actually needs to do
A Defence has two jobs: respond to what the plaintiff alleged, point by point, and set out your own version of events where it differs. It's not the place to simply vent about the situation — it's a structured response the court and the plaintiff will use to understand exactly what's actually in dispute.
Before you get into line-by-line responses, it's also worth ruling out whether timing alone might resolve things in your favour — see limitation period as a defence for when a claim may simply have been filed too late to proceed, regardless of its underlying facts.
Think of it from the judge's perspective at a later settlement conference or trial: they weren't there when the dispute happened, and their first real exposure to your side of the story is often your Defence. A document that's organized and specific makes it far easier for them to see your position clearly — a vague one leaves them relying almost entirely on the plaintiff's account by default.
The admit, deny, or no-knowledge framework
A useful way to work through the plaintiff's claim is to treat each factual statement in it as something you either admit, deny, or have no knowledge of:
- Admit what's simply true — for example, that an agreement existed, or that a certain amount was paid. Contesting facts that aren't actually in dispute wastes credibility you'll want later for the parts that matter.
- Deny what's factually wrong, and say specifically why — not just "this isn't true," but what actually happened instead.
- State you have no knowledge of something you genuinely can't confirm or deny — for example, an event you weren't present for.
Going through the claim this way, allegation by allegation, produces a far more credible and organized Defence than a general statement of disagreement. It also has a practical side benefit: doing this exercise early often reveals exactly where the real dispute lies, which is useful information heading into a settlement conference later.
Responding to each specific allegation
Read the plaintiff's particulars slowly, and respond to the substance of each part rather than the claim as a whole. If they say work was never completed and you say it was, state when it was completed and how you can support that. If they claim a specific dollar amount and you think it's wrong, say what you believe the correct amount is and why — silence on a specific point can be read as conceding it.
It helps to physically break the plaintiff's particulars into individual factual claims — one sentence or idea at a time — and write your response next to each before drafting your final Defence. This catches allegations that are easy to skip over when reading the claim as one continuous story, and it ensures nothing goes unanswered by accident.
Telling your side clearly
After responding to their allegations, lay out your own account in plain, chronological language — what happened, in what order, and why it supports your position. Stick to facts you can back up rather than characterizations of the other side's motives or character. "The delivery was two weeks late" is more persuasive and more defensible than "they never cared about doing the job properly."
If your defence rests on something the plaintiff left out of their claim entirely — for example, a verbal change to the agreement, or a problem on their side that caused the delay — this is the place to introduce it clearly, with dates, rather than assuming the judge will infer it from your denial alone.
Before and after: strengthening a weak Defence
A weak Defence might simply say: "I don't owe this money. The work was bad." It doesn't engage with any specific allegation, and gives a judge nothing concrete to weigh.
A stronger version
"I admit that I hired the plaintiff to install kitchen cabinets for $4,200, and that I paid this amount in full on March 5, 2026. I deny that the work was completed to the agreed standard. Three of the cabinet doors do not close properly, and the countertop was not sealed as specified in our written agreement. I raised these issues with the plaintiff by email on March 25 and April 2, 2026, and received no response. I am asking that the claim be dismissed, or in the alternative, that the amount awarded reflect the cost of completing the work properly, which I estimate at $1,100 based on a quote I have obtained."
This version admits what's true, denies what isn't with specifics, references documentation, and states a clear position on what should happen — everything a judge needs to actually engage with the dispute.
Including a Defendant's Claim if it applies
If you believe the plaintiff (or someone else connected to the dispute) owes you money related to the same situation, consider filing a Defendant's Claim alongside your Defence rather than as an afterthought. See Defendant's claims for how this works — it's generally more straightforward to raise this at the same time as your Defence than to add it in later.
A common example: a contractor sues for an unpaid final invoice, and the homeowner believes the contractor's own defective work caused additional costs to fix. Rather than starting a separate case, the homeowner may be able to raise that as a Defendant's Claim within the same proceeding, so both sides of the dispute get resolved together.
Referencing supporting documents
Where possible, refer to specific documents that support your Defence — an email, a revised quote, a photo — even if you're not required to attach everything at this stage. Doing so signals that your position is documented, not just asserted, and makes your eventual settlement conference or trial preparation more straightforward since you've already identified what supports each point.
If a document contradicts something in the plaintiff's claim directly — for example, an email where they acknowledge a delay was on their end — point to it specifically in your Defence rather than saving it as a surprise for later. There's little practical advantage to holding back your best evidence, and doing so can come across as though you're uncertain of your own position.
A quick checklist before you file
- Go through the plaintiff's claim line by line and confirm you've admitted, denied, or addressed every specific allegation.
- Check your own account is chronological and factual, not just an emotional response to being sued.
- Decide whether a Defendant's Claim applies, and include it now if so.
- Identify the documents that support your position, even if you're not filing them all yet.
- Confirm your filing deadline and the correct court location one more time before you submit.
Filing and serving your Defence
Once your Defence is written, it needs to be filed with the court by your deadline, along with the applicable fee — see filing fees. Filing alone isn't the end of the step: you're also generally responsible for making sure the plaintiff receives a copy, following similar rules to those that applied when you were served. See serving the defendant for the general principles, which apply in both directions.
Common mistakes to avoid
- A one-line denial that doesn't respond to specific allegations.
- Disputing facts that are actually true, which undermines credibility on the parts that genuinely are in dispute.
- Focusing on the plaintiff's character instead of the facts.
- Leaving out a Defendant's Claim when the dispute genuinely goes both ways.
- Missing the filing or service deadline while still drafting the perfect wording.
- Not keeping a copy of exactly what was filed and when.
Frequently asked questions
Can I change my Defence after I've filed it?
You may be able to amend your Defence later depending on the circumstances, but it's far simpler to get your Defence right the first time — treat filing as the moment to finalize your position, not a rough draft.
What if I agree with part of the claim but not all of it?
Say so specifically — admit the part that's accurate, and deny or explain the part that isn't. Partial agreement is common and doesn't weaken your position; vagueness does.
Do I need to prove my Defence is true when I file it?
No — filing is about stating your position clearly, not proving it. Proof comes later, at a settlement conference and, if needed, at trial.
What if I run out of time before I've gathered every document?
File based on what you know and have by the deadline — a Defence can often still be supported by further documents you gather afterward, but missing the deadline itself is a much bigger risk than filing before you've located every last document.
What if the claim against me contains factual errors mixed with true statements?
Respond to each part on its own terms — admit what's accurate, and specifically correct what isn't, rather than treating the whole claim as either entirely right or entirely wrong.
Can my Defence be longer than the plaintiff's claim?
There's no requirement that it match the claim's length. Focus on being complete and specific rather than hitting a particular length — a short Defence that addresses everything is better than a long one that pads around the actual issues.
Should I get help writing my Defence?
You're allowed to have a lawyer or licensed paralegal help, but many people write effective Defences themselves using a clear, specific structure like the one above.