You have a good program and a careful writer, and your applications still score in the middle. A common reason is that the narrative follows the order in which the team wanted to tell the story, not the order in which a reviewer has to score it. The reviewer then hunts for evidence, and anything they can't find earns no points.
This article shows you where the scoring rubric lives, how to divide your page space by points, how to write in the criterion's own words and how to check a draft against the rubric before you submit.
Find the rubric first
The label changes from funder to funder: review criteria, evaluation criteria, selection criteria, scoring rubric. The function is the same. It's the list of what a reviewer will judge and how much each part counts.
In a federal notice, look in the Application Review Information section. Under Appendix I to 2 CFR 200, that section must give a clear description of each criterion and sub-criterion and, if criteria vary in importance, the relative percentages, weights or other means used to distinguish them. It must also explain any statutory or regulatory preferences and say how they affect scoring, for example by adding points. And it must say how cost sharing will be considered in the review if it isn't an eligibility requirement.
Also look for what the notice says about the review process itself. Under 2 CFR 200.205, the merit review process must be described or incorporated by reference in the funding opportunity. Some agencies and foundations also publish reviewer guidance or a scoring form. If one exists, find it and read it as a reviewer would.
Foundation guidelines may not publish points at all. In that case, treat any list of "what we look for" as the rubric and ask the program officer how decisions are made.
Points decide page space
If a notice assigns weights, your page allocation should follow them. A 30-point section deserves more space and evidence than a 5-point one.
Say a rural food bank is applying under a notice with a 20-page narrative limit and these criteria:
| Criterion | Points | Share of 100 | Pages (of 20) |
|---|---|---|---|
| Need | 20 | 20% | 4 |
| Program design | 30 | 30% | 6 |
| Organizational capacity | 20 | 20% | 4 |
| Evaluation plan | 15 | 15% | 3 |
| Budget and sustainability | 15 | 15% | 3 |
| Total | 100 | 100% | 20 |
The common mistake is to let the section the writer enjoys grow longest. A need section that runs eight pages, because the research was interesting, takes space from program design, which carries more points.
Treat the allocation as a starting point. If a criterion has several sub-criteria, split its pages among them the same way.
Write in the criterion's own words
Reviewers have a form in front of them. Make it easy for them to fill it in.
- Mirror the headings and order. If the criteria are "Need," "Program Design" and "Capacity," use those as your headings, in that order, unless the notice tells you otherwise.
- Answer each verb directly. If a criterion says "the applicant demonstrates a clear plan for recruiting participants," open the section with a sentence that does so: "We will recruit participants through three channels…" and then show the detail.
- Cover every sub-criterion. A bulleted list of sub-criteria is a checklist. Tick each one off in your outline.
When the narrative instructions and the criteria are in a different order, follow the instructions for structure, because Appendix I requires notices to give any required order, format or headings for the narrative. Then cross-reference the criteria so a reviewer can find each one, for instance by labeling a paragraph "Addresses criterion 2b: staffing."
Read how to read a funding notice for where to find these instructions, and from notice to outline for turning them into a working outline.
Here's a before and after on a hypothetical sentence. Before: "Our organization has served the county since 1998 and has deep roots in the community." After, under a capacity criterion that asks about staff qualifications: "The program will be led by our operations director, who has managed a $400,000 federal nutrition grant, supported by two full-time staff." The second version answers the criterion; the first only describes the organization.
How reviewers use the criteria
Review practice varies by funder. Federal programs may use outside peer panels, agency staff or both. Appendix I says notices could describe the types of people who evaluate, the number of people on a panel and how conflicts of interest are avoided.
What is consistent is that the reviewer works from the criteria and the page. NIH's description of its peer review process is a useful example: reviewers score each criterion, and its guidance says each reviewer uses their own judgement to determine how each criterion weighs into the overall impact score. So a criterion you neglect can pull your overall result down even if your strongest section is excellent.
Points are lost in practice for a few repeatable reasons:
- Information the criterion asked for isn't there.
- The information is there but buried under a different heading.
- A claim has no number, source or example behind it.
None of these is a prose problem. They are structure and evidence problems, which you can fix.
Score yourself before the reviewer does
Before you submit, score your own draft. Print the rubric, read each section as a reviewer would and write a score and a one-line reason next to each criterion. Where you'd deduct points, either fix the section or accept the loss knowingly. The final read-through is the natural place to do this with a second reader.
Your next step
Take the last proposal you submitted and score it against the funder's published criteria. Note where you'd deduct points and why. Most writers find the same two or three patterns, such as thin evidence or a missing sub-criterion, and those become your checklist for the next application.
SoliContraX checks each section it drafts against what the notice asked for and lists what's still missing, which is the same exercise at speed. Upload the notice, approve a concept and take it from there to a finished application. Start your next application.