The entry form decides: seven UX rules for your award entry platform

Why incomplete entries are a form problem, not an entrant problem

Nobody assembles a project dossier, chases sign-off from management, marketing and legal, pays an entry fee — then deliberately submits it half-finished. When entries arrive with holes, the cause is rarely carelessness; it is a design fault in the form.

That is not politeness but a diagnostic rule. Individual mistakes scatter at random; form faults cluster in the same place across many people. If twelve dossiers leave "project budget" empty or fill it with "see attachment", that is a finding, not a coincidence.

Three failure patterns:

• Drop-off before the first field. Terms, fee and required material are nowhere to be seen, so the tab closes before anything is typed.
• Drop-off midway. No draft mode, a failed upload, or a required field whose answer nobody has to hand right now.
• Submitted but hollow. The form demanded an answer before a sensible one was possible. Result: "n/a", "to follow", "see attachment".

The third pattern is the expensive one because it is invisible: the completion rate looks healthy while the jury's material stays thin.

Where an award entry platform loses entries

Entries are lost at four points, visible in any back office.

Rule 1: Draft mode is basic equipment, not a luxury

An award entry is not a contact form. It takes shape over days, across several devices and authors. Without a draft mode everyone writes in Word first and pastes at the end, formatting problems included.

A draft mode earns its name once it saves automatically, shows when it last saved, reopens from a link in the confirmation email and keeps "draft" separate from "submitted". One that lives only in browser storage survives neither a change of device nor the colleague writing the section on impact.

Rule 2: Every field has to earn its place

Test each field with one question: which decision does this answer change? Three answers are legitimate — the jury needs it to score, the organising team for invoicing, category or ceremony, or the law requires it. Everything else is marketing curiosity and belongs after submission.

A reliable blueprint is one text field per scoring criterion, in the same order and wording as the jury scoring sheet. The jury then reads exactly what it is asked to judge. Give every text field a character limit and a live counter; a limit is not an obstacle but an honest statement of how much work you are asking for.

Rule 3: Validate required fields at the right moment

The most common mistake is a form that blocks while people are still writing. Nobody works linearly: they start with the easy section and fetch the finance figure two days later. A required field that prevents moving on produces exactly the placeholders you do not want to read.

What works is a staged approach. Nothing blocks in draft; each section carries a completeness indicator; the hard check runs only on submit — and then with the field name, the reason and a jump link, not a red banner atop a forty-field page. Publish the question set as a downloadable document so entrants can prepare offline.

Rule 4: Uploads are the hardest failure point

Uploads fail more often than anything else, and for the same reasons. Formats, size ceiling and file count appear in the error message instead of beside the button. A failed upload takes the typed text with it. Progress is invisible, so people cancel after forty seconds and start again.

Four fixes help immediately: state limits and permitted formats beside the field; store the upload independently of the rest of the form; show uploaded files with name, size and ideally a preview; rename files server-side so the jury never opens "final_final_v3.pdf". For video a link field is pragmatic, with the drawback that links expire.

Rule 5: Mobile is not an edge case

The link arrives by newsletter or from LinkedIn, so the first visit happens on a phone; the writing happens later at a desk. That is why the cross-device draft from Rule 1 is the real mobile strategy. On a phone people need to understand the award, read the terms, start a draft and check status — almost nobody types a full dossier there.

Beyond that the usual craft applies: correct keyboard types, thumb-sized controls, no tables running off the side, upload from the photo library. Plus one test more honest than any simulator — fill the form in once on a real phone on mobile data.

Rule 6: Settle eligibility and cost before the effort

A rejection on formal grounds after three hours of work does lasting damage; three to five filter questions at the start prevent it. In German-speaking Europe most awards are run by trade associations, chambers of commerce and trade publishers, where membership or region often decides eligibility. If the answer is no, point to a category that fits. The same goes for money: the current fee and the next deadline belong in the form, not in a PDF call for entries. Staging those phases is covered in the award season timeline.

Rule 7: The experience does not end at submit

Confirmation belongs on screen and in an email, with an entry number, the category and the files received. Add two sentences on editing: open until the closing date, locked afterwards so every juror scores the same version. At the upload, say who sees the data and how long it is kept — part of accountability under the GDPR, covered in the article on data protection in award entries.

What an award entry platform takes off your plate — and what it does not

Seven rules, none of which strictly requires new software. Draft mode, staged validation and reliable uploads are, however, where generic form tools stop: they know nothing about entry numbers, pricing phases or jury access.

Laureo covers that part — form builder, categories and criteria, draft mode for entrants, eligibility check, pricing phases with Stripe payment at zero commission and automatic PDF invoices, from € 1,790 net per award season. One caveat: a form builder makes it easy to add too many fields, and deciding which question to ask stays editorial work. The rest is in the feature overview.

Patterns described here come from running the HR Award (HR Inside Summit), July 2026. Laureo is a product of State of Innovation GmbH, Vienna.

Related reading