Nonprofit AI Prompts Library

54 ready-to-use AI prompts built for nonprofit teams. Pick a department, grab a prompt, paste it into ChatGPT, Claude, or Gemini, and get polished, mission-ready content in minutes.

54 Prompts 7 Departments 100% Free

How to Use These Prompts

Pick a Prompt

Browse by department and click any prompt card to expand it.

Fill in Brackets

Replace the [BRACKETED] placeholders with your organization’s details.

Send It

Paste into ChatGPT, Claude, or Gemini and get polished content back.

Nonprofit Fundraising Prompts

AI prompts to write compelling appeal letters, donor thank-you notes, campaign emails, major gift proposals, and lapsed donor re-engagement messages that increase nonprofit fundraising results.

Annual Fund Appeal Letter

Prompt Write a year-end Annual Fund appeal letter for [ORGANIZATION NAME] to [DONOR SEGMENT] donors that can be used for both print and email.

Prompt Write a year-end Annual Fund appeal letter for [ORGANIZATION NAME] to [DONOR SEGMENT] donors that can be used for both print and email. The appeal letter should: - Be 325-425 words total, fit on one page, with 4-6 short paragraphs and a 1-2 sentence P.S. restating the ask and urgency. - Follow this order: [SALUTATION with DONOR FIRST NAME] → Opening story (2-3 sentences) about [BENEFICIARY NAME/COMPOSITE] → Prior support acknowledgment or lapsed re-engagement → Case for unrestricted support → Urgency (match/deadline/goal) → Clear ask with gift string → CTAs → Warm close → [SIGNER NAME, TITLE] → P.S. - Lead with one vivid, dignity-first story detail; avoid savior language; include [PROGRAM AREA] and [CITY/COMMUNITY] context. - Make a concrete case for unrestricted support in 2-3 sentences, with examples like [UNRESTRICTED EXAMPLES] (e.g., keep staff on the frontlines, respond to urgent needs, keep doors open). - Personalize the ask using [LAST GIFT AMOUNT]; propose a three-option string [ASK 1]/[ASK 2]/[ASK 3] (anchor at 1.5–2x last gift) with specific impact notes [IMPACT PER $]. - Create urgency with [MATCH DETAILS] and/or [DEADLINE DATE], reference [YEAR-END GOAL], and a realistic consequence [CONSEQUENCE] if the goal is missed. - Include bracketed segment lines: [IF LAPSED], [IF CURRENT], [IF MAJOR], [IF MONTHLY], each 1 sentence tailored to that segment. - Use donor-centric language (aim for a 3:1 “you” to “we” ratio); open with gratitude; be authentic and specific. - Provide multiple CTAs: donate at [GIVE URL], scan [QR TEXT], or mail to [REPLY ADDRESS]; include a brief note on DAF/stock [ALT WAYS] if relevant. - Tone [TONE]: FORMAL (suited for board/major donors; polished, restrained), WARM (relational, gracious, community-centered), CASUAL (friendly, conversational, neighborhood vibe). Choose one. - Keep readability at 6th–8th grade; short sentences; no clichés (“now more than ever”), no jargon, no guilt or pity framing.Peer-to-Peer Fundraising Template - Also provide: Email subject line (5–7 words) and preview text (35–60 chars); signature block for [SIGNER NAME], [TITLE]; optional footer line with [EIN]. A strong letter feels human and mission-true: story first, clear unrestricted case, specific dollar handles, and respectful urgency. Avoid vagueness, stat dumps, or overpromising. The P.S. should repeat the ask and [MATCH/DEADLINE]. Ensure the piece is segment-ready with bracketed variations and includes at least two frictionless ways to give.

Use in:

Emergency/Urgent Appeal

The Prompt Create a rapid-turn, donor-ready emergency fundraising appeal for a genuine, time-bound need at [ORGANIZATION NAME].

The Prompt Create a rapid-turn, donor-ready emergency fundraising appeal for a genuine, time-bound need at [ORGANIZATION NAME]. The emergency appeal email should: - Be written for [AUDIENCE SEGMENT: ALL DONORS/MAJOR DONORS/MONTHLY DONORS/NEW DONORS] in [TONE: FORMAL (measured, data-forward), WARM (compassionate, community-centered), DIRECT (plain, calm-urgent)] aligned with [BRAND VOICE NOTES]. - Include: 3 subject lines, 1 preheader, salutation, body (250–350 words), clear CTA with [DONATION LINK]/[PHONE], P.S. restating deadline and impact, and sign-off from [SIGNER NAME/TITLE] (add [BOARD CHAIR NAME/TITLE] if appropriate). - Open with what happened [EMERGENCY TYPE/WHAT HAPPENED], who is affected [WHO IS AFFECTED], and where [GEOGRAPHY]—specific, witnessed details; avoid sensationalism. - State a precise, time-bound goal: “We must raise [SPECIFIC DOLLAR GOAL] by [DEADLINE DATE/TIME] to [PURPOSE].” Include the consequence of missing the deadline. - Provide a credible plan: 3–4 bullets on how funds will be used immediately (e.g., staffing, supplies, direct aid, logistics), with expected timeline. - Demonstrate readiness: 1–2 sentences on track record/partnerships [CREDIBILITY POINTS]. - Include an impact ladder tied to giving: “$[AMOUNT 1] = [IMPACT]; $[AMOUNT 2] = [IMPACT]; $[AMOUNT 3] = [IMPACT].” Use real, verifiable numbers [IMPACT PER $]. - If applicable, integrate [MATCH DETAILS] with clear terms and cutoff; otherwise omit. - Offer alternate ways to give (1 line): check/DAF/stock/[ALTERNATIVE GIVING METHODS]. - Maintain dignity-first language for people served; write at ~8th-grade level; avoid clichés (“now more than ever,” “unprecedented”) unless accurate; no guilt or fear tactics. - Add a 40–60 word “Board Fast-Track Justification” summarizing urgency, goal, deadline, and risk of inaction for quick approval. - End with a commitment to report back within 72 hours on initial impact and within 30 days on outcomes. Quality matters: authenticity + specificity build trust. Use concrete details, plain language, and verifiable figures. Keep the ask clear and immediate, not manipulative. If any bracketed detail is unknown, insert a plausible placeholder and tag [VERIFY] so staff can confirm quickly.

Use in:

GivingTuesday Campaign Email Series

The Prompt GivingTuesday Three-Email Campaign Generator BEFORE YOU BEGIN: Fill in these fields Organization Information - [ORGANIZATION NAME] – e.g...

The Prompt GivingTuesday Three-Email Campaign Generator BEFORE YOU BEGIN: Fill in these fields Organization Information - [ORGANIZATION NAME] – e.g., “City Youth Literacy Project” - [MISSION/CAUSE] – 5–8 words, e.g., “free tutoring for underserved students” - [EIN/LEGAL NAME] – e.g., “EIN 12-3456789, City Youth Literacy Project, Inc.” Campaign Details - [GIVINGTUESDAY DATE] – e.g., “December 3, 2024” - [TIME ZONE] – primary sending timezone, e.g., “ET” - [RECIPIENT TIME ZONE] – “Same as TIME ZONE” or specific zone(s); if national, write “Varies—note local time” - [DONATION LINK] – full URL to your GivingTuesday donation page - [HASHTAGS] – 1–2 tags, e.g., “#GiveLocal #LiteracyMatters” - [SOCIAL HANDLE] – e.g., “@CityYouthLit” - [DEADLINE TIME] – e.g., “11:59pm ET” Goal & Match - [GOAL TYPE] – choose ONE: “donors” or “dollars” - [GOAL NUMBER] – e.g., “500 donors” or “$25,000” - [MATCH DETAILS] – “amount, source, deadline” (e.g., “$10,000 match from Smith Family Foundation, through 11:59pm”), or “NONE” Impact Story - [BENEFICIARY/PROGRAM] – e.g., “Maria, a 3rd grader in our after‑school program” - [IMPACT UNIT] – e.g., “$25 provides 2 hours of one‑on‑one tutoring” Personalization & Signer - [FIRST NAME|"Friend"] – use fallback “Friend” if name not available - [FROM NAME] – e.g., “Sarah Chen” - [TITLE] – e.g., “Executive Director” - [TONE] – choose ONE: FORMAL (precise, respectful), WARM (friendly, mission‑forward), CASUAL (energetic, conversational) Email Setup (infrastructure) - [SENDER DISPLAY NAME] – e.g., “City Youth Literacy Project” - [SENDER EMAIL] – e.g., “[email protected]” - [REPLY-TO EMAIL] – e.g., “[email protected]” - [FORMAT] – choose ONE: “Plain text (recommended)” or “Simple HTML (minimal styling)” Compliance Footer - [PHYSICAL ADDRESS] – mailing address - [UNSUBSCRIBE LINK] – placeholder text “Unsubscribe” or your ESP tag - [PRIVACY LINK] – optional URL TASK: Create three GivingTuesday emails Email Timing & Labels - Email 1: Morning Launch (7–9am [TIME ZONE]; if [RECIPIENT TIME ZONE] differs, note “[send 7–9am local time]”) - Email 2: Mid‑Day Update (12–2pm [TIME ZONE]; note local time if varies) - Email 3: Final Push (6–9pm [TIME ZONE]; note local time if varies) For each email, include these components in this exact order: 1) Subject Line Options – 2 options, each 4–7 words 2) Preheader – 35–60 characters 3) Email Body – 150–220 words 4) CTA Button – 2–4 words linking to [DONATION LINK] 5) P.S. – one sentence 6) Social Share – one sentence inviting forward/share with [HASHTAGS] and [SOCIAL HANDLE] 7) Image Suggestion – one sentence with a recommended image and alt‑text (Email 1 and Email 3 only) Content Requirements (apply to all three emails) - Open with personalization using [FIRST NAME|"Friend"] - Lead with a 1–2 sentence impact mini‑story about [BENEFICIARY/PROGRAM] that includes [IMPACT UNIT] - State the campaign goal clearly: • Email 1: Introduce “[GOAL NUMBER] [GOAL TYPE]” • Email 2 and 3: Show progress with specific numbers (e.g., “127 of 500 donors so far — **25%** there” or “**$8,450** of **$25,000** raised”) - If [MATCH DETAILS] ≠ “NONE”: name the amount, source, and deadline; show how gifts are doubled/boosted until the stated deadline - If [MATCH DETAILS] = “NONE”: use a countdown to [DEADLINE TIME] and participation framing (“Add your name to today’s donor roll”) - Include one sentence noting that GivingTuesday gifts build momentum for year‑end, not replace it - Include social proof/community language (e.g., “Join 200 neighbors”) - Maintain one clear CTA only; no secondary asks - Signature from [FROM NAME], [TITLE] - Invite to forward/share with friends/family - Footer: tax‑deductibility with [EIN/LEGAL NAME], [PHYSICAL ADDRESS], and [UNSUBSCRIBE LINK] Email‑Specific Elements - Email 2 (Mid‑Day) Body: include one brief bulleted list with 3–5 bullets. Use bullets for any of: • Impact examples tied to [IMPACT UNIT] • Match/urgency status with numbers [... continued]

Use in:

Monthly Giving Pitch

The Prompt Create a donor-centered monthly giving appeal for [ORGANIZATION NAME] to convert recent one-time donors into sustainers.

The Prompt Create a donor-centered monthly giving appeal for [ORGANIZATION NAME] to convert recent one-time donors into sustainers. The monthly giving appeal should: - Be written for recent one-time donors in [CITY/COMMUNITY] who support [MISSION/CAUSE] - Deliver: 3 subject lines, 1 preview text (60–90 chars), and a 300–400 word body - Structure the body in this order: (1) Hook tied to [CURRENT NEED/SEASON]; (2) Why monthly matters for steady services; (3) Suggested monthly amounts [SUGGESTED AMOUNTS: e.g., 15/25/35] with a coffee comparison (e.g., “about [COFFEE COST]”); (4) Annual impact math for each amount using [IMPACT METRIC/UNIT COST EXAMPLES]; (5) Flexibility (“change or cancel anytime”); (6) Address “I already gave” graciously; (7) Benefits of joining [SUSTAINER PROGRAM NAME] ([BENEFITS LIST]); (8) 1–2 sentence donor quote: [DONOR TESTIMONIAL SNIPPET]; (9) Clear CTA line + button copy options (2–3) linking to [LINK]; (10) P.S. that reinforces ease/impact - Use [TONE]: FORMAL (professional, concise), WARM (friendly, grateful), or CASUAL (conversational, upbeat) - Write at a 6th–8th grade reading level; 1–2 sentence paragraphs; a few skimmable bullets - Emphasize reliability of monthly gifts (e.g., “keeps lights on, staff scheduled, clients served”) - Include optional fee note: invite ACH/bank transfer; offer “add $1–$2 to cover fees—totally optional” - Be donor-centered (“you”), concrete (name [PROGRAM EXAMPLE], cite [IMPACT METRIC]), and specific about outcomes this month - End with sign-off: [SIGNER NAME], [SIGNER TITLE], and a reply-to line for questions Aim for specificity, warmth, and clarity. Avoid jargon, guilt, crisis-only framing, or comparisons that disparage other services. Do not overpromise. Keep the monthly ask manageable, show annual impact math, and make flexibility explicit. The copy should be usable as both an email and donation page intro with minimal edits.

Use in:

Peer-to-Peer Fundraising Template

Create peer-to-peer fundraising message templates that volunteers can quickly personalize to invite their networks to donate to [ORGANIZATION NAME]...

Create peer-to-peer fundraising message templates that volunteers can quickly personalize to invite their networks to donate to [ORGANIZATION NAME]’s [CAMPAIGN/EVENT]. The templates should: - Provide 4 versions: (1) Email 180-220 words, (2) Text/DM 45-80 words, (3) Facebook/Instagram post 90-140 words with a simple image idea, (4) LinkedIn post 120-180 words. - Follow this order in each: (1) Why I’m involved (1-2 sentences), (2) 1-line org intro/what it does, (3) Specific impact ask with dollar handle ([IMPACT: $X = Y]), (4) Clear link early and again near the end, (5) Deadline/urgency, (6) Thanks + easy way to share. - Use [BRACKETED] prompts volunteers can fill in: [YOUR NAME], [RELATIONSHIP/WHY I’M INVOLVED – 1-2 sentences], [ORGANIZATION NAME], [PROGRAM/CAUSE], [IMPACT: $X = Y], [GOAL AMOUNT], [DEADLINE DATE], [MATCH INFO optional], [FUNDRAISING PAGE LINK – short], [CITY/COMMUNITY], [PHOTO ALT-TEXT], [PRONOUNS optional]. - Include 3 email subject lines (5-7 words each) and 3 text/DM openers. - Add a P.S. line in the email that restates the impact and link. - Include one follow-up/reminder message (60-100 words) and one thank-you/acknowledgment message (60-100 words) volunteers can send after gifts. - Tone options [TONE]: FORMAL (board/corporate—no emojis, full words), WARM (friends/family—friendly, 0-1 emoji), CASUAL (peers/social—conversational, 0-2 emojis). Apply consistently across versions. - Keep language concrete and human; use short sentences/paragraphs; scannable bullets OK in email. - Offer non-donation support option: [SHARE/ATTEND/LEARN MORE LINK]. - Add optional compliance line: “[ORGANIZATION NAME] is a [501(c)(3) STATUS]; gifts may be tax-deductible. [TAX ID optional].” - Sign-offs: [YOUR NAME], [RELATIONSHIP TO ORG], [CITY], [PRONOUNS optional]. Quality: Be specific (one clear $ ask and impact), people-first, and mobile-friendly. Avoid clichés (“now more than ever”), guilt/shame, acronyms/jargon, walls of text, or multiple competing CTAs. The final copy should be paste-ready with visible [BRACKETS] and a working link near the top.

Use in:

Year-End Campaign Email Series

(3-part) Year-End Fundraising Email Series (3-Part Campaign) Before You Begin - Gather These Details Required Information: - [ ] [ORGANIZATION NAME...

(3-part) Year-End Fundraising Email Series (3-Part Campaign) Before You Begin - Gather These Details Required Information: - [ ] [ORGANIZATION NAME] - [ ] [MISSION/CAUSE] - one sentence describing what you do - [ ] [PRIMARY CTA URL] - donation page link (to be used for all CTAs) - [ ] [TONE] - choose one: FORMAL (board/foundations; precise, restrained) / WARM (most donors; gracious, plainspoken) / CASUAL (peer-to-peer; friendly, energetic) - [ ] [SIGNER NAME] and [TITLE] - [ ] [DEADLINE DATE] and [TIMEZONE] (e.g., Dec 31, 11:59 p.m. [TIMEZONE]) - [ ] [TAX-DEDUCTIBLE LANGUAGE] and EIN Optional (recommended): - [ ] [PROGRAM/IMPACT EXAMPLE] - [ ] [MATCH DETAILS] (e.g., “All gifts doubled up to $XX,XXX through [DEADLINE DATE]”) - [ ] Suggested gift amounts [$X, $Y, $Z] tied to outcomes - [ ] [UTM CAMPAIGN/PARAMS] for all links - [ ] [CRM TAGS] naming convention - [ ] [FIRST NAME] merge field format and fallback (“Friend”) - [ ] [CITY] data availability - [ ] [LAST GIFT AMOUNT/DATE] availability Your Task Create a complete 3-email year-end fundraising campaign for [ORGANIZATION NAME] advancing [MISSION/CAUSE]. The series will deploy between December 1–31 and must be ready for copy/paste with minimal edits. Campaign Structure & Timing - Email 1 (Send Dec 1–10): Story-Driven Case for Support - Lead with impact and possibility - Introduce the year-end opportunity - Warm, invitational ask - Email 2 (Send Dec 15–23): Urgency + Social Proof - Reinforce deadline and momentum - Show community participation and progress - Stronger, more direct ask - Email 3 (Send Dec 28–31): Final Push - Anchor to tax-deductible deadline - Last-chance messaging - Clear, confident urgency with gratitude Note: If starting after Dec 10, adjust cadence accordingly and include recommended send dates within the output. Format Requirements for Each Email Length: - 200–300 words per email body Required Elements: - 3 subject line options (vary angles: impact, urgency, curiosity) - 1 preheader (35–80 characters, complements subject) - From line: [SIGNER NAME], [TITLE] - Opening hook (1–2 compelling lines) - Body copy (short paragraphs, scannable, mobile-friendly) - Primary CTA using [PRIMARY CTA URL] repeated 2–3 times with descriptive link text (avoid “click here”) - P.S. line (optional for Email 1; recommended for Emails 2–3 to reinforce urgency, add personal note, or highlight match) - Signature block: [SIGNER NAME], [TITLE] Content Elements to Include: - 1 concrete impact statistic - 1 short beneficiary or partner quote (2–3 sentences max) - Brief program example from [PROGRAM/IMPACT EXAMPLE] - If available: [MATCH DETAILS] with a visible countdown to [DEADLINE DATE/TIMEZONE] - Suggested amounts [$X, $Y, $Z] tied to tangible outcomes - [TAX-DEDUCTIBLE LANGUAGE] and EIN (at minimum in Email 3; can appear in all) Personalization: - Use [FIRST NAME|Friend] with graceful fallback - Incorporate [CITY] naturally if available - Reference [LAST GIFT AMOUNT/DATE] with appreciation if available - Never expose missing data Image Guidance: - Suggest 1–2 image placements per email (e.g., header image; mid-body pull-quote image) - Provide descriptive alt-text for each (e.g., “Photo of student reading in newly renovated library”) Tone & Voice Guidelines Selected Tone: [TONE - FORMAL/WARM/CASUAL] - Maintain consistent voice across all three emails - Balance gratitude and urgency - Ask clearly and confidently - Avoid guilt-based or crisis-only framing - Be concrete, human, and specific - Avoid clichés (“make a difference,” “give back”), jargon, and corporate-speak - Each email must stand alone yet build momentum across the arc Segmentation Variants For each email, provide the FULL BASE VERSION first, then include these targeted variants: 1) [DONORS WHO ALREADY GAVE] - Provide: Alternative subject line + opening paragraph - Lead with genuine thanks and recognition (reference [LAST GIFT AMOUNT/DATE] if available) - Offer a soft upgrade option or invite to share the campaign [... continued]

Use in:

Cultivation Strategy Plan

Develop a Major Donor Cultivation Strategy Plan for [ORGANIZATION NAME] to engage [PROSPECT NAME] over [TIMELINE MONTHS] months toward [PROPOSED AS...

Develop a Major Donor Cultivation Strategy Plan for [ORGANIZATION NAME] to engage [PROSPECT NAME] over [TIMELINE MONTHS] months toward [PROPOSED ASK RANGE] for [PROJECT/PURPOSE]. The Cultivation Strategy Plan should: - Use sections in this order: Header; 1) Prospect Snapshot; 2) Cultivation Goal & Case; 3) Strategy & Timeline; 4) Touchpoint Plan; 5) Engagement Signals & Decision Gates; 6) Roles & Coordination; 7) Risks/Contingencies; 8) Tracking & Next Steps; 9) Draft Ask Path & Natural Moment. - Prospect Snapshot: [ESTIMATED CAPACITY], affinity indicators, prior giving to us/others, decision-making process, known connectors, preferred communication. - Touchpoint Plan: outline 5–8 meaningful touches over 6–12 months; for each include objective, donor value, format (meeting/site visit/call/peer intro/salon/program update), owner ([PRIMARY RELATIONSHIP OWNER]/ED/Board/volunteer), date window, materials, and one qualification question. (Example: Site visit with program lead to observe [PROGRAM]; objective: connect impact to values; question: “How do you assess philanthropic priorities this year?”) - Mix formats; each touch must deliver substance (impact data, beneficiary voice, field insight, invitation to advise), not “just checking in.” - Roles & Coordination: when/why to involve [ED/BOARD INVOLVEMENT]/volunteer solicitor; briefing notes and follow-up responsibilities. - Engagement Signals & Decision Gates: define readiness (responsiveness, outcome questions, budget curiosity, referral offered) and what triggers the ask. - Draft Ask Path: framing for [PROPOSED ASK RANGE], designation options, likely objections with 1–2 sentence responses; identify the natural ask moment tied to a specific touch/event. - Tracking: specify updates/tasks in [SYSTEM/CRM], fields to update, and simple metrics (meeting secured/site visit completed/pre-ask commitment). - Capacity-aware: realistic for team of [TEAM SIZE]; include low-cost options and time estimates per touch. - Include key dates: [KEY DATES/EVENTS] and any deadlines (board meetings, fiscal year-end). - Word count: 600–900 words; internal planning document. - Tone: [TONE: FORMAL (board-ready, precise) / WARM (relationship-centered, professional) / CASUAL (clear, small-shop shorthand)]. - Header lists: Prepared by [PRIMARY RELATIONSHIP OWNER]; Reviewed by [ED/BOARD LEAD]. Quality: Be donor-centered, concrete, and sequenced. Avoid clichés, guilt appeals, org-centric jargon, and vague “touches.” Each touch must have a purpose, owner, and date window. Common pitfalls to avoid: involving ED/Board too early/late, stacking asks without value, or failing to document next steps within 48 hours.

Use in:

Donor Prospect Research Brief

Create a one-page Donor Prospect Research Brief for [ORGANIZATION NAME] to inform major gift cultivation of [PROSPECT NAME] using publicly availabl...

Create a one-page Donor Prospect Research Brief for [ORGANIZATION NAME] to inform major gift cultivation of [PROSPECT NAME] using publicly available information only. The brief should: - Use this order and headings: 1) Header, 2) Snapshot, 3) Professional & Wealth Indicators, 4) Philanthropy & 990 Data, 5) Connections to [ORGANIZATION NAME], 6) Interests/Passions, 7) Cultivation Plan, 8) Risks/Considerations, 9) Sources, 10) Update Log. - Header: Prospect name (incl. preferred name/pronouns), city/state, employer/title, connection level to org, Prepared by [NAME/ROLE], Date [DATE], For Internal Use Only. - Snapshot (4 lines max): Estimated giving capacity range with confidence (Low/Med/High) + basis; top 2-3 affinity indicators; readiness/timing signals; recommended initial ask range tied to [PROGRAM/CASE]. - Professional & Wealth Indicators: current/past roles, business ownership, notable liquidity proxies (public company equity, real estate assessed values, exits) with brief basis. Avoid speculation. - Philanthropy & 990 Data: top 3-5 gifts/orgs (size/recency when findable), board service, family foundation notes, cite 990/990-PF (org/year/URL). - Connections to [ORGANIZATION NAME]: alumni/volunteer links, shared networks; list 2-3 warm intro pathways (Name—relationship—how to approach). - Interests/Passions: causes, issue areas, quotes/memberships that signal affinity. - Cultivation Plan: 3-5 specific next steps, likely channel, timing window, entry points (events, site visit, program leader). - Risks/Considerations: reputational issues, conflicts, privacy flags (no sensitive categories). Note “Unknown” where data is absent. - Sources: 5-8 citations with URLs and access dates (LinkedIn, news, company site, Guidestar/Candid, IRS 990-PF, SEC, real estate records). - Update Log: blank lines for date/action/outcome. - Length: 300–450 words; concise bullets; no walls of text. - Tone: [TONE]=FORMAL (board/exec-ready), WARM (internal collaboration, default), CASUAL (working notes). Quality: Be concrete and verifiable; quantify where possible; tie capacity to visible indicators; do not guess net worth or use stereotypes; avoid jargon/clichés; flag “Unverified” if not sourced. If [KNOWN DETAILS OR LINKS] are provided, prioritize them.

Use in:

Major Donor Meeting Prep Notes

You are creating Major Donor Meeting Prep Notes for a nonprofit development team.

You are creating Major Donor Meeting Prep Notes for a nonprofit development team. This is a confidential, 1-page briefing to prep staff, board, or the Executive Director for a donor meeting. Estimated prep time: 15–20 minutes How to use 1) Fill the Intake Form below. 2) Paste any CRM notes/research under “Background Block.” 3) Select a Tone. 4) Submit; if data is missing, produce notes and mark gaps as [TO VERIFY]. Intake Form (copy/paste and complete) - Organization: [ORGANIZATION NAME] - Donor: [DONOR NAME] - Meeting date/time/location: [DATE / TIME / LOCATION] - Meeting length: [15 / 30 / 45 / 60 min] - Meeting type: [CULTIVATION / SOLICITATION / STEWARDSHIP / SITE VISIT / FIRST-TIME] - Attendees (names/titles) + roles: [Lead Asker] [Timekeeper] [Note-taker] - Authority to commit (decision rights): [WHO can say yes to what] - Primary goal (specific): [OUTCOME] - If solicitation: Ask amount/range [$], purpose [PROGRAM/PROJECT], timing [WHEN], who asks [NAME], pause plan [min. 5–10 seconds] - Tone: [FORMAL / WARM / CASUAL] - Attachments (list + links or “summary 1–2 bullets + link”): [FILENAME + URL] - Background Block (paste CRM notes/research): [TEXT] - Sensitivities/red flags: [NOTES] - Recognition preferences: [NOTES] Output requirements - 250–350 words, bullets only, no long paragraphs - Concrete, donor-centric, plain language; no jargon/clichés - Mark unknowns as [TO VERIFY]; do not invent facts - Fit to 1 page; optimize for skimming by a busy ED in under 3 minutes Prioritization by meeting length - 15 min: Include Header; Objective & Strategy (with Ask if applicable); 3 Talking Points; 4 Questions; Post-Meeting Plan. Condense Snapshot to 1–2 bullets. Omit Logistics unless critical. - 30–60 min: Include all required sections; add Relationship History, Likely Concerns, What Not to Say, and brief Logistics with agenda. Create the 1-page briefing with these sections (omit optional items if needed to meet word limit) 1) Header (always) - Date/time/location; attendees + roles; authority to commit; primary desired outcome 2) Donor Snapshot (3–4 bullets; 1–2 bullets if 15 min) - Background/connection; last gift/lifetime total; capacity indicators + vehicles (DAF/stock/cash); motivations aligned to mission/program 3) Relationship History (2–3 bullets; skip for first-time) - Recent touchpoints; who knows them; invites/stewardship; sensitivities 4) Meeting Objective & Strategy (always) - Primary goal; 1–2 acceptable fallbacks (e.g., site visit, spouse/advisor intro, multi-year exploration) - If solicitation: The Ask (exact amount, purpose, timing, who asks, exact phrasing, pause plan) 5) Tailored Talking Points (3–5 bullets) - Beneficiary-centered impact tied to program/project; include 1–2 proof points (metric/story) 6) Questions to Ask (4–6 open-ended) - Interests, timing, decision process, asset preference (DAF/stock), recognition, who else to involve 7) Likely Concerns + Responses (3–4 pairs; include if applicable) - Short, respectful replies that bridge back to impact 8) What NOT to Say (3–5 bullets; optional but recommended) - Confidential issues, crisis framing, politics, overpromising, jargon 9) Logistics & Choreography (brief; include agenda for 30–60 min) - 20–45 min agenda; materials to bring; follow-up artifacts; accessibility note (print at 12–14 pt, high contrast if sharing) 10) Post-Meeting Plan (always) - Thank-you plan (owner, within 48 hours); next steps with owners/due dates; CRM updates (contact report, next step, stage) Footer - Prepared by [STAFF NAME/TITLE] on [DATE] — Version [X] (Updated [DATE]) Conditional guidance - First-time: Skip Relationship History; add “Research Summary” bullet (public sources); focus Questions on discovery - Cultivation (no ask): Emphasize Questions/next engagement; skip Ask - Stewardship: Add “Impact Update” bullets tied to donor’s last gift; lead with gratitude Example snippets (for reference—adapt and keep concise) [... continued]

Use in:

Personalized Major Gift Proposal

BEFORE YOU START: Quick readiness check - Can you clearly answer: (1) Why this donor?

BEFORE YOU START: Quick readiness check - Can you clearly answer: (1) Why this donor? (2) Why this amount? (3) Why now? - If not, pause and gather more information before running this prompt. INFORMATION GATHERING CHECKLIST (mark what you have) REQUIRED: - [ ] [DONOR NAME] and [DONOR INTERESTS/PRIORITIES] (2–4 themes, e.g., first-gen students, climate resilience) - [ ] [PROJECT NAME] and [TOTAL PROJECT COST] - [ ] [PRIMARY ASK AMOUNT] and [YEARS] (pledge period) - [ ] [ORGANIZATION NAME] and [MISSION/FOCUS] - [ ] [SIGNER NAME, TITLE] and [CONTACT INFO] (email and phone) RECOMMENDED: - [ ] [CURRENT FUNDS RAISED] and [FUNDING GAP] - [ ] [ALT ASK 1] and [ALT ASK 2] (typically ~60% and ~150% of primary ask) - [ ] Donor touchpoints in past 12–18 months (gifts, visits, meetings, event attendance, emails) - [ ] [REPORTING CADENCE] (quarterly, biannually, annually) - [ ] [RECOGNITION OPTIONS] and [PRIVACY PREFERENCE] - [ ] [GEOGRAPHY/COMMUNITY] where the project operates OPTIONAL (enhances personalization): - [ ] [OPTIONAL: ANECDOTE/STORY] (2–3 sentences linking donor to mission) - [ ] [MATCH/CHALLENGE INFO] (source, timing, ratio, cap) - [ ] [MEETING DATE/DEADLINE] - [ ] [ED/BOARD APPROVAL STATUS] (e.g., ED approved; Board Dev. Committee endorsed) - [ ] [PER-UNIT COST EXAMPLES] (2–3 concrete items) - [ ] Key risks and mitigations - [ ] [FORMAT PREFERENCE: formal letter / PDF proposal / email proposal] - [ ] [TONE: FORMAL / WARM / CASUAL] PROMPT: Draft a personalized major gift proposal for [DONOR NAME] in support of [PROJECT NAME] at [ORGANIZATION NAME], tailored to [DONOR INTERESTS/PRIORITIES] and our work in [GEOGRAPHY/COMMUNITY]. OVERALL SPECIFICATIONS: - Length: For asks $50K+: 1,100–1,500 words. For asks under $50K: 800–1,000 words (combine sections as noted below). - Format: [FORMAT PREFERENCE: formal letter / PDF proposal / email proposal – default to formal letter]. - Visual/formatting: - Use clear section headings in Title Case (exact titles listed below). - Single-spaced, one blank line between paragraphs; bullet lists where specified. - For formal letter/PDF: include date and inside address block; place logo on letterhead if available. - For email: include a concise subject line and greeting; omit mailing address block. - Tone: [TONE – default to WARM]. Reading level: ~10th grade. Short paragraphs (2–4 sentences), active voice, specific numbers. - Personalization: Reference recent donor touchpoints (past 12–18 months) and make explicit links to [DONOR INTERESTS/PRIORITIES]. - If any data is missing, insert a clear placeholder [TK: describe missing item] and generate realistic, good-faith examples (especially for per-unit costs, outcomes, and milestones) based on the project type. STRUCTURE (use these headings and order) 1. Cover Letter (120–180 words) - Link [DONOR NAME]’s connection to [MISSION/FOCUS] and our shared values. - Reference a recent touchpoint (visit, gift, event) from past 12–18 months. - [OPTIONAL: Weave in ANECDOTE/STORY in 1–2 sentences]. - Preview the invitation to partner (do not state the ask amount yet). 2. Donor Alignment (150–200 words) - 3–5 bullet points mapping the project to [DONOR INTERESTS/PRIORITIES]. - Use specific touchpoints (date/year and nature of engagement). - Make explicit connections (e.g., “Your 2023 scholarship gift supporting first-generation students aligns with this project’s focus on …”). 3. Project Overview (250–350 words) Include: - What: Concise description of the project/program and scope. - Why now: Opportunity or timing without alarmist tone. - Who benefits: Define target population with numbers and geography (e.g., “120 formerly incarcerated adults annually in Maricopa County”). - How we deliver: Key activities and approach. - Equity/access considerations: How the project addresses barriers or advances inclusion. - Example: “Weekend and evening hours reduce access barriers for caregivers.” - Risks and mitigations: 1–2 realistic challenges and responses. [... continued]

Use in:

Donor Upgrade Ask

Monthly) Create a donor upgrade ask to convert a recent one-time donor to a monthly sustainer for [ORGANIZATION NAME].

Monthly) Create a donor upgrade ask to convert a recent one-time donor to a monthly sustainer for [ORGANIZATION NAME]. The [content type] should: - Specify channel: [CHANNEL: EMAIL/LETTER/SMS]. If email, include a compelling subject line (3 options) and preheader; if letter, include a headline. - Open with warm thanks referencing [DONOR FIRST NAME], their [LAST GIFT AMOUNT], what it supported ([PROGRAM/CAUSE]), and a specific result ([RESULT/IMPACT FROM LAST GIFT]); mention timing ([TIMING/TRIGGER]). - Introduce monthly giving as “spreading your impact throughout the year,” emphasizing donor control and ease: [FLEXIBILITY LANGUAGE: pause/adjust/cancel anytime]. - Present simple math with 2–3 options: [MONTHLY AMOUNT OPTIONS] and their annual totals [ANNUAL TOTALS], tied to concrete outcomes [IMPACT MATH EXAMPLE]. - Add social proof to reduce risk: [SOCIAL PROOF] (e.g., “Join 200+ neighbors giving monthly” or a short quote). - Address top objections succinctly: “I already gave” (affirm impact, monthly keeps it going) and “another subscription” (no contract, change anytime, receipts for taxes). - Include a clear CTA with button-style language [CTA BUTTON TEXT] linked to [EASY ENROLLMENT LINK]; provide a plain-text fallback link. - Offer an optional gentle nudge (e.g., “[MATCH OFFER]” or “Start by [SOFT DEADLINE/DATE]”) without pressure. - Close with gratitude and a donor-first frame (“you make this possible”); invite replies for questions. - Add a P.S. restating flexibility, suggesting a modest entry amount (e.g., $15/month), and repeating the link. - Length: 250–350 words, 6–8 short paragraphs, 6th–8th grade reading level, mobile-friendly, skimmable. - Tone: [TONE] = FORMAL (precise, respectful), WARM (friendly, relationship-centered), CASUAL (concise, plainspoken/SMS-friendly). Sign by [SIGNER NAME], [SIGNER TITLE], with [REPLY CONTACT]. Quality principles: Be donor-centric (use “you”), specific, and concrete; avoid jargon, guilt, or clichés. Use real numbers and plain language. Keep the ask modest and flexible. If any bracketed data is unknown, write a neutral, truthful alternative. Ensure links are clear and easy to tap on mobile.

Use in:

Lapsed Donor Re-Engagement Email

Email Write a lapsed donor re-engagement email for [ORGANIZATION NAME] to donors who last gave [LAPSE WINDOW].

Email Write a lapsed donor re-engagement email for [ORGANIZATION NAME] to donors who last gave [LAPSE WINDOW]. Output Format: 1) Subject Lines: 3 options, labeled A/B/C 2) Preheader Text: 1 option 3) Email Body: follow the structure below 4) Compliance Footer Email Body Structure: - Greeting with [DONOR FIRST NAME] - Acknowledgment paragraph (warm opening + gratitude for past support; reference [LAST GIFT MONTH/YEAR]) - Mission refresh + wins paragraph - Re-entry ask paragraph with single CTA button - Alternative engagement option - Reassurance line - Closing + signature ([SIGNER NAME], [SIGNER TITLE]) - Optional P.S. (include only if [MATCH DETAILS] is provided) Requirements: Subject Lines & Preheader: - Provide 3 curiosity-forward subject lines (40–55 characters each, labeled A/B/C) for easy A/B testing - Provide 1 preheader/preview text (60–90 characters) - Tone: inviting and warm—avoid desperation or guilt - Focus on curiosity, gratitude, and forward momentum Email Specifications: - Total length: 200–260 words - Reading level: Grade 6–8 - Paragraphs: 1–2 sentences each, skimmable - Mobile-friendly: short lines, clear hierarchy, plain language Content Elements: 1) Opening (Warm Acknowledgment): - “We’ve missed you” tone - Reference [LAST GIFT MONTH/YEAR] - Credit the donor for impact (no guilt or blame language) 2) Mission Refresh + Wins: - 1–2 sentence reminder of the mission - 1–2 concrete wins since their last gift (use specific numbers or a brief story) - Concrete wins examples: “500 meals delivered,” “opened a new tutoring site,” “92% of participants secured housing” - If [AREA/PROGRAM] is specified: tie the wins to that program - If [AREA/PROGRAM] is “general” or blank: use organization-wide impact (e.g., “Across all our programs, we…”) 3) Personalization (with fallbacks): - [DONOR FIRST NAME] → use “Friend” if unknown - [LAST GIFT AMOUNT] → use “your generous gift” if unknown - [LAST GIFT MONTH/YEAR] → use “when you last supported us” if unknown - [AREA/PROGRAM] → default to organization-wide impact if unknown - Use inclusive language: “your past support,” “donors like you” 4) Re-Entry Ask: - Offer a modest suggested gift: [SUGGESTED AMOUNT] or a monthly option [MONTHLY AMOUNT] - Include one clear CTA button: [CTA BUTTON TEXT] linking to [DONATION PAGE URL] - CTA button best practices: 2–4 words, action-oriented (e.g., “Give Again Today,” “Renew Support”) 5) Alternative Engagement (No-Pressure): - Offer ONE gentle alternative: either a 1-question check-in [SURVEY LINK] OR update preferences [PREFERENCES LINK] - Frame as helpful: “so we send what matters to you” - Do not include multiple competing options 6) Reassurance Line: - Include: “If your gift is on its way or you’ve already renewed, thank you—please disregard this message.” 7) Closing: - Express appreciation and forward-looking hope - Sign with [SIGNER NAME], [SIGNER TITLE] 8) Optional P.S.: - Include ONLY if [MATCH DETAILS] is genuine (e.g., real match or true deadline) - Never fabricate urgency - One sentence, max 20 words Tone Options: - [TONE] = FORMAL: Polished, professional, funder-appropriate - [TONE] = WARM: Friendly, community-centered (DEFAULT—use if not specified) - [TONE] = CASUAL: Conversational, personal (only if brand allows) Compliance: - Include [UNSUBSCRIBE LINK] - Include organization contact info (address/phone/email) placeholders - Follow CAN-SPAM requirements Quality Standards: - Donor-centric: focus on their impact, not organizational neediness - Specific: concrete details, not vague claims - Human: plain language, warm and respectful - Avoid: guilt language, neediness (“we’re desperate”), clichés, heavy jargon, urgency gimmicks, multiple competing asks - Subject lines: curiosity-driven; body: clear, grateful; one primary action, one gentle alternative Example Inputs: [ORGANIZATION NAME]: “River Valley Food Bank” [LAPSE WINDOW]: “18–24 months” [LAST GIFT MONTH/YEAR]: “March 2022” [LAST GIFT AMOUNT]: “$50” [... continued]

Use in:

Thank You Letter - First-Time Donor

Draft a personalized first-time donor thank-you letter for [ORGANIZATION NAME] to send within 48 hours of [DONOR NAME]’s gift.

Draft a personalized first-time donor thank-you letter for [ORGANIZATION NAME] to send within 48 hours of [DONOR NAME]’s gift. The letter should: - Be 150-250 words and feel human, warm, and concise. - Use [TONE]: FORMAL (polished, respectful), WARM (friendly, heartfelt), or CASUAL (conversational, approachable). Default: WARM. - Open with the donor’s name and clear acknowledgment of the gift: “[DONOR NAME], thank you for your gift of [AMOUNT] received on [DATE RECEIVED].” - Include a one-line mission anchor: “[ORGANIZATION NAME] [MISSION ONE-LINER].” - Specify concrete impact tied to the gift and program: “[PROGRAM/IMPACT AREA]” and a proof point ([IMPACT PROOF POINT]). If no data is provided, describe qualitative impact without inventing numbers. Example: “Your gift helps a new mom meet with a lactation counselor this week.” - Welcome them as a first-time supporter and, if known, reference context: “[HOW THEY CAME TO US: event/peer-to-peer/online].” - Keep donor-centric language (aim for a ‘you’ to ‘we’ ratio of ~2:1), simple sentences, and 6th–8th grade readability. - Avoid asks for another gift; you may include one non-monetary next step (choose one): invite to [TOUR/NEWSLETTER/SOCIAL HANDLE/UPCOMING VOLUNTEER ORIENTATION]. - Use this order: greeting; warm thanks + gift details; mission anchor; impact statement; welcome line; brief human detail/story image; gentle non-ask next step; sincere closing; signature. - Include an optional acknowledgment line if needed: “Your contribution is tax-deductible; no goods or services were provided.” [ADJUST FOR YOUR JURISDICTION] - End with a real sign-off from leadership: [SIGNER NAME], [TITLE], [DIRECT CONTACT INFO]. Optional P.S. reinforcing impact or the non-ask next step. - If any bracketed detail is unknown, omit that sentence rather than guessing. Quality matters: Be specific, human, and sincere. Avoid clichés (“on behalf of…,” “we couldn’t do it without you”), jargon, acronyms without explanation, emojis, or multiple exclamation points. The goal is to make the donor feel seen, know their impact, and feel welcomed—without being asked for more.

Use in:

Thank You Letter - In-Kind Donation

Draft a donor-ready thank you letter acknowledging an in-kind (non-cash) gift for [ORGANIZATION NAME].

Draft a donor-ready thank you letter acknowledging an in-kind (non-cash) gift for [ORGANIZATION NAME]. The letter should: - Be 150-250 words in 2-4 short paragraphs, suitable for email or print on letterhead. - Follow this order: 1) Warm opening with donor name, 2) Specific gift details, 3) Immediate use and impact, 4) IRS-compliant receipt language, 5) Next step/invitation, 6) Close/signature. - Name the gift precisely: [GIFT DESCRIPTION], [QUANTITY/SPECS/BRAND], received on [GIFT DATE]. If the donor provided a value, include: “Your stated fair market value: [DONOR-STATED VALUE].” Otherwise omit any dollar amount. - Explain immediate use: [PROGRAM/DEPARTMENT], and a concrete outcome (e.g., “[PEOPLE SERVED],” “[HOURS OF SERVICE ENABLED],” or “[COSTS AVOIDED]”). - Tie impact to mission in one sentence: [MISSION ONE-LINER]. - Include IRS receipt language: “No goods or services were provided in exchange for this contribution. [ORGANIZATION NAME] does not assign a monetary value to in-kind gifts. Date received: [GIFT DATE]. EIN: [EIN].” - Acknowledge volunteer time separately if applicable: “[HOURS] volunteer hours on [DATE] (not tax-deductible) meaningfully advanced this effort.” - Offer a relationship next step (tour, brief update, or recognition with consent): “With your permission, we’ll recognize you as [RECOGNITION NAME].” - Use [TONE: FORMAL (board-appropriate), WARM (friendly, professional), CASUAL (conversational, community vibe)] at a 6th–8th grade reading level. - Close with contact info and signature: [CONTACT NAME/TITLE], [EMAIL], [PHONE]; signed by [SIGNER NAME], [TITLE]. Keep it concrete and donor-centric; avoid clichés (“priceless,” “game-changer”), jargon, or tax advice. Do not invent values; omit any field you don’t have. Match the warmth you’d use for a cash gift while keeping compliance language clear and concise.

Use in:

Thank You Letter - Major Donor

Draft a highly personalized major-donor thank-you letter for [ORGANIZATION NAME] that a busy leader can send the same day a gift is received.

Draft a highly personalized major-donor thank-you letter for [ORGANIZATION NAME] that a busy leader can send the same day a gift is received. The letter should: - Be 250-350 words, one page, 3-5 short paragraphs, readable at Grade 8-10 level. - Include this order/structure: [DONOR ADDRESS BLOCK] > [DATE] > [SALUTATION] > Opening that references the call on [CALL DATE] > Clear thanks acknowledging [AMOUNT] and [GIFT TYPE] received on [DATE OF GIFT] > Specifics on how funds will be used for [PROGRAM/PROJECT] in [LOCATION] > Concrete early impact (numbers, timeline, example) > What happens next and when > Closing that frames partnership > [SIGNATURE BLOCK] > P.S. with a human, relational note. - Personalize with 1-2 details from cultivation: [SPECIFIC DETAIL FROM CONVERSATION] and [DONOR INTEREST/VALUES]. - Describe allocation and impact with specifics (e.g., “Your [AMOUNT] funds [X UNITS/SERVICES] by [MONTH/YEAR], serving [# PEOPLE/FAMILIES].”). - Name beneficiaries respectfully (people-first language), center community impact, not donor heroics. - Include stewardship plan and timing: [FOLLOW-UP ACTION] by [FOLLOW-UP DATE] (e.g., site visit, impact brief, photo update). - Confirm public recognition preference: “We will list you as [RECOGNITION NAME] unless you prefer anonymity.” - Note receipt handling without being transactional: “A formal receipt will arrive separately from our finance team.” - Use [TONE]=FORMAL (conservative, honorific, boardroom-ready) / WARM (professional, relational, gracious) / CASUAL (first-name, friendly, still respectful). - Author and sign from [SIGNER NAME], [SIGNER TITLE] (ED or Board Chair); optional co-sign by [CO-SIGNER NAME/TITLE]. Include direct contact line. - If any bracket is not provided, omit it gracefully. Quality: Make it specific, human, and partnership-oriented; avoid clichés (“game-changer”), jargon (“capacity-building”), exclamation overload, and any new solicitation. Reflect the same-day call, show exactly “what your gift makes possible,” and set one clear next step with a date.

Use in:

Thank You Letter - Mid-Level Donor

Create a personalized mid-level donor thank-you letter that a small nonprofit can send quickly while still feeling bespoke.

Create a personalized mid-level donor thank-you letter that a small nonprofit can send quickly while still feeling bespoke. The thank-you letter should: - Use these inputs: [ORGANIZATION NAME], [MISSION STATEMENT (1 sentence)], [DONOR NAME], [AMOUNT], [GIFT DATE], [PREVIOUS GIFT AMOUNT/DATE or “N/A”], [YEARS GIVING], [DONOR INTEREST AREA], [PROGRAM/IMPACT EXAMPLE], [IMPACT UNIT + COST (e.g., “$50 = one counseling session”)], [CITY/REGION], [NEXT TOUCHPOINT (e.g., program tour date/report month/event invite)], [FORMAT: LETTER/EMAIL], [TONE], [SIGNER NAME], [SIGNER TITLE], [PREFERRED SIGN-OFF]. - Length: 200–300 words for the main letter. - Tone options [TONE]: FORMAL (polished, restrained), WARM (professional and personable—default), CASUAL (conversational, friendly). - If [FORMAT: EMAIL], include a 4–7 word subject line; if LETTER, omit subject. - Follow this order: salutation; immediate thanks with [AMOUNT] and [GIFT DATE]; acknowledge upgrade and/or [YEARS GIVING]; 1–2 concrete impact sentences tied to [PROGRAM/IMPACT EXAMPLE] and simple math using [IMPACT UNIT + COST]; brief mission alignment; authentic human detail (no client identifiers if sensitive); mention [NEXT TOUCHPOINT] without asking for money; invitation to connect; closing and signature. - Make it donor-centered (use “you/your” more than “we/our”); plain language (grade 7–9 readability). - Localize with [CITY/REGION] if provided. - Include an optional P.S. that reinforces impact or the upcoming touchpoint (no solicitation). - Provide a 1–2 sentence phone call script for a follow-up within 1 week. - Provide a 1–2 sentence handwritten note version for card/enclosure. - Avoid clichés (“valued partner,” “make a difference”), jargon, guilt or savior language, passive voice, multiple exclamation points, and any links or asks. Quality bar: Specific, accurate, and human. Double-check names, amounts, dates, and impact math. Mid-level donors must feel seen: reference their history, show tangible outcomes at their giving level, and clearly signal the next touchpoint—without turning this into another ask.

Use in:

Thank You Letter - Monthly Donor

MONTHLY DONOR THANK-YOU LETTER GENERATOR Write a [FORMAT: EMAIL/PRINT LETTER] thank-you for a monthly donor.

MONTHLY DONOR THANK-YOU LETTER GENERATOR Write a [FORMAT: EMAIL/PRINT LETTER] thank-you for a monthly donor. Touchpoint: [ENROLLMENT/QUARTERLY CHECK-IN/ANNIVERSARY] QUICK START: MINIMUM REQUIRED FIELDS - [FORMAT], [DONOR FIRST NAME], [MONTHLY AMOUNT], [ORGANIZATION NAME], [PROGRAM/CAUSE], [SIGNER NAME], [TITLE] REQUIRED FIELDS (fill these in) - [DONOR FIRST NAME] → e.g., "Maria" - [MONTHLY AMOUNT] → e.g., "$25" or "twenty-five dollars" - [GIFT START DATE or # OF MONTHS] → e.g., "since March 2024" or "for 6 months" - [ORGANIZATION NAME] - [PROGRAM/CAUSE] → e.g., "literacy tutoring" or "meal distribution" - [CITY/COMMUNITY] → e.g., "East Portland" or "rural Appalachia" - [SUSTAINER NAME/TIER] → e.g., "Steady Circle" or "Monthly Champions" - [UPDATE OPTIONS: PORTAL LINK/EMAIL/PHONE] - [SALUTATION] → e.g., "Dear," "Hello," "Good afternoon," - [SIGNER NAME], [TITLE] - [CONTACT EMAIL/PHONE] LETTER REQUIREMENTS Length and tone - 150–200 words total - Tone: [FORMAL (reserved, donor/board-facing) / WARM (default, friendly and professional) / CASUAL (chatty, youth-oriented)] - Keep it warm, concise, and low-pressure; no fundraising ask Opening - Use [SALUTATION] with [DONOR FIRST NAME] - Acknowledge their [MONTHLY AMOUNT] monthly gift and [GIFT START DATE or # OF MONTHS] Body (include all) 1) Stability language - Use 1–2 phrases such as “dependable,” “steady,” or “sustained” to show how monthly gifts help [ORGANIZATION NAME] plan confidently 2) Concrete micro-story - Include one tangible impact detail tied to [PROGRAM/CAUSE] in [CITY/COMMUNITY] - Example format: “[MONTHLY AMOUNT] covers [SPECIFIC UNIT/OUTCOME].” Keep it human-scale and specific 3) Cumulative annual impact - Translate [MONTHLY AMOUNT] x 12 into meaningful outcomes - Format: “Across a year, your steady support means [ANNUALIZED IMPACT/OUTCOMES].” 4) Community recognition - Recognize them as part of your sustainer community: “[SUSTAINER NAME/TIER]” with inclusive, low-key pride (no upgrade ask) 5) Flexibility reassurance - Briefly state they can change amount, update payment method, or pause anytime via [UPDATE OPTIONS: PORTAL LINK/EMAIL/PHONE] 6) Optional next step (choose one; user selects) - Offer ONE non-monetary engagement option [USER SELECTS ONE: update communication preferences / read latest impact story / schedule a site tour / explore volunteer opportunities] - No fundraising link Closing - End with sincere appreciation - Sign from [SIGNER NAME], [TITLE] - Include [CONTACT EMAIL/PHONE] for easy help FORMAT-SPECIFIC REQUIREMENTS If EMAIL - Subject line: 45–60 characters, warm and specific - Preview text: 50–90 characters, extends the subject line - Example: - Subject: “Thank you for 6 months of steady support, Maria” - Preview: “Your $25/month is fueling literacy tutoring in East Portland.” If PRINT LETTER - Include a brief RE line (e.g., “RE: Your Monthly Gift”) - Add a soft P.S. with one of: [TAX RECEIPT REMINDER/PORTAL UPDATE LINK/CONTACT FOR QUESTIONS] QUALITY STANDARDS Do - Use specific, human language and real numbers - Show tangible outcomes and a clear annualized impact - Keep pride inclusive and tone authentic to your organization Avoid - Clichés: “game-changer,” “we couldn’t do it without you,” “make a difference” - Jargon or corporate buzzwords - Exclamation overuse (max 1 total) - Any upgrade ask, additional donation request, or fundraising link - Generic platitudes—be concrete Bad example (do not emulate) “Dear Friend, Your monthly gift is a game-changer! We couldn’t do it without you! Please increase your gift today to make an even bigger difference.” USAGE NOTE Best used at enrollment and then quarterly. Vary the micro-story each quarter to prevent repetition while reinforcing steadiness and cumulative impact. The goal is retention through appreciation, not an ask. OUTPUT FORMAT Provide text ready to copy-paste into [email platform/letterhead] with minimal formatting adjustments.

Use in:

Thank You Letter - Tribute/Memorial Gift

Gift Tribute/Memorial Gift Thank-You Letter Generator Purpose Create two ready-to-send letters acknowledging a tribute or memorial gift—one to th...

Gift Tribute/Memorial Gift Thank-You Letter Generator Purpose Create two ready-to-send letters acknowledging a tribute or memorial gift—one to the donor and one to notify the honoree’s family or honoree (if applicable). Outputs should be dignified, donor-centered, and immediately usable for print or email. What to Produce 1) Donor Thank-You Letter (150–200 words) 2) Family Notification Note (80–120 words; only if family notification requested) 3) Two email subject lines per letter (6–10 words each) 4) One recipient address block per letter (for mailing labels or email addressing) Critical Requirement Use the exact phrasing “[TRIBUTE TYPE] [HONOREE NAME]” prominently in the first sentence of BOTH letters. Quick-Start (Minimal Inputs) - Organization Name: - Tribute Type: IN MEMORY OF or IN HONOR OF - Honoree Name: - Donor Name: (or “Anonymous”) - Gift Date: - Mission/Program Impact (one specific sentence) - Notify family: YES or NO - Tone: WARM (recommended) or FORMAL or CASUAL (avoid CASUAL for memorials) - Signer Name and Title: - Contact Info (phone/email): Full Input Template (copy and fill in) TRIBUTE DETAILS - Tribute Type: [IN MEMORY OF / IN HONOR OF] - Honoree Name: [Full name] - Religious Context: [SECULAR / FAITH-BASED] DONOR INFORMATION - Donor Name: [Full name or “Anonymous”] - Gift Amount: [$XXX or leave blank] - Gift Date: [MM/DD/YYYY] - Include tax receipt line: [YES / NO] - Donor wishes to remain anonymous to family: [YES / NO] FAMILY/HONOREE NOTIFICATION - Notify family/honoree: [YES / NO] - Recipient Type: [Family Contact / Honoree] - Family/Honoree Name: [Name or N/A] - Mailing Address: [Full address or N/A] - Email (if sending by email): [address or N/A] - Disclose gift amount to family/honoree: [YES / NO / N/A] - Preferred notification method: [Mail / Email / Both] ORGANIZATION & SIGNER - Organization Name: [Your organization] - Tone: [WARM / FORMAL / CASUAL] - Signer Name: [Full name] - Signer Title: [Title] - Contact Information: [Phone and email] - Website (optional): [URL] - Logo/letterhead available: [YES / NO] IMPACT & PERSONALIZATION (optional but recommended) - Mission/Program Impact (one specific sentence): Examples: “Your gift will provide two weeks of emergency shelter for a family.” “This contribution funds five after-school tutoring sessions for local students.” - Program honoree cared about (if known): [Program or N/A] - Donor’s relationship to honoree (if shared): [e.g., friend, niece] - Personal memory or note (optional, quote-length): [Text or N/A] - Pronouns for honoree: [she/he/they or avoid pronouns] - Multiple honorees or joint donors: [List names exactly] Formatting & Localization (optional) - Date format: [MM/DD/YYYY or DD/MM/YYYY] - Currency/region: [USD-US / CAD-CA / GBP-UK / etc.] - Language: [English default; specify if different] Letter Structure Requirements DONOR THANK-YOU LETTER (150–200 words) 1) Opening: Immediately acknowledge the gift using the exact phrase “[TRIBUTE TYPE] [HONOREE NAME]” in the first sentence. 2) Recognition: - Memorial: Offer a gentle condolence without clichés or euphemisms. - Honor: Acknowledge the significance of celebrating the honoree. 3) Impact (one sentence): Tie the gift to a concrete outcome using the Mission/Program Impact detail. 4) Family/honoree notification status (if applicable): Confirm “has been sent to [NAME] at [ADDRESS]” or “will be sent” and method (mail/email) if provided. 5) Invitation: Offer to update contact details or share a memory for the family/honoree. 6) Tax line (only if Include tax receipt line=YES): Add a brief receipt statement. If applicable, include “No goods or services were provided in exchange for this gift.” 7) Close: Dignified, grateful closing with signature block. FAMILY/HONOREE NOTIFICATION NOTE (80–120 words; only if Notify=YES) 1) Notification: Inform that [DONOR NAME] made a gift “[TRIBUTE TYPE] [HONOREE NAME].” - If donor is anonymous to family: Use “A donor who wishes to remain anonymous.” [... continued]

Use in:

Want AI to handle fundraising tasks automatically? →

Nonprofit Grant Writing Prompts

AI prompts for drafting grant proposals, needs statements, budget narratives, executive summaries, and final reports that help nonprofits win and manage foundation and government funding.

Grant Budget Narrative

Draft a grant budget narrative for [ORGANIZATION NAME]’s [PROGRAM NAME] to submit to [FUNDER NAME], aligning precisely with the program description...

Draft a grant budget narrative for [ORGANIZATION NAME]’s [PROGRAM NAME] to submit to [FUNDER NAME], aligning precisely with the program description and [FUNDER BUDGET CATEGORIES/ORDER] for the [GRANT PERIOD]. The budget narrative should: - Stay within 350-550 words and mirror [FUNDER BUDGET CATEGORIES/ORDER] exactly, using the same headings. - Open with a 1-2 sentence summary: total request [REQUEST AMOUNT], total program budget [TOTAL PROGRAM BUDGET], participants served [NUMBER OF PARTICIPANTS], and key outcomes [KEY OUTCOMES]. - For Personnel: list each role with FTE, duties tied to [KEY ACTIVITIES LIST], salary basis, and math (e.g., “0.50 FTE Program Manager at $[ANNUAL SALARY] = $[AMOUNT]”). - For Fringe: state [FRINGE RATE %], what it covers, and apply to the correct base. - For Non-Personnel: justify each item with unit x quantity x months and program link (e.g., “[UNIT COST EXAMPLES]”). - For Shared/Allocated costs: explain [ALLOCATION METHOD] (e.g., by FTE, sq. ft., participant count) and why it’s fair. - For Indirect/Admin: state [INDIRECT RATE %] and base [INDIRECT BASE: MTDC/TDC], give a brief rationale (e.g., audited rate, historical awards), and clarify what is included to avoid double-charging. - For Match/Cost Share: indicate [MATCH REQUIREMENT %/AMOUNT], sources [MATCH SOURCES (cash/in-kind)], status (committed/pending), and in-kind valuation method (note 2 CFR 200 if federal). - Include cost-effectiveness: cost per participant and, if possible, cost per outcome. - Note key assumptions and exclusions [CALCULATION ASSUMPTIONS] and confirm totals equal [REQUEST AMOUNT] and align with the budget table. - Address sustainability: how costs will be maintained or decrease post-grant. - Cite allowability/compliance notes or link: [ALLOWABILITY NOTES or LINK]. - Tone options: [TONE] = FORMAL (government/foundation; precise, neutral), WARM (foundation/community; accessible, confident), CASUAL (internal drafting only; plain). - Closing line: “Prepared by [AUTHOR NAME, TITLE].” Deliver concrete justifications, plain language, and transparent math. Avoid clichés (“transformational”), vague labels (“miscellaneous,” “overhead”), or unexplained percentages. Every dollar requested should connect to planned activities and outcomes, match the funder’s categories, and pass a quick calculator check to prevent math errors that can sink proposals.

Use in:

Grant Executive Summary

GRANT EXECUTIVE SUMMARY GENERATOR Purpose: Create a compelling one-page executive summary to accompany your full grant proposal.

GRANT EXECUTIVE SUMMARY GENERATOR Purpose: Create a compelling one-page executive summary to accompany your full grant proposal. STEP 1: QUICK START CHECKLIST Fill in these core details first. Basic Information: - Organization: [ORGANIZATION NAME] - Funder: [FUNDER NAME] - Request amount: [$AMOUNT] - Grant purpose: [PURPOSE – e.g., “general operating support” or “youth employment program”] - Grant period: [TIMEFRAME – e.g., “12 months” or “July 2025–June 2026”] - Total project/program budget: [$TOTAL BUDGET] Program Details: - Program name: [PROGRAM NAME] - Number served: [NUM PARTICIPANTS] - Geography: [GEOGRAPHY – city/county/region] - Population: [POPULATION – be specific] - Delivery model: [DELIVERY MODEL – e.g., “weekly workshops,” “1:1 case management,” “mobile clinics”] - Key sites/partners: [SITES/PARTNERS] Funding Context: - Confirmed or matching funds: [MATCH/LEVERAGE] - Estimated per-participant cost (if relevant): [$COST PER PARTICIPANT] Tone: [Select ONE: FORMAL / WARM / CASUAL] - FORMAL: Precise, reserved language for institutional funders (foundations, government) - WARM: Approachable, community-centered for family/local funders - CASUAL: Plainspoken for relationship-based grassroots funders you know well STEP 2: DETAILED INFORMATION (INFORMATION YOU’LL NEED) Need Statement: - Geography: [GEOGRAPHY] - Population most affected: [POPULATION] - Key data points (2–3 stats showing scale/urgency): [KEY DATA POINTS] - Specific impact/harms: [IMPACT DESCRIPTION] Solution: - Program name: [PROGRAM NAME] - What will be done, where, and for whom: [PLAIN-LANGUAGE DESCRIPTION] - Number served: [NUM PARTICIPANTS] - Delivery model: [DELIVERY MODEL] - Key sites/partners: [SITES/PARTNERS] Request & Budget: - Amount requested: [$AMOUNT] - Purpose of funds: [PURPOSE] - Grant period: [TIMEFRAME] - Total project/program budget: [$TOTAL BUDGET] - Confirmed/matching/leveraged funds: [MATCH/LEVERAGE] - Per-participant cost (if applicable): [$COST PER PARTICIPANT] Outcomes (3–5 measurable results with targets + timing): [OUTCOMES – e.g., “Serve 250 youth; 85% on-time graduation within 12 months.”] Evidence & Evaluation: - Prior results or research base: [EVIDENCE] - How results will be tracked: [EVALUATION APPROACH – e.g., “quarterly surveys, case records, database reports”] Organizational Capacity: - Track record/years operating/people served: [QUALIFICATIONS] - Staffing/governance highlights: [STAFFING/GOVERNANCE] - Fiscal health (if strong): [FISCAL STATUS – e.g., “clean audits, 6-month reserves”] Funder Alignment: - Funder priority phrases (use 1–2 explicitly): [FUNDER PRIORITY PHRASES] - How your work connects: [ALIGNMENT STATEMENT] Equity & Community Voice: - Who benefits (demographics, barriers addressed): [EQUITY] - Community input in design: [COMMUNITY INPUT] - Access considerations (language, transportation, cultural responsiveness): [ACCESS] Timeline (3–4 milestones): [TIMELINE MILESTONES – e.g., “Months 1–2: hire staff; Months 3–6: enroll 100 participants; Month 9: midpoint evaluation; Month 12: final report.”] Sustainability: - How work continues post-grant (diversified funding, earned revenue, policy alignment, committed funders): [SUSTAINABILITY] Contact Information: - Contact (for questions; usually program/development staff): [CONTACT NAME, TITLE, EMAIL, PHONE] - Signer (only if funder requires; usually ED/CEO): [SIGNER NAME, TITLE] STEP 3: CONTENT REQUIREMENTS (GENERATE THE EXECUTIVE SUMMARY) Length: - 250–400 words total. Structure & Format: - Use micro-headings for skimming, in this order: Need, Solution, Request, Outcomes, Evidence & Evaluation, Organizational Capacity, Funder Fit, Equity & Community Voice, Timeline, Sustainability, Contact - Each section = 1 short paragraph of 2–3 sentences maximum - Bold the funding request amount and 2–3 key metrics/targets - Define acronyms on first use - Use active voice; plain language; avoid jargon and superlatives [... continued]

Use in:

Grant Final Report

Draft a funder-ready grant final report for [FUNDER NAME] about [GRANT TITLE] by [ORGANIZATION NAME], covering [GRANT PERIOD] and [AMOUNT].

Draft a funder-ready grant final report for [FUNDER NAME] about [GRANT TITLE] by [ORGANIZATION NAME], covering [GRANT PERIOD] and [AMOUNT]. The grant final report should: - Follow this section order: 1) Thank you/Context; 2) Executive Summary; 3) Objectives & Results; 4) Implementation & Partnerships; 5) Challenges & Lessons Learned; 6) Beneficiary Voice & Equity; 7) Financial Summary; 8) Compliance with [FUNDER NAME] questions; 9) Next Steps/Renewal; 10) Sign-off/Contact. - Objectives & Results: include an ASCII table (Objective | Target | Actual | Variance %) plus a text alternative for portals; add 1–2 sentences explaining any variance >10% and why it occurred. - Beneficiary Voice & Equity: provide one concise story (80–120 words) with a direct quote [BENEFICIARY QUOTE], and note who benefited ([GEOGRAPHY/POPULATION], key demographics), including unexpected outcomes (positive or mixed). - Implementation & Partnerships: 3–5 bullets on what was delivered, when, by whom, and notable collaborators. - Challenges & Lessons Learned: be candid yet constructive—what changed mid-course, mitigations taken, and how learning will inform future work. - Financial Summary: align to approved budget categories [BUDGET CATEGORIES]; show Grant Funds Spent, Other Funds/In-kind, Total; explain any category variance >10% and any cost savings or leverage. - Compliance: directly answer [FUNDER QUESTIONS/PORTAL LIMITS]; mirror funder terminology; provide plain-text versions if tables aren’t allowed. - Next Steps/Renewal: what continues, remaining need [$], and a respectful invitation for renewed/continued partnership. - Data integrity: use only provided data; if missing, insert [DATA NEEDED: source] and a suggested retrieval note; list data sources. - Clarity: write at an 8th–10th grade level; define acronyms on first use; avoid clichés and over-claims. - Length: [WORD COUNT RANGE: e.g., 700–1,000 words] total narrative. - Tone: [FORMAL = precise/compliance-first], [WARM = professional, relational, grateful], or [CASUAL = plainspoken/community]. - Sign-off: [SIGNATORY NAME, TITLE, EMAIL, PHONE]. Quality matters: be specific, consistent, and transparent. Match numbers in narrative and financials; keep names/totals consistent with the original grant. Avoid jargon (“impactful,” “leverage” without specifics), hype, or crisis language. Balance honesty about challenges with clear corrective actions and gratitude to [FUNDER NAME].

Use in:

Grant Needs Statement

Draft a grant needs statement for [ORGANIZATION NAME] to include in a proposal to [FUNDER NAME] focused on [PROGRAM/ISSUE AREA] in [GEOGRAPHY] serv...

Draft a grant needs statement for [ORGANIZATION NAME] to include in a proposal to [FUNDER NAME] focused on [PROGRAM/ISSUE AREA] in [GEOGRAPHY] serving [PRIMARY POPULATION]. The needs statement should: - Be 300-450 words and written in [TONE: FORMAL (precise, evidence-forward) / WARM (human-centered, plain language) / NEUTRAL (concise, objective)]. - Follow this order: (1) Local hook (stat or brief client vignette) tied to [GEOGRAPHY], (2) Magnitude and trend of the problem (local first, then state/national for context), (3) Who is most affected and equity disparities, (4) Root causes and contributing systems, (5) Gap between current state and desired state, including service capacity shortfall, (6) Consequences of inaction, (7) Alignment to [FUNDER NAME] priorities, (8) Why [ORGANIZATION NAME] is positioned to address it; close with a 1–2 sentence bridge to the proposed solution. - Quantify with 3–5 credible, recent data points (preferably ≤3–5 years old). Cite in-text (Source, Year) and include a brief source list with URLs. - Prioritize local sources: [LOCAL AGENCY/HEALTH DEPT/SCHOOL DISTRICT], [CITY/COUNTY DATA PORTAL], [UNITED WAY/COMMUNITY FOUNDATION], then reputable national sources for context: [CENSUS/CDC/ED/DOE/Annie E. Casey/Urban Institute]. - Include [OPTIONAL: 1 brief anonymized participant quote] to humanize the data without sensationalizing. - Explicitly connect the articulated need to [FUNDER PRIORITIES] and relevant funder geographic or demographic focus. - Differentiate from peers with 1–2 concise points (e.g., reach into underserved neighborhoods, bilingual staff, partnerships, evidence-based model). - Use plain language (8th–10th grade readability), avoid jargon and acronyms unless defined, and maintain urgency without desperation. - If local data are unavailable, flag “Data needed: [insert]” and recommend likely sources to verify. Aim for specificity, balance story with data, and use asset-based language (avoid blaming communities, clichés like “at-risk,” or sweeping claims). Do not overpromise or imply exclusivity of your solution; the goal is a credible case for solvable need that aligns with the funder’s mandate.

Use in:

Grant Project Description

Draft a funder-ready Grant Project Description/Narrative for [ORGANIZATION NAME]’s [PROGRAM NAME] to be submitted to [FUNDER NAME].

Draft a funder-ready Grant Project Description/Narrative for [ORGANIZATION NAME]’s [PROGRAM NAME] to be submitted to [FUNDER NAME]. The narrative should: - Use this structure (in order), matching funder headings if provided: 1) Executive Summary; 2) Organizational Capacity; 3) Community Need; 4) Program Design & Logic Model; 5) Implementation Plan & Timeline; 6) Staffing & Partnerships; 7) Equity & Accessibility; 8) Evidence Base & Innovation; 9) Evaluation & Learning; 10) Risks & Mitigation; 11) Budget & Sustainability; 12) Funder Alignment & Compliance; 13) Conclusion. - Open with a 3–4 sentence summary stating: request of [FUNDING AMOUNT REQUESTED], who is served ([POPULATION]) in [GEOGRAPHY], what changes will occur, and the [FUNDING PERIOD]. - Translate the model into a clear logic chain: Inputs → Activities → Outputs → Short-term Outcomes → Long-term Outcomes; include 3–5 SMART objectives with numeric targets tied to [OUTPUT METRICS] and [OUTCOME METRICS]. - Provide a realistic timeline with monthly/quarterly milestones, responsible roles, and critical dependencies for [FUNDING PERIOD] ([TIMELINE]). - Describe staffing and partners: roles, FTE/time allocation, qualifications, MOUs, and backup coverage for a lean team ([STAFFING], [PARTNERS]). - Address equity and accessibility (e.g., language, transportation, eligibility, ADA) and how community voice shaped design ([EQUITY STRATEGIES]). - Cite 2–4 credible sources supporting the approach ([EVIDENCE/CITATIONS]) and explain how any innovation is a low-risk adaptation with safeguards. - Detail evaluation: data sources, collection cadence, analysis, feedback loops, and reporting to [FUNDER NAME] ([EVALUATION PLAN], [DATA SOURCES]). - Name top risks and mitigations; include compliance steps ([RISKS/MITIGATION], [COMPLIANCE REQUIREMENTS]). - Summarize budget by category and tie to activities; note match/in-kind and plan to sustain beyond grant ([BUDGET SUMMARY], [SUSTAINABILITY]). - Length: [WORD COUNT RANGE] (e.g., 800–1,200 words). Tone: [TONE]=FORMAL (precise, neutral, citation-friendly) / WARM (people-centered, plain language) / PERSUASIVE (confident, evidence-grounded). - End with an attribution line: Prepared by [AUTHOR NAME, TITLE], [DATE]. Write for non-expert reviewers (8th–10th grade readability). Be concrete, numeric, and funder-aligned; mirror [FUNDER NAME] priorities/terms. Avoid clichés (“game-changing”), vague claims, excessive jargon/acronyms (define on first use), and overpromising beyond capacity. Ensure internal consistency across goals, activities, metrics, timeline, and budget.

Use in:

Grant Prospect Research Summary

Create a one-page Grant Prospect Research Summary for [ORGANIZATION NAME] to decide whether to pursue a foundation prospect quickly and confidently.

Create a one-page Grant Prospect Research Summary for [ORGANIZATION NAME] to decide whether to pursue a foundation prospect quickly and confidently. The Grant Prospect Research Summary should: - Follow this order: 1) Funder Snapshot, 2) Fit to [PROGRAM/PROJECT] in [GEOGRAPHY], 3) Giving Patterns, 4) Eligibility, 5) Application & Deadlines, 6) Typical Award Size, 7) Recent Similar Grantees, 8) Relationships, 9) Risks/Flags, 10) Decision & Next Steps. - Funder Snapshot: name, EIN, website, mission (direct quote ≤20 words), priority areas, geography served, assets and annual giving (latest available). - Fit: 1–2 sentences mapping funder interests to [PROGRAM/PROJECT], [BENEFICIARY POPULATION], and any [EQUITY PRIORITIES]. - Giving Patterns: typical/median size, multi-year? renewals? general operating vs program? first-time grantee openness. - Eligibility: 501(c)(3) required? fiscal sponsor allowed? invite-only? exclusions. - Application & Deadlines: LOI/full? portal? cycle and next due date(s); recommended lead time. - Recent Similar Grantees: list 3–5 with year and amount (note source: 990, website, press). - Relationships: known connections (board/staff/alumni), potential warm intro paths (e.g., LinkedIn), and cultivation ideas. - Success Likelihood: 1–5 rating with one-sentence rationale; recommended ask [FUNDING RANGE SOUGHT]; level of effort (estimated hours). - Risks/Flags: invite-only, narrow geography, issue misalignment, low payout history, long timelines—name specifics. - Decision: Pursue / Monitor / Skip with one-sentence reason and 2–3 concrete next steps. - Cite sources used: [RESEARCH SOURCES/LINKS]. Mark unknowns “Unknown” and list 2–3 follow-up research questions. - Length: 220–280 words. Tone [TONE]: FORMAL (board/CEO-ready), WARM (internal staff), CASUAL (quick notes). Prepared by [PREPARER NAME/TITLE], [DATE]. Aim for specific, verifiable facts (numbers, dates, named grantees). Avoid clichés (“great fit”), jargon, or promises. If data is >3 years old, label it “outdated.” Flag invite-only and eligibility deal-breakers early. Keep it scannable so small teams can prioritize high-probability prospects and avoid misaligned proposals. Letter of Support Request Draft a partner request package to secure strong Letters of Support for a grant submission. The Letter of Support Request package should: - Be tailored for [PARTNER NAME/ORG] regarding [PROGRAM NAME] and [FUNDING OPPORTUNITY] led by [ORGANIZATION NAME]. - Include 3 subject line options and a concise email body (150-200 words) with the first line clearly stating: DUE [DEADLINE DATE, TIME, TIME ZONE] via [SUBMISSION METHOD]. - Provide a 1-paragraph program summary (80-120 words) highlighting need, approach, community impact in [GEOGRAPHY], and equity considerations relevant to this partner. - List 5-7 specific talking points for their letter: their role/credibility; how we collaborate now; concrete commitments (quantify: referrals/space/staff time/data-sharing); anticipated community benefit; alignment with [FUNDING OPPORTUNITY] goals; evaluation touchpoints; sustainability. - Specify letter requirements: 1 page (250-350 words), on letterhead, signed by [SIGNATORY NAME/TITLE], PDF to [EMAIL/PORTAL], include grant name and [ORGANIZATION NAME]. - Include a customizable draft letter template with [BRACKETED FIELDS] and 2-3 optional personalization sentences so letters aren’t identical. - Offer support: “We can draft for your edits” and provide a 2–3 sentence short version if they’re under extreme time pressure. - Set a respectful follow-up plan: initial ask (2–3 weeks out), reminder at 1 week, 48-hour check-in, day-of confirmation; include who to cc and [SENDER NAME/TITLE/CONTACT]. - Provide a mini tracking checklist for multiple letters: Partner | Signer | Status | Due | Received | Notes. Tone options: [FORMAL (federal/universities/health systems)] / [WARM (most community partners/foundations)] / [CASUAL (longtime collaborators)]. [... continued]

Use in:

Need help with grant reporting automation? →

Nonprofit Communications Prompts

AI prompts to create website copy, blog posts, press releases, newsletters, social media calendars, case studies, and impact stories that amplify your nonprofit's message.

About Page Copy

Write concise, donor- and community-facing About page copy for [ORGANIZATION NAME] using the inputs provided.

Write concise, donor- and community-facing About page copy for [ORGANIZATION NAME] using the inputs provided. The About page copy should: - Follow this structure, in order: 1) H1 headline (6–10 words); 2) Mission statement (1–2 sentences); 3) Origin story (why founded, [YEAR FOUNDED], problem you set out to solve – 1 short paragraph); 4) What we do now (programs/services, [SERVICE AREA], who you serve, [PEOPLE SERVED]/year – 1 paragraph); 5) Impact snapshot (1–3 metrics with timeframe and source); 6) Values/approach (3–5 bullets); 7) Credibility cues (partners/accreditations/awards – optional); 8) Link line to Programs, Team, Annual Report; 9) Closing call to action. - Be 450–550 words with short sentences and scannable paragraphs. - Use [TONE]: FORMAL (polished, funder-facing), WARM (welcoming, community-centered), or CASUAL (friendly, youth-forward). Default WARM if unspecified. - Aim for Grade [READING LEVEL] (8–10 recommended); define acronyms on first use; avoid jargon. - Include these specifics: [YEAR FOUNDED], [SERVICE AREA], [PEOPLE SERVED]/year, [PROGRAMS/CORE SERVICES], [IMPACT METRICS] (e.g., “In 2024, 87%…”), [VALUES] or [APPROACH], [PARTNERS/ACCREDITATIONS] (optional), [AWARDS] (optional). - Write a benefit-focused H1 (center community impact, not the organization). - Replace vague claims with concrete facts; use active voice; people-first, inclusive language. - Add a “Learn more” line linking to: [PROGRAMS URL], [TEAM URL], [ANNUAL REPORT URL]. - Close with a single sentence CTA to [CALL TO ACTION] linking to [CTA URL] (e.g., Donate, Volunteer, Subscribe). - Do not fabricate data; if an optional element is unknown, omit it rather than guessing. - Avoid clichés (“make a difference,” “empower communities”) unless paired with a metric or example. - No personal sign-off; organizational voice only. Quality matters more than flourish. Prioritize clarity, specificity, and credibility. Center the community served before the organization; show change with time-bound metrics and plain-English outcomes. Keep copy skimmable for busy donors, partners, media, and volunteers. Avoid mission drift, buzzwords, and inflated claims; ensure dates, numbers, and service areas are accurate and current. Link to deeper content instead of over-explaining.

Use in:

Annual Report - Executive Summary

Summary Draft an Executive Director's Executive Summary for [ORGANIZATION NAME]'s [YEAR] Annual Report.

Summary Draft an Executive Director's Executive Summary for [ORGANIZATION NAME]'s [YEAR] Annual Report. Structure & Flow: The summary should flow naturally from hook → mission context → accomplishments → challenges → gratitude → finances → future priorities → CTA. Weave in the quote and formatting cues where they strengthen the narrative. Format as a single continuous document with paragraph breaks (not bulleted lists). Use subheadings sparingly or not at all. The executive summary should: - Length & Voice: 450–600 words at [READING LEVEL: 8th/10th grade], written authentically in the ED's voice. - Opening Hook: Begin with 1–2 sentences reflecting the year's theme/defining moment: [YEAR THEME]. Make it specific and vivid—avoid clichés like "challenging year" or "unprecedented times." - Mission Context: Reaffirm mission in plain language (who/where/why): [MISSION/FOCUS] in [GEOGRAPHY]. Ground readers in your purpose. - Accomplishments: Highlight 3–5 key accomplishments with concrete, verifiable metrics: [ACCOMPLISHMENTS + METRICS]. Tie each to strategy and community impact. Metrics should be specific (e.g., "340 families housed" not "many families helped"; "18% increase in graduation rates" not "improved outcomes"). - Challenges & Learning: Acknowledge 1–2 key challenges or pivots: [CHALLENGES] and what was learned or changed as a result. Show adaptability and honesty. - Gratitude: Thank supporters (donors, funders, volunteers, partners), quantifying support where possible: [SUPPORTER DATA]. Be specific and genuine. - Financial Transparency: Provide a clear financial headline (not a full report): [REVENUE], [EXPENSES], [PROGRAM %], [AUDIT/990 STATUS], and stewardship stance. Keep to one concise paragraph. - Community Voice: Include one brief quote from a community member or partner (1–2 sentences): [QUOTE + ATTRIBUTION]. Place it where it amplifies impact. - Future Focus: Look ahead with 2–3 focused priorities for next year and what support enables them: [PRIORITIES]. Be concrete about what's next. - Call to Action: Close with a modest, clear CTA (read full report, subscribe, attend event): [CTA/LINKS]. - Signature: Sign off with [SIGNATORY NAME, TITLE]. Note "Headshot here" with alt text: [HEADSHOT ALT TEXT]. Alt text should describe the person professionally (e.g., "Maria Rodriguez, Executive Director, smiling in front of community garden"). - Formatting for Design: Tag callouts as [SIDEBAR], charts as [CHART]. Identify 3–5 pull-quote candidates from the text (8–15 words each, emotionally resonant or data-driven) and mark them with [PULL QUOTE]. Tone: [TONE = FORMAL (board/funders, precise, restrained) / WARM (donors/community, appreciative, conversational) / CASUAL (youth-forward, plainspoken, still professional)]. Consistency Check: Ensure this year's message builds on (not repeats) last year's: [LAST YEAR THEME]. Show progression and evolution. Quality Standards: Be specific, humble, and credible. Avoid jargon, saviorism, deficit framing, hype, and phrases like "unprecedented" or "now more than ever." Use active voice, people-first language, and numbers that can be verified. Write something a small team can publish with minimal edits and that reads well to donors, funders, partners, volunteers, and community members. Example Inputs to Get You Started: [MISSION/FOCUS]: "We provide free, culturally responsive mental health counseling for youth and families" [GEOGRAPHY]: "east and south neighborhoods of Springfield, MA" [YEAR THEME]: "Growth with care—expanding services while deepening relationships" [ACCOMPLISHMENTS + METRICS]: "Served 1,247 students (up 23% from 2023); launched bilingual tutoring in 3 new schools; 89% of participants improved reading levels by 2+ grades; secured 14 new employer partners for internships; 92% program retention" [SUPPORTER DATA]: "312 individual donors; 8 foundation grants totaling $450K; 2,100 volunteer hours from 89 volunteers; 27 corporate matches" [... continued]

Use in:

Blog Post from Program Data

Turn [PROGRAM NAME] results from [TIMEFRAME] into an engaging, SEO-ready blog post for [ORGANIZATION NAME] using the notes/data below: [PASTE PROGR...

Turn [PROGRAM NAME] results from [TIMEFRAME] into an engaging, SEO-ready blog post for [ORGANIZATION NAME] using the notes/data below: [PASTE PROGRAM DATA/NOTES]. The blog post should: - Open with a 1–2 sentence hook (micro-story or surprising stat) tied to [BENEFICIARY GROUP] in [GEOGRAPHY]. - Include a short beneficiary vignette (3–5 sentences) with one direct quote; use a pseudonym if needed and state [CONSENT STATUS] and how consent was obtained. - Translate [KEY METRICS] into plain-language insights (what changed, for whom, why it matters); compare to [BASELINE/GOAL] and note any equity considerations. - Recommend 1–2 visuals we can realistically produce (e.g., simple bar chart from [DATA SOURCE], before/after photo); include captions and accessible alt text. - Use scannable structure: H1 title, then H2s in this order — The Need, Our Approach, Results in Numbers, Voices from the Program, What’s Next/How You Can Help. - Length: 650–850 words; short paragraphs (2–4 lines) and bullets where helpful. - Tone: [TONE] = FORMAL (funder-facing, precise), WARM (community-centered, appreciative), CASUAL (conversational, social-friendly). Stay on-brand for [ORGANIZATION NAME]. - SEO: target [SEO KEYWORDS]; provide a 150–160 character meta description; URL slug; 3–5 internal links (include [DONATE LINK] and relevant program pages) and 1–2 reputable external sources. - Accessibility and ethics: plain language (grade 8–10), define acronyms, person-first or identity-affirming language per [STYLE GUIDE], no savior framing, exclude sensitive identifiers. - Calls to action: primary [CALL TO ACTION] plus secondary option(s) (subscribe/volunteer) tailored to [TARGET AUDIENCE]. - Attribution: by [AUTHOR NAME/TITLE]; publish date [PUBLISH DATE]; include fact-check notes and a source list referencing [DATA SOURCE]. - Measurement/repurposing: suggest 3 KPIs (e.g., pageviews, time on page, conversions), a UTM example for links, and 2 social teasers (LinkedIn + Instagram). Quality: Prioritize specificity over slogans—use concrete numbers (“72% of 148 participants”), name the intervention, and connect data to human impact without exaggeration. Avoid clichés (“making a difference”), jargon, and deficit/savior language. Verify consent and privacy; double-check figures against [DATA SOURCE]. Keep sentences active and varied for readability. Output should be publish-ready with minimal edits by a small team and suitable for monthly cadence and cross-channel reuse.

Use in:

Case Study Template

Draft a grant-ready nonprofit case study for [ORGANIZATION NAME] about [PROGRAM/PROJECT] in [GEOGRAPHY] during [TIMEFRAME], serving [TARGET POPULAT...

Draft a grant-ready nonprofit case study for [ORGANIZATION NAME] about [PROGRAM/PROJECT] in [GEOGRAPHY] during [TIMEFRAME], serving [TARGET POPULATION], intended for [INTENDED AUDIENCE]. The case study should: - Be 900–1,200 words plus 3–6 citations/links. - Use [TONE]: FORMAL (precise, evidence-forward for funders), WARM (human-centered yet factual for donors/volunteers), or PROFESSIONAL (balanced, plain-language for practitioners/policymakers). - Follow this structure in order: 1) Executive Summary (3–5 bullet highlights), 2) Context/Challenge (need, baseline, equity considerations), 3) Intervention (what we did, dosage, timeline, staffing, [KEY PARTNERS], [BUDGET] range), 4) Methodology (design, [DATA SOURCES], sample size, measures, comparison/baseline, consent & privacy steps), 5) Results (outputs and outcomes with concrete metrics; compare to baseline/targets), 6) Analysis (why it worked; alignment with relevant research), 7) Lessons Learned & Limitations, 8) Next Steps & Funding Needs, 9) Citations & Acknowledgments. - Include concrete numbers (n, %, change over time); clearly distinguish correlation vs. causation. - Add one short client vignette (2–3 sentences) using a pseudonym and [CONSENT NOTE]; do not include PII. - Propose 1–2 visuals (e.g., bar chart of outcome change, funnel of service flow) and 1 photo concept with required consent language. - Use accessible language (define acronyms, 9th–10th grade reading level); avoid clichés and buzzwords. - Note any data gaps or assumptions as [DATA NEEDED] and recommend minimal follow-ups to program staff. - Include 1–2 pull-quote or stat callouts for reuse in grants/marketing. - Author line: By [AUTHOR NAME/TITLE]. Reviewed by [APPROVER NAME/TITLE]. A strong case study is specific, transparent, and replicable: cite sources, state methods, and name limitations without overstating impact. Avoid savior language, jargon, or unverifiable claims. Use this format for grant appendices, impact pages, donor reports, and board packets; it balances rigor with readability for small teams.

Use in:

Impact Story/Testimonial

Framework Impact Story Generator: Dignity-Centered Testimonial Framework Purpose: Create an ethical, compelling impact story for [CHANNEL: newslett...

Framework Impact Story Generator: Dignity-Centered Testimonial Framework Purpose: Create an ethical, compelling impact story for [CHANNEL: newsletter/website/grant report/social media] that centers participant voice and demonstrates program outcomes. BEFORE YOU START: Information Checklist Required (5–6 items): - Program name and 1-sentence description - Beneficiary first name or pseudonym (confirm consent on file) - 2–3 specific outcomes with numbers (e.g., “attended 12 sessions,” “increased income by 30%,” “secured housing within 60 days”) - 1–2 direct quotes from participant (2–4 sentences each) OR write “NEED QUOTES” - Target audience (donors/funders/community members/clients) - Channel (newsletter/website/grant report/social media) Optional but recommended: - Before/after context (barriers and what changed) - Program details (duration, partners, approach, supports provided) - General location (city/region; avoid exact sites) - Consent date and anonymization requirements (pseudonym, composite, minor safeguards) INPUT FORMAT (Copy and complete below) Program: [Name and 1-sentence description] Participant: [First name or pseudonym – consent on file: YES/NO/DATE] Outcomes (with numbers): [Bullet list; at least 2 concrete metrics] Quotes: [Paste 1–2 direct quotes, or write “NEED QUOTES”] Context: [2–4 sentences on before/after; avoid identifying details] Audience: [Donors/Funders/Community/Clients] Channel: [Newsletter/Website/Grant/Social] Tone: [FORMAL (funder-facing) / WARM (donor/community-facing) / CASUAL (social-friendly)] Location: [City/region only] Program details: [Duration, frequency, partners, supports; annual reach if relevant] Privacy notes: [Anonymization needed? Composite? Minor? Details to omit? Accessibility needs?] STORY OUTPUT REQUIREMENTS (300–450 words total) Use these section headers and word ranges: 1) Headline (8–12 words, benefit-focused) - Example: “From Uncertainty to Stability: Job Training Opens Doors for Maya” 2) Hook (1–2 sentences; 25–40 words) - Orient the reader with a clear before/now contrast. 3) Before: The Challenge (60–80 words) - What context led them to the program? Focus on environment and goals, not graphic details. Avoid deficit labels. 4) The Intervention (80–100 words) - What did your organization do? Include duration, frequency, who was involved (staff/volunteers/partners), supports provided (e.g., childcare, transit). - Add one program-level metric if useful (e.g., “part of a cohort of 24,” “program served 320 residents last year”). 5) After: The Outcome (80–100 words) - What specifically changed? Include 2–3 concrete metrics (attendance, time frames, credentials earned, income/hours, retention, housing stability). - Emphasize the participant’s choices, skills, and actions. 6) Direct Quote(s) (1–2 quotes; 2–4 sentences each) - If quotes are missing, insert: [PLACEHOLDER – QUOTE NEEDED]. 7) Call to Action (1–2 sentences) - Tailor to the audience and channel (donate, volunteer, refer, learn more, advocate). Include a link or clear next step if available. Writing Guidelines - Reading level: 8th–9th grade; short sentences; plain language. - Tone: Match the selected Tone (FORMAL/WARM/CASUAL) and channel. - Voice: Use active voice; make the participant the subject when possible. - Dignity-centered language: - Do: “Sam chose to enroll,” “built skills,” “partnered with,” “achieved,” “advocated for” - Avoid: “saved,” “rescued,” “gave a voice,” “unfortunate,” “disadvantaged” - Privacy and safety: - Use first name or pseudonym only; generalize location (“a local school”). - Omit identifying details (exact employer/school, diagnoses, case numbers). - For minors: note caregiver consent; avoid identifying descriptors and photos if not approved. - Composite stories: permitted when needed for privacy. Combine insights from 2–3 similar cases, avoid unique identifiers, and log composite use in Internal Documentation with leadership approval. - Metrics: Favor specific, verifiable numbers. [... continued]

Use in:

Press Release - New Program

Launch Draft a journalist-ready press release announcing the launch of [PROGRAM NAME] by [ORGANIZATION NAME].

Launch Draft a journalist-ready press release announcing the launch of [PROGRAM NAME] by [ORGANIZATION NAME]. The press release should: - Be 450–550 words; follow AP style; use people-first, plain language; short paragraphs (1–3 sentences); no exclamation points or jargon. - Use this order: Headline; Optional subhead; “For Immediate Release” or “Embargoed until [EMBARGO DATE/TIME TZ]”; Dateline (CITY, State — Month Day, Year); Lead; Body; Quotes; Call-to-action/assets; Boilerplate; Media contact. - Write a headline (8–12 words) in active voice that includes [CITY/REGION] or a compelling [LOCAL HOOK]/stat; avoid puns/colons. - Include release/embargo line and dateline as above. - Lead paragraph answers who/what/when/where/why/how: name [PROGRAM NAME], [LAUNCH DATE], [LOCATION/ONLINE], [PRIMARY BENEFICIARIES], [PROBLEM STAT], expected change, and scope (serve X people in Y timeframe). - Body (P2–P3): convert [PROGRAM DETAILS: 3–5 BULLETS] into concise sentences; include [PARTNERS], funding if relevant, and one [SUPPORTING STAT/STATISTIC + SOURCE] with hyperlink; tie to [LOCAL HOOK]. - Quote 1 (25–40 words) from [ED NAME, TITLE] on [ED QUOTE THEME]; specific and human (no “we’re excited”); include one vivid outcome or detail. - Optional Quote 2 (20–30 words) from [PARTNER SPOKESPERSON] or [BENEFICIARY FIRST NAME—with consent]; respectful, people-first. - Call to action for media: interview/site visit timing, [CALL TO ACTION], [PHOTO/ASSET LINKS], [WEBSITE URL]; plus a 6–9 word email subject line and a 2–3 sentence pitch tailored to [MEDIA TARGETS]. - Boilerplate (75–100 words): [ONE-SENTENCE MISSION], core programs, geography, annual reach (# served), year founded, website. - Media contact: [CONTACT NAME], [CONTACT TITLE], [CONTACT EMAIL], [CONTACT PHONE]. - Tone: [TONE = FORMAL (neutral, reporter-ready) / WARM (community-centered, plain) / CONVERSATIONAL (local-friendly, approachable)]; no byline—attribute quotes to speakers. A strong release is newsy (not promotional), local, and concrete: quantify goals, timelines, and beneficiaries; attribute stats; avoid clichés (“transformative,” “world-class”), acronyms, and savior language. Center community impact and dignity. If any bracketed detail is missing, ask up to three quick clarifying questions before drafting.

Use in:

Website Homepage Copy

Create mobile-first website homepage copy for [ORGANIZATION NAME] that converts visitors within 5–10 seconds and serves donors, beneficiaries, volu...

Create mobile-first website homepage copy for [ORGANIZATION NAME] that converts visitors within 5–10 seconds and serves donors, beneficiaries, volunteers, and partners. The homepage copy should: - Open with a hero: H1 (8–12 words), subhead (1 sentence stating who you serve and how using [ONE-LINE MISSION]/[PRIMARY BENEFICIARIES]/[GEOGRAPHY]), and three CTAs above the fold with labels and URLs: [TOP CTA URLS] (defaults: Donate, Get Help, Learn More). - Use this order: Mission (25–40 words) → Impact (1–2 specific stats from [IMPACT STATS] + 1 proof sentence) → Programs (3 benefit-focused bullets, 6–12 words each, with [PROGRAM LINKS]) → Get Involved (donate/volunteer/partner/newsletter microcopy + buttons) → For Those We Serve (1–2 sentences on eligibility + [HELP CONTACT]) → Testimonial (1–2 sentences from [TESTIMONIAL OR QUOTE]). - Include a short board-safe tagline under the logo using [ONE-LINE MISSION]. - Provide SEO: H1/H2s using [PRIMARY KEYWORDS] and [SECONDARY KEYWORDS]; 1–2 internal links; meta title (55–60 chars) and meta description (140–160 chars). - Be scannable: total 300–500 words; above-the-fold 50–80 words; paragraphs 1–2 sentences; clear headings. - Voice/tone: [TONE]= FORMAL (policy/funder-ready), WARM (approachable, inspiring), CASUAL (friendly, community-first). Follow [BRAND VOICE NOTES]. - Accessibility: grade 6–8 reading level; define acronyms on first use; inclusive, plain language; 2 alt-text suggestions (hero and impact image). Consider [ACCESSIBILITY NOTES]. - Provide two A/B hero headline + subhead options. - Default CTA labels if missing; include placeholders for any missing URLs or data. - Add footer microcopy: [EIN/LEGAL LINE] and concise contact snippet. - No byline or individual author. Prioritize concrete benefits, numbers, and clarity over slogans. Avoid jargon, guilt/framing that centers donors over community, clichés (“changing the world”), and vague claims. Write for real people on mobile screens, balancing SEO with readability and dignity-first storytelling. Awareness Day Post (International Day of...) Create a social media post for [AWARENESS DAY NAME] on [DATE] for [ORGANIZATION NAME], directly tied to our work in [MISSION AREA/ISSUE] and audience [AUDIENCE], to publish on [PRIMARY PLATFORM]. The post should: - Follow this structure: 1) concise hook naming the day and why it matters; 2) what we do about it (program or service); 3) 1 proof point ([IMPACT PROOF] or [PROGRAM EXAMPLE]); 4) clear action with link [RESOURCE/LINK]. - Be 80-120 words, plain language (6th–8th grade), active voice. - Use [TONE]: FORMAL (policy/funder-facing, precise, respectful), WARM (community-centered, invitational, hopeful), or CASUAL (friendly, conversational, emoji-light). - Include hashtags: [OFFICIAL HASHTAG], [ORGANIZATION HASHTAG], plus 1–2 niche/specific tags [NICHE HASHTAG 1-2]; avoid generic overcrowded tags beyond these. - Localize the post with [LOCAL/COMMUNITY ANGLE] and/or tag a relevant partner [PARTNER HANDLE OPTIONAL] if collaboration is real. - Specify a realistic original visual we can produce quickly (e.g., staff/participant photo with consent, simple stat graphic, program-in-action shot). Avoid trauma or exploitative imagery. - Provide image ALT TEXT (120–150 characters) that is respectful, people-first, and descriptive. - Include a posting time window (6–8 a.m. local) and note if time-sensitive content warrants earlier scheduling. - Add one prewritten moderator reply (1 sentence) to common comments/questions and any needed content warning. - If we do not have genuine relevance to this day, recommend skipping or suggest a more aligned observance. - Optional: add [SIGN-OFF OPTIONAL] if the platform/style calls for attribution. Quality principles: Be specific and authentic—show what we are doing, not just “raising awareness.” Avoid clichés (“we stand with,” “join the fight”), jargon, savior framing, or trauma [... continued]

Use in:

Social Media Content Calendar

Create a month-long social media content calendar for [ORGANIZATION NAME] for [MONTH/YEAR] that a one-person team can execute efficiently.

Create a month-long social media content calendar for [ORGANIZATION NAME] for [MONTH/YEAR] that a one-person team can execute efficiently. The calendar should: - Cover platforms: [FACEBOOK/INSTAGRAM/LINKEDIN/X/TIKTOK] (select which apply for our audience). - Plan [2-3/3-5/5-7] posts per week total; set a realistic split by platform based on [FOLLOWER SIZE] (e.g., Facebook 2-3x/week for <10K). - Organize by week with specific post dates and 1 “Flex/Timely” slot weekly for news, partnerships, or rapid response. - Follow 60-30-10: tag each post as Education/Impact (60%), Community/BTS (30%), or Ask (10%) and balance across platforms. - For each post include: platform, date, theme, caption template, visual/asset suggestion + aspect ratio, alt-text (20–30 words), best time (local [TIMEZONE]), 3–6 platform-appropriate hashtags, CTA/link (add [UTM CAMPAIGN]), audience segment [DONORS/VOLUNTEERS/CLIENTS/PARTNERS], and repurposing notes for other platforms. - Caption lengths: Facebook/Instagram 50–90 words; LinkedIn 80–150 words; X 200–240 characters. Emojis [EMOJI: NONE/SPARING/FREQUENT]. Use first-person plural “we,” and note when to sign off by [STAFF NAME/TITLE] for personal stories. - Optimize per platform (e.g., no links in IG captions; IG carousel/Reel guidance; LinkedIn mentions; X threads when needed). - Integrate key dates: [CAMPAIGNS/EVENTS/ADVOCACY DAYS], awareness days, and program milestones; map to [CONTENT THEMES/BRAND PILLARS]. - Include two batch-creation blocks with grouped tasks (copy, assets, approvals) and a suggested scheduling plan using [TOOL]. - Provide an end section: weekly review checklist, simple tracker (Date | Platform | Posted? | Link), and KPI targets (reach, saves, CTR) for learning. - Tone: [FORMAL/WARM/CASUAL] — FORMAL = funder/policy-ready; WARM = community-centered and hopeful; CASUAL = approachable and playful. - Total output length: 800–1,100 words. Prioritize clarity, inclusivity, and consent (no jargon, clichés, guilt/fright appeals, or “savior” framing). Use plain language (grade 7–9), people-first language, accurate alt-text, and ensure asks are specific and time-bound. Keep cadence consistent to reduce burnout; Flex slots maintain relevance without derailing the plan. X/Twitter Thread - Awareness Campaign Create an X/Twitter awareness thread for a nonprofit campaign using the inputs: [ORGANIZATION NAME], [MISSION IN 1 LINE], [TOPIC/ISSUE], [PRIMARY AUDIENCE], [GOAL/CTA], [KEY STAT], [BENEFICIARY SNAPSHOT—first name/role], [POLICY/CONTEXT], [LINK WITH UTM], [PARTNER/SPOKESPERSON HANDLES], [HASHTAG 1-2], [COUNTRY/LOCALE], [TONE], [THREAD LENGTH 5-8], [POST DATE/TIME]. The thread should: - Produce [THREAD LENGTH] tweets; each 180–240 characters (never exceed 260); number them “(1/[N])…(N/[N]).” Total 1,200–1,800 characters. - Structure: 1) Hook with surprising stat or question; 2) Problem in plain terms; 3) Human story (no saviorism); 4) What’s at stake (policy/community); 5) What works (your solution); 6) Clear CTA with link. Add up to 2 more tweets only if essential. - Make each tweet stand alone yet read as a cohesive arc. Include 1-2 hashtags total across the thread. - Use [TONE]: FORMAL (policy/press-ready), WARM (community/donor-friendly), CASUAL (youth/peer conversational). - Write at grade 6–8 reading level; avoid jargon; use concrete nouns, strong verbs, and numbers. - Attribute voice: first-person by [SPOKESPERSON NAME/TITLE] or organizational “we”—match consistently. - Tag [PARTNER/SPOKESPERSON HANDLES] only where it adds credibility or reach; avoid over-tagging. - Accessibility: suggest 2-3 rights-safe, low-cost visual ideas with ALT text (120–250 chars each). - Provide A/B options for the hook (2) and CTA tweet (2) for testing. - Include best timing recommendation (8–10am or 12–1pm weekdays) and scheduling note for [POST DATE/TIME]. - Add moderation toolkit: 2 concise, values-aligned replies to common misinformation; guidance to hide/mute/block per community guidelines. [... continued]

Use in:

Newsletter - Program Updates

Create a monthly program-update email newsletter for [ORGANIZATION NAME], focused on [ISSUE/COMMUNITY] and the period [MONTH/QUARTER/YEAR].

Create a monthly program-update email newsletter for [ORGANIZATION NAME], focused on [ISSUE/COMMUNITY] and the period [MONTH/QUARTER/YEAR]. The newsletter should: - Be 400–600 words, mobile-first, scannable; use short paragraphs (2–3 sentences), bullets, and headers under 5 words. - Follow this order (4 sections): 1) Program highlight with 1–2 concrete metrics and a 2–3 sentence beneficiary vignette; 2) Upcoming events (dates, 1-line purpose, simple RSVP link); 3) Donor/volunteer spotlight with a gratitude note; 4) Clear primary CTA [DONATE/VOLUNTEER/REGISTER] plus one secondary action. - Include 3 specific subject lines (45–65 chars), 1 preheader (35–70 chars), and preview snippet (20–30 words); avoid generic phrases like “Monthly Newsletter.” - Open and close with a personal note from [SIGNER NAME, TITLE: EXECUTIVE DIRECTOR/PROGRAM MANAGER]; include a short P.S. that tees up the CTA without hard pressure. - Place 1–2 photo placeholders with captions and meaningful ALT text; suggest easy-to-source images from [PROGRAM NAME/RECENT EVENT]. - Write for mixed audiences (donors, volunteers, partners); add two segmented P.S. variants: [DONOR P.S.] and [VOLUNTEER P.S.]. - Use accessibility and clarity best practices: descriptive link text, plain-text fallback, and 8th–10th grade reading level; define acronyms once. - Balance stewardship vs ask at roughly 80/20; center impact and gratitude. - Add footer placeholders: contact info, manage preferences link (“update email frequency”), and compliance language. - Track results: apply [UTM CAMPAIGN] to all links; list 3 KPIs beyond opens (e.g., CTR, event RSVPs, donation page views) and 1 A/B test idea (e.g., subject specificity vs. impact stat). - Recommend a send cadence [MONTHLY/QUARTERLY] and best send window for [AUDIENCE TIMEZONE]. - Tone: [TONE]= FORMAL (board/funders, precise, reserved), WARM (donors/partners, relational, encouraging), CASUAL (volunteers/community, friendly, energetic). Apply consistently. Quality: Be concrete, local, and human-centered; avoid clichés, guilt language, and heavy jargon. Protect dignity and privacy (first names/consent if used). The goal is steady stewardship that sets up future asks and reduces unsubscribes through value-first content. Welcome Email Series for New Subscribers Welcome Email Series Generator for New Subscribers Purpose: Create a 3–4 email automated welcome series that orients new subscribers to your organization and invites simple next steps—without pressure or jargon. Estimated time to prepare inputs: 10–15 minutes BEFORE YOU START: Information Needed Required (gather these first): - [ORGANIZATION NAME] - [TONE] (choose one): FORMAL (polished, funder/donor-facing), WARM (friendly, community-centered), CASUAL (light, conversational; minimal slang; no emojis required) - [MISSION/COMMUNITY] (1 sentence, e.g., “expanding after-school arts programs in [CITY/REGION]”) - [SIGNER NAME] and [SIGNER TITLE] (typically Executive Director or Communications Lead) - [REPLY-TO EMAIL] Helpful to have (use if available): - [LIST SOURCE] (e.g., website signup, event attendees, petition signers, volunteers) - [IMPACT METRIC] (e.g., “127 families housed,” “89% job placement,” “2,500 meals served last month”) - [BENEFICIARY QUOTE] (short, first name or anonymous, permission granted) - [VOLUNTEER NEED] (e.g., “meal packers,” “mentors,” “event set-up crew”) - [UPCOMING EVENT] and [EVENT DATE] - [CITY/REGION] (primary service area) - [ENTRY GIFT AMOUNT] (typically $10–$50) - [SOCIAL HANDLES] (e.g., Instagram @org, Facebook /org) - [EMAIL PLATFORM] (e.g., Mailchimp, Constant Contact, EveryAction, HubSpot) Standard links (you’ll paste real URLs when building): - [PREFERENCES LINK] (email preference center) - [DONATION LINK] (giving page) - [PRIVACY LINK] (privacy policy) - [PHYSICAL ADDRESS] (for footer compliance) - [UTM CAMPAIGN] (suggest: “welcome-series-2025”) SERIES STRUCTURE & TIMING Default cadence: - Email 1: Immediate (on signup) [... continued]

Use in:

See how AI agents automate content creation →

Nonprofit Program Management Prompts

AI prompts for building program descriptions, evaluation reports, outcome frameworks, theories of change, success stories, and volunteer management materials.

Evaluation Report Template

Create a comprehensive evaluation report template for [ORGANIZATION NAME]’s [PROGRAM NAME] covering [REPORT PERIOD] in [GEOGRAPHY].

Create a comprehensive evaluation report template for [ORGANIZATION NAME]’s [PROGRAM NAME] covering [REPORT PERIOD] in [GEOGRAPHY]. Quick start (minimal inputs): If you only provide [ORGANIZATION NAME], [PROGRAM NAME], [REPORT PERIOD], [GEOGRAPHY], and [TONE: BALANCED (default), FORMAL, or WARM], generate the full template using defaults for all other fields. If key details are missing, first ask these 5 questions, then proceed: 1) Primary audience and uses? [e.g., program staff to improve delivery; leadership to inform planning] 2) Funders/board version needed? [Yes/No; which funder/board?] 3) Key demographics for equity breakdowns? [e.g., age, race/ethnicity, income, language, zip code] 4) Main data sources available? [e.g., surveys, interviews, admin data, observations] 5) Team capacity? [TEAM SIZE/RESOURCES: e.g., 3 staff, part-time evaluator, $50K program budget] DELIVERABLE: Produce a complete, fill-in-ready template document that includes: - Section headings in the specified order with per-section word ranges - Writing prompts in [BRACKETS] for users to complete - At least one short, concrete example in the Executive Summary and one in the Findings section showing the expected level of specificity - Sample data table shells and visual placeholders with caption prompts - “In plain language” callouts translating evaluator terms - “How to adapt for funders/board” notes within each section - Equity and participation prompts embedded in methods and findings - Constructive subheads for mixed/negative results: “What we learned / Why this matters / What we’re changing” LENGTH TARGET: 10–25 pages total (adjustable). If user does not specify a page target, default to 10–25 pages. TONE: [BALANCED (default) | FORMAL | WARM] - BALANCED: Professional and approachable - FORMAL: Grant/board-facing, neutral - WARM: Community-centered, accessible AUDIENCES AND USES: - Primary audience: [PRIMARY AUDIENCE and intended uses] - Secondary audience(s): [SECONDARY AUDIENCE and intended uses] - Funders/Board: [FUNDERS/BOARD if applicable] TEMPLATE STRUCTURE AND SPECIFICATIONS 1) Executive Summary (350–600 words) Include prompts for: - Program purpose and who it serves: [Program aims; target population; high-level needs/context] - Reach and participation: [# served; eligibility; participation intensity/dosage; key demographics] - Top 2–3 findings: [Quantitative KPI highlights with %/#; qualitative themes with brief quote] - High-level recommendations: [Most actionable next steps] - Overall assessment/learning stance: [Balanced summary; what worked; what to improve] - In plain language: “This section tells busy readers what changed, for whom, and what we’ll do next.” - How to adapt for funders/board: Lead with outcomes tied to grant objectives; keep to one page; include grant KPIs and cost-per-outcome if available. Example (model the level of detail and tone): “In 2024, the Youth Pathways mentoring program served 127 students in Westview (62% Latinx, 28% Black; 71% eligible for free/reduced lunch). Attendance improved for 89% of participants; average chronic absence dropped from 16% to 9% over two semesters. Students completing 10+ mentoring sessions were 2.1x more likely to submit all homework on time. Youth and caregiver interviews highlighted stronger school belonging and improved communication at home. We recommend formalizing caregiver touchpoints and expanding peer mentoring to all cohorts.” 2) Program Overview (300–450 words) Prompts: - Goals and theory of change: [Brief aims; core assumptions] - Target population and eligibility: [Age/grade; geography; barriers addressed] - Activities and dosage: [What, how often, by whom; training/credentials] - Staffing/resources: [TEAM SIZE/RESOURCES; partnerships; budget range] - Context: [Relevant policy/school-year cycles; community factors] - Logic model reference: [Appendix reference] - Sample phrasing: “In [YEAR], [PROGRAM] served [#] participants through [KEY ACTIVITIES] [... continued]

Use in:

Outcome Framework from Data

You are an evaluation specialist helping a nonprofit program manager create a practical Outcome Framework.

You are an evaluation specialist helping a nonprofit program manager create a practical Outcome Framework. Transform the information provided below into a structured, realistic framework aligned with nonprofit evaluation best practices and small-team capacity. CHOOSE YOUR MODE - QUICK START (recommended for beginners): If you only have brief notes or limited data, I will produce a lean framework with clear placeholders, a starter indicator set, and a simple 90-day data plan. - FULL BUILD (advanced): If you have a logic model and some data, I will produce the complete framework with detailed indicators, baselines/targets, and a full data plan. BEFORE YOU BEGIN: Paste Your Information Below Required (paste what you have; raw snippets are okay): - Program name and 2–4 sentence description - Target population and geography - Timeframe (program duration and reporting cycles) - Logic model or theory of change (activities → outputs → outcomes). If none, describe what you do and the changes you expect. - Available data: surveys, attendance, assessments, admin data, feedback, baseline numbers, funder reports (paste raw data or summaries) Optional (helpful): - Funder requirements (indicators, disaggregation, deadlines) - Staff capacity for data (hours/week, tools in use) - Data systems (spreadsheets, CRM, case notes) - Equity priorities (e.g., focus on specific subgroups) If information is missing: I will flag gaps, propose conservative assumptions, and suggest pragmatic workarounds. No data will be invented; placeholders will be clearly labeled. EXAMPLES OF ACCEPTABLE INPUT - “Attendance CSV fields: ID, session_date, hours, site.” - “Survey Q3: ‘I know 3 ways to find a living-wage job’ (1–5 Likert). Pre: n=42 mean=2.6; Post: n=37 mean=3.9.” - “Funder asks for quarterly report on #served, % gainful employment within 6 months, and stories.” - “No baseline on retention; we can pull last year’s rosters.” OUTPUT REQUIREMENTS (8 sections in this order) 1) Program Snapshot (100–150 words) - Include: mission/focus, target population, geography, timeframe, brief logic model (activities → outputs → outcomes), and any funder requirements. 2) Outcomes (Short 0–12 mo; Medium 1–3 yrs; Long 3+ yrs) - Define 2–4 outcomes per tier using concrete, measurable language (avoid vague verbs). - For each outcome, note attribution vs. contribution. - List the indicator names (3–5 per outcome). Do not include indicator details here—details go in Section 3. 3) Indicators Detail Table (primary location for indicator specs) For each indicator listed in Section 2, provide: - Indicator name - Operational definition (exact measure, numerator/denominator if applicable) - Data source (survey, records, observation, interview, admin dataset) - Collection method (e.g., online form, SMS, file pull) - Frequency (e.g., per session, monthly, quarterly, pre/post, annually) - Disaggregation (race/ethnicity, gender, age, location, income, language—adapt to context) - Responsible role (data owner) Table format: | Indicator | Definition | Source | Method | Frequency | Disaggregation | Owner | 4) Outputs (50–100 words) - List 3–5 core outputs (service volumes) with simple counts to contextualize outcomes. - Clearly label these as OUTPUTS (activities/throughput), not outcomes. 5) Baselines & Targets (100–150 words) - Derive baselines from provided data; if missing, state “No current baseline” and describe how to establish one in the first cycle. - Set realistic annual targets with brief rationale (capacity, prior trends, comparison points). - Note confidence and data quality limits. 6) Data Collection Plan (150–200 words) - Instruments: specify concrete tools (e.g., 6-item pre/post, attendance export, brief exit interview guide). - Low-burden methods: align to staff capacity and participant burden. - Cadence: when and how often each source is collected. - Storage/management: where data lives (spreadsheet/CRM), file naming, access, retention. [... continued]

Use in:

Success Story from Beneficiary

Data Use the inputs below to draft an ethical, impact-focused success story from beneficiary data for [ORGANIZATION NAME].

Data Use the inputs below to draft an ethical, impact-focused success story from beneficiary data for [ORGANIZATION NAME]. The success story should: - Be tailored to [PRIMARY AUDIENCE: DONORS/FUNDERS/COMMUNITY] and centered on [BENEFICIARY PSEUDONYM OR FIRST NAME] ([PRONOUNS], [AGE OR AGE RANGE]) in [LOCATION (GENERALIZED)]. - Follow this structure with brief headings: 1) Headline; 2) Snapshot (1–2 lines: who, program, key outcome); 3) Before; 4) During [PROGRAM NAME]; 5) After/Results; 6) What this means (connect to broader impact); 7) Call to Action. - Integrate specific outcomes and data (e.g., [OUTCOME DATA POINTS], [TIMEFRAME]) that corroborate the story; avoid vague claims. - Include at least one participant voice quote: “[PARTICIPANT QUOTE]”; optionally one staff quote with role: “[STAFF QUOTE OPTIONAL].” - Emphasize participant agency (they set goals, took actions); present the program as support, not savior. - Protect privacy: use first name or pseudonym only; omit [IDENTIFIERS TO OMIT]; generalize dates/locations. If [MINOR OR VULNERABLE: YES], note guardian consent and remove school/workplace/time-specific details. - Confirm consent metadata: [CONSENT STATUS: YES/NO], [PHOTO CONSENT: YES/NO]. If photo consent is NO, omit photo mentions; if YES, include a suggested alt text. - Length: 400–600 words. - Tone [TONE]: FORMAL (clear, evidence-forward for funders) / WARM (human, respectful, mission-aligned for donors) / CASUAL (lighter, still dignified for social/community). - Include a specific, low-friction call to action: [CALL TO ACTION]. - Add byline: “By [AUTHOR NAME/TITLE]” and a one-line program descriptor for reuse. - Provide a 6–10 word headline and 1–2 pull quotes (15–25 words each). Aim for concrete, human-centered, and respectful. Avoid trauma details, savior language, pity, clichés (“changed forever”), and jargon. The before–during–after arc shows progress, data makes it credible, and quotes add dignity and voice. Keep details non-identifying and ensure the individual story reflects program-wide outcomes without overgeneralizing. Logic Model Framework Create a one-page Logic Model Framework for [PROGRAM NAME] at [ORGANIZATION NAME], serving [COMMUNITY/POPULATION] in [GEOGRAPHY] over [TIMEFRAME]. The logic model framework should: - Begin with 3–5 end outcomes/impact statements, then work backward to intermediate and short-term outcomes, outputs, activities, and inputs using clear if-then logic. - Present a single-page table with columns: Inputs | Activities | Outputs | Short-term Outcomes (6–12 mo) | Intermediate Outcomes (1–3 yrs) | Long-term Outcomes/Impact (3+ yrs) | Indicators & Targets | Data Sources & Frequency | Responsible Role | Assumptions/External Factors | Equity Considerations. Aim for 8–12 rows total. - Distinguish outputs (units delivered) from outcomes (changes in knowledge/behavior/status); include 1–3 SMART indicators per level with numeric targets where possible. - Include a concise 250–350 word narrative summary explaining program rationale, equity approach, key assumptions, and how the logic model will guide implementation and evaluation. - Add a 2-sentence note clarifying how this logic model differs from a theory of change (visual flow vs. broader causal narrative). - Right-size the plan for a small team of [TEAM SIZE] with a budget of [BUDGET RANGE]; propose feasible data collection methods aligned to [DATA CAPACITY: LOW/MEDIUM/HIGH]. - Name primary beneficiaries, disaggregate indicators by [EQUITY PRIORITY: e.g., age, race, zip] where appropriate, and avoid deficit framing. - List top 3 assumptions and top 3 risks/external factors; state mitigation steps. - Include a quarterly review cadence and “update triggers” (e.g., staffing shifts, policy changes, underperforming indicators). - Provide 3–5 discussion questions to align staff/partners and surface hidden assumptions. - Add a header: Prepared by [ROLE], for [AUDIENCE: funder/board/internal], Date [DATE]. [... continued]

Use in:

Program Description for Grant

Write a concise, funder-ready program description for [PROGRAM NAME] at [ORGANIZATION NAME], tailored to [FUNDER NAME] and aligned with [FUNDER PRI...

Write a concise, funder-ready program description for [PROGRAM NAME] at [ORGANIZATION NAME], tailored to [FUNDER NAME] and aligned with [FUNDER PRIORITIES]. The program description should: - Be 250-350 words, in active voice, at a 9th–11th grade reading level. - Use [TONE]: FORMAL (precise, objective, grant-ready), WARM (community-centered, accessible, still professional), or CASUAL (plain-spoken, minimal jargon; avoid slang). - Assume reviewers are not experts in [FIELD]; define any acronym on first use and avoid jargon. - Follow this exact structure and order: 1) One-sentence program summary; 2) Why: local need with 1–2 data points; 3) Who: target population and size; 4) What: core services/activities; 5) How: model/methods/evidence base; 6) When: frequency, duration, timeline; 7) Where: delivery setting(s); 8) Outputs/outcomes and how measured; 9) Capacity/partners/equity and access. - Quantify specifics: [ANNUAL UNDUPLICATED PARTICIPANTS], [TARGET POPULATION DESCRIPTION], [STAFFING/FTE AND ROLES], [DOSAGE/FREQUENCY/DURATION], [CASELOAD OR RATIO], [LOCATIONS/GEOGRAPHY], [PARTNERS]. - Cite or name the evidence base or practice model (e.g., “grounded in [MODEL/RESEARCH SOURCE]”) and note fidelity/adaptations relevant to [COMMUNITY CONTEXT]. - Describe equity and access strategies (language access, ADA, transportation, outreach) relevant to [TARGET POPULATION]. - Include concrete outputs and outcomes with indicators: [EXPECTED OUTPUTS], [SHORT-TERM OUTCOMES], [METRICS], and [DATA COLLECTION METHODS]. - Briefly note organizational capacity and fit: [RELEVANT EXPERIENCE], [YEARS RUNNING], [SYSTEMS/TOOLS], and how the scope matches a small team’s resources. - Explicitly connect to [FUNDER NAME] priorities using 1–2 mirrored keywords from the RFP. - Attribution: no signature needed; write in [ORGANIZATION NAME]’s voice. Aim for clarity and credibility: be specific, measurable, and realistic. Avoid clichés (“transformational,” “game-changing”), over-claims, and value judgments about participants. Do not include budget details unless requested. Keep sentences tight, prefer concrete numbers over adjectives, and ensure every claim is supported by a method, partner, or metric reviewers can recognize.

Use in:

Theory of Change Narrative

You are a nonprofit strategy consultant specializing in Theory of Change development.

You are a nonprofit strategy consultant specializing in Theory of Change development. Draft a clear, evidence-based Theory of Change narrative that explains how and why change will happen through this program. REQUIRED INPUTS (fill all bracketed fields before running) Program & Organization: - [PROGRAM NAME] - [ORGANIZATION NAME] - [TARGET POPULATION] (be specific: age, demographics, circumstances) - [GEOGRAPHY] (neighborhood, city, region, or service area) Audience, Tone, and Length: - [AUDIENCE: FUNDERS / BOARD / STAFF / PARTNERS] - [TONE: FORMAL (grant-ready) / WARM (community-facing) / CASUAL (internal draft)] - [LENGTH: STANDARD (800–1,200 words) / SHORT (500–800 words)] Evidence & Context: - [EVIDENCE SOURCES/LOCAL DATA] (name 2–4 specific sources you will cite in plain language; e.g., “2024 County Health Rankings; 2023 ACS/Census; City DHS homelessness dashboard; our 2024 community listening sessions; peer-reviewed meta-analysis on mentoring”) - [KEY PARTNERS] (list 2–3 organizations or agencies and their roles) Team Capacity: - [TEAM SIZE] (number of staff who will implement and track this) - [DATA CAPACITY/BUDGET CONSTRAINTS] (e.g., “limited—no evaluator,” “moderate—annual survey budget,” “strong—evaluation staff”) Document Control: - [VERSION NUMBER] (e.g., V1.0, V2.3) - [AUTHOR/TITLE] - [DATE] OUTPUT STRUCTURE Deliver a narrative organized as follows. Use short sentences, plain language (8th–10th grade), and concrete numbers/timeframes. 1) Header & Impact Statement (≈50 words) - Title, [VERSION NUMBER], [DATE], [AUTHOR/TITLE] - One-sentence ultimate impact that names [TARGET POPULATION] and the change in [GEOGRAPHY] Example: “Young adults ages 16–24 in Eastview secure stable jobs and income growth within five years, reducing youth unemployment in Eastview.” 2) Problem & Root Causes (STANDARD: 150–200 words; SHORT: 100–150 words) - Concise problem statement with 2–3 data points from [EVIDENCE SOURCES/LOCAL DATA] - 2–3 root causes, including structural inequities (policy barriers, discrimination, access gaps) - Why the problem persists locally Preferred evidence types: Census/ACS; County Health Rankings; CDC/state department datasets; school district or HMIS/admin data; local needs assessments; peer-reviewed studies; community listening sessions or focus groups. 3) Pathway of Change (STANDARD: 400–500 words; SHORT: 250–350 words) Map the if-then logic clearly: Activities (what we do) → Outputs (what we produce) → Short-term outcomes (6–12 months: knowledge/skills/attitudes) → Intermediate outcomes (1–3 years: behaviors/practices/systems) → Long-term outcomes (3–5+ years: conditions) → Impact (population-level change) For each link: - Make the causal connection explicit: “If we do X, then Y will happen because…” - Name the key assumption(s) that must hold true - Give brief rationale from research or practice experience - Use specific, measurable language with timeframes Example of one link: “If youth complete 40 hours of paid work experience with weekly coaching (activity), then 80% will show gains on a soft-skills rubric within 6 months (output/outcome). Assumes supervisors use youth-friendly practices and provide real tasks. Our last three cohorts showed 75% gains under these conditions, and a 2022 meta-analysis of work-based learning found similar effects.” 4) Preconditions & External Factors (STANDARD: 100–150 words; SHORT: 75–100 words) - Preconditions for success (e.g., stable funding, partner MoUs, referral pipelines, safe space, tech access) - What is within program control vs. external systems (policy, housing market, labor demand) - How you will monitor or adapt to factors you cannot control 5) Attribution & Partnership (STANDARD: 100–150 words; SHORT: 75–100 words) - [ORGANIZATION NAME]’s specific role and what you can credibly claim - How [KEY PARTNERS] contribute to specific links in the pathway - What outcomes require collective effort and how joint work influences systems [... continued]

Use in:

Volunteer Onboarding Checklist

Create a comprehensive, role-tailored Volunteer Onboarding Checklist for [ORGANIZATION NAME]’s [PROGRAM NAME] that balances warmth with compliance ...

Create a comprehensive, role-tailored Volunteer Onboarding Checklist for [ORGANIZATION NAME]’s [PROGRAM NAME] that balances warmth with compliance and works for small teams with limited admin time. CUSTOMIZATION FIELDS (fill in before generating) - Organization: [ORGANIZATION NAME] - Program: [PROGRAM NAME] - Volunteer roles: [VOLUNTEER ROLES, e.g., “tutors, event support, admin”] - Role risk level: [LOW/MEDIUM/HIGH; e.g., child-facing, transportation] - Background check type: [BACKGROUND CHECK TYPE, e.g., “state criminal, FBI fingerprint, MVR”] - Jurisdiction: [JURISDICTION, e.g., “CA, Ontario”] - Point of contact (POC): [POINT OF CONTACT NAME, EMAIL, PHONE] - Secondary/after-hours contact: [NAME, EMAIL, PHONE] (optional) - Tracking system: [Airtable/Google Sheets/Asana/Excel/other] - Languages available: [LANGUAGES] (optional) - Tone: [WARM / FORMAL / CASUAL] - Signature title: [TITLE, e.g., “Volunteer Coordinator”] - Today’s date: [DATE] CONTENT REQUIREMENTS Timeline structure (group all steps under these phases) 1) Pre-Start (before first shift) 2) Day 1 (first shift/orientation) 3) Week 1 (first 7 days) 4) Month 1 (first 30 days) For each checklist item include - Step name (start with a verb) - Why it matters (1 sentence) - Owner (Staff or Volunteer) - Due date/timing (specific: “before first shift,” “within 3 business days”) - Link/Location (URL, folder, or contact) - Checkbox (☐) - Plus columns for Status and Notes (for tracking) Example checklist row Complete background check | Protects clients and meets [JURISDICTION] rules | Staff | Within 5 business days of conditional offer | HR: /Volunteer/BackgroundChecks | ☐ Compliance essentials (include all; align to [JURISDICTION]) - [BACKGROUND CHECK TYPE] completed and cleared (add MVR for driving, sex offender registry where required) - Signed liability waiver - Confidentiality/privacy agreement (HIPAA/PHI/PII if applicable) - Photo/media consent (opt-in/opt-out) - Emergency contact info collected - Safety procedures review (exits, PPE, first aid, emergencies) - Incident reporting process - Code of conduct acknowledgment - Any [JURISDICTION]-specific items (e.g., mandated reporter training, TB test, food handler card) Role variations and safeguards - Role-specific tasks/training for [VOLUNTEER ROLES] - HIGH risk (child/vulnerable/transport): enhanced checks, boundaries training, supervised shadowing (2–4 shifts), two-adult rule, driving verification (license/insurance), tighter incident escalation - MEDIUM risk: standard checks, buddy system, first two shifts supervised - LOW risk: basic orientation, data privacy mini-training (if handling info) Orientation and culture - Mission, values, and who we serve - Program goals and impact - Role scope and boundaries (what to do/not do) - DEI expectations and inclusive language - Current health/safety protocols (COVID-19 or other) - Data handling and device/security basics - Facilities tour or virtual equivalent; access/badges - First assignment checklist and role tools overview Relationship-building - Welcome script (60–90 words) from program lead that thanks the volunteer, sets expectations, and invites questions - Introductions to key staff and experienced volunteers - Shadowing plan (who to observe, how many shifts) - Mentor/buddy assignment (name and contact) - First assignment checklist (step-by-step for the first shift) Support resources - FAQs (exactly 5): 1) Time commitment and scheduling 2) What to wear/bring 3) Parking/transport/facility access 4) Cancellation/absence policy 5) Who to contact for questions or problems - Key contacts block: - Primary: [POINT OF CONTACT NAME, EMAIL, PHONE] - Secondary/after-hours contact - Emergency number/location procedures - Simple welcome kit list (e.g., name tag, handbook, t-shirt, badge, parking info, tool links) Accessibility and inclusion - Ask: “Do you need any accommodations or have access needs (mobility, sensory, schedule, [... continued]

Use in:

Volunteer Recruitment Messaging

Create a volunteer recruitment message for [ORGANIZATION NAME] that converts busy people into committed volunteers for [MISSION/CAUSE] on [CHANNEL:...

Create a volunteer recruitment message for [ORGANIZATION NAME] that converts busy people into committed volunteers for [MISSION/CAUSE] on [CHANNEL: EMAIL/LANDING PAGE/INSTAGRAM/LINKEDIN/FLYER]. The message should: - Start with an impact-forward headline (max 10 words) tied to [MISSION/CAUSE]. - Open with a hook that shows beneficiary impact (not organizational need), citing 1 concrete outcome or stat: [IMPACT METRIC/OUTCOME] benefiting [BENEFICIARY/COMMUNITY]. - Clearly describe the opportunity: [VOLUNTEER ROLE(S)], primary tasks, who it’s ideal for, [TIME COMMITMENT], [SCHEDULE WINDOW], [LOCATION/VIRTUAL], [ACCESSIBILITY/LOGISTICS], training/support provided, and point of contact. - State a volunteer value proposition for [AUDIENCE SEGMENT] (e.g., skill-building [SKILLS], networking, purpose, family-friendly) using “you” language. - Address top objections in 1–2 short lines (time, skills, transportation/childcare) and show flexible entry points: [ENTRY OPTIONS: one-time/ongoing/virtual/skilled/group/family]. - Include one authentic 1–2 sentence testimonial with name/role [TESTIMONIAL] (confirm permission implied). - Add a brief inclusion note that welcomes diverse volunteers and lived experience [DEI MESSAGE]; use plain language (grade 7–9). - Provide visual guidance: suggest 1–2 photos of real volunteers in action with consent [PHOTO DESCRIPTION]. - End with one clear CTA that combines action + timeframe + link/button [CTA/URL]; include a micro-commitment (e.g., “15‑minute info session”). - Supply 2 alternative headlines/subject lines and 2 CTA variants for A/B testing. - Word count: 250–350 words (photo notes and A/B lines do not count). - Tone: [TONE = FORMAL (for partners/funders; precise, respectful) / WARM (community-centered, encouraging) / CASUAL (youthful, energetic; still professional)]. - Sign as [SIGNER NAME/TITLE] if used for email or letter; omit for social. Deliver copy that is concrete, specific, and free of jargon and guilt appeals. Avoid clichés (“change the world,” “rockstar”), saviorism, and vague asks. Prioritize clarity (what, where, when, how long), show real impact, and make next steps effortless—so small teams can paste, post, and launch with minimal edits.

Use in:

Volunteer Role Description

Draft a clear, welcoming volunteer role description for [ORGANIZATION NAME] that helps busy nonprofit teams recruit well-matched volunteers.

Draft a clear, welcoming volunteer role description for [ORGANIZATION NAME] that helps busy nonprofit teams recruit well-matched volunteers. QUICK INTAKE (copy/paste and fill; leave “TBD” if unknown) - Organization: [ORGANIZATION NAME], mission/cause: [MISSION/CAUSE] - Volunteer type: [ONE-TIME EVENT / ONGOING DIRECT SERVICE / SKILLED-PRO BONO / VIRTUAL / BOARD-LEADERSHIP] - Role title: [ROLE TITLE] - Impact metric: [e.g., “serve 50 meals per shift,” “support 12 students weekly”] - Time & place: [X hours/week], [duration], [schedule/flexibility], [location], [on-site/remote/hybrid] - Supervisor: [SUPERVISOR TITLE] - Training/support: [TRAINING PROVIDED]; materials/resources: [LIST]; stipends/reimbursements: [MILEAGE/PARKING/MEALS or “None”] - Screening: [e.g., background check—cost covered by ORG; none] - Application: [APPLICATION LINK/EMAIL], response time: [e.g., within 5 business days], target start: [DATE or Rolling] - Inclusion/accessibility contact: [NAME/EMAIL/PHONE] - Contact/signature: [CONTACT NAME], [TITLE], [PHONE/EMAIL] - Tone: [FORMAL / WARM / CASUAL] If a field is blank, propose a sensible default and flag it in [brackets]. If something doesn’t apply, write “Not applicable” or omit. STRUCTURE & CONTENT (output must use these 9 numbered headings) 1) Role Title 2) Brief Overview (2–3 sentences) - What the volunteer will do and why it matters. - Include impact: “Each shift helps [IMPACT METRIC], advancing [MISSION/CAUSE].” 3) Responsibilities (4–6 bullets) - Be concrete. GOOD: “Greet visitors and check them in using our sign-in iPad.” BAD: “Support front desk operations.” - Tailor to [VOLUNTEER TYPE] (e.g., one-time event = day-of tasks; board = governance/strategy; skilled = defined deliverables; virtual = tools/platforms). 4) Time Commitment - State: [HOURS/WEEK], [DURATION], [SCHEDULE/FLEXIBILITY], [LOCATION], [ON-SITE/REMOTE/HYBRID]. 5) Qualifications - Required (must-have): keep minimal. - Preferred (nice-to-have): end with “Don’t meet every preferred item? We encourage you to apply.” 6) Training & Support - Note training, supervision, materials. Add reimbursements/stipends if applicable; if none, say “No out-of-pocket costs.” 7) Screening & Requirements - State simply (e.g., “Background check—cost covered by [ORG NAME]”). Include age/confidentiality only if essential. If none, write “No background check required.” 8) Inclusion & Accessibility - Always include: “We welcome volunteers of all backgrounds and abilities. To request accommodations, contact [NAME/EMAIL/PHONE].” 9) Application Process & Contact - How to apply, response time, target start date, and “Posted by [CONTACT NAME], [TITLE], [PHONE/EMAIL], [ORGANIZATION NAME].” STYLE & TONE - Length: 250–350 words total; prioritize clarity over strict count. - Reading level: 8th–10th grade; short sentences; plain words. - Tone: [FORMAL / WARM / CASUAL] (choose one and use consistently). - Format: plain text with numbered headings and bullets; include hyperlinks in parentheses for digital use; spell out URLs for print. EXAMPLE SNIPPET (tone: WARM, ~50 words) “As a Weekend Pantry Greeter, you’ll welcome neighbors, check them in on our iPad, and answer simple questions. Each 3-hour shift helps 60 households access fresh, healthy food—moving us closer to a hunger-free community. We’ll train you on our check-in app and have a staff lead nearby for support.” MUST DO - Be honest about time and requirements. - Make tasks specific and scannable. - Use inclusive, welcoming language. NEVER DO - Use legalese, clichés (“rockstar”), or vague phrases (“other duties as assigned”). - Create unnecessary barriers in “Required.” QUALITY CHECK Before finalizing, ensure someone could read this in 90 seconds and know if they’re a fit, what they’ll do, and how to apply. OUTPUT Produce one polished role description following the 9 headings above. Do not include tips or commentary in the final output.

Use in:

Volunteer Thank You Letter

VOLUNTEER THANK‑YOU LETTER GENERATOR (NONPROFIT) Goal: Generate a personalized volunteer thank‑you letter that strengthens retention, shows genuine...

VOLUNTEER THANK‑YOU LETTER GENERATOR (NONPROFIT) Goal: Generate a personalized volunteer thank‑you letter that strengthens retention, shows genuine appreciation, and works for email or print—without any fundraising asks. HOW TO USE (QUICK START: 5 REQUIRED FIELDS) Fill these, then add any optional fields you have. 1) [VOLUNTEER NAME] (preferred name) 2) [PROGRAM/PROJECT] (e.g., “Saturday food distribution,” “after‑school tutoring”) 3) [CONTRIBUTION] (what they did; e.g., “sorted 500 lbs,” “mentored 3 students”) 4) [TIME PERIOD] (e.g., “in March,” “this spring,” “Jan–Mar 2025”) 5) [SIGNER NAME & TITLE] (e.g., “Maria Chen, Volunteer Coordinator”) Optional: [ORGANIZATION NAME] (for subject line), [TONE] (WARM default / FORMAL / CASUAL), [GENERATE MODE] (SINGLE LETTER default / TEMPLATE FOR BULK) LETTER REQUIREMENTS Structure (follow this order): 1) Salutation using inclusive name/pronouns 2) Specific appreciation tied to mission and their role in [PROGRAM/PROJECT] + [CONTRIBUTION] 3) Quantified impact with concrete numbers + one brief example/anecdote 4) Sense of community/belonging 5) Optional next touchpoint (non‑fundraising) 6) Warm close and signature block 7) Optional P.S. with one concise impact stat Format: - 150–220 words total - 6th–8th grade reading level; plain language; short sentences - Scannable: 2–4 short paragraphs (2–3 sentences each), plus optional P.S. - Dual‑purpose: email body or printable letter - If [ORGANIZATION NAME] provided, include an email subject line Tone (choose one): - WARM (default): friendly, heartfelt, personal - FORMAL: polished, respectful (board/corporate/leadership) - CASUAL: upbeat, conversational (peers/youth) Must include: - At least one specific number (e.g., hours, items, people served, % change) - Clear link to mission and community - Zero fundraising or donation language Avoid: - Clichés (“we couldn’t do it without you,” “rockstar”) - Jargon (“leverage,” “stakeholders,” “synergy”) - Generic praise without specifics OPTIONAL ENHANCEMENTS (ADD WHAT YOU HAVE) Personalization: - [VOLUNTEER LEVEL] (FIRST‑TIME / RECURRING / TEAM LEAD / BOARD / INTERN / EVENT‑DAY) - [TENURE] (e.g., “since 2023,” “40 total hours,” “started 9/15/2024”) - [PREFERRED PRONOUNS] (for inclusive salutation) - [VOLUNTEER COMMUNITY NAME] (e.g., “Garden Squad,” “our volunteer family”) Impact details: - [HOURS] (e.g., “12 hours in March”) - [OUTPUT] (e.g., “600 meals packed,” “25 kits assembled”) - [IMPACT METRIC] (e.g., “helped 180 families,” “15% increase in students reached”) - [SPECIFIC EXAMPLE] (brief anecdote or quote from staff/participant) Mission and next step: - [MISSION SHORT] (10–15 words) - [NEXT TOUCHPOINT] (non‑ask; e.g., “training on April 12,” “appreciation picnic,” “newsletter signup”) Signature and delivery: - [CONTACT INFO] (email/phone) - [SIGNATURE IMAGE ALT‑TEXT] (for accessibility; else omit) - [DELIVERY CONTEXT] (EMAIL / PRINT) if you want slight formatting tweaks FALLBACKS (IF DATA IS MISSING) - No anecdote? Insert [ADD SPECIFIC EXAMPLE] as a visible placeholder. - No hours or output? Use program‑level [IMPACT METRIC] if available. If none, use neutral phrasing and insert [NUMBER NEEDED] as a placeholder. Do not fabricate numbers. - Not sure of level/tenure? Omit those lines rather than guessing. MAIL‑MERGE / BULK USE - If [GENERATE MODE] = TEMPLATE FOR BULK, retain all [BRACKETED] fields for mail‑merge and do not invent data. - Keep placeholders visible for fields you will import later (e.g., [VOLUNTEER NAME], [HOURS], [SPECIFIC EXAMPLE]). OUTPUT WILL INCLUDE - Email subject line (if [ORGANIZATION NAME] provided) - Complete letter that follows the required structure and word count - Bracketed fields preserved for mail‑merge; no invented data - Signature block: [SIGNER NAME], [SIGNER TITLE], [CONTACT INFO] - Optional P.S. with one concise stat - If [SIGNATURE IMAGE ALT‑TEXT] provided, include one line noting it for accessibility SAMPLE OUTPUT PREVIEW [... continued]

Use in:

See how AI agents automate program reporting →

Nonprofit Event Planning Prompts

AI prompts to plan event concepts, write sponsorship packages, create post-event thank-you emails, and design virtual event engagement strategies for nonprofits.

Event Concept and Theme

Brainstorm You are an expert nonprofit event strategist.

Brainstorm You are an expert nonprofit event strategist. Develop an event concept and theme brainstorm for [ORGANIZATION NAME] that balances creative differentiation with revenue and capacity realities. BEFORE YOU BEGIN: Information-Gathering Worksheet Fill in brackets with specific details. If unsure, leave blank—the AI will make reasonable assumptions and note them. Essential Inputs (Required) - [ORGANIZATION NAME] - [MISSION/CAUSE] (1 sentence; e.g., “Ending food insecurity in rural communities”) - [PRIMARY GOAL] (e.g., “Raise $25K net” or “Engage 50 new major donors”) - [TARGET AUDIENCE] (be specific; e.g., “Young professionals 25–40, HHI $75K+, socially conscious”) - [BUDGET RANGE] (e.g., “$8,000–12,000 all-in” or “Under $5K”) - [STAFF CAPACITY] (e.g., “1 dev. dir. 10 hrs/wk x 8 wks + 1 volunteer coord. 5 hrs/wk”) - [DATE OR SEASON] (e.g., “Spring 2025—Apr/May” or “Before FY end Jun 30”) - [CITY/REGION] (e.g., “Portland, OR metro” or “Virtual—Pacific Northwest focus”) Important Inputs (Highly Recommended) - [NET REVENUE TARGET] (e.g., “$15,000 net after expenses”) - [ATTENDANCE TARGET] (e.g., “75–100 in-person” or “200+ virtual”) - [SPONSORSHIP GOAL] (e.g., “$10K from 3–5 sponsors” or “Not pursuing”) - [PAST EVENTS]/[PAST EVENT RESULTS] (e.g., “2023 Trivia: 60 attendees, $4K net, fun but low $; 2022 Gala: 120 attendees, $18K net, high staff load”) - [RISK TOLERANCE] (e.g., “Low—need proven” or “High—willing to experiment”) - [ACCESSIBILITY NEEDS] (e.g., “Wheelchair accessible, ASL, sliding scale pricing”) - [DIFFERENTIATORS/NEARBY EVENTS] (e.g., “3 local youth org 5Ks in fall—avoid 5K”) Optional Inputs - [VIRTUAL/HYBRID PREFERENCE] (e.g., “Prefer in-person, open to hybrid”) - [BOARD PRIORITIES] (e.g., “Feature youth speakers” or “Include program tour”) - [CAUSE/COMMUNITY PARTNERS] (e.g., “Local breweries, arts council, university”) - [AVERAGE TICKET PRICE] (e.g., “$50–75” or “Free—donations only”) - [TONE] Select ONE: FORMAL (board-facing, concise), WARM (donor-friendly, mission-forward), CASUAL (creative, plain language) - [NAME/TITLE] - [AUDIENCE] (e.g., “Executive Director + Board Development Committee”) - [DATE] OUTPUT STRUCTURE 1) EXECUTIVE SNAPSHOT (100–150 words) - Primary Goal: [PRIMARY GOAL] - Target Audience: [TARGET AUDIENCE] - Success Metrics: Net revenue [NET REVENUE TARGET]; Attendance [ATTENDANCE TARGET]; Sponsorships [SPONSORSHIP GOAL] - Key Constraints: Timeline ([DATE OR SEASON]); Location ([CITY/REGION]); Budget ([BUDGET RANGE]); Staff ([STAFF CAPACITY]); Risk ([RISK TOLERANCE]); Accessibility ([ACCESSIBILITY NEEDS]); Format ([VIRTUAL/HYBRID PREFERENCE]) - Mission Context: [1 sentence linking to MISSION/CAUSE] - Competitive Note: [DIFFERENTIATORS/NEARBY EVENTS] - Must-Include: [BOARD PRIORITIES] 2) EVENT CONCEPT PORTFOLIO (10–15 distinct concepts) Requirements: - At least 3 low-cost concepts (≤30% of [BUDGET RANGE]) - At least 2 hybrid or virtual options - At least 2 scalable concepts (pilotable small → expand later) - Mix formats: social, challenge/competition, educational, community, virtual For each concept, provide exactly this structure (80–120 words): [Concept Number]. [EVENT TITLE] - Tagline/Theme: [1 compelling sentence] - Mission Connection: [Specific, concrete tie to MISSION/CAUSE] - Audience Fit: [Why TARGET AUDIENCE will attend; clear draw] - Experience: [What attendees actually do—sensory and concrete] - Venue/Season: [Venue type + ideal timing in [CITY/REGION]] - Accessibility/Inclusion: [How it addresses ACCESSIBILITY NEEDS; inclusive pricing] - Differentiation Hook: [What makes this distinct from DIFFERENTIATORS/NEARBY EVENTS] - Revenue Model: Ticket price [range; align with/assume [AVERAGE TICKET PRICE]], fundraising mechanisms (e.g., peer-to-peer, auction-lite, pledges), sponsorable assets (e.g., named segments/stages, swag, program ads) - Cost Drivers: [Top 3 expense categories] - Capacity Intensity: [LOW/MEDIUM/HIGH with brief reason] [... continued]

Use in:

Post-Event Thank You Email

Write a segmented, post-event thank-you email for [ORGANIZATION NAME] to send within 48–72 hours after [EVENT NAME] on [EVENT DATE].

Write a segmented, post-event thank-you email for [ORGANIZATION NAME] to send within 48–72 hours after [EVENT NAME] on [EVENT DATE]. The post-event thank-you email should: - Produce separate versions for selected segments: [SPONSORS/DONORS OR TICKET BUYERS/VOLUNTEERS/GUESTS OR COMMUNITY PARTNERS]. If [SEGMENTS] not specified, create all four. - Include for each segment: Subject line (6–9 words) and preview text (35–55 characters) optimized for opens. - Open with a personalized salutation using [FIRST NAME] and a specific thank-you tied to their role (e.g., “for sponsoring,” “for attending,” “for volunteering the [HOURS] hours,” “for purchasing a ticket”). - Share an “impact snapshot” with 2–3 concrete outcomes from the event using placeholders where needed: [DOLLARS RAISED], [ATTENDEES], [PROGRAM IMPACT METRIC], [QUOTE OR 1-LINE TESTIMONIAL]. - Highlight one memorable moment from the event: [HIGHLIGHT MOMENT], and include 1–2 photo links with descriptive alt text: [PHOTO 1 DESCRIPTION – LINK], [PHOTO 2 DESCRIPTION – LINK]. - Thank sponsors prominently. For the sponsor segment, lead with impact tied to their support and include a sponsor benefits nod or next-step debrief: [SPONSOR DEBRIEF LINK]. For non-sponsors, include a brief “Thanks to [TOP SPONSOR NAME(S)]” line. - Include gentle, stewardship-first next steps (no hard ask): [SURVEY LINK], [ALBUM LINK], [NEXT EVENT SAVE-THE-DATE], and one optional soft pathway tailored by segment (e.g., [VOLUNTEER LINK], [DONATE LINK – OPTIONAL], [NEWSLETTER LINK]). - Note any follow-up commitments made at the event (e.g., receipts, slides, photos) and when they’ll arrive: [FOLLOW-UP ITEM] by [DATE]. - Keep structure scannable: 2–3 short paragraphs plus a 2–3 bullet impact list; reading level 6th–8th grade; mobile-friendly lines under ~75 characters. - Word count per segment: 150–220 words. - Tone: [TONE] = FORMAL (corporate/funders; polished, concise), WARM (default; human, appreciative, mission-forward), CASUAL (volunteers/young audiences; friendly, simple). Keep consistent throughout. - Sign off personally from [SIGNER NAME], [TITLE] (preferably Executive Director or Event Chair), with an optional brief P.S. reinforcing one next step. Aim for concrete, human, and specific. Avoid clichés (“game-changer,” “on behalf of”), jargon, or multiple exclamation points. Do not include a big, urgent ask—stewardship first. Link to assets instead of attaching files. Use inclusive language that centers the community you serve and double-check all placeholders for accuracy before sending.

Use in:

Sponsorship Package Description

Write a one-page sponsorship package description for [EVENT NAME] hosted by [ORGANIZATION NAME] on [DATE] at [LOCATION].

Write a one-page sponsorship package description for [EVENT NAME] hosted by [ORGANIZATION NAME] on [DATE] at [LOCATION]. The sponsorship package description should: - Open with a 2–3 sentence mission snapshot linking sponsor support to [BENEFICIARIES/PROGRAM IMPACT] and the event’s purpose. - Present 3–5 tiers with clear names and amounts: use [TIER NAMES/AMOUNTS] if provided; otherwise propose levels appropriate for a [SMALL/RURAL/URBAN] market and [EXPECTED ATTENDANCE]/[EVENT BUDGET], with meaningful differentiation. - For each tier, list concrete benefits sponsors care about and your small team can deliver: logo placements ([WEBSITE/EMAIL/PROGRAM/ON-SITE SIGNAGE]), recognition ([STAGE/MC/SCREEN]), quantified digital posts, ticket/VIP quantities, activation/speaking rights, exhibit table, and category exclusivity (if any). - Include an In‑Kind Sponsor option specifying [IN‑KIND NEEDS] (e.g., printing, catering, A/V, media) valued at fair market rate and mapped to the closest cash tier. - Provide audience and reach: [EXPECTED ATTENDANCE], [AUDIENCE DEMOGRAPHICS], [EMAIL LIST SIZE], [SOCIAL FOLLOWERS], [MEDIA PARTNERS/SPONSORS], to indicate marketing value. - Add a “Why It Matters” section with 3 impact lines that translate dollars to outcomes (e.g., $5,000 = [IMPACT EXAMPLE]). - State deadlines: commitment by [COMMITMENT DEADLINE]; assets by [ARTWORK DEADLINE] and [PRINT DEADLINE]; note that benefits depend on timely materials. - Offer optional add‑ons (limited quantity): [BRANDED ACTIVATION/EMPLOYEE VOLUNTEER DAY/MATCHING CHALLENGE/PHOTO BOOTH/STEP‑AND‑REPEAT LOGO]. - Include recognition policy and tax note: logo order by level, exclusivity rules, and 501(c)(3) acknowledgment language (no goods/services value vs. fair market value). - Close with a clear CTA and contact block signed by [NAME], [TITLE], [EMAIL], [PHONE]. - Word count: 450–650 words. Tone: [TONE]—FORMAL (corporate/procurement), WARM (community/mission‑forward), CASUAL (youth/culture). Deliver scannable, specific benefits (quantify posts/tickets/impressions), keep mission‑first, avoid clichés/jargon (“win‑win,” “synergy”), don’t overpromise, and price tiers to cover 40–60% of event costs pre‑ticket sales. Use clear headers and bullets so this can be dropped into a one‑pager with minimal edits.

Use in:

Virtual Event Engagement Strategy

Create a comprehensive Virtual Event Engagement Strategy and Run-of-Show for [EVENT NAME], a [EVENT TYPE: FUNDRAISING GALA/WORKSHOP/PANEL/TOWN HALL...

Create a comprehensive Virtual Event Engagement Strategy and Run-of-Show for [EVENT NAME], a [EVENT TYPE: FUNDRAISING GALA/WORKSHOP/PANEL/TOWN HALL/CELEBRATION] hosted by [ORGANIZATION NAME] on [DATE/TIME/TIME ZONE] for [TARGET AUDIENCE(S)]. Format the output as a [OUTPUT FORMAT: Google Doc outline/Planning spreadsheet columns/Presentation outline/Plain text] with clear headings and bullet points. If any bracketed item is not finalized, use “TBD” and provide general best-practice guidance. Output Structure: Generate a complete event package including: (1) Strategy overview (450-650 words), (2) Minute-by-minute run-of-show, (3) Scripts and talking points, (4) Technical/production checklist, and (5) Follow-up plan. Elements beyond the strategy overview are supplementary and not counted toward the word limit. Event Parameters: - Team size: [TEAM SIZE] - Budget: [BUDGET RANGE] - Platform: [ZOOM/TEAMS/WEBEX/OTHER] - Expected attendance: [EXPECTED ATTENDEE COUNT] - Speakers/presenters: [NUMBER AND FORMAT] - Event history: [FIRST-TIME/ANNUAL/RECURRING] Strategy Overview (450-650 words): - One-sentence purpose statement - Three SMART goals tied to mission outcomes (e.g., donor conversions, volunteer sign-ups, policy actions) - How format and interactive elements support these goals - Key accessibility and inclusion commitments (captioning/ASL, language access, visual contrast) Minute-by-Minute Run-of-Show (75–90 minutes total): - Detailed timeline with time stamps (e.g., 0:00–0:05 Welcome and land acknowledgment) - Interactive touchpoints every 10–15 minutes (polls, chat prompts, breakouts, reactions, Q&A) - Mark technical transitions, speaker handoffs, production cues, and buffer time - Identify fundraising/CTA moments and countdown cues Platform & Access Details: - Registration flow and confirmation process (include calendar hold link) - Donation button/link CTA: [CTA LINK] - Accessibility: [CAPTIONING/ASL/OTHER NEEDS]; visual descriptions as needed - Dial-in backup number and instructions - Recording policy: [WILL RECORD AND SHARE/WILL RECORD FOR INTERNAL USE/NO RECORDING]; post-event access: [RECORDING AVAILABLE TO ALL/ATTENDEES ONLY/NOT AVAILABLE] - Security settings (waiting room, rename, chat permissions) Team Roles & Responsibilities: - Emcee/Host: [EMCEE NAME/TITLE]—on-camera engagement and transitions - Chat Moderator: curate questions, flag issues, post links - Tech Lead: platform management, screen shares, troubleshooting, backup plan - Speaker Wrangler: cues, timing, bios, green-room coordination - Escalation protocol (3 steps): Tech Lead attempts fix → switch to backup (slides-only/dial-in) → Emcee acknowledges and pivots agenda Pre-Event Communications: - Registration confirmation email (100–150 words): event details, calendar hold, what to expect, accessibility info, platform download link - 24-hour reminder (75–100 words): login link, “test your tech” note, what to have ready, teaser - 1-hour day-of reminder (≤50 words): direct login link - Subject lines for each email Scripts & Talking Points: - Opening (30–45 sec): welcome, purpose, what to expect - Inclusive welcome/land acknowledgment (if appropriate) - Donor/volunteer acknowledgment (20–30 sec): concise gratitude without long lists - Mission story (60–90 sec): vivid, specific, outcome-tied narrative - Closing (30–45 sec): thanks, next steps, clear CTAs Interactive Elements: - Polls: 2–3 multiple-choice questions (3–5 options each), timed with purpose noted (e.g., Poll 1 at 15:00 to gauge familiarity) - Chat prompts: 3–5 exact questions (e.g., “Share your city,” “One action you’ll take this week?”) - Breakout (optional, 5–7 min): clear prompt, roles, time warning, debrief plan - Q&A flow: how to submit, moderation rules, time limits, spam/troll handling (mute/remove, chat limits) Fundraising Moment: - 90-sec story: who/what funds support and impact - Specific ask: [FUNDRAISING GOAL] with tiers (e.g., $50 does X, $100 does Y) [... continued]

Use in:

Nonprofit Board & Leadership Prompts

AI prompts for preparing board meeting agendas and drafting professional meeting minutes that keep nonprofit leadership aligned and informed.

Board Meeting Agenda

Draft a concise, board-ready agenda for [ORGANIZATION NAME]’s [QUARTERLY/MONTHLY/SPECIAL] Board Meeting on [MEETING DATE] ([IN-PERSON/VIRTUAL/HYBRI...

Draft a concise, board-ready agenda for [ORGANIZATION NAME]’s [QUARTERLY/MONTHLY/SPECIAL] Board Meeting on [MEETING DATE] ([IN-PERSON/VIRTUAL/HYBRID] at [LOCATION/ZOOM LINK], [TIME ZONE]). The agenda should: - Fit on one page (agenda body 250–350 words) and open with logistics: date/time, location/link, RSVP, accessibility note ([ACCESS NEEDS CONTACT]), and meeting length [MEETING LENGTH]. - List sections in this order: 1) Call to Order & Mission Moment (2–3 min), 2) Consent Agenda, 3) Strategic Discussion (primary), 4) Brief Operational Updates, 5) Committee Items (only if decision needed), 6) Finance/Fiduciary, 7) Governance/Board Development, 8) Executive Session (if needed), 9) Action Recap & Adjourn. - For each item include: time allotment, presenter, desired outcome [VOTE/DISCUSS/FYI], and pre-read title/link (pre-reads sent by [PREREAD DATE]). - Use a Consent Agenda for routine items (e.g., prior minutes, ED report, routine contracts under [$THRESHOLD]); note “Members may pull items for discussion.” - Put Strategic Discussion first (e.g., “[STRATEGIC TOPIC]”) with 2–3 guiding questions and a clear decision or next-step output. - Clearly mark motions requiring approval (e.g., “Motion: Approve Q2 Financials”) with estimated time and who introduces the motion. - Time-box all reports to minimize “read-outs;” prioritize dialogue; ensure 50–60% of total time is strategic. - If [MEETING LENGTH] > 120 minutes, insert a 5-minute break and include a brief stretch or check-in. - Name roles: Facilitator, Timekeeper, and Note-taker; specify who tracks the parking lot and action items. - Close with Action Recap (owner + deadline) and Next Meeting date. - Tone: [FORMAL (board governance emphasis)/WARM (collaborative and mission-focused)/CASUAL (small team, informal culture)]. - Footer: Prepared by [ED NAME] and [BOARD CHAIR NAME]; Questions: [GOVERNANCE CONTACT]. Aim for clarity and brevity; avoid jargon, long reports, or items without a defined outcome. Follow Robert’s Rules loosely (motions/seconds recorded) while keeping engagement high. Use this agenda when you need balanced governance, clear decisions, and respect for volunteers’ time.

Use in:

Board Meeting Minutes Template

Create a nonprofit-compliant Board Meeting Minutes Template for [ORGANIZATION NAME] that small teams can complete quickly and boards can approve co...

Create a nonprofit-compliant Board Meeting Minutes Template for [ORGANIZATION NAME] that small teams can complete quickly and boards can approve confidently. The Board Meeting Minutes Template should: - Begin with a header: [ORGANIZATION NAME], [MEETING TYPE: Regular/Special/Annual], [DATE], [TIME & TIME ZONE], [LOCATION/VIRTUAL LINK], [MEETING CALLED TO ORDER AT], [CHAIR], [SECRETARY], [QUORUM: Yes/No], [CONFLICTS OF INTEREST DISCLOSED: Yes/No]. - List attendance by category: Board (Present/Absent), Staff, Guests; note late arrivals/early departures when relevant. - Include agenda approval and prior minutes approval (motion, second, vote outcome). - Capture reports received (title, presenter) and reference attachments: [REPORT NAME] – stored at [FILE PATH/DRIVE LINK]; do not embed content. - Record motions verbatim with mover/seconder, vote method (voice/roll call), tally (For/Against/Abstain), recusals, and outcome; include decisions made without formal motion if permitted by [BYLAWS REFERENCE]. - Summarize key discussion points in neutral, past tense (2–4 bullets per topic); no verbatim quotes or editorializing. - Provide an Action Items table: Item, Owner, Due Date, Status; highlight deadlines impacting programs/funders. - Note Executive Session as a line item with start/end times and general purpose only; no details. - Include public comment (if applicable) and any declared conflicts of interest or recusals. - Conclude with adjournment time and next meeting details. - Add approval/signature block: “Approved by the Board on [DATE]” with lines for [BOARD CHAIR NAME/TITLE] and [SECRETARY NAME/TITLE]; “Prepared by [MINUTE-TAKER NAME/TITLE].” - Compliance footer: “Draft within [X DAYS, e.g., 7]; retain for [RETENTION PERIOD] per [STATE/BYLAWS].” - Provide a brief example narrative (250–350 words) using [TONE: FORMAL = precise, legal record; WARM = plain, readable yet compliant; CASUAL = only for internal committees, not recommended for board minutes]. Quality principles: Be specific, factual, and concise. Avoid jargon, opinions, attributions of sensitive remarks, and unnecessary detail. Prioritize motions, decisions, and action owners. Common pitfalls: failing to record vote tallies/recusals, mixing attachments into the body, over-transcribing, and omitting storage locations. Committee Charter Draft a board committee charter for [ORGANIZATION NAME] that the board can approve and use immediately to guide the work of the [COMMITTEE NAME] in [CURRENT YEAR]. The committee charter should: - Be 600–900 words (1–2 pages), with clear headings and bullets; plain, accessible language. - Open with Committee Name, Purpose, and Link to [MISSION/STRATEGIC PRIORITY], stating 2–3 concrete outcomes for the year. - Define Scope and Boundaries: list 5–7 “In-Scope” tasks and 3–5 “Out-of-Scope” items to prevent overlap with [RELATED COMMITTEES]. - Specify Authority and Decision Rights: what the committee may decide, what requires board approval, any dollar thresholds ([BUDGET AUTHORITY]), and reference to bylaws/policies. - Detail Composition: [COMMITTEE SIZE] voting members; allowance for non-board/community members if board size is [BOARD SIZE]; Chair selection [CHAIR SELECTION METHOD]; terms [TERM LENGTH]; DEI considerations. - List Responsibilities: 6–10 specific, time-bound duties (e.g., “Review monthly financials; recommend annual budget to board by [MONTH]”), avoiding vague verbs like “support” or “oversee” without specifics. - Set Meetings and Decision-Making: [MEETING FREQUENCY]; quorum of [QUORUM %]; how decisions are recorded; use of virtual meetings if applicable. - Define Reporting: cadence to board ([REPORTING CADENCE]), required materials (brief written report, dashboard), and escalation path for risks. - Clarify Staff Support: [STAFF LIAISON TITLE] role (agenda prep, data, minutes), realistic time expectations given staff size [STAFF SIZE]. [... continued]

Use in:

Nonprofit Operations & HR Prompts

AI prompts to write employee handbooks, job descriptions, onboarding checklists, performance reviews, remote work policies, and standard operating procedures for nonprofits.

Employee Handbook Section

Employee Handbook Section Generator for Nonprofits BEFORE YOU START: Gather This Information (examples in parentheses) Organization Basics: - [ORGA...

Employee Handbook Section Generator for Nonprofits BEFORE YOU START: Gather This Information (examples in parentheses) Organization Basics: - [ORGANIZATION NAME]: (e.g., River Valley Food Bank) - [SECTION TOPIC]: (e.g., Remote Work; Paid Time Off; Workplace Safety) - [MISSION/PROGRAM CONTEXT]: 1 sentence (e.g., We distribute food to 5,000 families monthly across three counties) Legal & Compliance: - [JURISDICTIONS]: (e.g., California; New York and New Jersey) - [IMPLEMENTATION DATE]: (e.g., January 1, 2025) - [REVIEW FREQUENCY]: (e.g., annually; every two years) Staff Details: - [STAFF TYPES]: (e.g., full-time, part-time, seasonal, interns) - [WORK MODES]: (e.g., hybrid; fully remote; on-site only) - [UNION STATUS]: (e.g., non-union; SEIU Local 123 members) Your Capacity: - [CAPACITY NOTES]: (e.g., Executive Director manages HR 3–5 hours/week; one part-time operations coordinator handles HR) - [CONTACT ROLE]: (e.g., Operations Director; Executive Director) Style Preferences: - [READING LEVEL]: (e.g., 8th grade; high school; general adult) - [TONE] (choose ONE; examples below) - FORMAL example: “Employees must submit requests using the Time Off Form within 48 hours of the absence. Supervisors approve or deny within two business days. Failure to follow these steps may result in the absence being unpaid.” - WARM example: “Please use the Time Off Form and let your supervisor know within two days of any absence. We try to respond within two business days. If you’re unsure what to do, ask—we’re here to help.” - CASUAL example: “Need time off? Fill out the Time Off Form and give your supervisor a heads-up within two days. We’ll aim to confirm in a couple of business days. Questions? Just ping your supervisor.” - [LANGUAGE ACCESS]: (e.g., Spanish; Spanish and Mandarin; English only) Approval Chain: - [PREPARED BY]: (e.g., Operations Coordinator) - [APPROVED BY]: (e.g., Executive Director and Board Personnel Committee) - [LEGAL REVIEW]: (e.g., Pro Bono Partnership; Smith & Associates; internal review only) Optional Settings: - [WORD COUNT RANGE]: (default 500–750; use 800–1,100 for complex topics like harassment; 350–550 for simple topics like dress code) YOUR PROMPT: Draft an Employee Handbook Section for [ORGANIZATION NAME] on [SECTION TOPIC], aligned with our mission ([MISSION/PROGRAM CONTEXT]) and compliant with [JURISDICTIONS] law. This is for a small nonprofit team with [CAPACITY NOTES]. Formatting Rules: - Use numbered section headers (1–13) with the exact titles below. - Use short paragraphs and bullet lists where helpful. - Procedures must be a numbered checklist with who/what/when and named forms/tools. Required Structure (follow this exact order): 1. Title 2. Policy Statement – 2–4 sentences stating what is required/allowed/prohibited (not aspirational) 3. Purpose/Values Link – 1–2 sentences tying to our mission 4. Scope/Eligibility – Specify: - Staff types: [STAFF TYPES] - Union status: [UNION STATUS] - Work modes: [WORK MODES] - Volunteers/contractors: included or excluded 5. Definitions – 3–5 plain-language terms 6. Procedures – Numbered steps with WHO does WHAT by WHEN; include forms/tools; realistic for [CAPACITY NOTES] 7. Legal/Compliance References – Name relevant [JURISDICTIONS] laws/regulations; note when local law supersedes this policy 8. Exceptions & Accommodations – How to request disability/religious accommodations; Contact: [CONTACT ROLE]; response timeframe (e.g., within 5 business days) 9. Reporting/Confidentiality/Anti‑retaliation – Reporting channels; privacy limits; anti-retaliation; recordkeeping and retention timeframes (or “per local law”) 10. Roles & Responsibilities – Employee; Supervisor; Operations/HR; Executive Director; Board (if applicable) 11. Related Policies – Cross-reference 2–4 connected sections 12. Effective Date/Review – Include: - Effective: [IMPLEMENTATION DATE] - Review: [REVIEW FREQUENCY] - Version control template: “Version [X.X] | Effective [DATE] | Last Reviewed [DATE]” [... continued]

Use in:

Job Description Template

You are creating an inclusive, mission-forward nonprofit job description that attracts qualified, values-aligned candidates while staying realistic...

You are creating an inclusive, mission-forward nonprofit job description that attracts qualified, values-aligned candidates while staying realistic about small-team capacity. STEP 1: PROVIDE THESE REQUIRED INPUTS (copy this checklist, fill in the brackets, then submit) Basic Information (required): - [ROLE_TITLE]: - [REPORTS_TO_TITLE]: - [DEPARTMENT_TEAM]: - [LOCATION_AND_WORK_ARRANGEMENT]: (e.g., “Remote within CA,” “Hybrid, Chicago 2 days/week”) - [EMPLOYMENT_TYPE]: (Full-time/Part-time) - [FLSA_STATUS]: (Exempt/Non-exempt) - [SALARY_RANGE]: (e.g., “$55,000–$65,000”) — required for equity; if unknown, provide best current range Organization Context (required): - [ORGANIZATION_NAME]: - [MISSION_ONE_LINER]: (What you do in one sentence) - [WHO_BENEFITS]: (Who you serve) Role Details (required): - [ROLE_PURPOSE]: (Why this role exists; gap it fills) - [KEY_IMPACT_AREAS]: (3–5 bullets: main areas of work) - [TEAM_SIZE_STRUCTURE]: (e.g., “Reports to ED; collaborates with 8-person team; supervises 1 coordinator”) - [SCOPE_METRICS]: (Budget size, caseload, volunteers/year, events/year, partners, etc.) Requirements & Constraints (required): - [REQUIRED_QUALIFICATIONS]: (5–7 bullets; include “or equivalent experience” if listing a degree) - [PREFERRED_QUALIFICATIONS]: (3–5 bullets) - [SCHEDULE_CONSTRAINTS]: (Evenings/weekends [FREQUENCY], travel [TRAVEL_%], seasonal peaks) - [PHYSICAL_ENVIRONMENTAL_REQUIREMENTS]: (Only if essential—examples: “lift up to 25 lbs for event setup,” “prolonged computer work,” “local travel up to 25%.” Include “valid driver’s license” ONLY if driving is essential.) Compensation & Application (required): - [BENEFITS_SUMMARY]: (Health, dental/vision, PTO days, holidays, retirement match/stipend, professional development budget, flexible scheduling, wellness, transit, etc.) - [TONE_PREFERENCE]: pick one — FORMAL (policy/compliance-focused), WARM (approachable, community-centered), CASUAL (nimble/startup feel) - [APPLICATION_MATERIALS_REQUIRED]: (e.g., “Resume and 1-page cover letter”; “Portfolio link”) - [WHERE_TO_SUBMIT]: (email or application link) - [TIMELINE]: (pick one format) • Rolling: “Applications reviewed on a rolling basis starting [DATE]; open until filled.” • Priority: “Priority deadline [DATE]; interviews week of [DATE]; target start [DATE].” • Urgent: “We aim to hire by [DATE]; applications reviewed as received.” - [HIRING_MANAGER_TITLE]: - [HR_RECRUITING_CONTACT_EMAIL]: - [JOB_CODE]: (optional) If any required inputs are missing (especially [SALARY_RANGE]), pause and ask for them in a single, concise list before generating. STEP 2: AI WILL GENERATE THIS STRUCTURE (450–550 words total; plain language, 8th–10th grade; scannable; minimal jargon) 1) Header - Job Title: [ROLE_TITLE] - Reports to: [REPORTS_TO_TITLE] - Department: [DEPARTMENT_TEAM] - Location/Schedule: [LOCATION_AND_WORK_ARRANGEMENT] - Employment Type/FLSA: [EMPLOYMENT_TYPE], [FLSA_STATUS] - Salary Range: [SALARY_RANGE] 2) About [ORGANIZATION_NAME] (1–2 sentences) - State [MISSION_ONE_LINER] and who benefits [WHO_BENEFITS]. 3) Role Summary (3–4 sentences) - Connect the role to mission impact and why it matters now. 4) Key Responsibilities (5–8 bullets; action-oriented; measurable) - List the top 3 first (most critical). Quantify scope using [SCOPE_METRICS]. - Use strong verbs (Lead, Manage, Develop, Coordinate, Analyze). 5) Qualifications - Required (5–7 bullets): Essential skills/experience only; include “or equivalent experience” for any degree. - Preferred (3–5 bullets): Nice-to-haves, sector tools/knowledge. 6) Working Conditions & Expectations - Name constraints honestly: [SCHEDULE_CONSTRAINTS]; clarify cross-functional duties (e.g., program coordination, donor communications, event logistics). - Physical/environmental requirements ONLY if essential: [PHYSICAL_ENVIRONMENTAL_REQUIREMENTS]. - Add: “Reasonable accommodations available upon request.” 7) Compensation & Benefits [... continued]

Use in:

New Employee Onboarding

Checklist You are creating a New Employee Onboarding Checklist for a nonprofit organization.

Checklist You are creating a New Employee Onboarding Checklist for a nonprofit organization. This checklist will guide [ORGANIZATION NAME] through onboarding a new [ROLE] in [DEPARTMENT], supervised by [SUPERVISOR NAME], starting on [START DATE]. SECTION 1 — REQUIRED INPUTS (complete before generating) Organization Context: - Organization name: [ORGANIZATION NAME] - Staff size: [5–10 / 11–25 / 26–50 / 50+] - Work setting: [IN-PERSON / REMOTE / HYBRID] - Location (state/country): [STATE/COUNTRY] - Compliance needs (check all): [Youth-serving / Healthcare / Government-funded / Data privacy (GDPR/HIPAA) / None] Role Details: - New hire role: [ROLE] - Department: [DEPARTMENT] - Supervisor: [SUPERVISOR NAME] - Start date: [START DATE] - Executive Director (for welcome email): [EXECUTIVE DIRECTOR NAME] Team Structure (write “N/A” if not applicable; tasks default to Operations Coordinator, then Executive Director): - HR/Operations contact: [NAME or N/A] - IT contact: [NAME or N/A] - Finance contact: [NAME or N/A] - Facilities contact (if applicable): [NAME or N/A] Tools Your Organization Uses (write “None” if not applicable): - CRM/case management: [SYSTEM NAME or None] - Payroll/HRIS: [SYSTEM NAME or None] - Communication tools: [Zoom, Slack, Teams, etc. or None] - Password manager: [1Password, LastPass, etc. or None] Tone: - [WARM AND PROFESSIONAL] (default) OR [FORMAL] (recommended for government-funded/healthcare settings) SECTION 2 — CHECKLIST REQUIREMENTS Structure and Timeline (in this order): 1) Pre-Start 2) Day 1 (limit to 5–7 essential tasks) 3) Week 1 (Days 2–5) 4) Weeks 2–4 5) 30/60/90-Day Milestones 6) Ongoing (recurring items) Task Table Format (each task must include): - Columns: Priority [Essential/Optional] | Task (≤12 words, specific) | Owner [HR/OPS/IT/SUPERVISOR/FINANCE/FACILITIES/PROGRAMS/DEVELOPMENT/New Hire] | Due Date/Window | Link/Resource [INSERT LINK] | Notes (low-cost alternative/workaround) - Define “low-cost alternative” as free/open-source or manual workaround (e.g., Google Forms instead of paid HRIS). - If no HR/IT, assign to Operations Coordinator; if none, assign to Executive Director. - Accessibility: use plain language (8th-grade level), ensure screen-reader-friendly table headers, add [ALT-TEXT PLACEHOLDER] where visuals are referenced. Examples: - Good: “Send offer letter with salary, benefits, start date” | Owner: HR | Due: Day -14 | Link: [Template] | Notes: Use free e-sign - Bad (too vague): “Orient new hire to organizational culture” Content to Include (adapt to [STATE/COUNTRY] and [COMPLIANCE NEEDS]): - Compliance: offer/handbook acknowledgment; I-9; W-4/state tax; E-Verify/background checks (if required); confidentiality; child-safeguarding (if youth-serving); DEI commitment; harassment prevention; safety training. - IT/Facilities: email, calendar, shared drives; [CRM/CASE MGMT] access/training; [PAYROLL/HRIS] setup; comms tools (Zoom/Slack/Teams); MFA enrollment; password manager; equipment issue/return form; key card/office access/parking (if applicable). - Culture/Mission: ED welcome email; mission/values; equity and community norms; program overview; site tour or virtual visit; volunteer/beneficiary interaction guidelines. - Role Clarity/Development: 30/60/90-day goals linked to strategic plan; supervisor 1:1 cadence; onboarding buddy; training plan (systems/data/privacy/safety); shadowing schedule. - Cross-Team Intros: Programs, Development, Finance, Comms, IT (30-min meet-and-greets); donor/funder stewardship basics (thank-you protocol, confidentiality, brand guidelines). - Small-Team Pacing: mark essentials vs. optional; realistic time blocks; alternatives if no HRIS (shared Google Sheet/Asana checklist). - Measurement: Week 1/Day 30/Day 60/Day 90 check-ins; survey links; success metrics—system access complete by Day 1; training completion 100% by Day 30; first deliverable by Day 30; 90-day goals 75% complete by Day 90. [... continued]

Use in:

Performance Review Template

Create a fillable, nonprofit-specific Performance Review Template for [ORGANIZATION NAME], used by [EXECUTIVE DIRECTOR/OPERATIONS COORDINATOR] for ...

Create a fillable, nonprofit-specific Performance Review Template for [ORGANIZATION NAME], used by [EXECUTIVE DIRECTOR/OPERATIONS COORDINATOR] for [REVIEW PERIOD] reviews across roles (programs, development, operations, volunteer coordination). The Performance Review Template should: - Open with 80-100 words of instructions emphasizing developmental intent, equity, confidentiality, and a 60-minute discussion requirement. - Follow this order: Employee Info; Role Summary; Review of Last Year’s Goals; Competency Ratings; Strengths & Impact; Development Areas; Next-Period SMART Goals; Support & Resources; Overall Rating; Compensation/Recognition Summary; Signatures & Dates; 90-Day Check-In Plan (for new hires). - Use a 3-point scale with behavioral anchors: Exceeds Expectations, Meets Expectations, Developing. Tie to nonprofit indicators (e.g., donor stewardship quality, grant/report timeliness, program outcomes, community partnership, fiscal stewardship, DEI practice, collaboration). - Include mirrored Self-Assessment prompts for each section with space for 100-150 words and evidence fields (data, dates, stakeholder feedback). - Limit competencies to 3-5 aligned to [VALUES/COMPETENCIES]; provide sample anchors relevant to [MISSION AREA]. - Require review of 3-5 prior goals (status, results, lessons) and creation of 3-5 new SMART goals with measures, deadlines, and low-cost supports (training, mentoring, schedule adjustments). - Add a Development Plan (2-3 actions, owner, timeline) and Manager Support commitments tailored to small-team capacity. - Provide a Compensation/Recognition section aligned to [RAISE POLICY] and budget limits; list non-monetary options (title refinement, flexible schedule, PD stipend, conference speaking, public recognition). - Include signature lines: Employee, Supervisor, [ED/HR], plus acknowledgement of receipt and 90-day follow-up date. - Length: 500-700 words of template text, with clear fillable fields and prompts. - Tone options: [FORMAL] policy-aligned and precise; [WARM] supportive and plain-language; [CASUAL] friendly while professional. - Prepared by [SUPERVISOR TITLE]; co-authored by [EMPLOYEE NAME]; reviewed by [ED/HR]. Quality: Be concrete and evidence-based; avoid vague adjectives, corporate jargon, or punitive language. Prioritize clarity, equity, and documentation that protects the organization while advancing staff growth.

Use in:

Remote Work Policy

Draft a nonprofit-specific Remote Work Policy for [ORGANIZATION NAME] that balances flexibility with program delivery, equity, and donor/client con...

Draft a nonprofit-specific Remote Work Policy for [ORGANIZATION NAME] that balances flexibility with program delivery, equity, and donor/client confidentiality. The policy should: - Be 900–1,100 words (≈2–3 pages) and usable by a small HR/operations team. - Use [TONE]: FORMAL (policy/legal, board-facing), WARM (people-centered, professional), or CASUAL (plain language, still compliant). - Follow sections in this order: Purpose & Scope; Definitions (Remote/Hybrid/In-Office); Eligibility by Role; Work Schedules & Core Hours; Communication & Meetings; Technology & Security; Workspace & Ergonomics; Performance & Accountability; Equity & Accessibility; Expenses & Equipment; Office Use/Travel; Implementation (Trial, Review, Exceptions); Compliance & Acknowledgment; Governance & Signatures. - State eligibility: list [ELIGIBLE ROLES] and [INELIGIBLE ROLES] with mission/program rationale and any on-site requirements. - Set availability norms: core hours [CORE HOURS] in [TIME ZONE]; response time [RESPONSE TIME]; meeting cadence [MEETING CADENCE]; camera expectations [CAMERA EXPECTATIONS]. - Specify communication tools [TOOLS LIST]; when to use each; documentation norms for decisions and client/donor records. - Define technology/security: devices [EQUIPMENT PROVIDED/BRING YOUR OWN]; MFA/VPN; data handling (donors/clients); compliance [COMPLIANCE FRAMEWORK]; IT support expectations [IT SUPPORT/SLA]; incident reporting. - Include workspace/ergonomics: safety checklist; stipend or cap [STIPEND AMOUNT]/[REIMBURSEMENT CAP]; ADA accommodation process. - Clarify performance: outputs-based KPIs [KPI LIST]; check-ins; timekeeping and overtime rules for [STATE/COUNTRY]; consequences applied consistently. - Address equity/pay: consistent criteria; geographic pay policy [PAY POLICY]; fairness for part-time and volunteer coordination roles. - Implementation: effective date [EFFECTIVE DATE]; trial length [TRIAL LENGTH]; annual review in [REVIEW MONTH]; exceptions approved by [APPROVER TITLE]. - Governance: Issued by [ISSUER TITLE]; Approved by [BOARD/COMMITTEE]; Revision date [DATE]; include employee acknowledgment language. Produce concrete, non-jargon guidance with numbers, examples, and simple steps suitable for limited budgets and IT capacity. Include a brief mission-aligned rationale and board-facing metrics [METRICS] (e.g., service outputs, fundraising goals, turnaround times, cost savings). Avoid clichés, blanket promises, or language that conflicts with at-will and local laws; note “subject to legal review.” Ensure inclusive, consistent application across roles. Meeting Agenda Template Create a reusable, nonprofit-ready meeting agenda template for [MEETING TYPE] at [ORGANIZATION NAME] that improves outcomes while respecting small-team capacity. The agenda template should: - Start with a one-line purpose: “By the end of this meeting we will [OBJECTIVE]” (1–2 sentences max). - Include a header block with fields: [DATE], [TIMEZONE], [MEETING LENGTH], [LOCATION/ZOOM LINK], [FACILITATOR], [NOTETAKER], [ATTENDEES/ROLES], [ACCESSIBILITY/INCLUSION NOTES]. - Use an agenda table with columns: Time (mins), Topic, Lead, Purpose (Decision/Discussion/FYI), Pre-reads/Links, Desired Outcome. - Time-box items to total [MEETING LENGTH] (60–90 minutes for weekly staff; add a 5-minute break if 90+ minutes). Put decisions before updates. - Add a 2–3 minute grounding check-in (mission/values or equity moment) and a 2-minute closing (next steps + appreciation). - Include a “Parking Lot” with Owner + Follow-up Plan to capture off-topic items without derailing. - Add “Decisions Made” and “Action Items” (Owner, Due Date, First Next Step) plus “Comms Out” (who needs to be informed: board, funders, volunteers, partners). - Include a “Risks/Blocks/Resource Needs” section to surface capacity constraints early. - Specify pre-work with due-by dates: [PRE-READS] with links; limit live updates to 10–15 minutes total. [... continued]

Use in:

Standard Operating Procedure

(SOP) BEFORE YOU START: Gather these details to customize your SOP: - [PROCESS NAME] – e.g., “Monthly Donor Acknowledgment Letters,” “Client Intake...

(SOP) BEFORE YOU START: Gather these details to customize your SOP: - [PROCESS NAME] – e.g., “Monthly Donor Acknowledgment Letters,” “Client Intake and Enrollment” - [ORGANIZATION NAME] – Your nonprofit’s name - [PRIMARY ROLE OWNER] – Job title who normally does this, e.g., “Development Coordinator” - [BACKUP ROLE] – Who covers when primary is out, e.g., “Executive Director,” “Program Assistant” - [TOOLS/SYSTEMS] – Software/platforms used, e.g., “Salesforce NPSP, Gmail, Google Drive” - [COMPLIANCE REQS] – Regulations that apply, e.g., “HIPAA,” “FERPA,” “IRS charitable receipt rules,” or “None” - [STORAGE LOCATION] – Where this SOP will live, e.g., “Google Drive > Operations > SOPs” - [TONE] – Choose one: FORMAL, WARM, or CASUAL Draft a Standard Operating Procedure (SOP) for [PROCESS NAME] at [ORGANIZATION NAME], designed for a small nonprofit team with limited time and budget. When to use this prompt: Use for recurring processes performed by more than one person, tasks critical to compliance or donor relations, or areas at risk if a single staffer leaves. For one-off or highly variable work, consider a simple checklist instead. Required SOP Sections: Essential (include in every SOP): 1) Purpose and Audience (2–3 sentences) - Why this procedure exists and who will use it (e.g., new staff, volunteers, temp coverage). - Example: “This SOP ensures all donors receive accurate, timely tax receipts per IRS rules. Used by Development Coordinator; backup: ED.” 2) Scope and Timing - When it’s triggered, how often performed, expected duration. - Example: “Triggered within 48 hours of gift entry. Frequency: 2–3x weekly. Duration: 15 min per 10 gifts.” 3) Roles and Coverage - [PRIMARY ROLE OWNER], [BACKUP ROLE]; include required permissions/access. - Example: “Requires Salesforce NPSP edit rights and Drive folder access.” 4) Tools and Systems - List [TOOLS/SYSTEMS] with direct links and brief access steps (e.g., “Log in at app.salesforce.com with @orgname.org”). - Offer low-cost alternatives if primary tool is down (e.g., “Use Google Sheet template [link] and sync later”). 5) Step-by-Step Instructions (Numbered, 5–15 steps) - For each step: who does what, where to click/type, fields to complete, time estimate. - Include decision points (e.g., “If gift > $1,000, notify ED via Slack”). - Add [Screenshot of ____] placeholders for key screens. - End with a mini-checklist summarizing critical steps. 6) Definition of Done / Quality Standards - What must be true before marking complete. - Example: “✓ Receipt PDF in Drive > Donor Files > [Year]; ✓ CRM ‘Receipt Sent [Date]’ field updated; ✓ Donor tagged ‘Receipt Sent [Year]’.” Recommended (add as relevant): 7) Troubleshooting (3–7 common issues) - Use “If X, then Y” fixes; include nonprofit-specific cases. - Example: “If donor declines a receipt, note in CRM and send thank-you only. If client lacks ID, follow Emergency Enrollment SOP.” 8) Data, Privacy, and Accessibility - PII handling, retention, and [COMPLIANCE REQS]. - Language access (e.g., Spanish templates available). - ADA-friendly tips for public-facing materials. 9) Communication Templates/Snippets - 1–3 short email/script templates as needed. - Example: “Subject: Your tax receipt from [ORGANIZATION NAME]…” 10) Related Procedures and Escalation - Link related SOPs (e.g., Gift Entry, Donor Corrections). - Who to contact for help (name/role/contact method). Mandatory Footer: 11) Version Control - Author: [Name] - Process Owner: [PRIMARY ROLE OWNER] - Approver: [Name/Title] - Version: [e.g., 1.0] - Effective Date: [MM/DD/YYYY] - Next Review Date: [One year from effective date] - Storage Location: [STORAGE LOCATION] 12) Signature Lines Process Owner Approval: ______________________ Date: ________ [PRIMARY ROLE OWNER name/title] Executive Approval: __________________________ Date: ________ [Approver name/title] Length: 500–900 words total (adjust for complexity; simple processes may be ~400 words, complex up to 1,000). [... continued]

Use in:

See how AI agents automate onboarding and HR →

No prompts match your search. Try a different keyword.

Need Help Getting Started with AI?

Our team helps nonprofits adopt AI tools the right way, with training, strategy, and hands-on support tailored to your mission.

Nonprofit AI Prompts Library

How to Use These Prompts

Pick a Prompt

Fill in Brackets

Send It

Nonprofit Fundraising Prompts

Nonprofit Grant Writing Prompts

Nonprofit Communications Prompts

Nonprofit Program Management Prompts

Nonprofit Event Planning Prompts

Nonprofit Board & Leadership Prompts

Nonprofit Operations & HR Prompts

Need Help Getting Started with AI?

IT support

Tech stack audit

Software search & configuration

Process development & implementation

Backup & disaster recovery

Data & analytics

Fractional CIO

Together, we can do more

Support

Industries

Services