Five questions to ask before your next awards cycle opens. For the people who own the outcome, not the settings.

Five questions to ask before your next awards cycle opens.

For the people who own the outcome, not the settings.

By Ion Despoiu. .

Before you reopen your awards program, ask five questions:

  1. What did last cycle actually cost?
  2. Who held it together?
  3. Can we explain the decisions?
  4. What did participants experience?
  5. What will we measure this time?

Most awards programs reopen the same way. Last year’s form, last year’s dates, last year’s judges, a new year in the header. That is reasonable. It worked, the winners were announced, and the gala happened.

These questions are not about the form or the settings. They are for the people who own the outcome at an association: the executive director, the awards chair, the board member who will be asked why someone won. A short conversation will show where the gaps are. Some answers will take follow-up, and that follow-up is the point. None of it requires new software.

I spent years supporting the systems behind association programs. These are the questions I wish had been asked more often before a call for nominations went out.

1. What did last cycle actually cost?

An awards round is usually measured in entries. The more useful unit is hours.

Eighty entries, read by three judges each, at fifteen minutes a read, is sixty hours of volunteer time before a single decision gets made. Say the program asked judges for about two hours a week over a three week judging window. That round needs ten judges. With eight, each judge carries two and a half hours a week, a quarter more than the commitment you asked of them.

The free reviewer capacity calculator does this math for your own numbers in under a minute.

Then add the staff hours nobody logs: chasing late scores, answering the same nominee question by email, rebuilding the results spreadsheet the night before the committee meets. The spreadsheet breaking point counts those chores for your own numbers.

A good start is asking the staff lead to walk through the last two weeks before the deadline and the judging window, day by day, and to estimate where the time went. The number is often larger than anyone expected.

2. Who held it together?

Every awards program has a person who knows where everything is. The spreadsheet on the side. The judge who needs a phone call instead of an email. The sponsor who was promised a mention in the ceremony program, in an email two years ago.

That knowledge is a gift to the program, and it is also a risk. It usually lives in one inbox and one memory.

A simple way to find it: ask what would break if that person were out for two weeks during judging. If the honest answer is “most of it,” the program is not running on a process. It is running on staff heroics, and heroics do not transfer, scale, or survive a resignation letter.

3. Can we explain the decisions?

Sooner or later someone asks why. A finalist who did not win. A sponsor whose category drew a surprise. A board member fielding a call from a longtime member.

A clear record answers part of that question: which judges scored the entry, how the scores were combined, and who stepped aside because of a conflict.

The rest of the answer is about the process itself:

  • Were the criteria, their weights, and the tie-breaking rule agreed before judging started, or settled once the scores came in?
  • Did every nominee in a category get the same number of reads, against the same criteria?
  • When the committee departed from the scores, did the program’s rules allow it to, and was the reason written down at the time? A documented reason helps, but it only holds up if the rules gave the committee that discretion before judging began.

If those answers live across three email threads and a spreadsheet with a filename ending in final, you can still answer the question. It just takes a week, and it feels less certain than it should. Finding that out before the cycle opens is far better than discovering it after the winners are announced. For an executive director or a board, this is the question that matters most. See also every awards and grants program produces a decision someone will eventually question.

4. What did participants experience?

Silence is not the same as satisfaction.

A judge who read everything on the last Sunday often will not mention that the load was too much. They said yes, and saying it was too much can feel like going back on their word. More often, they are simply busy next year. A nominee who emailed twice and heard nothing rarely files a complaint. They remember instead.

You can find out without a formal survey. A short personal note to last year’s judges, asking what one thing would make judging easier, tends to get honest answers. If your form tells you how many nominations were started and how many were finished, the gap between those two numbers is worth a look too.

5. What will we measure this time?

Most programs can only report what they happened to capture: entries received, winners selected. The questions above are harder to answer because nobody decided in advance to measure them.

Decide now. Hours per judge. Nominations started versus submitted. How far apart judges scored the same entry. Days from the deadline to the committee decision. Pick two or three that matter to your program and agree on how you will capture them before the first nomination comes in.

A cycle you can learn from is worth more than a cycle that simply ran.

Who should be in the room

Start with three people: the executive director or awards chair, the staff lead who ran last cycle, and someone who will be asked to defend the results. A first meeting of about thirty minutes is enough to name the gaps and decide who follows up on what.

The answers will shape the decisions that are easy to change now and hard to change later: the judging window, the number of judges to recruit, the conflict of interest step, and what you promise nominees about communication.

Where the platform fits

I built New Empact Work so that each cycle leaves a better record for the next one. In an awards program, scores, conflict declarations and final decisions are logged and traceable through the full review. When judges score the same entry far apart, AI flags it so a person can take a second look. It never scores an entry or decides who wins. That is the line worth drawing.

A record will not tell you why a judge quietly stepped away, or what your most experienced staff member carries in her head. It does mean next year’s conversation starts with evidence instead of memory.

Frequently asked questions

When should we ask these questions?

A few weeks before the call for nominations opens, ideally before dates are announced. Once the dates are public, the judging window and the number of judges you need are much harder to change.

Who should answer them?

The person who owns the outcome, usually the executive director or the awards chair, together with the staff lead who ran the last cycle. For the fourth question, the most useful answers come from last year’s judges themselves.

Do we need software to answer them?

No. All five can be answered with conversations, last year’s email, and a calendar. Software helps by capturing more of the evidence as the cycle runs, so less has to be reconstructed from memory.

What if we cannot answer question three?

That is the most important finding of the five. It does not mean last year’s decisions were wrong. It means they would be hard to explain if challenged, and that is worth fixing before the next round of finalists is chosen.

Do these questions apply to scholarship and grant programs?

Most of them do, with different vocabulary. This guide is written for awards programs, where the nominee, the judges, and the public announcement make the questions especially visible. The same planning questions apply to scholarship and grant programs.

Carry the cycle forward

Most platforms help you run a program. New Empact Work is designed to carry it forward.

If you would like to see how an awards cycle runs with a traceable record from start to finish, request a demo.

← Back to resource library