A named awards owner or a shared inbox? Business awards operating workflow

What to take away

• A Manchester organiser with 300 entries and two staff usually loses a week to entries sitting in a shared inbox with no owner.
• Name one workflow owner, one deputy and one escalation route before the entry window opens.
• Write it as numbered steps with an owner and a deadline on every step, not a policy paragraph nobody reads.
• Test the incident route once, in advance, rather than discovering it during judging week.
• Keep the workflow reviewable, because service standards change as schemes grow.

Who owns each step of the workflow?

A workflow without a named owner is a wish. For a small England scheme, one person should own the entry window end to end, with a deputy for holidays and sickness. Escalation goes to a director, not a group chat.

Write the owner's name, the deputy's name and the date on the workflow document.

Ownership matters most in the two weeks before the deadline, when entries pile up, queries multiply and a missed upload can cost a finalist place.

Keep the owner separate from the judging chair. The person chasing entries should not also be marking them.

What does the numbered workflow look like?

1. Publish the category list and rules, with a version number and a date.
2. Open the entry form and confirm the confirmation email arrives.
3. Assign each entry to a named reviewer within two working days.
4. Check eligibility and evidence before scoring begins.
5. Score against the published criteria, recording comments.
6. Moderate scores and resolve gaps above an agreed threshold.
7. Notify shortlisted entrants, then publish the shortlist.
8. Run the ceremony and capture the results for next year.

Each step needs a deadline and a named owner. Steps 4 and 6 are where most disputes start.

If a cyber incident affects the entry portal, follow the government route for reporting a cyber incident and tell entrants what has happened. Do not wait for the full picture.

How do you handle handovers between teams?

Handovers fail when the receiving team learns about the work too late. Move entries from marketing to judging with a written handover note: volume, exceptions, unresolved queries.

Agree one shared tracker as the single source of truth. If two spreadsheets exist, one is wrong.

The wider operations and delivery guide sets out how this workflow sits inside the annual programme.

Build a short risk list. Supply chain disruption can affect sponsor commitments, and supply chain visibility guidance from BSI explains how to see those risks earlier.

Which categories need extra checks?

Employment initiatives awards need current labour market context, because entry claims are easy to make and hard to verify. The Office for National Statistics data on people not in work gives a defensible baseline for those categories.

Sponsor-funded categories need a conflict check. Anyone with a commercial link to a sponsor should step back from scoring that category.

Categories with minors, health claims or safeguarding angles need a second reviewer. Add that reviewer to the workflow, not to a side conversation.

How do you keep the workflow current?

Review the workflow after every cycle. Ask which step caused the most emails, which deadline slipped, and which owner was overloaded.

Change one thing at a time, so the knowledge that made the workflow work survives the review.

Store the current version in one place with the date visible, and archive old versions rather than deleting them.

Set a review date before the next entry window opens, so changes land while there is still time to test them.

Common questions

How many people does a small awards workflow need?

For a scheme with a few hundred entries, two people can run it: one owns the process, the other covers judging. Add a third for the ceremony period. For example, a team processing 400 entries might need one full-time coordinator for six weeks.

Should the workflow live in software or a document?

Both. Keep the workflow as a document anyone can read, and use software for scoring and notifications. The document is the authority when tools fail.

What is the first step to fix a broken workflow?

Name the owner. Most failures trace back to unclear responsibility rather than missing tools. Once one person owns the process, the other gaps become visible.

When should the workflow be tested?

At least once before the entry window opens, using a dummy entry. Test the confirmation email, the reviewer assignment and the escalation route. Fix what breaks before real entrants arrive.