Creating Evidence Briefs

What a Brief Is and Why Structure Matters

An evidence brief is a self-contained document that compiles all the evidence and arguments needed to run or answer a specific position. Think of it as a playbook: it should contain everything a debater needs to execute the argument without having to search through other files during a round.

The difference between a well-structured brief and a loose collection of cards is the difference between finding the evidence you need in 10 seconds and spending 2 minutes scrambling while your partner stalls. In policy debate, where prep time is limited and rounds move fast, a brief's organizational structure is as important as the evidence it contains.

Anatomy of an Effective Brief

A well-built brief follows a consistent structure that any team member can navigate. Start with a table of contents listing every section with page numbers. Then include a one-page overview that summarizes the argument's structure in plain language: what the position claims, its key warrants, and how it fits into the broader strategy.

The body should be organized by argument flow, matching the order you would present or encounter the arguments in a round. For an affirmative case, this means inherency, harms, plan, solvency. For a disadvantage, this means uniqueness, link, internal link, impact. For answers, organize by the arguments you are responding to.

Within each section, place your strongest evidence first. Judges pay the most attention to the first card read on any argument. Follow with supporting evidence and then analytical arguments that do not require cards. End each section with extension evidence that provides additional depth if the argument becomes a key point of clash in later speeches.

Maintaining and Updating Briefs

A brief is a living document. After every tournament, review which arguments were run against you, which of your evidence was challenged, and where you needed cards you did not have. Add new evidence and remove cards that proved ineffective or were successfully challenged. The best teams debrief after each tournament and assign specific brief updates to team members.

Version control matters. Label your briefs with dates and keep previous versions. If a card you removed turns out to be needed later, you can recover it. Shared team folders with clear naming conventions prevent the chaos of multiple outdated versions floating around. A naming convention like 'Sanctions-DA_v3_2026-04-10' tells every team member what the brief covers, which version it is, and when it was last updated.