How to give feedback to award entrants without creating conflict

The Awards Platform - Deciding feedback or silence

Every awards program gets the question: “Why didn’t we win?”. Sometimes it comes politely, a genuine desire to understand and improve for next time. Sometimes it comes defensively,  a challenge to the outcome dressed as an inquiry. Either way, how you respond matters.

Feedback done well builds relationships and strengthens your program’s reputation. Entrants who understand why they fell short often return with stronger submissions. Organisations that feel heard, even when they didn’t win, become advocates rather than critics. And transparency about evaluation, handled carefully, reinforces the credibility that makes your awards worth pursuing.

But feedback done poorly creates conflict. Entrants dispute scores they disagree with. Judges feel exposed when their comments reach people who might respond negatively. Subjective assessments get treated as objective failures that demand correction, and every explanation becomes an opening for negotiation about whether the outcome was right.

The challenge is finding the middle ground, providing enough information to be useful and fair, but not so much that you invite endless debate or undermine judge willingness to participate.

This guide covers how to give feedback effectively: what to share, what to protect, how to frame difficult messages, and how to handle the pushback that sometimes follows.

The case for providing feedback

Before deciding what to share, it’s worth understanding why feedback matters, and to whom.

It helps entrants improve

The most straightforward argument. Entrants who understand what evaluators saw, strengths and weaknesses, can improve their next submission. Feedback transforms rejection from a dead end into a development opportunity.

For entrants genuinely committed to the work your awards recognise, this guidance is valuable. They want to know whether their entry failed to communicate achievements effectively, or whether the achievements themselves didn’t meet the bar.

It demonstrates process legitimacy

Programs that can articulate why entries scored as they did signal that real evaluation occurred. Feedback, even limited feedback, shows that judges engaged seriously with submissions rather than making arbitrary or influenced decisions.

This matters particularly for programs concerned about pay-to-play perception. When entrants see thoughtful assessment, they’re less likely to conclude that outcomes were predetermined.

It builds long-term relationships

How you handle unsuccessful entrants affects whether they return. Organisations that feel dismissed or stonewalled may conclude your program isn’t worth pursuing. Those that receive respectful, useful feedback often enter again, and sometimes win. The entrants you reject this year are potential winners, sponsors, and advocates in future years. Feedback is relationship investment, not just information transfer.

It surfaces program problems

Feedback requests sometimes reveal legitimate issues. If multiple entrants ask the same question, “We don’t understand how we scored lower on impact when our results exceeded the winner’s”, that’s information about how your criteria, communication, or judging might need refinement. Entrant confusion isn’t always entrant misunderstanding. Sometimes it’s program design that needs work.

The case for caution

Feedback also carries risks that justify careful boundaries.

Judges need protection

Judges volunteer expertise and time. They shouldn’t face blowback from entrants unhappy with their scores. Feedback that exposes individual judges, by name or by identifiable comment, can make judges reluctant to provide honest assessment or to participate at all.

Judge willingness is a scarce resource. Protecting it matters more than satisfying every feedback request fully.

Subjective assessment invites dispute

Judging involves professional judgement. Reasonable people can disagree about whether an entry demonstrates “significant innovation” or “strong evidence of impact.” When feedback shares subjective assessments, entrants may argue that the judgement was wrong.

You can explain that judges found evidence of impact insufficient without convincing an entrant who believes their evidence was compelling. The disagreement isn’t resolvable through further discussion, but the discussion may continue anyway.

Detailed feedback creates negotiation openings

Every specific point of feedback becomes something an entrant can challenge. “You said our metrics weren’t clear, but they were in section three” invites a back-and-forth that rarely ends with entrant satisfaction and often consumes administrator time.

The more detail you provide, the more surface area exists for dispute.

Comparison creates problems

Entrants often want to know how they compared to winners or other finalists. This comparison feedback is particularly risky, sharing relative assessments can feel like ranking organisations publicly, and it invites arguments about whether the comparison was fair.

Even if you’re confident in the comparison, sharing it rarely ends well.

Some entrants won’t accept any answer

A subset of feedback requests aren’t genuine inquiries, they’re complaints seeking validation or outcomes seeking reversal. No amount of explanation will satisfy someone who fundamentally disagrees with the result and wants it changed.

Recognising when feedback won’t help, and declining to engage indefinitely, protects program resources and sanity.

What feedback to provide

Given the tension between value and risk, what should programs actually share?

Aggregate scores with criteria breakdown

Sharing overall scores and scores by criterion gives entrants meaningful information without exposing individual judge assessments.

Example: “Your entry scored 3.4 overall (scale of 1–5). By criterion: Innovation 3.8, Impact 3.0, Evidence 3.2, Execution 3.6.”

This tells entrants where they were relatively strong and weak without revealing which judge said what. They can see that impact and evidence were areas for improvement without accessing the specific comments that led to those scores.

General themes rather than specific comments

Summarise feedback themes rather than sharing verbatim judge comments.

Instead of: “Judge 2 wrote: ‘The claimed customer satisfaction figures seem inflated and weren’t supported by methodology explanation.'”

Share: “Judges noted that some metrics would benefit from additional context or supporting methodology to strengthen credibility.”

The theme communicates the concern. The specific comment stays protected.

Criteria-level guidance for improvement

Frame feedback as forward-looking guidance rather than backward-looking criticism.

Example: “For future submissions, consider including third-party validation for performance claims. Judges look for evidence beyond self-reported metrics when evaluating impact.”

This gives entrants actionable direction without requiring them to agree with how their current entry was assessed.

Position relative to field (carefully)

If you provide any comparative context, keep it general.

Acceptable: “Competition in this category was particularly strong this year, with many high-quality entries.”

Risky: “Your entry ranked fifth out of twelve submissions.”

Very risky: “You scored lower than [Winner Company] on innovation because judges felt their approach was more novel.”

General context about field strength is useful. Specific rankings or named comparisons create problems.

What feedback to protect

Some information should stay confidential regardless of entrant requests.

Individual judge identities

Don’t reveal which judges evaluated which entries, or which judge provided which score or comment. Aggregate feedback protects judges while still providing useful information.

If entrants know that “Judge Smith gave us a 2 on innovation,” Judge Smith may face direct contact, professional awkwardness, or reputational implications. This harms judges and makes future recruitment harder.

Verbatim judge comments

Raw judge comments are often written with the expectation of confidentiality. They may be blunt, informal, or reference factors that make sense in evaluation context but could be misinterpreted when shared directly. Summarise themes rather than sharing exact wording.

Deliberation discussions

If judges discussed entries during deliberation, those conversations should remain confidential. Internal discussion, where judges might speculate, change positions, or express uncertainty, isn’t meant for external audiences.

Other entrants’ information

Never share how other entrants scored, what feedback they received, or any information about their submissions. Comparative feedback requests should be declined: “We don’t share information about other entries.”

Close-call details

For entries that just missed finalist selection or nearly won, sharing how close they came can create more frustration than closure. “You were our sixth-ranked entry in a five-finalist category” may feel like useful information, but it often intensifies disappointment and invites arguments about why the line was drawn where it was.

How to frame feedback constructively

How you communicate matters as much as what you communicate. The same information can feel helpful or dismissive depending on framing.

Lead with acknowledgment

Before discussing weaknesses, acknowledge what the entry did well. This isn’t empty praise  it’s accurate recognition that most entries have strengths alongside areas for improvement.

Example: “Judges noted that your entry demonstrated strong execution and clear project management. The areas where your submission could be strengthened were…”

Entrants who feel their work was genuinely considered are more receptive to improvement guidance.

Focus on the submission, not the organisation

Frame feedback as assessment of the entry rather than judgement of the organisation’s overall quality.

Instead of: “Your company’s innovation efforts aren’t as strong as competitors.”

Frame as: “This particular submission didn’t fully demonstrate the innovation criteria judges were evaluating.”

The distinction matters. You’re evaluating a submission, not rendering a verdict on an organisation’s worth.

Use forward-looking language

Position feedback as guidance for future success rather than criticism of past failure.

Instead of: “Your evidence was insufficient.”

Frame as: “Future submissions would be strengthened by including more detailed evidence , particularly third-party validation and methodology explanation for claimed metrics.”

This gives entrants something to do with the feedback rather than something to argue about.

Acknowledge subjectivity where present

When feedback involves judgement calls, acknowledge that reasonable perspectives can differ.

Example: “Judges felt that while your results were solid, the evidence presentation made it difficult to fully assess impact. We recognise that evaluation of evidence sufficiency involves professional judgement, and different evaluators might weigh factors differently.”

This validates that the entrant’s perspective isn’t crazy while maintaining that the judges’ assessment stands.

Be clear about finality

If results aren’t changing, say so clearly and early. Don’t leave space for entrants to believe that enough argument will change outcomes.

Example: “Our judging results are final and aren’t subject to reconsideration. However, we’re happy to share feedback that might help strengthen future submissions.”

This sets boundaries while offering what you can genuinely provide.

Timing and delivery

When and how you provide feedback affects how it’s received.

Don’t provide feedback immediately after results

Emotions run high right after announcements. Entrants who just learned they didn’t win are processing disappointment, and feedback provided in that moment often triggers defensive responses.

Wait at least a few days, ideally a week or two, before engaging in detailed feedback conversations. Let initial reactions settle.

Offer feedback proactively or upon request

Programs take different approaches:

  • Proactive feedback, providing scores and summary comments to all entrants automatically, signals transparency and treats feedback as standard practice rather than something that requires asking.
  • Request-based feedback, providing feedback only when entrants ask, reduces workload and targets feedback toward those who genuinely want it. Either approach works. What matters is that your policy is clear and applied consistently.

Written feedback first

Start with written feedback rather than phone calls. Written communication:

  • Ensures consistent messaging
  • Gives entrants time to process before responding
  • Creates documentation if disputes arise
  • Allows careful framing

If entrants want to discuss further, phone or video conversations can follow , but starting in writing manages the exchange better.

Set expectations about depth

Be clear about what level of feedback you provide.

Example: “We provide aggregate scores by criterion and general themes from evaluation. We don’t share individual judge comments, comparative rankings, or detailed scoring justifications.”

When entrants know what to expect, they’re less likely to push for information you’ve already explained isn’t available.

Handling pushback and disputes

Some feedback conversations turn difficult. Preparation helps.

Acknowledge frustration without conceding

Entrants may express disappointment, disagreement, or frustration. Acknowledge the emotion without agreeing that the outcome was wrong.

Example: “I understand this isn’t the result you hoped for, and I can hear that you’re disappointed. Our judges evaluated all entries against the published criteria, and while I can share feedback on your submission, the results themselves are final.”

This validates feelings while maintaining boundaries.

Don’t re-litigate the evaluation

When entrants argue that judges got it wrong, avoid point-by-point defence of the scoring. You won’t convince them, and the debate has no productive endpoint.

Instead of: “Actually, your evidence wasn’t as strong as you think because…”

Redirect: “I understand you see your evidence differently than judges did. That difference in perspective doesn’t change the evaluation outcome, but I hope the feedback is useful for future consideration.”

Know when to stop

Some entrants will continue pushing regardless of what you say. It’s appropriate to end conversations that aren’t progressing:

Example: “I’ve shared the feedback we’re able to provide, and I understand you disagree with the outcome. Our results are final, and I don’t think further discussion will change either of our perspectives. I wish you well with future entries.”

Polite but firm closure protects your time without being hostile.

Document difficult interactions

If an entrant becomes hostile, threatens public criticism, or makes demands beyond feedback, document the exchange. You may need records if the situation escalates.

Most entrants are reasonable even when disappointed. But for the occasional difficult interaction, documentation matters.

Don’t make exceptions under pressure

If an entrant argues aggressively enough that you’re tempted to share more than your policy allows, individual judge names, comparative rankings, or other protected information, resist. Making exceptions under pressure rewards the behaviour and creates inconsistency.

Apply your policies consistently regardless of entrant intensity.

Building a feedback system

Consistent feedback requires systematic process, not ad hoc responses.

Define your feedback policy in advance

Before judging begins, decide:

  • What information will you share? (Aggregate scores, themes, criteria breakdown?)
  • What will you protect? (Judge identities, verbatim comments, comparisons?)
  • When will you provide feedback? (Proactively? Upon request? After what delay?)
  • Who handles feedback requests?
  • What are the boundaries for difficult conversations?

Written policy ensures consistent application and makes individual conversations easier, you’re following established process, not making it up as you go.

Prepare template language

Create templates for common feedback scenarios:

  • Standard feedback for non-finalists
  • Standard feedback for finalists who didn’t win
  • Response to requests for information you don’t share
  • Response to disputes or complaints

Templates ensure consistency and reduce the energy required for each feedback conversation.

Aggregate judge comments during judging

If you want to share thematic feedback, you need to capture it. Build judge comment collection into your evaluation process:

  • Require judges to provide written reasoning for scores
  • Ask judges to note key strengths and areas for improvement
  • Summarise themes across judges during results processing

Trying to reconstruct feedback after judging is difficult. Build it into the workflow.

Track feedback interactions

Record which entrants received what feedback and any follow-up conversations. This:

  • Ensures consistency if entrants contact you again
  • Identifies entrants who may need careful handling
  • Reveals patterns (multiple entrants confused about the same issue)
  • Protects you if disputes escalate

Simple tracking , even a spreadsheet, is better than relying on memory.

Checklist

Feedback that helps without creating conflict

Policy definition

[  ] Feedback scope defined (what you share, what you protect)
[  ] Timing established (proactive vs. request-based, delay after results)
[  ] Responsibility assigned (who handles feedback requests)
[  ] Boundaries documented (when to decline or end conversations)

Information preparation

[  ] Aggregate scores compiled for sharing
[  ] Judge comments summarised into themes
[  ] Template language prepared for common scenarios
[  ] Forward-looking improvement guidance drafted

Framing

[  ] Feedback acknowledges entry strengths before weaknesses
[  ] Language focuses on submission, not organisation
[  ] Tone is forward-looking, not backward-critical
[  ] Subjectivity acknowledged where present
[  ] Finality of results stated clearly

Delivery

[  ] Appropriate delay after results before feedback
[  ] Written communication as initial channel
[  ] Expectations set about feedback depth
[  ] Documentation maintained for interactions

Difficult situations

[  ] Approach defined for handling pushback
[  ] Closure language prepared for unproductive conversations
[  ] Exception policy confirmed (don’t make them)
[  ] Escalation path identified if needed

Conclusion

Feedback done well builds relationships, entrants who understand why they fell short often return with stronger submissions, and organisations that feel heard become advocates rather than critics. But feedback done poorly creates conflict that consumes time and damages credibility. The balance lies in sharing enough to be useful without inviting endless debate. Provide aggregate scores with criteria breakdowns so entrants can see where they were strong and weak. Summarise judge comments into themes rather than sharing verbatim remarks. Frame everything as forward-looking guidance for future submissions rather than backward-looking criticism of past failures. And protect what needs protecting: individual judge identities, specific comments written with confidentiality expected, deliberation discussions, comparative rankings, and information about other entrants. When you do share feedback, lead with acknowledgment of what the entry did well, focus on the submission rather than the organisation’s overall worth, and be clear early that results are final.

Build a systematic approach rather than handling each request ad hoc. Define your feedback policy before judging begins, what you’ll share, what you’ll protect, when you’ll provide it, and who handles requests. Prepare template language for common scenarios so you’re not crafting responses from scratch under pressure. Capture judge reasoning during evaluation so you have thematic feedback to draw on later. And when pushback comes, because it will, acknowledge frustration without conceding that outcomes were wrong, avoid re-litigating the evaluation point by point, and know when to end conversations that aren’t progressing. Apply your policies consistently regardless of how aggressively an entrant argues, because making exceptions under pressure rewards the behaviour and creates inconsistency. Most entrants are reasonable even when disappointed, and the ones who receive respectful, useful feedback often become your strongest future participants.

Related reading:

→ How to write judging criteria that judges can actually use
→ What to do when judges disagree on scores
→ Managing conflicts of interest in awards judging
→ Judging & Scoring Best Practices

Frequently Asked Questions

The safest approach is to share aggregate scores and high-level themes tied to your published criteria, while clearly stating that results are final. For example, provide overall and criterion-level scores, along with summary observations such as where the submission was strong and where it could be strengthened.

Avoid debating the merits of the outcome or defending individual scoring decisions. Frame the conversation as forward-looking guidance for future submissions rather than a re-evaluation of past results. This gives entrants clarity without opening negotiation over the decision.

No. Verbatim judge comments and individual judge identities should remain confidential. Judges provide candid assessments with the expectation that their feedback won’t be attributed or exposed, and sharing it can discourage honest evaluation or future participation.

Instead, summarise recurring themes across judges. For example, convert detailed remarks into neutral, criteria-based summaries such as: “Judges noted that additional third-party validation would strengthen impact claims.” This preserves usefulness while protecting judges.

The most useful feedback combines:

- Aggregate scores by criterion
- Clear identification of relative strengths and weaknesses
- Forward-looking suggestions for improvement

Entrants benefit most from understanding where they fell short (e.g., impact evidence scored lower than innovation) and how to improve (e.g., include methodology explanation or independent validation). Feedback that focuses on actionable improvements is more constructive than explanations about why another entry performed better.

Set boundaries early and clearly. State that judging outcomes are final and that feedback is offered to support future submissions, not to reconsider decisions. This reduces the expectation that argument or additional explanation could change the outcome.

If entrants challenge specific scoring points, avoid re-litigating the evaluation. Acknowledge that reasonable perspectives can differ, but reinforce that the published criteria were applied consistently across all entries and that the decision stands.

Generally, no. Sharing exact rankings, “close call” details, or how many points separated them from finalists often increases frustration rather than providing closure. It can invite arguments about where the cutoff was drawn or why a marginal difference mattered.

If providing context, keep it general, such as noting that competition in the category was particularly strong, without revealing comparative rankings or specific positions relative to other entrants.

Avoid providing detailed feedback immediately after results are announced. Emotions are typically highest at that moment, and feedback given too soon may trigger defensive reactions.

Waiting several days or ideally one to two weeks, allows entrants time to process disappointment. Written feedback as the first step is usually more effective, as it ensures consistent messaging and gives recipients space to reflect before responding.

Acknowledge their disappointment without conceding that the result was incorrect. Reinforce that the evaluation was conducted against published criteria and that outcomes are final. Keep responses calm, factual, and consistent with your established feedback policy.

If the discussion becomes repetitive or unproductive, it is appropriate to close the conversation politely but firmly. Continuing to debate subjective assessments rarely changes minds and consumes resources that should be directed toward maintaining a fair and consistent program.

A predefined feedback policy ensures consistency, protects judges, and prevents ad hoc decisions made under pressure. It should specify:

- What information will be shared (e.g., aggregate scores, thematic summaries)
- What will remain confidential (e.g., judge identities, deliberations, comparisons)
- When and how feedback will be delivered
- Who handles requests and disputes

Clear policy reduces uncertainty, supports defensibility if outcomes are challenged, and ensures all entrants are treated fairly regardless of how assertively they request feedback.

Kristal Ó Gribín

Co-founder of The Awards Platform | 20 years in digital marketing, customer engagement and product management. Exploring how industry awards are designed, managed and used to recognise achievement, with real-world examples and practical insights for awards organisers.