NIH Scientific Review Officer (SRO) Outreach: What They Can Tell You and When to Ask

Who Is the SRO and Why Applicants Often Don't Know Them

The Scientific Review Officer, sometimes called the Scientific Review Administrator or SRA, is the NIH staff member who runs the logistics and integrity of peer review for a specific study section or special emphasis panel. Every standing study section has a designated SRO. Every special emphasis panel convened for a particular funding opportunity also has one assigned to it.

The SRO's job is fundamentally different from a Program Officer's. They don't manage a research portfolio or have a say in whether your funded application gets an award. They organize the review meeting, manage reviewer conflicts of interest, prepare the summary statement, and handle procedural questions about review. If a reviewer discloses a conflict after assignment, that goes to the SRO. If a reviewer declines after the application is already logged, the SRO handles reassignment. If the meeting format shifts from in-person to virtual, the SRO sends the notice.

Applicants tend to know POs and not SROs because POs attend scientific conferences, give talks, and are listed prominently on institute websites. SROs work mostly behind the scenes. Their contact information is on the study section roster, but many applicants never look there until something goes wrong in review. That's the wrong time to introduce yourself.

SRO vs. Program Officer: Two Jobs With Strict Lanes

The clearest way to understand the SRO's role is to understand what they're not allowed to discuss. They can't talk to you about whether your science is a good fit for a particular institute or program. They can't tell you whether a PO is interested in your work. They can't help you frame your Specific Aims for maximum impact, recommend reviewers, or give you any hint of whether your application is competitive. All of that belongs to the Program Officer.

The lane is narrow, but within it the SRO is actually the authoritative source. A PO who answers a question about review logistics is guessing or going by general practice; the SRO is going by the actual assignment in the system. One other thing worth noting: the SRO writes and releases your summary statement. If the statement contains an error — a wrong score transcribed, an aim description that doesn't match what you proposed — the SRO is who you contact.

Before You Submit: Questions the SRO Can Actually Help With

The most underused contact window is before you submit, particularly if you're uncertain about which study section your application will land in. The SRO assigned to a standing study section can tell you, in general terms, the scope of expertise represented on that panel. They won't give you reviewer names, but they can confirm whether a given topic routinely falls to their section or gets reassigned elsewhere. If you're deciding between two standing sections to request in your cover letter, a brief call or email to the SRO of each section can help you make that choice with better information than you'd get from reading the roster alone.

You can also ask the SRO whether a special emphasis panel is planned for the funding opportunity you're targeting. Special emphasis panels sometimes have different expertise profiles than a standing section, and knowing that a SEP is likely can affect your cover letter strategy. NIH typically doesn't announce SEP rosters until close to the review meeting, but the SRO can often confirm that one is being organized.

If your project sits at the intersection of two or three fields — computational biology meets clinical trial design meets rare disease, for example — a pre-submission conversation with the SRO of your preferred section can clarify whether that panel has the expertise to evaluate all three components, or whether a different section would be a better home. This is one place where a focused, specific question genuinely changes the outcome. Just keep expectations realistic: the SRO isn't running a consulting service, and a long email asking for general advice won't get a useful response.

During Peer Review: The Window When Nobody Can Talk to You

Once your application is under review — from the time the study section meets until the summary statement is released — there's very little productive communication to have with anyone in the review process. This is intentional. NIH review is designed to be independent, and even inadvertent communication that could be perceived as attempting to influence review is taken seriously.

Don't try to contact reviewers during this period. Don't send supplemental materials. Don't follow up with the SRO to ask whether your application was discussed. The summary statement will tell you, and it typically arrives within 30 days of the review meeting date posted in eRA Commons.

The one exception is a genuine administrative emergency: an error in the application file, a technical issue in eRA Commons, or a reviewer conflict that you become aware of after review begins. In those cases, contact the SRO promptly with a factual description of the issue. Don't frame it as advocacy for your application. Report the administrative fact and let the SRO handle it.

After Peer Review: What the SRO Can Clarify

Your summary statement arrives and something doesn't add up. The scores are fine, but one reviewer appears to have evaluated Aim 2 based on a method you never proposed. Or the statement lists a concern about statistical power that you addressed directly in the Research Strategy. Or your Impact score is notably different from what the criterion scores would predict. These are legitimate factual questions, and the SRO is the right person for some of them.

The SRO can confirm whether the summary statement reflects the review accurately — whether the criterion scores are correctly transcribed and whether the discussion captured the major concerns. What they can't do is advocate for a rescore or explain why reviewers reached a particular scientific conclusion. Review is confidential. The SRO can't tell you what was said in the room beyond what the written summary captures.

For questions about scientific interpretation — what specifically bothered reviewer 2 about your experimental design, or whether a reviewer misread your preliminary data — the Program Officer is the right contact. POs often have informal visibility into review concerns that didn't make it into the summary in full. A resubmission strategy conversation with your PO, anchored by what the SRO confirmed about summary statement accuracy, is often the most productive post-review combination. Think of it as two separate calls serving two separate purposes, rather than one long conversation about everything.

Study Section Assignment: Making the Cover Letter Work

The cover letter is your formal mechanism for requesting study section assignment and flagging conflicts of interest. The SRO reviews it and uses it — along with their own assessment of the science — to make assignment decisions. This means the SRO reads your cover letter more carefully than most applicants realize.

One situation where SRO pre-submission outreach makes the most difference: highly interdisciplinary applications. If your project sits at the boundary between two standing sections and could legitimately land in either, a brief email to each SRO before you submit can tell you which section has the deeper expertise in the components that matter most. That's information you can't get from the roster alone, and it can change which section you request. The key is to ask a narrow question — "Does your section regularly review computational approaches to X?" — not to ask which section would give you a better score.

Common Mistakes Applicants Make With SRO Outreach

Three patterns come up repeatedly.

Frequently Asked Questions