Nonprofit Grant Runway and Revenue Projection Memo
Draft an executive email to board trustees detailing grant pipeline forecasts, renewal risks, and operating runway.
Use this template when presenting financial forecasting updates to nonprofit board committees or executive directors. It translates statistical pipeline models into clear runway projections and governance decision points.
Role: Senior Nonprofit Finance Director and Predictive Modeling Specialist
Context
- Organization: {{nonprofit_name}}
- Forecasting horizon: {{fiscal_cycle}}
- Active grant pipeline figures: {{grant_pipeline_data}}
- Donor attrition and renewal variables: {{renewal_risk_assumptions}}
- Baseline operational expenses: {{operating_burn_rate}}
- Minimum reserve policy: {{reserve_threshold_months}}
Task
Draft a concise, high-stakes email to the Board of Trustees and Executive Leadership detailing the rolling revenue forecast, anticipated funding cliffs, and recommended budgetary adjustments for the upcoming fiscal cycle.
Method
- Calculate baseline revenue under three scenario weights (conservative, expected, optimistic) using {{grant_pipeline_data}}.
- Adjust incoming cash projections against attrition variables defined in {{renewal_risk_assumptions}}.
- Compare net projected revenue against {{operating_burn_rate}} to determine net cash flow per quarter.
- Calculate the projected cash runway in months and benchmark against {{reserve_threshold_months}}.
- Isolate top variance drivers across institutional, government, and philanthropic revenue streams.
- Formulate two proactive mitigation strategies for revenue shortfall risks identified in the conservative scenario.
- Structure the email for immediate executive consumption with prioritized bottom-line figures upfront.
Constraints
- MUST express all probability distributions in concise ranges rather than singular definitive numbers.
- MUST clearly separate committed grant funding from uncommitted pipeline probabilities.
- MUST NOT exceed 450 words in total email length.
- Technical statistical terminology must be translated into plain governance language.
- Avoid speculative program cuts without tying them directly to model deficit triggers.
Output format
- Subject line: Clear, actionable, naming {{nonprofit_name}} and {{fiscal_cycle}}.
- Executive Summary: 2-3 sentences covering net runway and primary financial posture.
- Scenario Comparison Table: Plain-text markdown comparison (Conservative, Expected, Optimistic) detailing Projected Revenue, Burn, and Runway Months.
- Critical Variance Drivers: 3 bullet points.
- Recommended Board Actions: 2 numbered recommendations.
Self-review
- Does the runway calculation explicitly reflect {{reserve_threshold_months}} constraints?
- Are conservative vs optimistic revenue assumptions plainly justified based on {{renewal_risk_assumptions}}?
- Is the tone objective, urgent if necessary, but strictly non-alarmist?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.