Frontlining is the skill that decides whether your 1AR survives or collapses. Here's a concrete method for doing it under real time pressure.
"Frontlining" means going back to your own case after the other side has attacked it and rebuilding it — answering their specific objections rather than just repeating what you already said. It's most associated with the 1AR in Policy and LD, widely considered the hardest speech in either format, but the same skill shows up any time you have to defend a case against a full speech of attacks in less time than it took to attack it.
The math is the problem. In Policy, the negative gets a combined 2NC + 1NR block — often thirteen minutes total — to attack the affirmative case and run new off-case positions. The 1AR then has four to five minutes to answer all of it: extend what's dropped, frontline what's contested, and respond to anything new, simultaneously. In Lincoln-Douglas, the 1AR faces a seven-minute NC in four minutes. There is no version of this that isn't tight. The skill is in how you spend the limited time you have, not in somehow finding more of it.
Before you say a word, look down your flow and sort your original arguments into two piles: dropped (the other side never answered it, so you just extend it briefly) and contested (they gave a real response, so you need to frontline it). Don't spend 1AR time re-explaining something that was never attacked — extend it in one sentence and move on. Your limited time belongs entirely to the contested arguments.
The single most common frontlining mistake is repeating the original argument louder instead of answering what was actually said against it. If they said your link evidence is outdated, "our impact is still real" doesn't respond to that — you need to either defend the link's currency or explain why the impact holds regardless. Read their attack back in your head before you answer it. If your response would make sense without their attack existing, it isn't a frontline.
Even a well-answered attack often leaves both sides' claims technically "standing" on the flow. That's exactly when you need to explicitly tell the judge why your side's version still wins — which impact is bigger, which link is more probable, which argument comes first analytically. A frontline that ends in "so both arguments are true" hasn't actually won you anything; a frontline that ends in "and here's why ours matters more even if theirs is also true" has.
A judge has to be able to follow your frontline back to the specific attack it's answering, in real time, while you're talking. If your flow has the attack and your response in the same row, you can point at it (literally, in some formats) or simply structure your speech in the same order your flow is organized — down the page, one contested argument at a time — rather than jumping around.
The debaters who frontline well aren't the ones who talk fastest. They're the ones whose flow already tells them exactly what to say next.
If your flow lines up their attack directly across from your original argument — the way a flow is supposed to work — frontlining stops being a memory exercise and becomes a reading exercise: read down the row, answer what's actually there. This is exactly what a linking feature is for. In RoundFlow, hitting Respond → on any card drops your reply into the next column, already connected back to the exact argument it answers, so by the time you're prepping your 1AR the connections are already drawn — you're not reconstructing them from memory under a four-minute clock.
This matters most in the two formats where frontlining is most punishing: Policy's 1AR, answering a full 2NC/1NR block, and LD's 1AR, answering a seven-minute NC in four. Both format guides walk through the full speech order and timing if you want the complete picture.
Free, no account needed — Respond → keeps every frontline connected to what it's answering.