Common mistakes that sink a strong nominee
The best person in the room often writes the weakest entry. Here is why that happens, and what a judging panel needs to see instead.
Have you ever watched a brilliant defender lose to a weaker one, simply because the weaker one had a better-written entry? It happens every cycle, in every category. A panel can only judge what reaches the page. When a strong nominee submits a thin or unfocused entry, the panel has nothing to reward, and the work goes unseen.
The good news is that almost every fault is fixable before the deadline. The patterns repeat, which means you can spot them in your own draft. What follows is drawn from years of reading entries against published criteria, and from the gap that opens, again and again, between what a person did and what they wrote down.
None of this is about polish. A judge reading evidence does not care about adjectives. They care about whether the claim in front of them is specific, true, and tied to an outcome they can weigh.
Writing about the team when the award names a person
The most common mistake is scope. An individual award asks what one person did. A great many entries answer with what the team did, the department achieved, or the organisation now claims. The panel reads three paragraphs of collective progress and cannot find the nominee inside it.
This usually comes from modesty, which is a fine instinct in a person and a fatal one in an entry. If you led the response, say you led it. If you wrote the detection that caught the intrusion, say you wrote it. The reverse fails too. An organisation or team award filled with one founder's personal story leaves the panel unsure who is actually being recognised. Match the subject of your sentences to the subject of the category. Read the category definitions before you write a word, because the 2026 programme separates five individual awards from five organisation awards, and the evidence each one needs is different.
A useful test: count how many sentences in your entry have the nominee as the active subject. If the answer is two or three, the panel will struggle to score a person they can barely see.
Claiming impact without the evidence to carry it
The second pattern is the unsupported claim. Entries say a nominee improved security, raised resilience, or transformed a programme. Those are conclusions, not evidence, and a panel cannot award a conclusion. The work that earns recognition is specific. A responder who shortened dwell time on a live intrusion. A researcher who disclosed a flaw responsibly and waited for the patch before taking any credit. A leader who rebuilt a function after a hard year and kept the people through it.
Reach for verifiable detail. What changed, by when, and how you know. If you can attribute a wider trend to a real source, do so plainly. Bodies such as the Verizon DBIR, ENISA, and the NCSC publish defensible findings on dwell time, incident patterns, and the cost of delay, and a judge respects an entry that grounds its context in real work rather than invented numbers. Do not manufacture a precise statistic to look rigorous. A panel that catches one fabricated figure will distrust the whole entry, and rightly so.
Quiet work counts here more than anywhere. A breach that never happened makes no headline, and a team that held together through a bad night gets no press. Name that work in concrete terms, because it is exactly the kind a panel exists to find.
Treating the entry like a marketing exercise
The third mistake is tone. Some entries arrive written for a sales deck, dense with the language of brochures. A judge reads past it quickly, because none of it answers the question on the form. Recognition here is judged on merit. It cannot be bought, and it cannot be talked into existence by volume. The panel is looking for the thing the nominee actually did, not how loudly the entry can say it.
Three smaller faults sit alongside this one. Missing the deadline, which no quality of work can recover. Ignoring the published criteria and writing the entry you wanted to write instead of the one the category asked for. And leaving the entry to the last hour, when a colleague reading it fresh would have caught the gap you could no longer see. Write it early, set it down, and read it once more as a stranger would.
Writing a strong nomination
Why do strong people sometimes write weak entries?
Modesty and scope. Capable defenders tend to credit the team and write in conclusions rather than specifics, which leaves a panel with nothing concrete to score. The fix is to make the nominee the active subject and to give verifiable detail for every claim.
How specific does the evidence need to be?
Specific enough to weigh. State what changed, by when, and how you know. A judge can reward a shortened dwell time or a responsible disclosure that waited for the patch. A judge cannot reward the phrase "improved security".
Can I include statistics to strengthen my entry?
Yes, if they are real and attributed. Cite defensible findings from sources such as the Verizon DBIR, ENISA, or the NCSC for context. Never invent a precise figure. One fabricated number undermines the whole entry.
Does a polished, marketing-style entry help?
No. Recognition here is judged on merit and cannot be bought or talked into existence. The panel reads past brochure language for the work the nominee actually did, so plain, specific writing scores far better.