Grant writer note-taking determines whether funder research is lost or cumulative, whether proposal experience improves or repeats itself, and whether relationships with program officers are recalled or reconstructed from scratch each application cycle.
The grant writer who doesn't take systematic notes starts each funder engagement largely from zero, rediscovers what they learned in prior application cycles, and can't build on relationship conversations because they didn't capture what was said. The one who maintains consistent notes has a compounding intelligence advantage: each funder engagement enriches the knowledge base, each proposal cycle adds to the craft knowledge, and each program officer conversation deepens the relationship intelligence.
Four note types serve different purposes: funder research and relationship notes (the intelligence that accumulates across funder engagements), proposal development notes (the thinking captured during proposal creation), grant outcomes and reporting notes (the accountability record), and professional reflection notes (the craft development from experience).
Template 1: Funder Research and Relationship Notes
Funder research and relationship notes are the primary intelligence asset — what the grant writer knows about each funder that makes subsequent proposals better targeted than if starting from scratch.
When to capture: After initial funder research; after every conversation with a program officer; after reviewing a funder's 990 or publications; after receiving a funding decision with feedback.
FUNDER RESEARCH AND RELATIONSHIP NOTE
Date: [Date]
Funder: [Foundation name]
Contact (if applicable): [Program officer name and title]
Note type: [Initial research / Program officer conversation / Site visit / Decision feedback / Annual update]
WHAT I LEARNED:
About the funder's priorities:
[What this engagement taught me about what they fund and why]
[What's changed from what I previously knew or expected]
[What seems to be the direction they're moving]
About what they actually fund vs. what they say:
[If there's a gap between guidelines and grantee patterns — what I observed]
[What the grantee list from their 990 shows about actual funding patterns]
About their culture and process:
[How they prefer to communicate; what they emphasize in their process]
[What they care about that isn't explicit in their guidelines]
From this conversation specifically (if applicable):
[What the program officer said — verbatim for anything important]
[What I asked; what I learned from their answer]
[What they implied that wasn't explicit]
[What they asked about our organization — what they were assessing]
WHAT THIS MEANS FOR OUR PROPOSALS:
[How this changes or confirms my understanding of how to approach this funder]
[What framing, emphasis, or language this suggests]
[What this suggests about our application strategy]
WHAT I WANT TO REMEMBER:
[The most important intelligence from this engagement]
[What to bring up in the next conversation]
[What to include or avoid in the next proposal]
RELATIONSHIP STATUS:
Our relationship before this: [Where it was]
Our relationship now: [What this engagement changed]
Next step: [What I should do next; when]
WHAT I'M STILL UNCERTAIN ABOUT:
[What this engagement didn't answer; what to find out next]
"What the program officer implied that wasn't explicit" is the relationship intelligence field. Program officers communicate indirectly as often as directly — the hedge when asked about organizational fit that suggests uncertainty, the enthusiasm when a specific program element was described that suggests alignment, the pause before answering that suggests the question hit something important. Capturing these inferences (clearly labeled as interpretation, not direct statement) builds the relationship intelligence that experienced grant writers have with their closest funder partners.
Template 2: Proposal Development Notes
Proposal development notes capture the strategic thinking behind each proposal — the decisions made, the arguments constructed, and the judgments about what to include or exclude. These notes are valuable both for improving this proposal during revision and for producing better proposals to the same funder in subsequent cycles.
When to capture: During proposal development — as the grant writer is making strategic decisions about approach, argument, and content.
PROPOSAL DEVELOPMENT NOTE
Date started: [Date]
Funder: [Foundation name]
Proposal: [Brief description — program; amount requested]
Deadline: [Submission date]
STRATEGIC DECISIONS:
THE MAIN ARGUMENT:
What's the strongest argument for why this funder should fund this program?
[My answer — specific]
Why I'm leading with this argument:
[What I know about this funder that suggests this is the strongest approach]
WHAT I'M EMPHASIZING AND WHY:
Which program outcomes I'm highlighting: [And why these for this funder]
Which aspects of our approach I'm leading with: [And why these for this funder]
How I'm framing the problem: [Why this framing for this funder]
WHAT I'M NOT INCLUDING AND WHY:
What I considered but decided not to include: [What; why]
What would weaken this proposal if included: [What to avoid; why]
ORGANIZATIONAL INFORMATION I'M USING:
Outcome data being cited: [Source; date; verified by]
Program capacity claims: [What we're saying; basis for claim]
Staff credentials being cited: [Who; what specifically]
FUNDER-SPECIFIC ADAPTATIONS:
What I've changed from our standard narrative: [For this funder specifically]
Language I'm using that's specific to this funder: [Their vocabulary]
How I'm addressing their specific requirements or emphases: [From guidelines or conversations]
CHALLENGES I'M NAVIGATING:
[What's hard about this proposal — fit issues, data gaps, competition concerns]
[How I'm addressing each challenge]
[What I'm uncertain about in my approach]
WHAT I DECIDED AND WHY:
[Key decisions made during development — with rationale]
[What alternatives I considered and why I chose the approach I chose]
WHAT I WANT TO REMEMBER FOR NEXT CYCLE:
[What to do differently next time with this funder]
[What worked in this proposal that I should replicate]
[What I'm uncertain about that the result will clarify]
"What I'm not including and why" is the strategic discipline field. Proposal development involves as many decisions about what to leave out as what to include. The grant writer who captures why they decided not to include a specific program element, why they chose one framing over another, or why they led with a particular argument — and what the result was — builds the decision-making intelligence that produces progressively better proposals.
Template 3: Grant Outcomes and Reporting Notes
Grant outcomes and reporting notes build the accountability record — what was delivered on funded grants, how outcomes compared to what was promised, and what was learned that affects future proposals and grant management.
When to capture: At grant reporting time; when significant outcomes data becomes available; when a grant period closes; when a grant is declined.
GRANT OUTCOMES AND REPORTING NOTE
Date: [Date]
Funder: [Foundation name]
Grant: [Period; amount; program funded]
Note type: [Mid-year report / Final report / Outcomes review / Decline analysis]
WHAT WAS PROMISED:
[From proposal — what outcomes we said we'd achieve]
[From grant agreement — what requirements were specified]
[From prior conversations — any additional commitments]
WHAT WAS ACHIEVED:
For each promised outcome:
Target: [What we said]
Actual: [What happened]
Variance: [+ or - how much; percentage]
Explanation: [Why this variance — specific and honest]
WHAT WE LEARNED FROM THIS GRANT:
What worked better than expected: [With what this suggests about the program]
What worked less well than expected: [With what this suggests about the program]
What we changed during the grant period: [With funder notification if required]
What we'd do differently with this grant: [Honest reflection]
HOW THE RELATIONSHIP IS AFTER THIS GRANT:
Based on the outcomes: [Strong / Maintained / Challenged]
What the program officer's response has been: [If known]
What this grant positions us for: [Re-application? Increased amount? Different program?]
What I need to do to maintain/strengthen this relationship: [Next steps]
WHAT THIS TEACHES FOR FUTURE PROPOSALS:
What to promise and what to qualify: [Based on what we actually achieved]
How to describe this program in future proposals: [Informed by actual outcomes]
What this funder now knows about our capacity: [From what we delivered]
For declines:
DECLINE ANALYSIS:
What they said in feedback (verbatim or detailed paraphrase):
What I think was the real reason (may differ from feedback):
What was within our control to have done differently:
What wasn't within our control (fit, competition, timing):
What I'll change in the next proposal to this funder:
Whether to re-apply: [Yes / No / Wait — with reasoning]
"What I think was the real reason — which may differ from feedback" is the analytical intelligence field in decline notes. Funder feedback on declined proposals is often diplomatically softened and may not capture the actual reason for the decline. A grant writer who has experience with a funder can often read the feedback in context — "they said our proposal was well-written but the budget was too large; I think the real issue is that we're a direct service organization and they've been moving toward advocacy-focused grants." Capturing this analysis (clearly labeled as interpretation) builds the funder intelligence that makes subsequent proposals more accurately targeted.
Template 4: Professional Reflection Notes
Professional reflection notes capture what the grant writer has learned from the work — what's improving, what's challenging, and where to invest in professional development.
When to capture: After completing a major proposal; after receiving a significant funding decision; periodically (monthly or quarterly) as deliberate reflection.
PROFESSIONAL REFLECTION NOTE
Date: [Date]
Type: [After major proposal / After funding decision / Periodic reflection / Career development]
WHAT I'M LEARNING FROM MY CURRENT WORK:
What's getting easier: [Specific — what I do better than I used to]
What's still hard: [Where I still struggle; what takes too long; what I'm uncertain about]
What patterns I'm noticing: [Across proposals; across funders; in my own work]
WHAT MY RECENT PROPOSALS HAVE IN COMMON:
Strongest sections: [Where my writing is consistently strongest]
Weakest sections: [Where I consistently need more work]
What I'm repeating that I should change: [Habits that aren't serving me]
WHAT I'VE LEARNED FROM RECENT FUNDING DECISIONS:
Funded proposals — what they had in common: [Pattern]
Declined proposals — what they had in common: [Pattern]
What the pattern suggests: [What to do more of; what to change]
WHAT I WANT TO DEVELOP:
Current gap I'm most aware of: [What's limiting my effectiveness]
What improving this would do for funded proposals: [Why it matters]
How I'm going to develop it: [Specific — not vague]
WHAT I'D TELL A NEWER GRANT WRITER:
[What I know now that I didn't when I started — specific to this work]
[What I wish I'd known earlier]
[What makes the biggest difference in funded success]
Key Takeaways
-
"What the program officer implied that wasn't explicit." Relationship intelligence includes inference, clearly labeled as interpretation.
-
"What I'm not including and why." Proposal strategy is as much about exclusion as inclusion.
-
"What I think was the real reason — which may differ from feedback." Decline analysis that's more than the funder's diplomatic language.
-
Funded and declined proposal patterns — comparison. The comparative analysis that produces the most actionable craft intelligence.
-
Capture notes during proposal development, not after. Strategic decisions are clearest while being made.
Conclusion
Grant writer note-taking templates across four types: funder research and relationship notes ("what the program officer implied that wasn't explicit" as the relationship intelligence field; what I learned — about funder priorities, about what they actually fund vs. say, about their culture and process, from this conversation specifically with verbatim important statements; what this means for our proposals — framing, emphasis, language; relationship status before and after with next step; "what I'm still uncertain about" as the follow-up intelligence target); proposal development notes ("what I'm not including and why" as the strategic discipline field; the main argument with why I'm leading with this for this funder; what I'm emphasizing and why — outcomes highlighted, approach leading, problem framing; challenges being navigated with how I'm addressing each; key decisions with alternatives considered and rationale; "what I want to remember for next cycle" — what to do differently, what worked to replicate, what the result will clarify); grant outcomes and reporting notes ("what I think was the real reason — which may differ from feedback" as the analytical intelligence field in decline notes; what was promised from proposal and grant agreement; what was achieved per outcome with target, actual, variance, explanation; what we learned — what worked and didn't, what we'd do differently; how the relationship is after and what this positions us for; decline analysis — verbatim or detailed feedback, interpretation of real reason, what was within vs. outside our control, whether to re-apply); and professional reflection notes (what's getting easier and what's still hard; funded and declined proposal patterns comparison; "what I'd tell a newer grant writer — what makes the biggest difference in funded success" as the career intelligence field; current development gap with why it matters and how I'm developing it). Capture timing: funder notes after every engagement; proposal notes during development while decisions are being made; outcome notes at reporting time; reflection notes monthly or after major events.
Related reading: Web Clipping for Research Papers.