Tabula Debate

Framework (FW)

6 min read · Intermediate

Framework is an argument about how the judge should decide the round. Before the judge can weigh arguments, the judge needs a rule for what counts. Framework supplies that rule. It comes up most when one team argues about the plan's results and the other team argues about ideas, words or debate itself. Each team says its way of deciding is fairer or teaches more, and the judge picks one.

On this page

Two meanings of "framework"

The word is used in two related ways. Know which one a team means.

UseWho usually runs itThe question
Framework against a kritikThe aff, against a neg kritik (K)Should the judge weigh the plan's results, or the aff's ideas, or both?
Framework against a kritikal affThe neg, against an aff with no planMust the aff defend a government plan that fits the resolution?

Both are about the rules for the round. They have different shapes, so they are explained separately below.

Framework against a kritik

When the neg runs a kritik, an argument that questions the ideas behind the aff, the aff often argues that the judge should weigh the plan's consequences against the neg's best policy option.

The aff's side, often:

  • The resolution asks about a policy, so the round should be about the policy's results.
  • The aff prepared to defend the plan. Judging its words or assumptions instead moves the target.
  • Weighing consequences is how real policy choices are made.

The neg's side, often:

  • Ideas and language shape which policies get made, so they matter before the results.
  • The aff chose its words and its reasons. It should defend them.
  • Debate is an education. Questioning assumptions is part of what it teaches.

Middle grounds are common. Many judges let the aff weigh the plan, and let the neg win if it shows the aff's ideas make the plan's results worse. This is called a K that turns the case. Teams should say which middle ground they want, if any. See Framework against a kritik.

Framework against a kritikal affirmative

Some affirmatives do not defend a government plan. These are kritikal affirmatives, or K affs. See Kritikal affirmatives. The neg often answers with framework (sometimes called T-USFG, short for "topicality: United States federal government," because many resolutions name the federal government as the actor). It looks like topicality.

PartExample (generic)
Interpretation"The aff must defend action by the federal government that fits the resolution."
Violation"The aff does not defend government action."
Standards"Limits and predictable ground: the neg prepares for the resolution. Fairness and clash."
Voter"Fairness and education. Vote neg."

Limits means a set range of affs to prepare for. Ground means arguments a side can count on. Clash means the teams answer each other directly.

The neg's side, often:

  • A shared, stable topic lets both teams prepare. That is what makes the game fair.
  • Debating government action teaches useful skills, such as policy analysis and research.
  • The aff could still make its critical arguments while defending a plan.

The aff's side, often:

  • The neg's rule leaves out important voices, ideas and ways of arguing.
  • The aff is still connected to the topic, even without a plan.
  • Debate's value is in what it teaches the people in it, and the aff's approach teaches more.
  • It offers a counter-interpretation (its own rule) that includes the aff, and answers the limits standards.

This is one of the most debated topics in the activity. Judges hold a wide range of views. Many state their view in their paradigm. See Framework against a kritikal affirmative.

How to answer framework

  • Counter-interpretation: offer a way of deciding that includes your arguments.
  • Answer the standards: show your approach still allows fair, educational debate.
  • Impact your own standards: say why what your approach gains is more important.
  • Win under their framework too, if you can. For example, a neg can show the K turns the case even if the judge weighs consequences. An aff can show the case outweighs even if the judge looks at ideas.

How to judge framework

  1. Decide framework first. It tells you what counts. Then judge the rest of the round under it.
  2. Use what the teams argued. Do not import your own framework unless no one argued one.
  3. Look for "win either way" arguments. If one team wins under both frameworks, framework may not decide the round.
  4. Explain the decision. In the RFD (reason for decision), say which framework won and why. This is the part of the round teams most want to understand.

Example in flow shorthand

Framework against a kritik. The neg ran a security kritik, which questions how the aff describes threats. The aff answered with framework. Each group is one argument, speech by speech. The 2AC is the aff's answer to the neg's first speech. The block is the neg's next two speeches. The 1AR is the aff's next speech. The 2NR and 2AR are each side's last speech. Key: FW = framework. Reps = representations, the words and framing a team uses. Ext = extend. W/o = without.

HOW TO WEIGH
2AC:   weigh plan vs a policy
       option
Block: ideas shape policy; judge
       reps first
1AR:   Ext: policy resolution;
       plan is what we prepared
2NR:   aff chose its words;
       defend them
2AR:   weigh plan; even under
       their FW, case is clear

GROUND
2AC:   K moves the target
Block: aff should defend its
       reasons
1AR:   neg can still run DAs and
       CPs
2NR:   ideas first is real
       education
2AR:   they never said why their
       FW gives better education

EDUCATION AND MIDDLE GROUND
2AC:   education: policy skills
Block: middle: weigh plan, but K
       can turn it
1AR:   accept middle: weigh plan,
       K can turn it
2NR:   K turns case under either
       FW
2AR:   K does not turn case: plan
       works w/o threat framing

How to read it: in the last group, the 1AR accepted the neg's middle ground (weigh the plan, but the K can turn it). Both sides still extend their framework claims in the first two groups, but the framework debate has narrowed. Under the middle ground, the round turns on the last group: does the K turn the case? That is common: a framework debate often narrows to one smaller question the judge can decide.

Common mistakes

  • Running framework with no counter-interpretation. Fix: say exactly how the judge should decide.
  • Treating framework as all-or-nothing. Fix: offer and answer middle grounds.
  • Winning framework but nothing else. Fix: also win under the other team's framework if you can.
  • Neg (vs a K aff): standards with no impact. Fix: explain why limits and fairness matter, not only that they exist.
  • Aff (vs framework): ignoring the topic link. Fix: explain how your aff connects to the resolution.
  • Judges: deciding framework by personal preference. Fix: decide it as argued, and explain it in the RFD.