Contacting Program Officers Before You Apply: What to Ask, When to Call, and What Not to Do

Why Program Officers Want to Hear from You

Most first-time applicants assume program officers are gatekeepers who would rather not be bothered. The opposite is true. Program officers at NIH, NSF, DOE, and other federal agencies are evaluated partly on the quality of the proposals their programs attract. They have a direct professional incentive to help you submit a stronger application, steer you toward the right funding mechanism, and prevent you from wasting months on a proposal that does not fit their portfolio.

At NIH, program officers (POs) manage scientific portfolios, advise investigators on grant mechanisms, interpret summary statements after review, and make funding recommendations to institute leadership. At NSF, they are called program directors and serve a parallel function: shepherding proposals through merit review and shaping programmatic priorities. At DOE and its sub-agencies like ARPA-E, program managers often have deep technical expertise and actively recruit proposals that align with specific technology roadmaps.

Reaching out before you submit is not presumptuous. It is expected. NIAID explicitly states that contacting a program officer before submission of virtually all grant applications is "highly recommended." NSF publishes guidance encouraging applicants to reach out "as early as possible, even if you are in the early stages of planning your proposal." Skipping this step is one of the most common strategic errors in federal grant writing.

What Program Officers Can and Cannot Tell You

Understanding the boundaries of these conversations prevents awkward exchanges and helps you extract maximum value from every interaction.

What They Will Discuss

Programmatic fit. This is the single most valuable piece of information a program officer provides. They will tell you whether your proposed work aligns with their program's current priorities, whether it overlaps with their existing portfolio, and whether another program or institute would be a better home for your application. At NIH, this can save you from submitting to an institute that has no interest in funding your disease area. At NSF, it can redirect you from a program with a 5% funding rate to one actively seeking proposals in your subfield.

Funding mechanisms. Program officers will help you choose between an R01 and an R21, or between an NSF CAREER award and a standard research grant. They understand which mechanisms match your career stage, the scope of your project, and your preliminary data.

Strategic plan alignment. They can tell you whether your work maps to their institute's current strategic plan, congressionally mandated priorities, or new initiatives that have not yet been broadly announced. This is intelligence you cannot get from reading the funding opportunity announcement alone.

Study section and review considerations. NIH program officers can suggest which study section might be most appropriate for your work, discuss how to request assignment to a specific section via the cover letter, and explain what types of expertise sit on relevant panels. NSF program directors can describe the merit review process and what weight different criteria carry in their program.

Resubmission guidance. If you received a scored but unfunded application, the program officer can help you interpret the summary statement, distinguish between concerns that must be addressed and those that are less critical, and advise on whether the gap between your score and the payline is bridgeable.

What They Will Not Discuss

Funding decisions on pending applications. Once your proposal is under review, program officers cannot discuss whether it has been recommended for funding or declined. They are bound to maintain the integrity of the merit review process.

Your probability of funding. Asking "what are my chances?" puts the program officer in an impossible position. They cannot predict review outcomes. They can tell you whether your topic fits the program, but not whether your specific application will score well.

How to write your proposal. Program officers will not draft your specific aims, edit your research strategy, or tell you what sentences to include. They can point you to resources, describe what reviewers generally look for, and flag areas where past applicants have struggled, but the writing is your responsibility.

Confidential review information. They cannot share reviewer identities, specific scores before official release, or deliberation details.

The Gray Zone

Some questions fall into productive territory if framed correctly. Asking "what are common weaknesses in proposals to this program?" is appropriate. Asking "what should I write to get funded?" is not. The distinction is between seeking general programmatic intelligence and asking them to do your work.

When to Reach Out: Timing That Works

Timing your outreach correctly determines whether you get a substantive conversation or a perfunctory reply.

The Ideal Window: 8 to 16 Weeks Before the Deadline

Contact the program officer well before you have a finished draft. The sweet spot is two to four months before the submission deadline. At this stage, you have a research idea and perhaps a rough set of specific aims, but you have not yet invested hundreds of hours in a full proposal. If the program officer redirects you to a different mechanism, institute, or program, you still have time to pivot.

For NIH R01 applications with standard due dates (February 5, June 5, October 5), this means reaching out in late November for the February cycle, late March for June, and late July for October.

Acceptable but Less Ideal: 4 to 8 Weeks Before

You can still get useful feedback at this stage, but your options for major pivots narrow. Program officers are also busier as deadlines approach, particularly if they manage programs with the same due date. Expect slower response times.

Too Late: Less Than 2 Weeks Before

Contacting a program officer the week before a deadline signals poor planning. They may still respond to a simple question about eligibility or mechanism, but they will not have time for a substantive discussion about your research direction. Worse, it creates a negative first impression with someone who may later be involved in your funding decision.

After Submission: Still Valuable

Contact is not limited to the pre-submission phase. After you receive your summary statement, the program officer becomes your most important ally. They can contextualize reviewer comments, explain payline dynamics, and advise on whether to resubmit or try a different approach.

Agency-Specific Timing Rules

Department of Defense: Many DoD programs impose a communications blackout after a solicitation is released. Program officers cannot discuss the opportunity with potential applicants until after the review process concludes. Check the solicitation for explicit instructions.

DOE and ARPA-E: These agencies often publish a window of dates during which program managers will answer questions about a funding opportunity announcement. During this window, they can be candid and detailed. After it closes, they will answer only basic procedural questions. Miss this window and you lose access to your best source of guidance.

NSF: Program directors are generally available for contact at any time, though they may be less responsive during proposal review periods (typically several weeks after a deadline).

How to Make Contact: Email, Phone, and In-Person

Email First, Almost Always

Email is the default channel and the one program officers prefer. It gives them time to review your materials, think about their response, and loop in colleagues if needed.

Subject line structure: Make it scannable. Include the program name or funding opportunity number and a brief topic descriptor.

Subject: Pre-submission inquiry — R01 on microbiome-gut-brain axis in Parkinson's disease (PAR-26-XXX)

Subject: Project fit inquiry — NSF CBET Biosensing program, wearable metabolite monitoring

Email body structure: Keep it under 300 words. Program officers receive dozens of emails daily. A wall of text gets skimmed or deferred.

Here is a template for a first-contact email to an NIH program officer:

Subject: Pre-submission inquiry — R01 on [brief topic descriptor] ([FOA number if applicable])

Dear Dr. [Last Name],

I am an [assistant professor / associate professor / research scientist] in the Department of [X] at [Institution], and I am considering submitting an R01 application to [Institute] for the [month/year] cycle.

My proposed research focuses on [2-3 sentences describing the central question, approach, and significance]. This work builds on my recent findings showing [brief mention of preliminary data or published results].

I am writing to ask whether this line of inquiry aligns with the current priorities of [program name or branch]. Specifically, I would appreciate your guidance on:

1. Whether this topic fits within your program's portfolio
2. Whether an R01 is the appropriate mechanism, or if another mechanism (R21, R34, etc.) would be better suited
3. Any current or upcoming initiatives that might be relevant to this work

I have attached a one-page summary of the proposed specific aims for your reference. I would welcome the opportunity to discuss this by phone at your convenience.

Thank you for your time.

[Full name] [Title, Department, Institution] [Email and phone number]

And a template adapted for NSF program directors:

Subject: Project fit inquiry — [Program name], [brief topic]

Dear Dr. [Last Name],

I am a [position] at [Institution] working in [research area]. I am developing a proposal for the [program name] program and would like to confirm that my project aligns with the program's scope before I invest significant effort in the full submission.

The proposed work will [2-3 sentences: what you plan to do, why it matters, what methods you will use]. I believe this connects to the program's interest in [reference a specific program description or priority area from the solicitation].

I would appreciate any feedback on:

1. Whether this project fits within the program's current priorities
2. Whether you would recommend any modifications to improve alignment
3. Whether there are related programs I should also consider

I have attached a two-page project summary. I am happy to discuss this further by phone or video call if that would be helpful.

Best regards,

[Full name] [Title, Department, Institution] [Email and phone number]

The One-Page Attachment

Both templates reference an attached summary. This document is critical. It gives the program officer something concrete to react to, rather than forcing them to evaluate a vague description from memory.

For NIH, attach a draft specific aims page. This is the single most important page of your application, and program officers are accustomed to reviewing them. It should include your long-term goal, the specific problem or gap you are addressing, your central hypothesis, your specific aims (typically two to four), and a brief statement of expected outcomes and significance.

For NSF, attach a one-to-two-page project summary that covers the intellectual merit, broader impacts, and proposed methodology. Mirror the structure NSF reviewers will use to evaluate your proposal.

For DOE and ARPA-E, focus on the technical approach, performance targets, and how your work fits the stated program goals from the funding opportunity announcement.

Phone Calls

If the program officer responds to your email and suggests a call, prepare thoroughly. Have your specific aims page in front of you. Write down your three to five most important questions in advance. Take notes during the conversation.

Productive phone questions include:

• "Based on the aims I sent, are there aspects you think reviewers would find weak or underdeveloped?"
• "Are there investigators in your portfolio doing closely related work I should be aware of?"
• "How would you characterize the current funding climate for this topic area?"
• "Is there anything I did not ask that I should have?" (This open-ended closer consistently yields the most useful information.)

Keep the call to 15-20 minutes unless the program officer extends it. Thank them afterward with a brief follow-up email summarizing what you discussed and any action items.

In-Person at Conferences

Scientific conferences provide a less formal setting for meeting program officers. NIH and NSF staff attend major disciplinary meetings and often hold informational sessions, office hours, or booth events. Regional grants conferences hosted by NSF and NIH are specifically designed for this purpose.

At conferences, you have the advantage of a face-to-face interaction without the formality of a scheduled call. Program officers are generally open to brief conversations about research interests and programmatic fit. Keep it to five minutes unless they invite you to continue. Have a concise verbal summary of your project ready — the equivalent of an elevator pitch — and bring a printed one-page summary to leave with them.

Do not corner a program officer at a poster session and deliver a 20-minute monologue about your research. Do not interrupt them during meals unless they have explicitly made themselves available. And do not treat the interaction as a lobbying opportunity for a pending application.

Questions Worth Asking (and How to Frame Them)

The quality of your questions determines the quality of the answers you receive. Generic questions get generic responses. Specific, informed questions demonstrate that you have done your homework and prompt the program officer to share insights they would not offer unprompted.

High-Value Questions

"Does my proposed work overlap with anything currently in your portfolio?" This helps you differentiate your proposal and avoid duplicating funded work. If there is overlap, the program officer may suggest a complementary angle.

"Which study section (or review panel) would be most appropriate for this work?" At NIH, study section assignment significantly affects your review outcome. The program officer's recommendation carries weight with the Center for Scientific Review.

"Are there any new or upcoming initiatives relevant to this topic?" Agencies sometimes plan special funding announcements, supplements, or set-aside funds that are not yet public. Program officers may hint at these opportunities without revealing confidential details.

"What are the most common weaknesses you see in proposals to this program?" This gives you a roadmap of pitfalls to avoid. Common answers include insufficient preliminary data, unclear significance, and budgets that do not match the proposed scope.

"For a resubmission: which reviewer concerns should I prioritize in my response?" Program officers understand the difference between a major scientific concern that torpedoed your score and a minor formatting complaint that will not matter on resubmission.

Low-Value Questions (Avoid These)

"Can you read my proposal and give feedback?" Program officers do not provide line-by-line manuscript review. Asking this misunderstands their role and wastes their time.

"What should I write to get funded?" This is unanswerable and suggests you want them to do your work.

"What is the funding rate / payline?" This information is usually public. Look it up before the conversation. Asking signals that you have not done basic research.

"Will my proposal be funded?" They cannot tell you this, and asking creates an awkward interaction.

Seven Mistakes That Damage Your Credibility

1. Not Reading the Solicitation First

The fastest way to lose a program officer's respect is to ask questions that are answered on page two of the funding opportunity announcement. Read the entire solicitation, the agency's strategic plan, and any relevant program descriptions before making contact. Your questions should demonstrate that you have absorbed the publicly available information and are seeking guidance that goes beyond it.

2. Sending a Five-Page Email

Your initial email should be under 300 words plus a one-page attachment. Program officers triage their inboxes rapidly. A multi-page email with extensive background, preliminary data descriptions, and a full literature review will not be read in its entirety. Save the details for your actual application.

3. Asking the Same Question Multiple Program Officers Answered

If you contacted one program officer and received a clear answer, do not email three more hoping for a different response. Program officers within an institute communicate with each other. Shopping your question around suggests you did not like the first answer.

4. Contacting the Wrong Person

NIH has hundreds of program officers across 27 institutes and centers. Emailing a program officer at NIMH about a cardiovascular proposal wastes everyone's time. The funding opportunity announcement lists the scientific/research contact. Start there. If you are unsure which institute is right, use the NIH RePORTER to see which institutes fund work similar to yours.

5. Following Up After Two Days

Program officers manage large portfolios and may take one to two weeks to respond. If you have not heard back after two weeks, a polite follow-up is appropriate. Sending a "just checking in" email after 48 hours signals impatience and a lack of understanding of their workload.

6. Treating the Interaction as a Commitment

A program officer saying "this sounds like it could fit our program" is not a promise of funding, a guarantee of favorable review, or an endorsement of your proposal. It is a general assessment of topical alignment. Do not reference this conversation in your application as evidence that the program officer supports your work unless they have explicitly agreed to be named.

7. Ignoring Their Advice

If a program officer tells you that your project does not fit their program, believe them. If they suggest a different mechanism, seriously consider it. Applicants who receive clear guidance and then submit anyway to the wrong program or mechanism are remembered, and not favorably.

Building a Long-Term Relationship

The most successful grant-funded investigators treat program officer interactions as ongoing professional relationships, not one-off transactional exchanges. After your application is submitted, keep the program officer informed of significant developments: a high-impact publication, an invited talk, new preliminary data that strengthens your case. These updates keep your work on their radar without being pushy.

If you are funded, the relationship deepens. Program officers monitor the progress of awards in their portfolio. They appreciate investigators who communicate proactively about timeline changes, preliminary findings, and emerging challenges. Investigators who build this kind of rapport find that their program officers become advocates during tight funding discussions.

If you are not funded, the post-review conversation with your program officer is arguably more important than the pre-submission one. They can decode reviewer language, identify the two or three changes that would most improve your score, and help you decide whether to resubmit or try a completely different approach.

Frequently Asked Questions

Is it appropriate to contact a program officer if I am a graduate student or postdoc, not a PI?

Yes, though the conversation will be different. Program officers welcome inquiries from early-career researchers exploring fellowship mechanisms (F31, F32 at NIH; GRFP at NSF) or trying to understand which programs might support their future independent research. Mention your career stage upfront so the program officer can tailor their advice. If you are planning to apply as a PI on a research grant, having your mentor copied on the initial email adds credibility without being required.

How many program officers should I contact for a single proposal?

Start with one: the scientific/research contact listed on the funding opportunity announcement. If they redirect you to a colleague, follow that referral. For proposals that span multiple disciplines, it is acceptable to contact program officers in two programs to determine the best fit, but be transparent that you are doing so. Do not blast the same email to five program officers hoping one will bite.

What if the program officer never responds to my email?

Wait two full weeks, then send a brief follow-up referencing your original message. If you still receive no response after another week, try calling their direct line during business hours. Some program officers strongly prefer phone communication. If all attempts fail, contact the grants management specialist listed on the funding opportunity announcement and ask them to help route your inquiry. Persistent non-response is rare but does happen, particularly during peak review periods.

Should I contact a program officer about a foundation or state grant, not a federal one?

The principles in this guide apply primarily to federal agencies. Private foundations operate differently. Some foundation program officers welcome pre-submission contact and even require a letter of inquiry before a full proposal. Others explicitly prohibit unsolicited contact. Always check the foundation's published guidelines. State agencies vary widely. Some model their processes on federal norms, while others have minimal pre-submission engagement. When in doubt, call the contact number listed on the solicitation and ask whether pre-submission inquiries are welcome.

Can contacting a program officer hurt my chances of funding?

In virtually all cases, no. Program officers are walled off from the peer review process and cannot influence your score. A pre-submission conversation does not create bias for or against your application. The only scenario where contact could hurt you is if you behave unprofessionally, ignore explicit advice, or repeatedly contact the wrong person after being redirected. Treat every interaction with the same professionalism you would bring to a job interview, and the interaction will only help.

---

Granted helps researchers and organizations navigate the full grant lifecycle, from identifying the right funding opportunities to building competitive proposals with AI-powered writing and compliance tools.