September/October 2026 PF Topic: Data Centers
Last updated: August 1, 2026. The resolution below is the announced, final wording.
September and October are the months where prep gaps show up most, because nobody has a backfile yet and everyone is reading the same three articles. Getting ahead is mostly about starting earlier than the people you hit in round one.
The topic is out, so that clock is running now.
What is the September/October 2026 PF topic?
Resolved: The United States federal government should enact a moratorium on hyperscale data center construction.
The NSDA announced it on August 1, 2026. It beat the other ballot option, a federal emissions trading system, and it was not close: per the NSDA's announcement, 530 coaches and 2,401 students voted, and the moratorium took 80% of the coach vote and 68% of the student vote.
We called this one on July 28, before the vote, and said on this page that we would own it either way. The reasoning was that summer camps across the country ran data center topics this year, so thousands of debaters and their coaches walked into the vote already holding data center prep, and communities vote for the topic they are prepared on. The 80% coach split is about what that theory predicts.
What happened to the other option?
The ballot was two options, and the emissions trading system lost. It is worth about sixty seconds of your attention and no more: the two resolutions overlap enough that a little of the reading transfers.
Did not win. Resolved: The United States federal government should enact an emissions trading system.
Both were federal interventions in how electricity gets produced and paid for, both put consumer energy prices on the flow, and both came down to the same question: should the government slow down something economically valuable to cut its environmental cost? If you prepped cap and trade in July, the electricity-market and cost-pass-through reading still pays off. The rest of it does not. Move on.
The resolution, term by term
The two words doing the work here are "moratorium" and "hyperscale." A moratorium is a pause on new construction rather than a shutdown of what already exists, so the pro is not defending turning off anyone's servers. "Hyperscale" is a size category, which means the resolution draws a line somewhere and both sides will argue about where.
The background numbers are already public. Pew Research reports that "U.S. data centers consumed 183 terawatt-hours (TWh) of electricity in 2024", more than 4% of total US electricity consumption, and that "by 2030, this figure is projected to grow by 133% to 426 TWh." The same piece notes the concentration problem that makes this a live political fight: in 2023 data centers used roughly 26% of Virginia's total electricity supply, 15% in North Dakota, and 12% in Nebraska.
The arguments will run through electricity prices, grid capacity, water use for cooling, local tax revenue, construction jobs, and whether a pause pushes the buildout to other countries instead of stopping it.
How does NSDA topic voting work?
The NSDA's Public Forum wording committee writes a slate of potential resolutions each year and assigns two of them to each topic cycle, and the membership picks between them by vote. Per the NSDA's Topic Creation Hub, the committee is made up of coaches and alumni selected through an application process, and their job includes researching topics, evaluating options against the NSDA Topic Rubric, gathering feedback from the community, and meeting virtually between January and June.
The full year's potential resolutions are released the Monday after the National Tournament ends. Then, one week before each topic cycle's release date, voting opens. Eligible voters are member students and one chapter advisor per active school. The option with the most votes becomes the resolution.
For Public Forum the ballot is always two options, which is why the outcome is worth watching rather than assuming. This cycle the favorite won by a wide margin. That is not the usual case.
When was the September/October 2026 topic announced?
August 1, 2026, following voting that closed at 4:00 p.m. CT on July 31. It is posted at speechanddebate.org/topics, which is the only authoritative source for the exact wording.
Get the wording off that page, not off a screenshot in a group chat. Every word in a resolution is arguable, and the gap between "should enact" and "should establish" is exactly what a definitions debate turns on. That applies to this page too: we quote the announced wording above, but the NSDA is the source of record.
What should you do in the first 48 hours after the topic drops?
The first two days set up the next two months. You are not trying to finish a case. You are trying to understand the topic well enough that everything you cut afterward has somewhere to go.
Hours 1 to 2: read the resolution like a lawyer. Write out every term that could be defined more than one way. Here that is "moratorium," "hyperscale," and "construction." How long is the pause, what size threshold counts as hyperscale, and does construction include expansion of an existing site? Then decide what the resolution actually forces the pro to defend. Most of the confusion in week one is a definitions problem nobody said out loud.
Hours 3 to 6: find the conversation, not the articles. Every resolution sits on top of a policy argument researchers and agencies have been having for years. Go find that argument before you cut anything. Search the subject plus "policy brief," "congressional testimony," "regulatory impact," or "literature review." What you want is the five or six sources everyone in the field keeps citing. Those become your backbone.
Hours 7 to 10: write link chains on paper. Three pro contentions, three con contentions, each as uniqueness, link, internal link, impact. Still no cards. If you cannot write the chain without evidence in front of you, you do not understand the topic yet, and everything you cut at that stage gets thrown out later.
Day 2, first half: cut one contention all the way. Pick the pro argument you believe most and finish it, tags and cites and highlighting. One complete contention teaches you more about what evidence exists than six half-cut ones.
Day 2, second half: cut the case you are most afraid of. Then answer it. This is the single most valuable thing you can do in week one, because everyone else is still writing their own case and nobody has answers to anything yet.
Keep a source log the whole time. One doc, every URL you open, one line on whether it was worth it. In week six when you need "that one study about electricity prices," you find it in ten seconds instead of forty minutes.
What to skip in the first week
Do not write the final version of anything. The topic looks different after you have hit it three times, and first-week cases exist to be replaced.
Do not chase the fanciest argument on the topic either. Somebody in your Discord will post a creative angle on day two; it is usually under-carded and it gets answered. Win the central argument first.
And do not cut cards for arguments you have not written yet. Cutting without a link chain to hang the card on just produces files you never open again.
When does the next topic come out?
Public Forum runs on two-month cycles, so the September/October resolution is replaced by the November/December topic. The potential resolutions for every cycle in the 2026-2027 season are already published on the NSDA's topics page, with each cycle's vote opening one week before its release date. If you want to look ahead, they are all there now.
Updates to this page
- July 29, 2026: Published with the ballot options, voting mechanics, and the first-48-hours plan. Called the data center moratorium as the likely winner.
- August 1, 2026: Updated with the announced resolution and the vote breakdown. The data center moratorium won with 80% of the coach vote and 68% of the student vote. Trimmed the emissions trading sections, which are no longer live.
Once the resolution drops, the bottleneck stops being "what do I argue" and becomes "how fast can I turn sources into cards." That second part is the part worth speeding up. The strategy is still yours to make, and it should be. If you want the mechanical half to go faster, DebateCardAI takes a URL and a claim and hands back the extraction, the tag, the cite, and the highlighting.
Written by Zaid Anwar, founder of DebateCardAI. Resolution text and voting dates quoted from the National Speech & Debate Association.