TLDR
A program officer is the foundation staff member responsible for managing a grant portfolio within a specific programmatic area — reviewing applications, making funding recommendations, monitoring grantee progress, and maintaining funder-grantee relationships.
The program officer is the person at the foundation who knows your work, advocates for your application internally, and holds you accountable to the terms of your grant. Understanding how program officers operate — and how to work with them — is as important as writing a strong proposal.
What a program officer does
A program officer’s job has three phases:
Before the grant: receiving and reviewing letters of inquiry, inviting full proposals, conducting due diligence, making funding recommendations. In most foundations, the PO writes a funding memo that summarizes the application, analyzes the organization’s track record, assesses the fit with foundation priorities, and recommends a grant amount and conditions. The board or grants committee reviews that memo and approves, modifies, or declines the recommendation. A strong PO relationship means your application gets a well-informed, accurate memo.
During the grant: serving as the primary contact for questions about grant terms, reviewing modification requests (budget changes, timeline extensions, scope adjustments), and maintaining the relationship with grantee staff. Program officers who visit grantee sites or attend program events understand the work at a level that paper reporting cannot convey. That understanding protects grantees when circumstances change.
After the grant: reviewing progress and final reports, assessing whether grant objectives were met, determining whether to continue the relationship with a renewal grant or a new application cycle. Program officers also contribute to the foundation’s learning agenda — synthesizing what they observe across their grantee portfolio to inform future grant strategy.
How program officers differ by foundation type
Private foundation program officers typically work in smaller teams with deeper portfolios. At a $100 million private foundation with five program staff, each officer may manage 30–60 active grants. They may have more latitude to exercise personal judgment and build long-term grantee relationships. Priorities can shift with the interests of family members who control the foundation.
Community foundation program officers administer both the foundation’s own grantmaking and donor-advised fund grants. They often manage a defined geographic focus rather than a thematic one and serve as connectors within the local philanthropic community. Community foundation POs frequently have less discretionary authority than private foundation counterparts — their recommendations go through multiple committee layers.
Corporate foundation program officers align grantmaking with corporate priorities — employee engagement, community relations, brand positioning in specific markets. Decisions may involve both the foundation’s internal team and the corporate parent’s communications or public affairs department. Corporate foundation priorities can shift rapidly in response to business conditions or corporate leadership changes.
Working effectively with program officers
Treat the LOI conversation as the beginning, not the transaction. Many program officers will speak with prospective grantees before a formal application. Those conversations are an opportunity to understand what the foundation is actually trying to accomplish with its grantmaking — which may not be fully captured in the published guidelines. A proposal that addresses the PO’s actual priorities, as expressed in conversation, is stronger than one that strictly follows the published template.
Be honest about challenges. Program officers who have been in the field long enough have seen organizations that failed to acknowledge problems until the problems became crises. An organization that surfaces a program challenge in a progress report — with a clear explanation of what happened and what it is doing about it — is treated very differently than one that projects false confidence and is later discovered to have misled the funder. Honesty builds trust; dishonesty ends relationships.
Ask before deviating from grant terms. Budget modifications, timeline extensions, and scope changes all require funder approval in most grant agreements. Organizations that make unilateral changes and report them after the fact — or fail to report them at all — create compliance problems that damage the relationship and sometimes require grant refunds. The right approach is to contact the program officer as soon as a significant deviation becomes likely, explain the circumstances, and request formal approval before the change is made. Most program officers accommodate reasonable modifications when asked in advance.
Keep the PO informed of significant organizational changes. Leadership transitions, budget challenges, program redesigns, mergers, and other significant events should be communicated to program officers whose active grants are affected. Finding out about major organizational changes from a news article or from a peer foundation is a trust-damaging experience. POs who are informed early can help navigate the situation and will advocate for reasonable accommodation.
What program officers look for in a grant report
Reporting requirements vary by foundation, but most program officers are looking for the same things in a progress or final report:
- Honest accounting of what was accomplished versus what was proposed — the report should compare actual outputs and outcomes to the targets stated in the application
- Explanation of variances — when targets were not met, why, and what the organization learned
- Financial report showing that grant funds were spent as budgeted (or documenting approved modifications)
- Specific examples or stories that illustrate program impact — quantitative data alone rarely tells the full story
- A clear statement of what comes next — what the organization plans to do with the program going forward, including how it will sustain activities after the grant ends
Program officers who receive reports that are vague, overly positive, and inconsistent with what they observed during site visits will become skeptical. The report is not primarily a marketing document; it is a compliance and relationship document.
The relationship beyond the grant
The PO relationship matters beyond any single grant. A program officer who has funded an organization over multiple cycles, visited program sites, and developed a genuine understanding of the work will advocate for that organization during difficult funder conversations, connect them with other foundation resources, and facilitate introductions to peer funders.
Long-term PO relationships are built through consistent honesty, clear communication, high-quality reporting, and demonstrated program effectiveness. They are not built through performative optimism or over-stated impact claims.
GrantPipe’s funder reporting templates and grant pipeline management tools help development staff track the reporting requirements and relationship touchpoints for each program officer relationship — so nothing falls through the cracks. For a complete framework covering the grant cycle from application through compliance, see the Grant Lifecycle Guide.
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.