The quality of the entries you receive depends almost entirely on the quality of the questions you ask, which isn’t an obvious thing to believe, because most organisers assume that good work produces good entries and that a weak entry means an entrant who couldn’t be bothered. In practice, entry quality tracks question design far more closely than it tracks the achievements being described, so the strongest piece of work in your program can arrive as an unscoreable entry simply because nobody asked the right thing.
The failure modes are fairly consistent. Vague questions produce vague answers, compound questions produce partial answers, questions that don’t line up with your judging criteria produce answers your judges can’t use, and questions with no guidance attached produce responses so varied that comparing them fairly becomes almost impossible.
Well-designed questions fix all four at the source, because they point entrants towards the information judges need and they do it in a format judges can assess consistently. The real prize is that they narrow the gap between strong work and strong entries, by making clarity the easiest thing for an entrant to produce rather than something they have to reach for.
On this page
- Why question design matters more than you’d think
- The most common question design mistakes
- The principles of effective question design
- Building your form around the CARE framework
- Writing questions for specific purposes
- Setting word limits that work
- Supporting materials, and what to ask for
- Guidance that helps without hemming entrants in
- Testing your questions before launch
- Aligning your entry form with your judging
Why question design matters more than you’d think
Most programs put real effort into the judging end of things, recruiting a qualified panel, designing a scoring rubric and running a calibration session, and comparatively little into the questions, even though the questions determine what the panel will actually have in front of them.
Judges can only assess what they’re given, so if the entries don’t contain what they need, no amount of rigour further down the line will make up for it. The evaluation is limited by the submission, and the submission is shaped by the question.
Think about what happens with something like “tell us about your achievements”. Some entrants will write a comprehensive narrative covering everything they’ve done in three years, others will focus narrowly on a single highlight, some will fill the box with metrics and others will offer only qualitative description. Your judges are now holding submissions that differ not just in quality but in kind, and comparing them means working out what each entrant chose to include and why they chose it, which is guesswork dressed up as evaluation.
Now take a specific version: “what measurable outcomes did this project achieve? Include specific metrics and the timeframe over which they were measured.” Entrants know exactly what to provide, responses become comparable because everybody is answering the same question in much the same shape, and judges can spend their time evaluating substance instead of extracting it.
The most common question design mistakes
Five patterns account for most of the damage, and they turn up in programs of every size, so it’s worth checking your current form against them before you write anything new.
Compound questions that ask for several things at once
When you bundle multiple requests into one prompt, entrants answer the part they’re most comfortable with and skim the rest, which means you reliably get an incomplete response rather than a shorter complete one.
Problematic: “Describe your project, explain what made it innovative, and outline the results you achieved.”
That’s three distinct questions wearing a single coat, and most entrants will develop one or two of them properly while shortchanging whatever’s left. Split it into three questions with a word limit on each, and you’ll get all three answered.
Open-ended prompts that invite rambling
Questions such as “tell us why you should win” or “describe your success” hand the entire job of structuring an answer to the entrant, and because entrants have no idea what you’re weighting, the responses come back varying wildly in focus, length and relevance. Open questions feel generous, but the inconsistency they produce hurts entrants as much as it hurts judges.
Questions that don’t line up with your criteria
If your entry form and your scoring sheet were written by different people at different times, entrants will supply information judges don’t need while missing what they do. Where judges are scoring innovation, impact and execution, your form should ask about each of those by name, because entrants shouldn’t have to guess which paragraph of a general narrative will be read against which criterion.
Word limits so generous they encourage padding
A long word limit looks accommodating and usually isn’t, because when someone has a thousand words for a question that needs two hundred, they fill the gap with repetition and promotional language, and the genuinely useful sentences end up buried somewhere in the middle. Tighter constraints force entrants to decide what matters most, which is exactly the decision you want to see them make.
No explanation of why the question is being asked
When entrants don’t know what a question is assessing or how the answer will be scored, they guess, and some of them guess correctly while others don’t, which adds noise to your results for no good reason. A sentence of guidance under each question removes most of that variation.
The principles of effective question design
Good questions tend to share four characteristics, and they’re easier to apply as a checklist than as a philosophy.
One question, one concept
Ask for one thing at a time, and where you need several pieces of information, use several questions, because a combined question always produces a partial answer.
Splitting questions also makes your word limits mean something, since you can give 150 words to context and 200 to results and be confident each gets the depth it needs, rather than letting entrants distribute a single large allowance however they like.
Specific prompts rather than open invitations
The more precisely you define what you want, the more comparable the responses become.
General
“Describe your achievements.”
Specific
“What measurable outcomes did this initiative achieve? Include specific metrics, the timeframe over which they were measured, and how they compare to your starting point or to relevant benchmarks.”
The specific version tells entrants exactly what belongs in the box, and because everyone then supplies the same types of information, the responses can be set side by side and read against each other.
Direct alignment with your judging criteria
Every criterion should have at least one question feeding it, so that judges have what they need to score it without interpretation. If innovation is scored on a five-point scale then ask about innovation explicitly, and if impact carries 35% of the weighting then your form should devote roughly proportionate space to gathering impact evidence.
This alignment serves everybody at once, because entrants learn what matters, judges receive what they need, and the final scores reflect what was actually submitted rather than how skilfully each judge mined a general narrative for relevant material.
Constraints that force prioritisation
Word limits, format requirements and structural guidance all improve quality, because they make entrants choose, they prevent padding, and they keep the reading load manageable for your panel.
Set each limit according to how much you genuinely need rather than how much you think entrants would like. A context question might need 100 to 150 words while a results question might need 150 to 250, and the right limit feels tight without feeling impossible β challenging enough to force focus, generous enough to allow substance.
Building your form around the CARE framework
“CARE” stands for context, action, results, evidence. It gives you a reliable structure for an entry form, because it walks a judge through the same sequence they’d follow if they were interviewing the entrant, and it makes sure nothing essential gets left out on the way.
Context: what was the situation?
Judges need the starting point in order to evaluate the finish, since without it an achievement floats free of any scale and there’s no way to tell whether the outcome was remarkable or simply expected.
- The challenge, problem or opportunity being addressed
- Constraints or conditions that shaped the work
- Why it mattered to the organisation or its stakeholders
What challenge or opportunity did this project address? Include relevant context about the situation before this work began. (100β150 words)
Action: what did you do?
This is where entrants explain their approach and the decisions behind it, and the emphasis should sit firmly on what this entrant contributed rather than on industry background or general trends, which is a place a lot of entries lose their way.
- The specific approach or methodology used
- Key decisions, and the reasoning behind them
- What set this approach apart from the alternatives
Describe the approach you took to address this challenge. Focus on specific decisions, strategies or innovations rather than general activities. (150β200 words)
Results: what happened?
Outcomes usually carry the heaviest weighting in judging, so this question has to work harder than the others and should be written to elicit specific, measurable information rather than a general declaration of success.
- Specific metrics, and how they changed
- The timeframe over which the results were achieved
- Comparison points that give the numbers meaning
What measurable outcomes did this work achieve? Include specific metrics, timeframes and comparison points, such as before and after, against target, or against benchmark. (150β250 words)
Evidence: how can you prove it?
The evidence question is what separates a substantiated achievement from an assertion, and it works best as a separate field rather than as a clause tacked onto the results question, because otherwise it gets absorbed into the narrative and disappears.
- Data sources and methodology behind the metrics cited
- Third-party validation or independent recognition
- Supporting documentation the entrant can provide
What evidence supports these results? This might include the methodology behind any metrics cited, as well as third-party validation, customer testimonials or other documentation. (100β150 words, or a supporting document upload)
Writing questions for specific purposes
Some subjects go wrong in predictable ways, and in each case the fix is the same move: replace the general noun with a specific request.
| Asking about | Don’t ask | Ask instead |
|---|---|---|
| Innovation | “Describe what makes this work innovative.” | “What is novel about this approach compared to existing alternatives? Explain what you did differently and why it represents an advance on established practice.” |
| Impact | “Describe the impact of this work.” | “What measurable changes resulted from this work? Include specific metrics with timeframes, and explain how they compare to your starting point or to relevant benchmarks.” |
| Challenges | “What challenges did you face?” | “Describe a significant obstacle you encountered and how you addressed it. Focus on your specific response and what it reveals about your approach.” |
| Leadership | “Describe your leadership of this initiative.” | “What specific decisions did you personally make, and what outcomes resulted directly from your involvement? Distinguish your individual contribution from broader team efforts.” |
A few of these deserve a note. Innovation is the most frequently misjudged criterion of the four, because the word means genuinely different things to different people, and a vague prompt will bring you responses ranging from something nobody has attempted before to a conventional project executed well β so if the category depends on it, consider breaking innovation into components and asking about each separately: novelty of approach, application to a new context, and improvement on the alternatives.
The challenges question is deliberately singular, because asking for one significant obstacle rather than a list gives you a fuller answer in fewer words, and you learn more from how somebody handled a single hard problem than from a summary of five.
The leadership question reverses for team awards. Where the individual version pushes an entrant to separate their contribution from the group’s, a team award needs questions that capture collective achievement, so watch that a form built for individual categories doesn’t get reused unchanged.
Setting word limits that work
Word limits shape entries more than most organisers realise. Set them too high and responses turn padded and unfocused, set them too low and entrants can’t give you enough to score, whereas the right limit forces clarity while still leaving room for substance.
| Question type | Suggested limit | Why |
|---|---|---|
| Context and background | 100β150 words | Enough for the essential framing, not so much that the setup dominates the entry |
| Approach and methodology | 150β200 words | Room for a meaningful explanation without inviting exhaustive detail |
| Results and outcomes | 150β250 words | Usually the highest-weighted element, so it earns the most space |
| Evidence and support | 100β150 words | Often better replaced or supplemented by a document upload |
| Overall statement | 200β300 words | Only if you include one, and keep it tightly focused |
For most categories, somewhere between 600 and 1,000 words across the whole form is plenty, because that forces entrants to prioritise and keeps the judging workload sane. A complex or technical category might stretch to 1,200 or 1,500, but if you find yourself needing more than that, it usually means two or three of your questions want consolidating rather than that the subject genuinely requires the space.
Whatever you settle on, display the limit next to each question, and show a live word count if you can, because entrants who know exactly how much room they have will use it far more deliberately than entrants who are guessing.
Supporting materials, and what to ask for
Written answers only tell part of the story, and documents, images, data and testimonials can add evidence and credibility that prose can’t carry on its own. Badly managed, though, supporting materials create confusion for entrants and a reading burden for judges that nobody signed up for, so the guiding question is simple: will a judge actually look at this?
If your panel has twenty entries to get through, they aren’t going to watch a five-minute video for each one, which means anything that takes real time to consume needs to justify itself or be made optional.
Worth requesting
Summary data or metrics in an accessible format
Images or visuals, for creative or physical work
Brief testimonials or quotes, rather than long documents
Before-and-after comparisons
Third-party validation or recognition
Avoid, or make optional
Lengthy reports judges won’t have time to read
Extensive video content
Documentation that simply repeats the written answers
Raw data with no interpretation attached
Anything mandatory that most entries won’t benefit from
Be specific about the format as well as the content, because ambiguity here produces exactly the inconsistency you were trying to avoid in the written answers.
Upload up to three images showing your work. Accepted formats: JPG, PNG. Maximum 5MB per file. Include a brief caption explaining what each image shows.
Finally, be clear about what’s required and what’s merely welcome, and make sure anything you mark as required is genuinely necessary for a complete submission, since a mandatory upload that most entrants have nothing to put in is just a barrier.
Guidance that helps without hemming entrants in
Entrants perform better when they understand what you’re looking for, and a sentence or two beneath each question closes most of the gap between what you need and what they’d otherwise assume you want.
Question: What measurable outcomes did this project achieve?
Guidance: Judges will evaluate both the significance of the outcomes and the quality of the evidence provided. Include specific metrics with timeframes and comparison points where possible.
Keep it short, because guidance that runs to a paragraph starts to feel like an exam rubric and begins to flatten the entrant’s own voice. Lines such as “this question is heavily weighted in judging, so be specific about outcomes” or “focus on measurable results rather than activities or intentions” do the job in a dozen words.
Anything longer belongs outside the form, in a set of pre-entry resources entrants can read before they start:
- Category definitions, clarifying what belongs where
- Eligibility requirements, stated explicitly
- Judging criteria, with their weightings
- Tips for a strong submission
- Sample or anonymised example entries, if you have any you can share
- An FAQ covering the questions you get asked every year
Testing your questions before launch
Questions that read perfectly clearly to the person who wrote them routinely confuse the people who have to answer them, and you’d much rather discover that now than after two hundred entries have come in. Four quick tests will find most of the problems.
The colleague test
Give the form to somebody who knows nothing about the program and ask them to explain what each question is asking for and what a good answer would contain. Wherever their reading differs from your intention, the question needs work.
The response test
Have two or three people complete the form for real or imagined work, then compare what comes back. Where the responses diverge sharply in structure or content, the question was ambiguous rather than the entrants inconsistent.
The judge’s-eye test
Read those sample responses as though you were scoring them. Does each one give you what you need for your criteria, and are they comparable to each other? If not, you’ve found the questions to rewrite.
The feedback loop
After judging, ask your panel about entry quality. Complaints such as “entries didn’t address the criteria” or “I couldn’t find the information I needed” are question design problems wearing a judging costume.
Aligning your entry form with your judging
Your entry structure should mirror your judging structure, because when the two match, scoring becomes almost mechanical, whereas when they don’t, every judge has to translate between what was submitted and what they’re being asked to assess β and no two judges translate the same way.
Work through each criterion and identify which question or questions will supply the information needed to score it. Every criterion should have clear coverage, and no question should survive that isn’t connected to something you’re evaluating.
| Criterion | Weight | Entry question |
|---|---|---|
| Innovation | 25% | “What is novel about this approach?” |
| Impact | 35% | “What measurable outcomes did this work achieve?” |
| Execution | 25% | “Describe your approach and how you addressed challenges” |
| Evidence quality | 15% | “What evidence supports these results?” plus supporting materials |
Depth should follow weight, so if impact carries 35% of the score then the form should give roughly proportionate attention to capturing impact evidence, which might mean more words, or an extra question, or both.
Try to keep the same core structure across categories as well, because it helps the judges who assess several categories and it helps the entrants who submit to several. Category-specific questions can vary as much as they need to, as long as the underlying shape stays stable.
The ripple effect of better questions
Better questions produce clearer entries, clearer entries make judging faster and more consistent, consistent judging produces outcomes you can explain, and outcomes you can explain are what give a program its credibility. The chain runs in one direction, and it starts at the form.
What makes this worth doing is the return. A few hours spent refining your questions can save dozens of hours of judging and head off the disputes that would otherwise eat your attention for a fortnight after the results go out.
Strong programs don’t hope for great entries. They design questions that make great entries the natural thing for an entrant to produce.
Frequently Asked Questions
The quality of award entries is largely determined by the quality of the questions entrants are asked. Clear, focused questions guide entrants to provide the information judges need, while vague or poorly structured questions often result in inconsistent, incomplete, or difficult-to-evaluate submissions.
Well-designed questions improve fairness by making responses more comparable and ensuring judges assess achievements based on relevant evidence rather than writing style alone.
Many award programs unintentionally make it harder for entrants by asking compound questions, using vague prompts, misaligning questions with judging criteria, setting excessive word limits, or providing little guidance.
These issues often lead to incomplete answers, inconsistent submissions, and additional work for judges who must interpret missing or unclear information instead of evaluating evidence directly.
Single-purpose questions produce clearer and more complete answers because entrants know exactly what information is being requested. When several requests are combined into one question, people often answer only the parts they find easiest, leaving important information out.
Separating topics such as context, innovation, and results also allows organisers to assign appropriate word limits and makes judging more consistent.
Every judging criterion should have a corresponding question that gathers the evidence judges need to score that criterion. For example, if innovation, impact, execution, and evidence are scored separately, the entry form should include dedicated questions for each area.
This alignment helps entrants understand what matters most and ensures judges can evaluate submissions consistently without searching through unrelated content.
The CARE framework structures entry questions around four essential elements:
Context: What challenge or opportunity existed?
Action: What specific approach was taken?
Results: What measurable outcomes were achieved?
Evidence: What proof supports those results?
Using this framework ensures entrants provide complete, well-organised information while giving judges a consistent basis for evaluation.
Rather than asking entrants to simply describe what was innovative, stronger questions ask what was genuinely novel compared with existing alternatives and why the approach represented an improvement.
This encourages entrants to explain the originality of their work with specific examples instead of relying on subjective claims that something was "innovative."
Word limits should be based on the amount of information judges genuinely need rather than giving entrants as much space as possible. Short, focused limits encourage clarity, while overly generous limits often result in repetitive or promotional writing.
Typically, context requires fewer words than results, allowing the entry form to emphasise the areas that carry the greatest judging weight.
Testing entry questions with colleagues, sample entrants, or judges helps identify confusing wording, ambiguous prompts, and inconsistencies before submissions open. Even questions that seem clear to organisers may be interpreted differently by entrants.
Reviewing trial responses also highlights whether the questions collect the evidence judges need and whether answers are comparable enough to support fair and consistent evaluation.