When Grant Reviewers Give Different Scores

Explain the gap, preserve the assessments and record the funding recommendation

Published

Monochrome illustration connects two separate reviewer assessment sheets to a funding-recommendation folder and discussion notes.

Two reviewers give a community grant application 62 and 88 out of 100. One sees a convincing delivery plan; the other thinks the team needs more experience. They also disagree about the matched funding in the budget. The programme officer needs to understand the gap before putting a funding recommendation to the approver.

Review the reasons behind different scores before deciding whether anything should change. Check that reviewers used the same application and scoring criteria, correct factual or calculation errors through the approved process, and preserve differences in judgement that remain. Keep the individual assessments and the panel’s reasoning with the recommendation.

Follow the disagreement through to a decision

  1. 1 · Compare

    Check the basis

    Confirm the application, budget and scoring criteria used by each reviewer. Read the comments behind each score.

  2. 2 · Resolve

    Record what changed

    Use the programme’s procedure to correct errors or record panel moderation, while retaining original assessments.

  3. 3 · Recommend

    Explain the outcome

    Identify the accepted reviews, remaining differences and calculation or panel reasoning submitted for approval.

Calibration means helping reviewers apply the scoring criteria consistently. A large gap is a reason to look at the evidence; it does not establish which reviewer is right or require both to arrive at the same score. Agree the discussion and correction process before the funding round starts.

Check what explains the gap

Start with the review package. A revised budget or a missing attachment can explain different assessments without either reviewer misreading the material they received. Record which package was released to whom and decide whether the affected applications need another review under the programme’s procedure.

Then compare the criteria and comments. An arithmetic error, a mistaken reading of eligible cash and a different view of delivery risk need different responses. A correction should identify the input and rule that changed the score. Where reviewers reasonably disagree, retain their explanations and follow the programme’s method for producing a recommendation.

If the discussion reveals a conflict of interest, follow the reviewer-conflict process, including the authorised treatment of that reviewer’s assessment. Score discussion alone does not resolve a participation problem.

Worked example: 62 and 88 describe different assessments

Fictional funding round, scoring rules and application. A community skills fund uses three criteria totalling 100 points. Its procedure calls for discussion when the two totals differ by more than 20 points. After any authorised corrections, it uses the arithmetic mean of the two accepted reviews for its recommendation score. Funding approval remains a separate decision.

Both reviewers assessed application GRT-2086, package revision 2, using rubric version 1. The budget shows $20,000 cash and $10,000 in-kind support. This fictional rubric gives 12 matched-funding points for $20,000 eligible cash and 24 for $30,000; in-kind support does not count in that criterion. Reviewer B mistakenly counted both contributions as cash.

Only the matched-funding error changes Reviewer B’s assessment. The other differences remain for the panel to explain.
Criterion and maximumReviewer AReviewer B, submittedReviewer B, corrected
Community benefit · 40303636
Delivery plan · 30202828
Matched funding · 30122412
Total · 100628876
  1. Open the discussion with the original reviews

    The initial 26-point gap triggers the programme’s review procedure. The officer keeps both submitted assessments and confirms their package and rubric references before the panel considers a change.

  2. Correct the cash interpretation

    The panel checks the budget against the rubric. Under the approved procedure, Reviewer B submits a corrected assessment of 76, identifying the 12-point matched-funding correction. The file retains the original 88, the revised assessment, reason, reviewer and acceptance record.

  3. Keep the remaining judgement visible

    Reviewer A remains concerned about delivery experience; Reviewer B gives more weight to the proposed partnerships and community reach. The panel records those explanations. The accepted totals remain 62 and 76, a 14-point difference.

  4. Prepare the recommendation

    The officer records the programme’s calculation: (62 + 76) ÷ 2 = 69. The recommendation identifies both accepted reviews and the correction, and explains the remaining differences alongside funding priorities and the available budget. A score of 69 does not by itself authorise an award.

  5. Submit for the funding decision

    The configured FormKiQ workflow routes the recommendation document to the authorised approver. The application records the resulting award state, while the grant file retains the application package, rubric, assessments, discussion record and approval basis.

Preserve the rules for the whole funding round

A discussion can uncover a wider interpretation problem. Record whether other assessments need the same check and who owns that review. A change to criterion weights or eligibility is a programme-policy decision: the owner needs to decide its scope before the application recalculates rankings.

When the procedure permits a panel adjustment, identify whether it replaces an individual score, creates a separate panel score or changes the recommendation only. Keep its rationale and authority. Retain the rules and accepted inputs used for an earlier recommendation so a later configuration change does not silently rewrite its basis.

Checklist for a grant-review pilot

  • Agree the scoring criteria, weights, discussion triggers, correction authority and recommendation method before review begins.
  • Confirm each reviewer receives the intended application and budget versions, with the agreed visibility of other assessments.
  • Test an arithmetic error, a mistaken criterion interpretation and a legitimate difference in judgement.
  • Retain submitted assessments, accepted corrections and any separately authorised panel score or adjustment.
  • Check that only permitted staff can change assessments, accept corrections and approve funding, including direct document and API access.
  • Reconstruct the recommendation from its exact inputs and rules, then change the rubric and verify that the earlier decision record remains understandable.

Sources and related guidance

Make the funding recommendation explainable

A different score should lead to a useful question about the evidence or the reviewer’s judgement. Keep the answer, any authorised change and the accepted inputs together. The approver can then see how the programme reached its recommendation and what disagreements remain.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call