Case Construction: What Goes Into a Case, and Why Each Piece Is There

You will read your affirmative case out loud somewhere between fifteen and thirty times before the topic changes. Every other speech is improvised against whatever the other person just did. This one is a script, it is yours, and it is the only place in competitive debate where you get unlimited time to make six minutes as good as you can make them.

Most novices treat the case as an essay with debate vocabulary sprinkled on it. It is closer to a piece of engineering: every part is load-bearing, and you can tell which part failed by where the round fell apart.

Six minutes of speech at a pace a judge can follow and take notes on is roughly 800 to 950 words. Writing 1,400 and reading faster is not a solution. The judge's pen is the bottleneck, and an argument the judge did not write down did not happen.

So the case is a budget, and every sentence is competing with another sentence for the same seconds. Definitions that nobody will contest are expensive. A second piece of evidence for a point already won is expensive. A fourth contention is very expensive, which is why most strong cases run two or three.

An opening line or short framing observation, which can be a quotation or a single sentence establishing what the debate is about. Fifteen seconds is generous.

The resolution, read as written. Then definitions, but only for the terms that will actually be fought over. On Resolved: Outer space colonization is a moral imperative, "moral imperative" decides the round and "outer space" does not.

The framework: your value and your criterion. The value is the thing that matters most in this debate, like justice or human survival. The criterion is the test a judge applies to decide which side achieved it better. What a framework is covers this in full, and the value and criterion builder walks you through producing one that is yours rather than one borrowed from a camp file.

Then the contentions, each one a complete argument with its own evidence, each one ending in a sentence that connects it to the criterion by name.

Then, if the time is there, a short preempt of the response you already know is coming. Twenty seconds spent answering an argument before it is made is worth more than a minute spent answering it in the first affirmative rebuttal, where minutes are scarce.

A closing line that is a reason to vote, not a summary.

The framework decides what counts as a good argument, so writing contentions before you settle it means writing arguments that may point somewhere the ballot is not.

The order that works: read the resolution until you can say what moral question it is really asking, pick the value that question is about, build a criterion that is an actual test rather than a synonym for the value, and only then go find contentions that the criterion rewards. The step by step walkthrough has the longer version of this sequence.

The test for a criterion is whether you can lose under it. "Maximizing good outcomes" is not a test. "Reducing the probability of unrecoverable harm" is, because the negative can argue their side does that better, and sometimes they are right.

A contention is the same three-part object from claim, warrant, impact, with room to breathe. The contention heading is the claim, compressed to something a judge can write in five words. The body is the warrant, this time with evidence attached and the mechanism explained rather than asserted. The last sentence is the impact, and it names the criterion.

Put the mechanism in your own words before the card, so the argument survives the moment your opponent goes after the source. And write the last sentence of every contention as though it were the only sentence the judge will remember from it, because on a busy flow it sometimes is.

Order them by strength, not by chronology. Most judges are most attentive early, and the first affirmative rebuttal will eventually force you to pick two things to defend, so build the case so the strongest thing is already in the most memorable position.

Seven minutes, two jobs, and no idea in advance which affirmative case you are answering. The usual shape is a framework of your own, one or two contentions, and then line by line answers to the affirmative.

What makes it hard is that your case and your answers compete for the same clock. A negative who spends all seven minutes refuting has built nothing to vote for, and a negative who spends all seven minutes reading a case has conceded the affirmative's. The split is the strategy, and it should change depending on whether the round is going to turn on framework or on evidence.

Read it out loud, timed, standing up. Silent reading hides every sentence that is hard to say and every place you run out of air.

Cut to time by removing whole sentences rather than by speaking faster. If it is thirty seconds long, one piece of evidence is doing work another piece already did.

Hand it to somebody and ask them to tell you what the criterion was without looking. If they cannot, the framework is not on the page clearly enough yet.

Then run the case structure checklist before you take it to a tournament, and read an annotated case in full to see the pieces assembled.

After every tournament, mark the two places the case got hit hardest and rewrite those before the next one. A case that goes unchanged across a whole topic cycle is a case nobody learned anything from.

Also in this series: how one argument is built, the round clock, and offense and defense.