1. Severe Error (-.5) Reserved for mistakes that disturb the routine in an extreme way, such as a wild throwaway, a long, embarrassing break in the routine, or an incident that clearly endangers the audience. Judges are cautioned to make a Severe Error deduction only when the audience is clearly endangered, not just when players perform near the audience. Catches near the audience may add to a routine's excitement without endangering spectators.
I noticed something at Paganello while helping Lui tabulate the results of the Co-op finals. A judge gave three teams in my pool a Severe Error - including one in my routine with Gery Nemeth and Balu Major. As implied in the definition above, Severe Errors are most often wild throaways, discs thrown out of the reach of the teammate. I was surprised because I didn't remember any throwaways during our performance. I'll have to wait until the videos hit YouTube to remind myself of what happened during our five minutes.
I bring this up not as a sob story. We would have placed the same with or without that deduction. I bring this up because Severe Errors are rare, especially indoors, and yet three teams were given the Severe Error deduction during the finals, so it's a good window into how judges perceive the judging system and the routine they watch.
Judging competency is essential. As so many players emerge into the competitive scene, it's super important that judges are trained and that players can expect to be evaluated consistently. One of the best ways to improve our judging competency is through discussion. So let's talk about the Severe Error. When do you give them, what's your threshhold for the difference between Major and Severe Error? What do we need to do to communicate the difference to new judges?
I give Severe Errors rarely because that's the intention of the judging system. They are Severe. Most teams don't stray into Severe territory. They may make mistakes, but most don't make gigantic, severe mistakes that match the definition of this deduction.
For throwaways, I adhere very strictly to the definition. It's got to be a
wild throwaway. The teammate doesn't even have a chance to touch the disc. Someone used to use the phrase "throw to the ghost," like the disc was thrown to someone not even on the team.
Regular bad throws usually get a 0.2 or 0.3 from me. If the disc is dropped or doesn't reach the teammate, but it's not a huge, embarrassing error, I give a 0.3. Occasionally, I'll downgrade for 0.2 if someone is able to seamlessly pick or kick the disc back into play.
The other scenarios for Severe Error rarely happen. I personally have not seen a player endanger the audience. I've seen many flow interruptions, but the play hardly ever stops long enough for it to be a Severe Error.
What kind of disruptions would merit a Severe Error if I were a judge? Let's say the team not only forgot where they were in the routine but started a long conversation about what to do. After about 10 seconds of absolutely nothing going on, I'd probably give the Severe Error. Usually, teams make some sort of throw before that, so this situation rarely comes up.
How about teams that endanger the audience? For me, the line that distinguishes between aggressive play, going after a disc off the field, and a Severe Error is body control. If the player is tracking the disc AND the audience, and if they make good decisions about where to run/jump, it's not a severe error for this judge. But, if the player recklessly runs into the audience with a great chance of collision, or if they jump with little body control so there's a very real possibility of them landing on an audience member, they get the 0.5 deduction.
I want to make an important distinction. There are players who can play into an audience without endangering them. It's probably not the best situation, but I'll let the Artistic Impression judges deal with that. The point is: the player isn't endangering the audience by doing it, and that is the essential difference between a Severe Error and a questionable decision that's not really an error.
22 comments
Most Recent Post: 04/02 06:06PM by John Weyand
