Nonprofit professionals engage in two fundamentally different types of information work, but rarely have distinct structures for each.
Ongoing intelligence reading is the cadence-driven activity: scanning funder newsletters, staying current with policy developments affecting the populations served, following sector research and peer organization news, and monitoring funding landscape shifts. Intelligence reading builds the background knowledge that makes development and program work more informed. It produces knowledge base entries and strategic awareness.
Deliverable-triggered research is the demand-driven activity: researching a new funder prospect before writing a letter of inquiry, building an evidence base for a proposal due in three weeks, investigating program models before designing a new initiative. This research has a defined output and a deadline.
Mixing the two produces the familiar problem: reading sessions that consume time but don't produce organized intelligence, and proposal research sessions that start from scratch because prior reading wasn't captured in a retrievable form. The workflow below separates them structurally, assigns appropriate cadences to each, and creates the routing discipline that converts both into knowledge base contributions.
The Intelligence Reading Structure
Tier 1: Funder Landscape Monitoring (Weekly)
The funding landscape changes continuously: grant programs open and close, funder priorities shift, new funders enter program areas, and relationships between sectors and foundations evolve. Weekly funder landscape monitoring keeps the organization's prospecting and relationship strategy current.
Sources (weekly review, 20-30 minutes):
- Funder newsletters from current and prospect foundations (scan for priority updates or new programs)
- Grant database service alerts (calibrated to the organization's funding range and program areas)
- Sector-specific philanthropy news (Chronicle of Philanthropy, Inside Philanthropy, relevant listservs)
Triage filter:
Is this a grant opportunity within our range and program areas with a near deadline? → Grant calendar addition; development director notified.
Does this represent a funder priority shift relevant to a current or prospect relationship? → Funder intelligence entry updated.
New prospect funder identified? → Prospect entry created for initial research.
General funder landscape awareness? → Note if interesting; no entry.
Tier 2: Sector and Policy Intelligence (Monthly)
Policy developments affecting the populations served (housing, education, workforce, health — each area has significant policy dynamics), academic and practice research in the program areas, peer organization news and program developments, and government funding priority changes.
Monthly sector reading (60-90 minutes):
MONTHLY SECTOR READING — [Date]
Duration: 60-90 minutes
POLICY DEVELOPMENTS:
[Any policy changes this month affecting the populations we serve?]
[What's the implications for our programs? For our grant narrative?]
RESEARCH AND FIELD DEVELOPMENTS:
[Any new research or evaluations relevant to our program area?]
[What does this suggest about our program model or evidence base?]
PEER ORGANIZATION INTELLIGENCE:
[What are peer organizations doing? Any new program models, evaluations, or partnerships?]
[Any implications for our strategy or funder conversations?]
FUNDER LANDSCAPE:
[Any significant funder priority shifts or new programs this month?]
[Any implications for our prospect list or existing relationships?]
KB UPDATES:
[ ] Evidence base entries updated with any new research found?
[ ] Sector intelligence entries updated?
[ ] Funder intelligence entries updated?
[ ] Any new grant prospects added to the tracking list?
Tier 3: Field Publications and Deep Reading (Quarterly)
Major program evaluations, sector-wide studies, government program research, and comprehensive reports from major foundations and research organizations. This reading is depth-oriented — the quarterly block processes material that doesn't fit in the weekly scan or monthly review.
Quarterly field reading (2-3 hours):
The quarterly reading block is protected time specifically for depth reading: a major program evaluation in the organization's program area, a foundation's sector analysis, a government accountability report on a relevant funding stream. These are longer-form documents that require focused attention and produce substantial knowledge base contributions.
The Deliverable-Triggered Research Structure
The Research Anchor (Before Any Research Session)
Before any research session for a deliverable — grant prospect research, evidence base building, program design research — the research anchor prevents starting from scratch.
RESEARCH ANCHOR — [Date]
DELIVERABLE: [Letter of intent / Grant proposal / Program design / Other]
DEADLINE: [When is this needed?]
RESEARCH TIME BUDGET: [Hours available]
KNOWLEDGE BASE CHECK:
[ ] Funder prospect entry: [Found? Last verified? What's in it?]
[ ] Evidence base for this program area: [Found? How current? What's missing?]
[ ] Program learnings relevant to this design: [Found? What do we have?]
[ ] Peer organization intelligence: [Found? What do we know about what others are doing?]
WHAT'S CURRENT AND USABLE: [List]
WHAT NEEDS VERIFICATION: [List]
WHAT NEEDS NEW RESEARCH: [List — this defines the research scope]
ADJUSTED RESEARCH SCOPE:
[This session targets the gaps — not the full research landscape]
Funder Prospect Research
When a new funder is identified as worth researching, a structured 60-90 minute prospect research session produces the intelligence needed to decide whether to invest in a relationship or proposal.
FUNDER PROSPECT RESEARCH — [Date]
Funder: [Foundation name]
Time budget: 60-90 minutes
SOURCES:
[ ] Funder website: Program areas, guidelines, FAQ, current priorities
[ ] 990 (last 1-2 years): ProPublica Nonprofit Explorer or Foundation Directory
[ ] Candid profile: History, geographic focus, organization size data
[ ] Recent grant listings: Who they fund, in what amounts, for what programs
[ ] Any press releases or published reports
FINDINGS:
Current funding priorities: [With source and date]
Geographic focus: [National / Regional / Specific]
Organization size: [What size organizations do they fund?]
Grant range: [From 990 and public grant listings]
Application process: [Open application / LOI required / Invited only]
Grant cycle: [When applications are accepted; timeline to decision]
FIT ASSESSMENT:
Program alignment: [Strong / Moderate / Weak — specific basis]
Organization size fit: [Are we the right size?]
Geographic fit: [Do we operate where they fund?]
STRATEGIC RECOMMENDATION:
[ ] Pursue actively — [What's the first step?]
[ ] Track for future cycle — [Why not now?]
[ ] Not a fit — [Why]
KB ROUTING:
[ ] Prospect entry created in funder intelligence archive
[ ] Grant calendar updated if decision to pursue
The fit assessment discipline:
Not every foundation that funds nonprofits is a fit for every organization. A clear-eyed fit assessment — program alignment, organization size, geography — prevents investing relationship and proposal development time in prospects that are unlikely to convert.
Evidence Base Research
For grant proposals requiring a strong evidence base, the evidence base research session fills the specific gaps identified in the research anchor.
Session structure:
EVIDENCE BASE RESEARCH — [Date]
Program area: [Area being researched]
Time budget: [Hours]
KNOWLEDGE BASE CHECK:
Current evidence base entry: [What's there; what's current; what's missing]
Identified gaps: [What research types are missing from the KB entry]
SOURCES SEARCHED:
[ ] Google Scholar — search terms: [List]
[ ] PubMed (for health-related programs)
[ ] Social Science Research Network (SSRN)
[ ] Government research repositories (NIJ, HUD, Department of Education, etc.)
[ ] Foundation research repositories (Urban Institute, Brookings, etc.)
FINDINGS:
New studies found:
[Study 1: Author, Title, Year, Key Finding, Methodological Quality]
[Study 2: ...]
What the evidence collectively shows:
[Summary of what the evidence base now demonstrates]
[With honest limitations noted]
KB ROUTING:
[ ] Evidence base entry updated with new studies
[ ] Synthesis updated to reflect the fuller evidence base
Integrating Both Streams Into the Month
MONTHLY STRUCTURE
Weekly (20-30 min each week):
Funder landscape monitoring → triage
→ Grant calendar updates
→ Funder intelligence entries updated
→ Prospect list maintained
Monthly (60-90 min, first week):
Sector and policy reading → synthesis
→ Evidence base updated with new research
→ Sector intelligence entries updated
→ Funder landscape notes updated
As needed (deliverable-triggered):
Funder prospect research: 60-90 min per prospect
Evidence base research: 1-3 hours per program area gap
Program design research: 2-4 hours per new program initiative
→ Always preceded by research anchor
→ Always followed by KB routing
Quarterly (2-3 hours):
Deep field reading block → substantial KB contributions
The Grant Cycle Research Structure
Grant proposal season creates an intensive research period — often four to eight weeks before a major proposal deadline. The research anchor discipline prevents this season from becoming a from-scratch research project:
GRANT CYCLE RESEARCH STRUCTURE
4+ weeks before deadline:
[ ] Research anchor completed — what does the KB have? What are the gaps?
[ ] Funder prospect research completed (if new funder)
[ ] Evidence base research sessions scheduled for identified gaps
2-3 weeks before deadline:
[ ] Evidence base gaps filled through research sessions
[ ] Program learnings entry reviewed and current
[ ] Partner intelligence reviewed (any partnerships relevant to this proposal?)
[ ] Proposal structure outlined from research anchor synthesis
1 week before deadline:
[ ] All research complete — no new research initiated this close to deadline
[ ] Proposal drafting from organized research (not simultaneous research and drafting)
Post-submission:
[ ] KB routing: what new intelligence from this cycle belongs in the KB?
[ ] Grant calendar: next deadline / follow-up date added
[ ] Intelligence notes: any new funder intelligence from this cycle?
Common Reading and Research Failures in Nonprofits
Failure 1 — No structured funder landscape monitoring. Development staff read funder newsletters reactively — when something interesting lands in the inbox — without a structured weekly review that maintains the prospect list and funder intelligence entries. Fix: 20-30 minute weekly funder monitoring scan with explicit triage and KB routing.
Failure 2 — Evidence base research done only at proposal time. Every proposal requiring an evidence base section is researched from scratch against a deadline. Fix: monthly sector reading that builds the evidence base continuously, so proposal research targets the specific gaps remaining rather than building the full base under pressure.
Failure 3 — No research anchor. Grant prospect research and evidence base building starts with an open browser, no KB check, and produces research that duplicates prior work. Fix: 10-minute KB check before every research session, defining the scope as the gaps — not the full research project.
Failure 4 — No post-research KB routing. The prospect research done for a proposal is filed in the proposal folder. The next proposal to the same funder starts the research over. Fix: KB routing as a required final step of every research session.
Failure 5 — Intelligence reading not routed to the KB. Useful articles from the monthly sector reading are read and closed. The evidence and sector intelligence they contained doesn't get captured. Fix: evidence base and sector intelligence KB entries are updated from the monthly reading block as a required final activity of the session.
Key Takeaways
-
Nonprofit reading and research have two separate structures. Intelligence reading is cadence-driven (weekly funder landscape monitoring, monthly sector and policy reading, quarterly deep field reading) and produces KB entries. Deliverable-triggered research is demand-driven (preceded by a research anchor, targeted at KB gaps, followed by KB routing).
-
The research anchor prevents starting from scratch on every proposal. 10 minutes of KB check before any research session defines the scope as the gaps — not the full research project. For familiar funders and established program areas, this often reduces the research scope by 50-70%.
-
Weekly funder landscape monitoring (20-30 minutes, structured) is the primary prospecting discipline. Calibrated funder alerts reviewed systematically against the prospect list and funder intelligence archive, with routing to the grant calendar and KB, produces consistent prospecting activity rather than reactive response to what lands in the inbox.
-
Monthly sector reading builds the evidence base between proposal cycles. Research done in advance, when there's no deadline pressure, is deeper and more systematic than research done in the two weeks before a proposal is due. The monthly reading block converts ongoing sector awareness into proposal-ready evidence base entries.
-
Post-research KB routing is the step that makes the reading and research work compound. Every funder research session, every evidence base update, and every sector reading block ends with explicit KB routing: what's new, what belongs where, what needs a currency date update. Without this step, each research session produces notes that don't build the organizational knowledge base.
Conclusion
The reading and research workflow for nonprofits converts information work from a reactive, deadline-driven activity into two structured streams that each produce specific, retrievable organizational knowledge. Ongoing intelligence reading — with calibrated funder landscape monitoring, monthly sector and policy synthesis, and quarterly deep reading — builds the background intelligence that makes proposal research faster and more substantive. Deliverable-triggered research — anchored before starting with a KB check, targeted at identified gaps, and followed by KB routing — converts each research project into a knowledge base contribution. Together, these two streams create the compounding organizational knowledge system that distinguishes organizations that improve with each grant cycle from those that rebuild from scratch each time.
See also: The Personal Knowledge Management Guide.