The oral adjudication (the "oral") is the part most new judges dread. You've made your call, you know who won, and now you have to stand up and explain it to a room full of people who care deeply about the result. Some of them will disagree with you. Here's how to do it well.
The structure
There's a formula which works. Use it until you're experienced enough to deviate from it.
Start with the motion and the major clashes. "This was a debate about X. The major clashes were Y and Z." This frames the oral and tells the debaters you understood the round. It takes 20 seconds and it matters more than you think, because teams want to know the judge was paying attention.
Then walk through each clash. For each one: what did the government bench say? What did the opposition bench say? Who won the clash and why?
Be specific about why. "OG won this clash because their mechanism was more clearly explained and OO's response didn't address the root cause" is good. "OG was just better here" is useless. Teams can't learn from "just better."
Then explain the ranking. "CG is first because they won the most important clash, which was X, and their extension added Y which nobody responded to. OO is second because while they lost on clash X, they won on clash Z and that was the second most important issue in the round."
Here's what that sounds like in practice. Say you're judging a round on whether companies should be prohibited from regulating employees' private behavior. The major clashes were: (1) company property rights versus worker autonomy, and (2) whether regulation chills unionization. Your oral might start: "This was a debate about the boundary between work and private life. The two major clashes were property rights and unionization. On property rights, OO argued companies have a legitimate interest in protecting their brand through employee conduct. OG responded by distinguishing between conduct which affects output and conduct which doesn't. I found OG's distinction persuasive because OO never explained why an employee's weekend social media post affects Monday's output. On unionization, OG argued private behavior regulation gives companies a tool to retaliate against organizers. This was the stronger clash because it affected more people more deeply. OO didn't engage with it directly."
That's specific. Teams can hear exactly where they won and lost.
End with brief feedback if time allows. One thing each team did well, one thing to work on. Keep it actionable. "Your mechanism was strong but you didn't weigh it against the other side's impact" is actionable. "Good speech" is not.
The tone
An oral is not a lecture. You're talking to people who just spent an hour thinking hard about something they care about. Some of them are going to be disappointed. Respect that.
Be confident but not arrogant. You're explaining your reasoning, not declaring universal truth. "I found OG's mechanism more convincing because..." is better than "OG clearly proved that..."
Acknowledge difficult calls. If the round was close, say so. "This was a very close round between OG and CG" is honest and it helps the losing team understand they didn't do badly. Pretending a close round was obvious is disrespectful.
Don't apologize for your call. If you believe it's right, stand behind it. "I think OG wins, though I can see it the other way" is fine. "I'm sorry, but OG wins" undermines your credibility.
What to do when teams push back
It happens. A team thinks you got it wrong and they want to argue about it. Some tournaments have formal processes for this; follow them. In informal settings, here's what works.
Listen to the point they're making. Sometimes teams raise something legitimate which you missed or forgot. If that happens, it doesn't mean you need to change your call (the call is final), but you can acknowledge it: "That's a fair point, and I can see how that strengthens your case."
Don't get defensive. The worst thing you can do is dig in and refuse to engage. That makes teams feel unheard and it teaches them nothing. Engaging with their point, even if you still disagree, shows you're taking them seriously.
Stay on your reasoning. If your call was based on which team won the major clashes, explain that framework. "I hear your point about the depth of your impact, but I weighted the probability clash higher because OG's mechanism was more clearly established." You don't need to agree with the pushback, but you do need to explain your decision-making process.
Giving feedback which helps
The oral is often the only feedback debaters get from a judge. Make it count.
Focus on one thing per team. If you try to give five pieces of feedback to every team, nobody remembers any of it. Pick the single most impactful thing each team could improve. For a novice team, that might be "your argument jumped from the problem to the impact without explaining how the mechanism works." For an experienced team, it might be "your weighing came too late in the speech and the comparison wasn't specific enough."
Frame feedback as what to do, not what went wrong. "Next time, try spending 30 seconds explaining why your impact is more important than the other side's" is more useful than "you didn't weigh." The first one gives them something to practice. The second one just identifies a gap.
Be honest about strengths. If a team lost but ran one genuinely good argument, say so. "Your second argument on institutional accountability was strong, and if you'd spent more time developing it instead of splitting between three arguments, it might have changed the result." This gives them a clear path forward.