Best Awards Management Software for UK Programmes

What awards management software does

Awards management software is a system for collecting entries, organising them by category, running structured judging across one or more rounds, communicating with entrants and judges, and reporting on outcomes. It sits between form builders, which collect entries but cannot evaluate them, and event platforms, which handle logistics but rarely handle judging.

The category is growing quickly. The award management software market was valued at USD 0.84 billion in 2025 and is forecast to reach USD 2.74 billion by 2034, a compound annual growth rate of 14.1 per cent, with the United Kingdom holding around 7 per cent of the global market (source: Fortune Business Insights, Award Management Software Market).

That growth has a practical consequence for you: more vendors, longer feature lists, and a harder shortlisting job. Most buying guides on this topic are published by a vendor that happens to rank itself first, which is why this piece sets out criteria rather than a league table.

The week spreadsheets stop coping

Programme teams rarely switch because of a feature gap. They switch because of a specific week.

You know the shape of it. A third of the entries arrive in the final 48 hours, several by email because the form gave up. The shortlist gets assembled by hand the night before the panel meets, and nobody can say with confidence that the tie in category four was broken the same way as the tie in category seven.

Chambers Ireland hit the version of this that hurts most. Judging three programmes, the team printed every application five times, one copy per judge, and posted the folders out. Judges could only work with the folder in front of them, volunteers were increasingly put off by the workload, and entry volumes kept climbing. Moving judging online is what fixed it.

That is the real competitor for most UK programmes. Not another platform: email, a shared drive and a spreadsheet, held together by one person who remembers how it all works.

Where a manual process breaks, stage by stage

The failure is never the whole process at once. It is one specific handover, repeated five times.

• Entries arrive. Duplicates and late email submissions sit outside whatever system you have, so the entry count is never quite right until someone reconciles it by hand.
• Collating and checking. Two files share a name, and nobody is certain which version the panel is supposed to judge.
• Distribution to judges. Once the packs leave your inbox you have no view of who has started, so chasing becomes guesswork and the polite reminders go to people who have already finished.
• Score collection. Judges read the same 1 to 5 scale differently, and one of them scores half a category then goes quiet.
• Agreeing the shortlist. The final numbers exist, but the reasoning behind them does not, so the decision cannot be reconstructed when someone asks.

Five criteria that should decide your shortlist

1. Can it model your judging, or must your judging bend to it?

This decides most outcomes, and it is the thing demos skate over. Bring your own structure to the call and ask for it to be built in front of you: your category list, your stage gates, your rubric with its real weightings.

Then work through the specifics. Can the platform run separate rounds for nomination, shortlisting, final judging and public voting, each with its own form, criteria and permissions? Can panels be assigned automatically by category or tag instead of by hand? Is blind review available, so identifying details are hidden where fairness requires it? Are conflict of interest controls built in, so a judge who works for an entrant never receives that entry? Is there tie-break logic, given that ties happen every year and a rule invented on the night is the rule that gets challenged?

Submit.com awards management software was built around this layer, with multi-round judging, weighted scoring, anonymised review and conflict of interest controls configured without code.

2. The entrant experience, tested on a phone

Most entries are finished under time pressure, often on a phone, often late at night.

So the features that matter are the unglamorous ones: autosave, visible progress, conditional logic so an entrant only sees questions relevant to their category, and support for whatever files the programme needs, including video and image portfolios. A long form without autosave is the clearest single cause of abandoned entries.

If your programme is run by a council, an NHS trust, a university or another public sector body, accessibility is a legal duty rather than a preference. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require public sector websites and mobile applications to meet the WCAG 2.2 AA standard and to publish an accessibility statement (source: GOV.UK, Understanding accessibility requirements for public sector bodies). An entry portal you put your logo on counts. Ask any vendor for their accessibility conformance report and their statement, and treat vague reassurance as a no.

3. Would the audit trail survive a challenge?

Every programme eventually takes a call from an entrant who wants to know why they did not make the shortlist. Sometimes the caller is a sponsor.

The test is whether you can reconstruct the decision months later without relying on anyone’s memory. That needs a record of every score and comment with its author and timestamp, every status change, every declared conflict, and who had access to what. Spreadsheets fail this test quietly. The file shows you the final numbers, not how they were reached.

4. UK data protection duties stay with you

Entry forms collect names, contact details, employment information and sometimes commercially sensitive material. Under the UK GDPR your organisation is the controller of that data, whichever platform holds it.

Two principles do most of the work. Data minimisation requires personal data to be, in the wording of the principle, “adequate, relevant and limited to what is necessary” for the purpose you are processing it for, which is a good reason to cut the three questions nobody actually scores (source: ICO, Principle (c): Data minimisation). Storage limitation means you must not keep personal data for longer than you need it, so the platform has to delete on a schedule you can justify rather than quietly accumulate a decade of entries (source: ICO, Principle (e): Storage limitation).

The platform is where both principles are actually enforced, or quietly ignored, which is why the hosting, retention and access questions belong in your requirements document rather than in an email sent a fortnight after go-live.

5. Reporting on the day the shortlist lands

Reporting is usually last on the buyer’s list and first on the marketing team’s.

What programme teams actually need is narrow: entries by category over time, judging progress per panel so you know who to chase, score distributions that reveal a panel marking harder than the rest, and a clean shortlist and winner export within the hour of sign-off. If producing the sponsor report still takes a day of copy and paste, the platform has not replaced your spreadsheet. It has been added to it.

What a multi-round programme actually looks like

If you have only ever run a single round, the structure worth planning for is a sequence of gates, each narrowing the field on a different basis.

1. Nominations. Entries come in and are checked against eligibility rules before any judging starts, so panels never spend an evening scoring entries that were never eligible.
2. Shortlisting. A wider group scores against the rubric to produce a manageable shortlist in each category. Scoring at this stage is usually lighter, with fewer criteria and a shorter comment box.
3. Final judging. A smaller panel applies the full weighted rubric to the shortlist, with the tie-break rule agreed in advance rather than invented on the night.

Where a programme uses public voting, it normally runs alongside or after the final round and carries its own weighting rather than replacing the panel’s judgement. Results, reports and entrant notifications follow from whichever combination you settle on.

Four things should hold at every stage rather than only the last one: blind review where fairness requires it, automatic exclusion of any judge with a declared conflict, panels allocated by the system according to category or tag, and an audit trail of scores and comments. Each round carries its own criteria, scoring and permissions, which is precisely the flexibility a spreadsheet cannot give you.

Four kinds of platform, and who each one suits

Set the vendor names aside and the market divides into four archetypes. Working out which archetype fits your programme narrows the shortlist faster than any feature comparison, because it rules out whole categories of product in one decision.

Swipe left or right to see the full table on mobile.

There is no prize for buying more capability than your programme needs. There is a real cost, paid in reputation, for buying less.

Put the compliance questions in the requirements document

Accessibility and data protection duties are not things to discover at contract stage. Whether you are running a formal tender or a straight comparison of two vendors, put these in writing before the first demo, because the answers will remove at least one option from your list.

• The accessibility standard the entry portal must meet, plus a request for the vendor’s conformance report and published accessibility statement.
• Where entrant data is hosted, and which subprocessors touch it.
• Whether retention periods can be set per programme, and what actually happens to entries when a period expires.
• How subject access requests are handled, and how quickly the vendor commits to responding.
• Which access roles exist, and whether a judge can be prevented from seeing entries outside their own category.
• What the audit log records, how long it is retained, and whether you can export it yourself.

If your awards sit inside a wider organisation, the information security review will arrive whether you plan for it or not. Role-based permissions, encryption, multi-factor authentication and audit logging are the usual asks, and Submit.com documents its position on all of them on the security and compliance page.

Questions worth asking on the demo

Send these ahead so the demo is built around your programme instead of the vendor’s sample data.

• Build three of my categories and two judging rounds, live, on this call.
• How does a panel get assigned to a category, and can a judge with a declared conflict be excluded automatically?
• Show me the full audit record for one entry, including score history and who accessed it.
• What happens when a judge scores half a category and stops replying?
• How do we break a tie, and where is that rule recorded?
• Show me the shortlist export a sponsor would actually receive.
• How long from signature to a live entry form, and who does the configuration work?

Timing the switch around your programme calendar

Almost nobody changes platform mid-cycle, and they are right not to.

The window that works is the few weeks after results, when last year’s structure is still fresh and next year’s launch is not yet urgent. The worst window is a month before entries open. Bring four things to implementation: last year’s entry form, a settled category list, the scoring rubric with its weightings, and the judge list with categories and known conflicts. Teams who arrive with those four launch quickly. Teams still arguing about categories during configuration do not.

For a fuller walk through of selection and implementation, read our guide to choosing the right awards management software.

Frequently asked questions

What is awards management software?

Awards management software is a system for collecting entries, organising them by category, running structured judging across one or more rounds, communicating with entrants and judges, and reporting on outcomes. It differs from a form builder, which collects entries but cannot evaluate them.

Can awards management software handle multi-round judging?

Yes. A purpose-built platform lets you configure separate rounds for nomination, shortlisting, final judging and public voting, each with its own forms, criteria, scoring and permissions. Submit.com awards management software supports multi-round judging with weighted scoring, anonymised review and conflict of interest controls, configured without code.

Do UK awards programmes need to meet accessibility rules?

If the programme is run by a public sector body such as a council, an NHS trust or a university, yes. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require public sector websites and mobile applications to meet the WCAG 2.2 AA standard and to publish an accessibility statement. An entry portal counts.

Is a dedicated platform worth it for a single awards programme?

It depends on judging complexity rather than entry volume. A single category judged once by three people can be run on a form builder and a spreadsheet. Two rounds, several categories, or a panel of more than a handful of judges is where manual processes start producing inconsistent scores and weak audit trails.

Can entry fees be collected through the platform?

Yes. Submit.com supports integrated payment processing, so entry fees can be collected alongside the submission rather than reconciled separately in a spreadsheet.

How long does it take to set up an awards programme?

It depends on how settled your structure is. Teams that arrive with last year’s entry form, a final category list, a scoring rubric with weightings and a judge list can go live quickly, and Submit.com awards programmes are typically launched in days rather than months. Teams still deciding their categories during configuration take longer.