Grant writers face an information problem with an unusual character: the volume of theoretically relevant information is enormous, but most of it won't produce a funded grant. Funder newsletters, grant databases, sector trend reports, nonprofit management publications, program evaluation research — all of it might be useful in some proposal, and almost none of it is urgent.
The grant writer who tries to read everything relevant to grant writing reads most of it at the expense of actually writing proposals. The discipline is ruthless triage: five information streams, each with a purpose, each with a clear standard for what enters it, and each protected from the others so that the proposal writing time — the work that actually produces funding — isn't sacrificed to information management.
Stream 1: Funder landscape and opportunities — Identifying and qualifying funding opportunities; understanding funder priorities and strategy.
Stream 2: Organizational program and outcomes knowledge — Understanding what the organization's programs do, what outcomes have been achieved, and what can be accurately claimed.
Stream 3: Proposal development information — What each specific proposal requires; submission requirements; deadlines; funder-specific guidance.
Stream 4: Relationship management — Communication with program officers; relationship cultivation; follow-up on submissions.
Stream 5: Professional development — Grant writing craft; sector knowledge; professional community.
Stream 1: Funder Landscape and Opportunities — Qualification Over Volume
The funder landscape is the information stream with the most volume and the least return on broad reading. Grant databases contain tens of thousands of funders. Sector trend reports discuss philanthropy broadly. Most of this information won't produce a funded proposal.
FUNDER LANDSCAPE AND OPPORTUNITY TRIAGE
The qualification question for all new opportunity information:
"Is this funder a realistic prospect for our organization in the next 18 months?"
If yes → Research thoroughly
If maybe → Add to watch list for quarterly review
If no → Discard regardless of grant size
Criteria for "realistic prospect":
Geographic fit: They fund in our geography
Mission alignment: Their priorities align with our programs — genuinely, not creatively
Organization type fit: They fund organizations like ours (size, stage, type)
Application access: Open to unsolicited applications, or we have a relationship
WHAT QUALIFIES FOR IMMEDIATE RESEARCH:
Alert that a known funder has opened an application cycle: [Research immediately]
Alert that a known funder has changed their priorities: [Research immediately — does this help or hurt?]
Introduction to a new funder from a trusted source: [Research this week]
WHAT QUALIFIES FOR WATCH LIST:
New foundation in our geography with mission alignment: [Add; research when application opens]
Known funder that doesn't currently fit but might: [Add; revisit quarterly]
WHAT GETS DISCARDED:
Large national funder with no track record of funding organizations like ours
Funder outside our geography with no exception history
Opportunities that technically fit our programs but require significant proposal shaping to seem relevant
INFORMATION SOURCES THAT ARE WORTH MONITORING (weekly scan):
Foundation websites for funders in active prospect list: [What's new; priorities changes]
Sector-specific funding alerts: [One source only; set geographic and mission filters]
State and local community foundation announcements: [If relevant to our geography]
INFORMATION SOURCES THAT AREN'T WORTH MONITORING:
Large grant databases without filtering: [Noise to signal ratio too low]
National philanthropy trend reports: [Interesting; rarely produces prospects]
General nonprofit sector news: [Usually not funder intelligence]
"Realistic prospect for our organization in the next 18 months" is the opportunity qualification discipline. The grant writer who researches every plausible-sounding opportunity researches many more than they can pursue and writes proposals to funders who were never likely to fund. The one who applies this qualification filter directs research toward opportunities with genuine fit — and produces more funded proposals with fewer proposals submitted.
Stream 2: Organizational Program and Outcomes Knowledge — Current and Verified
Organizational program and outcomes knowledge is what makes proposals accurate. But this information doesn't come from external reading — it comes from staying current with what's happening in the organization's programs.
ORGANIZATIONAL KNOWLEDGE TRIAGE
WHAT REQUIRES IMMEDIATE ATTENTION:
New outcomes data from program evaluation: [Updates what we can claim; read immediately]
Program changes: [New services; discontinued programs; capacity changes — affects proposals in progress]
Leadership or staff changes: [Affects proposals that reference key personnel]
Financial audit completed: [Affects what we can say about organizational health]
WHAT REQUIRES PERIODIC REVIEW (monthly):
Updated participant counts and demographics: [From program staff or database]
Grant report outcomes: [What we've reported to funders — must be consistent with proposals]
New organizational initiatives or partnerships: [May create new proposal opportunities]
WHAT REQUIRES ANNUAL REVIEW:
Complete organizational data review: [Verify all statistics used in proposals are current]
Program descriptions updated: [Match current program delivery]
Staff bios updated: [Key personnel descriptions accurate]
KEY INTERNAL RELATIONSHIPS FOR THIS STREAM:
Program staff: [Who provides outcomes data; response time expectations]
Executive director: [What requires their review; timeline]
Finance staff: [Budget data; audit; financial health]
Evaluation staff (if exists): [What data they have; when available]
WHAT SLOWS DOWN PROPOSALS:
Waiting for outcome data that should be readily available
Getting conflicting information from different staff members
Having to correct proposals because program information was outdated
PREVENTION:
Maintain a current organizational fact sheet: [Updated quarterly at minimum]
Know who to call for what information: [Clear internal contacts]
Build update requests into proposal timeline: [Request current data with 2-week lead]
Proposal development information is the most deadline-sensitive stream — everything related to a specific proposal in progress, including submission requirements, funder guidance, and deadline management.
PROPOSAL DEVELOPMENT INFORMATION TRIAGE
Per proposal in progress:
WHAT TO READ FIRST (before beginning a proposal):
Complete RFP or funder guidelines: [All of it; carefully]
Prior feedback from this funder: [If we've applied before]
Recent grants awarded by this funder: [From 990 or grantee list — what they've funded recently]
Notes from prior communication with program officer: [What we've been told directly]
WHAT TO READ DURING PROPOSAL DEVELOPMENT:
Organization's prior proposals to this funder: [What's been submitted; what worked]
Program descriptions and outcome data: [Current and accurate]
Funder's most recent annual report or strategic plan: [Current priorities; recent language]
WHAT NOT TO READ DURING PROPOSAL DEVELOPMENT:
Other grant opportunities: [This creates distraction; other opportunities wait]
General research on the issue area: [Beyond what this specific proposal requires]
WHAT TO READ BEFORE SUBMISSION:
Complete guidelines one more time: [Did we address everything?]
Submission portal requirements: [Technical requirements; file formats; character limits]
Checklist of required attachments: [Letters of support; financials; IRS determination letter]
DEADLINE MANAGEMENT:
Submission deadline: [Hard; calendar with alert 2 weeks before]
Internal working deadline: [Hard; 2 weeks before submission]
Review deadline: [When executive director must receive for review]
Budget approval deadline: [When finance must receive for approval]
Supporting documents deadline: [Letters, financials — these take time to collect]
Stream 4: Relationship Management — Responsive and Intentional
Relationship management with funders is the stream that requires the fastest response time and the most careful attention.
RELATIONSHIP MANAGEMENT TRIAGE
WHAT GETS SAME-DAY RESPONSE:
Communication from program officers on submitted proposals: [Status inquiries; requests for information]
Invitations for meetings or site visits: [Accept and confirm immediately]
Notification of funded grant: [Acknowledge promptly; begin processing]
Notification of decline: [Respond graciously; request feedback if appropriate]
WHAT GETS RESPONSE WITHIN 48 HOURS:
General correspondence from funders in active prospect list
Program officer reaching out to share news about their program
Inquiries about eligibility for upcoming grant cycle
WHAT CAN WAIT FOR WEEKLY PROCESSING:
Funder newsletters: [Scan for opportunities or priority changes; not urgent]
Conference announcements from funders: [Add to calendar if relevant; process weekly]
RELATIONSHIP CULTIVATION DISCIPLINE:
Proactive outreach to program officers: [Scheduled; not reactive to opportunities only]
Thank you notes after funded grants: [Immediate]
Relationship touches during non-application periods: [Sharing relevant organizational news]
WHAT TO TRACK PER RELATIONSHIP:
Last contact: [When; what about]
What I know from the conversation: [Key intelligence]
What they said that's relevant to future proposals: [Specific — not general notes]
When next appropriate contact is: [Not too frequent; strategic]
Stream 5: Professional Development — Scheduled Investment
Professional development keeps grant writing skills current and builds the craft knowledge that improves proposal quality over time.
PROFESSIONAL DEVELOPMENT TRIAGE
WHAT QUALIFIES FOR SCHEDULED TIME:
Proposal writing craft: [What makes proposals compelling; how to write specific sections better]
Sector and field knowledge: [The issue areas covered by proposals — enough to write authoritatively]
Philanthropy trends: [Funder strategies; sector-wide shifts]
Evaluation and outcomes measurement: [How to describe and demonstrate impact]
WHAT'S THE DEVELOPMENT FOCUS:
Current area of active development: [One focus; not scattered]
Why this area: [Where it will most improve funded proposals]
Resources: [Specific — not general intention to "read more about this"]
SCHEDULING:
Weekly (60 minutes): [Professional development; scheduled; protected]
Community: [Grant Professionals Association chapter; peer group; if relevant]
NOT: Leftover time; it doesn't materialize
WHAT DEVELOPMENT PRODUCES:
Not: Interesting knowledge about grant writing
Yes: Specific changes to how I write proposals
"What will I do differently in my next proposal because of this?" — the application question
Protecting Proposal Writing Time
The architecture that protects writing time:
DAILY TIME PROTECTION FOR GRANT WRITERS
PROPOSAL WRITING BLOCK (morning — protected):
No email processing during this time
No funder newsletter reading
No opportunity research
Output: Proposal sections drafted
EMAIL AND COMMUNICATION PROCESSING (designated windows):
2-3 times per day: Not continuous
Program officer communication: Same-day response during these windows
Funder communications: Same-day response
Internal communication: During these windows unless urgent
OPPORTUNITY AND FUNDER RESEARCH (afternoon — designated):
Weekly: Not daily for most funders
Triggered by: Application cycle opening; priority change; new prospect
PROPOSAL DEVELOPMENT TASKS (filling around writing):
Information gathering from internal staff
Supporting document collection
Budget development
WHAT NEVER HAPPENS DURING PROPOSAL WRITING TIME:
Reading funder newsletters
Exploring new opportunities
General research not required by current proposals
Key Takeaways
-
"Realistic prospect for our organization in the next 18 months." The opportunity qualification question that concentrates research where it produces proposals.
-
Proposal writing time is protected — not a remainder. The work that produces funding requires protected time.
-
Organizational information is maintained current — not gathered during proposal writing. Current fact sheet updated quarterly.
-
Program officer communication: same-day response. Funder relationships are built on responsiveness.
-
One professional development focus at a time. "What will I do differently in my next proposal?" — the application standard.
Conclusion
Grant writer information overload across five streams: funder landscape and opportunities ("realistic prospect for our organization in the next 18 months" as the qualification question; criteria — geographic fit, mission alignment, organization type fit, application access; immediate research for known funder application cycle opening or priority change; watch list for new prospects with alignment that aren't currently open; discard large national funders without track record of funding organizations like ours; one sector-specific funding alert source with filters; grant databases without filtering not worth monitoring); organizational program and outcomes knowledge (immediate attention for new evaluation data, program changes, leadership changes, audit completion; monthly review for participant counts and demographics, grant report outcomes, new initiatives; annual review for complete statistics verification; "what slows down proposals" — waiting for data that should be available, conflicting information, correcting proposals for outdated info; current organizational fact sheet updated quarterly; build data requests into proposal timeline with 2-week lead); proposal development information (read first before beginning — complete RFP, prior feedback, recent grants awarded, program officer notes; read during — prior proposals to this funder, current outcomes data, funder's most recent annual report; not during writing — other opportunities, general research beyond what this proposal requires; submission: complete guidelines review, portal requirements, required attachments checklist; deadline management: working backward from submission with internal, review, budget, and supporting document deadlines); relationship management (same-day response for program officer communication, invitations, funding decisions, declines; 48-hour response for general correspondence from active prospects; weekly processing for newsletters and conference announcements; track per relationship — last contact, what I learned, relevant specifics, next appropriate contact); and professional development (one active development focus; "what will I do differently in my next proposal?" as the application standard; 60 minutes weekly scheduled; Grant Professionals Association if relevant). Time architecture: protected morning writing block; designated email windows 2-3 times daily; afternoon opportunity research; no funder newsletters during writing time.
For more on this, see Building a Personal Knowledge Base.