Handling a Dispute Over a Grade

Every organizer eventually hears some version of “that should have counted.” It isn’t a sign the hunt went wrong — it’s just what happens once submissions get judged by a person instead of checked against one correct answer. The real question isn’t how to prevent disputes. It’s what you do in the two minutes after one starts, with a team standing there waiting on you.

Assume misunderstanding before you assume anything else

A team arguing a rejected photo usually isn’t trying to get away with something. They read the task one way, you meant it another, and both readings were reasonable enough. Starting from that assumption changes the whole conversation — “walk me through how you read that” gets somewhere. “No, read it again” just turns a genuine mix-up into an argument nobody wins.

A fast call beats a perfect one

A team standing on a corner waiting to hear if they can move on is worse off than a team that got an imperfect decision made on the spot. This is the same principle behind grading fairly and fast: speed is part of fairness, not a trade-off against it. Get a call wrong and you can fix it later — a decision that never arrives costs every team stacked up behind that one, not just the team arguing.

Note why, not just what

The real risk in a dispute isn’t one bad call. It’s grading the same kind of submission two different ways for two different teams, because nothing got written down the first time. A one-line note next to a rejected submission — “didn’t show the whole landmark, just the angle” — costs a few seconds and means the next similar submission gets judged by the same standard instead of whatever you happen to remember feeling an hour ago.

Reversing a call is fine. Defending a bad one isn’t.

If a closer look shows you actually got it wrong, change it. That’s the process working, not a crack in your authority. What actually damages trust is holding a bad call out of stubbornness, because admitting the mistake feels worse than the mistake itself did. Make the correction the same way you made the original call: visibly, and by the same standard you’d apply to anyone else asking.

Sometimes the argument isn’t really about the task

Every so often, what’s in front of you isn’t really about the submission on the screen. A team that’s felt like it’s been losing ground all game will push harder on a borderline call than a team comfortably ahead, even reviewing the exact same kind of photo. You don’t need to fix that feeling. You just need to notice it’s there, so you’re resolving the actual disagreement in front of you instead of refereeing the whole game because one moment tipped someone over the edge.