Peer Review and Case Testing

Writing Is Only Half the Work

A case that looks strong on paper may fall apart under pressure. Arguments that seem airtight when you write them alone in your room may have obvious flaws that a teammate spots in thirty seconds. Evidence that reads well silently may be unclear when spoken aloud at speed. The only way to discover these problems is to test your case before the tournament.

Case testing serves three purposes. First, it reveals structural weaknesses: arguments that do not flow logically, evidence that does not actually prove what your tagline claims, and contentions that contradict each other. Second, it simulates tournament conditions, forcing you to deliver your case under time pressure and respond to challenges you did not anticipate. Third, it gives you practice with the physical performance of debating — pacing, emphasis, eye contact, and clarity — which no amount of writing can substitute for.

Three Methods for Testing Cases

Method 1: The read-through. Read your case aloud to a teammate or coach while they follow along. They should interrupt whenever something is unclear, whenever an argument seems unsupported, or whenever they can think of an obvious response you have not addressed. This low-pressure format catches writing-level problems before you invest time in practice rounds.

Method 2: The devil's advocate round. Have your strongest teammate argue the opposing side as aggressively as possible. Their job is to find every possible weakness: attack your evidence quality, propose permutations to your counterplans, and exploit logical gaps in your reasoning. Write down every argument they make that you struggle to answer. Those are your case's vulnerabilities, and each one needs a block.

Method 3: The judge simulation. Find someone unfamiliar with your case — a parent, a younger student, or a coach from a different event. Deliver your case to them and ask them to explain it back to you. If they cannot accurately summarize your main arguments and why they matter, your case has a clarity problem. Judges at tournaments often hear your case for the first time; if a fresh listener cannot follow it, neither will they.

From Feedback to Revision

After each testing session, organize the feedback into three categories. 'Must fix' items are structural problems that will lose you rounds: a contention that contradicts your framework, evidence that has been misrepresented, or an argument that every practice opponent easily defeated. 'Should fix' items are improvements that would strengthen the case: better evidence for a weak subpoint, a clearer transition between contentions, or additional weighing analysis. 'Nice to have' items are polish: word choice improvements, rhetorical flourishes, or additional examples that are not essential but would enhance the presentation.

Address must-fix items immediately. Schedule should-fix items for the next preparation session. Save nice-to-have items for after you have tested the revised version and confirmed the structural problems are resolved. This triage prevents the common trap of polishing language while ignoring a fundamental argument flaw.