Program Officer

Examples

Worked examples

Is an instance
At NIH, a Program Officer (also called Program Official) is assigned to a funded grant after the Scientific Review Group has scored it; NIH separates this role from the Scientific Review Officer (SRO), who manages the peer-review study section itself, and from the Grants Management Specialist (GMS), who handles the legal, financial, and administrative terms of the Notice of Award. Applicants are encouraged to contact the relevant Program Officer before submission to discuss whether a proposed project fits the funding opportunity.
Is an instance
At NSF, a Program Officer/Program Director oversees one or more disciplinary or cross-cutting programs, assembles merit-review panels, weighs panel and ad hoc reviewer input against program priorities and available funds, and makes the funding recommendation that NSF's Division of Grants and Agreements then executes as an award. Many NSF program officers are rotators — scientists on temporary assignment (typically one to four years) from a university or research organization — rather than permanent federal staff.
Is an instance
At private foundations, a program officer typically manages a thematic grantmaking portfolio (e.g., a specific disease area, a geographic region, or a field of study), screens letters of inquiry, shepherds promising applicants toward a full proposal, and is often the named relationship contact for grantees during the award period.

Counter-examples

Looks similar, but isn't

Not an instance
A Grants Management Specialist (at NIH) or a contracting/grants officer more generally is not a program officer: that role holds the legal authority to obligate federal funds, issue the Notice of Award, and approve certain post-award actions, but does not make the underlying programmatic/scientific funding recommendation.
Not an instance
A Scientific Review Officer (SRO) who organizes and runs an NIH study section is not a program officer: the SRO's role ends with the peer-review score and summary statement, before the funding decision is made.
Not an instance
An institution's own Office of Sponsored Programs (OSP) research administrator, who helps an applicant assemble and submit a proposal on the applicant's side, is a distinct role from a program officer, who sits on the funder's side of the relationship.

Editorial commentary

Because a program officer’s authority and title vary by funder, research administrators dealing with an unfamiliar agency or foundation should not assume the title on a business card maps directly onto NIH or NSF conventions — the safest identifying test is functional: does this person make or directly shape funding recommendations for a bounded portfolio, and are they the funder-side contact for programmatic (not financial/legal) questions about that portfolio?

Why the distinction matters for research administrators

Federal and foundation funders routinely split what looks, from an applicant’s side, like a single relationship into separate roles with separate authority: a program officer for programmatic fit and scientific direction, a review official for merit assessment, and a grants/contracting officer for the legally binding award terms. Directing a question to the wrong role wastes time and, in a small number of cases, creates a documentation problem — for example, a program officer at NIH cannot unilaterally approve certain post-award actions that require the Grants Management Specialist’s sign-off, even if the program officer is sympathetic to the request. Research administrators who route pre-award programmatic questions (does this project fit the funding opportunity announcement’s scope?) to the program officer, and post-award administrative/financial actions (rebudgeting, no-cost extensions, carryover) to the grants management contact listed on the Notice of Award, avoid delays caused by a request landing with someone who lacks authority over it.

Program officers across funder types

The role’s scope and permanence differ meaningfully by funder type:

Federal science agencies (NIH, NSF, and equivalents elsewhere) typically assign program officers to disciplinary institutes, centers, or divisions. At NIH, program officers (Program Officials) are attached to a specific Institute or Center and typically stay engaged with an awarded grant for its full project period. At NSF, many program officers are “rotators” on time-limited assignment from academia, which means the named program officer on a multi-year award can change mid-award.
Mission agencies and departments (e.g., DOE, DOD components, USDA) use comparable roles, sometimes under different titles such as program manager or technical point of contact, with authority and process shaped by that agency’s own grants regulations.
Private and philanthropic foundations generally give program officers broader discretion over which proposals reach a board or committee for a funding vote, since foundations are not bound by the uniform federal grants regulations at 2 CFR 200 that separate programmatic and grants-management authority at federal agencies.

See CASRAI’s NIH Grants Overview and NSF Grants: An Overview guides for how the program officer role fits into each agency’s fuller award lifecycle, and the Office of Extramural Research (OER) and NIH Study Section entries for the surrounding NIH review structure. CASRAI’s Grant Management Systems guide covers how institutions track program-officer contacts and correspondence alongside award data.

Machine-readable encodings

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Program Officer"
      vocab-term-identifier="https://casrai.org/dictionary/term/program-officer" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/program-officer",
  "name": "Program Officer",
  "identifier": "https://casrai.org/dictionary/term/program-officer",
  "description": "<p>A <strong>program officer</strong> (sometimes called a <strong>program director</strong> or <strong>program official</strong>, depending on the funder) is the funding-agency or foundation staff member who manages a defined portfolio of grants within a scientific, technical, or thematic program area and serves as the primary point of contact between the funder and applicants/awardees throughout the funding lifecycle &mdash; before submission (fit-to-program questions, letters of intent), during review (assembling panels, contextualizing scientific merit for funding decisions), and after award (progress-report monitoring, no-cost extensions, scope changes, and, at many agencies, the funder's side of pre-award and post-award programmatic decisions). A person or role counts as a program officer when three things are true together: they hold programmatic (not purely administrative/financial) authority over which proposals get recommended for funding within their portfolio; they are the named contact awardees are expected to reach for scientific or programmatic questions about an active or prospective award; and their responsibility is bounded to a defined subject area, directorate, or program rather than the funder's entire portfolio.</p>",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/funding-finance#set",
  "url": "https://casrai.org/dictionary/term/program-officer",
  "sameAs": [],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-07-18T06:30:49",
  "inLanguage": "en"
}