Writing to the rubric: how federal objective reviewers actually score

What objective review is designed to do

For competitive discretionary programs, the Uniform Guidance at 2 CFR 200.205 requires federal agencies to design and run a merit review process and to describe it in the notice of funding opportunity. Many agencies, including the HHS operating divisions, use objective review panels of non-federal experts. Reviewers sign conflict of interest statements, receive the NOFO and a scoring guide, read a set of applications independently and score each one against the published criteria.

The panel's scores are advisory. Agency officials make final funding decisions, and they can consider factors such as funding priorities, geographic distribution and the pre-award risk review required under 200.206. But in most competitions, an application that does not score in the fundable range on objective review will not be funded. Understanding how reviewers score is therefore the most practical knowledge a writer can have.

How a reviewer actually reads your application

Having served on panels for health center and behavioral health programs, I can describe the experience plainly. A reviewer typically receives several applications, sometimes ten or more, with a short window to read and score them before the panel meets. They read with the scoring form open. For each criterion, they look for the required elements, judge how well each is addressed, and write strengths and weaknesses that justify the score they assign.

Reviewers are instructed to score only what is in the application. They cannot assume you will do something because organizations like yours usually do. They cannot give credit for information that appears in an attachment the criterion does not reference, unless the NOFO allows it. If an element is missing or hard to find, it is scored as missing or weak. This is the single most important fact for a writer to absorb.

Strengths and weaknesses drive the score

Most scoring guides ask reviewers to write strengths and weaknesses for each criterion and to make the score consistent with them. A criterion worth 20 points with three substantive strengths and no weaknesses will score near the top. The same criterion with two strengths and two significant weaknesses will land well below it. Your goal as a writer is to make strengths easy to write down and weaknesses hard to justify.

Strengths come from specificity. 'The applicant will hire a bilingual community health worker by month two, supervised by the clinical director, to conduct outreach at four named farmworker housing sites' gives a reviewer a strength they can copy into their comments. 'The applicant will conduct culturally appropriate outreach' gives them nothing. Weaknesses come from gaps, vagueness, inconsistency between sections, and claims without support.

• Name who does the work, when, where and how often
• Tie each activity to a stated objective and a measure
• Support each claim of need or capacity with a cited source
• Keep numbers identical across narrative, work plan and budget

Panel discussion and score movement

After independent scoring, panels usually meet to discuss each application. Reviewers with very different scores explain their reasoning, and individual reviewers may revise their scores in light of the discussion. Many agencies also have the panel prepare a summary of strengths and weaknesses that becomes part of the feedback applicants receive.

Discussion tends to amplify clear weaknesses. If one reviewer notices that your evaluation plan has no baseline data and says so, others who missed it will usually agree once they look. Inconsistencies are especially damaging in discussion: a work plan that says 200 participants and a budget that funds case management for 120 is the kind of detail that moves an entire panel down. Read your application specifically for internal consistency before you submit.

Make every element findable

Because reviewers score against a list, you should help them check that list. Use the criterion names and the NOFO's numbering in your headings. Answer the sub-elements in the order the NOFO lists them. When a criterion asks for something that lives in an attachment, such as a staffing plan or a logic model, reference it by attachment number in the narrative and summarize its key points in a sentence or two, so the reviewer does not have to leave the narrative to find the evidence.

Tables help when the content is naturally tabular, such as a work plan with activities, responsible staff, timelines and measures. They hurt when they replace argument. A reviewer still needs a paragraph explaining why the approach will work. Keep fonts, margins and page limits exactly as the NOFO specifies. Pages beyond the limit may be removed before review, and some agencies will not review an application that fails formatting requirements at all.

Read your summary statement, then use it

Whether you are funded or not, request and study the reviewer comments. They tell you how your application read to people who score for a living. Weaknesses that appear across several reviewers are the ones to fix first, and they often recur across cycles if you do not address them.

Store the comments with the application, tagged by criterion. Before the next competition for the same program, read them side by side with the new NOFO. Criteria change between cycles, but reviewer concerns about thin evaluation plans, vague staffing or unsupported need data tend to carry over from one panel to the next.

ELIXIR CONSUMERS' rubric library maps each section of a draft to the criterion it answers and scores it for review readiness before submission, using the language of the NOFO. It drafts only from your vault documents, so every claim a reviewer reads has a source behind it. Whatever process you use, write for the person holding the scoring form: make each element easy to find, specific enough to praise, and consistent from the first page to the last.