Claude Prompt Library

Claude Prompts for Nonprofits

30 copy-paste prompts

Paste in your program, donor, or grant details and get a finished proposal, letter, or report back in one reply. Not "give me some advice".

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Grant Proposals & Funder Communications

5 prompts

Grant Proposal Narrative for a Program

1/30

You are a senior grant writer at a nonprofit. <context> A program officer needs a full grant proposal narrative for a specific foundation's application before the deadline. </context> <inputs> - Program name, the need it addresses, and target population: [PLACEHOLDER] - Funder name and funding priorities stated in their guidelines: [PLACEHOLDER] </inputs> <task> Draft a grant proposal narrative covering need statement, program description, goals and measurable objectives, and evaluation plan. Invent realistic sample program details if none are given. This is a drafting aid, not a substitute for the program lead's review before submission. </task> <constraints> - Tie every goal to a specific, measurable objective with a number and timeframe. - Mirror language from the funder's stated priorities where it genuinely fits the program. - Keep the narrative under 1200 words unless the funder's format requires more. </constraints> <format> A structured grant proposal narrative with labeled sections. </format>

Drafts a full grant narrative with a need statement, measurable objectives, and an evaluation plan for a specific funder.

๐Ÿ’ก

Pro tip: Pull 2 or 3 exact phrases from the funder's own guidelines into the narrative, reviewers notice language that mirrors their own priorities back to them.

Letter of Inquiry to a Foundation

2/30

You are a development director at a nonprofit. <context> A foundation accepts letters of inquiry before a full proposal, and one needs to be drafted to request an invitation to apply. </context> <inputs> - Foundation name and its stated giving focus: [PLACEHOLDER] - Program to be funded and requested amount: [PLACEHOLDER] </inputs> <task> Draft a one to two page letter of inquiry introducing the organization, the need, the proposed program, and the requested amount. Invent realistic sample organization details if none are given. </task> <constraints> - Open with a single sentence stating the ask and the amount. - Keep the full letter to 2 pages maximum. - Close with a specific, named next step, not a generic "looking forward to hearing from you". </constraints> <format> A formatted letter of inquiry. </format>

Drafts a concise letter of inquiry that states the ask upfront and closes with a specific next step.

๐Ÿ’ก

Pro tip: State the dollar amount in the first paragraph, not buried near the end, program officers skim for the ask before reading the story.

Grant Budget Narrative

3/30

You are a grants manager at a nonprofit. <context> A grant application requires a budget narrative explaining the line items in the attached budget spreadsheet. </context> <inputs> - Budget line items and amounts (staff, materials, overhead, etc.): [PLACEHOLDER] - Total grant request and program period: [PLACEHOLDER] </inputs> <task> Write a budget narrative explaining what each major line item covers and why it is necessary to the program. Invent realistic sample line items if none are given. </task> <constraints> - Address every line item over 10% of the total budget individually. - State the indirect or overhead rate explicitly if one is used. - Keep each line item explanation to 2 to 3 sentences. </constraints> <format> A structured budget narrative document. </format>

Explains each major budget line item's purpose and cost basis for a grant application.

๐Ÿ’ก

Pro tip: State your indirect rate as the exact percentage the funder allows, an unstated or vague overhead line is one of the most common reasons budgets get sent back.

Grant Report to a Funder

4/30

You are a program manager at a nonprofit reporting on a completed grant period. <context> A funder requires a report on how grant funds were used and what results the program achieved during the funding period. </context> <inputs> - Program activities completed and people served during the period: [PLACEHOLDER] - Original goals from the grant agreement and actual results: [PLACEHOLDER] </inputs> <task> Draft a grant report covering activities completed, results against original goals, budget summary, and lessons learned. Invent realistic sample results if none are given. </task> <constraints> - Report results against the original stated goals side by side, not just as a narrative. - Include one specific story or example alongside the aggregate numbers. - Note any goal not fully met with a plain explanation, not a euphemism. </constraints> <format> A structured grant report document. </format>

Reports results against original grant goals side by side, with one specific story alongside the aggregate numbers.

๐Ÿ’ก

Pro tip: Name any missed goal plainly rather than softening it, funders trust future proposals more from organizations that report shortfalls honestly.

Follow-up Email After a Declined Grant

5/30

You are a development director at a nonprofit. <context> A grant application was declined and the organization wants to keep the relationship warm for a future cycle. </context> <inputs> - Foundation name and any feedback given on the decline: [PLACEHOLDER] - Next application cycle or deadline, if known: [PLACEHOLDER] </inputs> <task> Draft a short, gracious follow-up email thanking the funder for their consideration and asking about the next opportunity to apply. Invent realistic sample context if none are given. </task> <constraints> - Keep the email under 150 words. - Do not re-argue the case for the declined proposal. - Ask one specific, answerable question about future cycles. </constraints> <format> A short, client-ready email. </format>

Keeps a funder relationship warm after a decline with a short, gracious note and one specific question.

๐Ÿ’ก

Pro tip: Send this within 2 weeks of the decline, while the program officer still remembers the proposal, not months later when it needs re-introducing.

Donor Letters & Fundraising Appeals

5 prompts

Year-End Fundraising Appeal Letter

6/30

You are a development director at a nonprofit. <context> The year-end giving season is approaching and a fundraising appeal letter needs to go out to the full donor list. </context> <inputs> - Organization's mission and the specific program the appeal supports: [PLACEHOLDER] - Fundraising goal for the campaign and the deadline (e.g. December 31): [PLACEHOLDER] </inputs> <task> Draft a year-end appeal letter that opens with a specific story, states the need and the ask clearly, and closes with a sense of urgency tied to the deadline. Invent a realistic sample story if none are given. </task> <constraints> - Open with one specific person or moment, not a general mission statement. - State a specific suggested gift amount or a range, not just "any amount helps". - Keep the letter to one page. </constraints> <format> A one-page appeal letter. </format>

Opens a year-end appeal with a specific story and closes with a clear ask and deadline.

๐Ÿ’ก

Pro tip: Use a real story with the donor's or client's permission, not the invented placeholder, sign-off from a lived example almost always outperforms a composite.

Major Donor Cultivation Letter

7/30

You are a major gifts officer at a nonprofit. <context> A prospective major donor has shown interest in the organization and needs a personalized cultivation letter before an ask meeting. </context> <inputs> - Donor's known interests or past involvement with the organization: [PLACEHOLDER] - Program or initiative most aligned with those interests: [PLACEHOLDER] </inputs> <task> Draft a personal cultivation letter connecting the donor's specific interests to a matching program, without making a direct ask yet. Invent realistic sample donor interests if none are given. </task> <constraints> - Reference the donor's specific interest or past involvement in the first paragraph. - Do not include a specific dollar ask in this letter. - End with an invitation to a conversation or visit, not a donation request. </constraints> <format> A personalized letter. </format>

Connects a major donor's specific interests to a matching program and invites a conversation, no ask yet.

๐Ÿ’ก

Pro tip: Confirm the donor's stated interest with your CRM notes before sending, a cultivation letter that misreads what they actually care about can set the relationship back.

Donor Thank-You Letter After a Gift

8/30

You are a donor relations coordinator at a nonprofit. <context> A donor just made a gift and needs a prompt, specific thank-you letter, not a generic receipt. </context> <inputs> - Donor name, gift amount, and program or fund it supports: [PLACEHOLDER] - One specific, concrete impact that gift size typically funds: [PLACEHOLDER] </inputs> <task> Draft a thank-you letter that names the specific gift, connects it to a concrete impact, and avoids sounding like a form letter. Invent a realistic sample impact statement if none are given. </task> <constraints> - State the exact gift amount and date. - Translate the gift into one specific, concrete outcome (a number of meals, sessions, or families served), not a vague "makes a difference". - Include the required tax-deductibility statement as a placeholder line for the finance team to confirm. </constraints> <format> A one-page thank-you letter. </format>

Thanks a donor by name and connects their exact gift amount to one concrete, specific outcome.

๐Ÿ’ก

Pro tip: Send this within 48 hours of the gift, thank-you letters that go out a week or more later measurably hurt repeat giving.

Lapsed Donor Re-engagement Email

9/30

You are a development associate at a nonprofit. <context> A donor who gave in the past has not given again in over a year and needs a re-engagement email. </context> <inputs> - Donor's giving history (last gift amount and date): [PLACEHOLDER] - What has changed or grown in the organization's work since then: [PLACEHOLDER] </inputs> <task> Draft a re-engagement email that acknowledges the donor's past support, shares one specific update, and makes a low-friction ask to give again. Invent realistic sample updates if none are given. </task> <constraints> - Reference the donor's last gift specifically, not generically. - Share exactly one update, not a full newsletter recap. - Make the ask a single clear sentence with a specific suggested amount. </constraints> <format> A short, client-ready email. </format>

Re-engages a lapsed donor with one specific update and a single, low-friction ask.

๐Ÿ’ก

Pro tip: Reference their exact last gift amount, not a rounded figure, specificity signals the organization actually tracks its donors rather than mass-emailing a list.

Peer-to-Peer Fundraising Toolkit Email

10/30

You are a peer-to-peer fundraising coordinator at a nonprofit. <context> Supporters have signed up to fundraise on the organization's behalf and need a toolkit email with sample messaging to get started. </context> <inputs> - Campaign name, goal, and end date: [PLACEHOLDER] - Individual fundraising target per participant: [PLACEHOLDER] </inputs> <task> Draft a toolkit email for peer fundraisers that includes their personal page setup steps, 2 sample social posts, and one sample ask email they can send to their own network. Invent realistic sample copy if none are given. </task> <constraints> - Include exactly 2 short social post drafts, one casual and one direct ask. - Include one sample email the fundraiser can copy and personalize. - State the individual fundraising target as a specific number. </constraints> <format> A toolkit email with embedded sample copy. </format>

Gives peer fundraisers ready sample posts and an ask email so they can start fundraising the same day.

๐Ÿ’ก

Pro tip: Give fundraisers copy they can personalize in one line, not copy they have to rewrite from scratch, friction at setup is the main reason signed-up peer fundraisers never post.

Impact Reports & Program Evaluation

5 prompts

Annual Impact Report Summary

11/30

You are a communications director at a nonprofit. <context> The organization's annual impact report is due and needs a narrative summary pulling the year's key results together. </context> <inputs> - Year's key program metrics (people served, programs run, outcomes): [PLACEHOLDER] - Total funds raised and how they were allocated across programs: [PLACEHOLDER] </inputs> <task> Write an annual impact summary covering the year's reach, key outcomes, and how funds were used, opening with the single most compelling result. Invent realistic sample metrics if none are given. </task> <constraints> - Open with one headline number, not a mission recap. - Show fund allocation as a simple percentage breakdown by program area. - Keep the summary to 500 words, suitable as the lead narrative in a longer report. </constraints> <format> A structured summary document. </format>

Opens an annual impact report with the year's single strongest result, then breaks down reach and fund allocation.

๐Ÿ’ก

Pro tip: Pick the headline number your board argued about most this year, it's usually the one your donors will find most convincing too.

Live Program Impact Dashboard

12/30

You are a data and evaluation manager at a nonprofit. <context> The organization wants a visual dashboard of program impact metrics to share with the board and major donors instead of a static PDF. </context> <inputs> - Program metrics by quarter for the year (people served, sessions delivered, outcomes achieved): [PLACEHOLDER] - Reporting year and program name: [PLACEHOLDER] </inputs> <task> Build a self-contained HTML dashboard with summary KPI cards at the top and a chart showing the quarterly trend for people served and outcomes achieved. Use realistic seeded sample data if none are given. </task> <constraints> - Use only inline CSS and inline SVG or canvas charting, no external libraries or network calls. - Include exactly 4 KPI summary cards above the chart. - Make the dashboard readable on both light and dark backgrounds. </constraints> <format> A single self-contained HTML file, previewable as a live artifact. </format>

Generates a self-contained HTML impact dashboard with KPI cards and a quarterly trend chart for board or donor use.

๐Ÿ’ก

Pro tip: Pull the quarterly numbers straight from your program database export, not from memory, a dashboard is only as trustworthy as the data behind it.

Program Outcomes One-Pager for a Funder

13/30

You are a program officer at a nonprofit. <context> A funder wants a concise one-page summary of a specific program's outcomes for their own internal reporting. </context> <inputs> - Program name, target population, and time period covered: [PLACEHOLDER] - Key outcome metrics achieved in that period: [PLACEHOLDER] </inputs> <task> Produce a one-page outcomes summary with the program's purpose, who it served, and its measurable outcomes. Invent realistic sample outcome metrics if none are given. </task> <constraints> - Limit the summary to exactly one page. - Present outcomes as a short bulleted list with a number in every bullet. - Include the time period covered directly under the program name. </constraints> <format> A one-page outcomes summary document. </format>

Summarizes one program's measurable outcomes on a single page, formatted for a funder's own internal reporting.

๐Ÿ’ก

Pro tip: Ask the funder what metrics their own board actually reads before writing this, matching their internal reporting format gets your program cited more often.

Case for Support Document

14/30

You are a development director at a nonprofit. <context> The organization needs a core "case for support" document that lays out why the work matters, to be reused across grant applications and donor conversations. </context> <inputs> - Organization's mission and the problem it addresses: [PLACEHOLDER] - Evidence of the problem's scale and the organization's track record: [PLACEHOLDER] </inputs> <task> Draft a case for support covering the problem, why it matters now, the organization's approach and track record, and what support enables next. Invent realistic sample evidence if none are given. </task> <constraints> - State the scale of the problem with at least one specific statistic. - Include exactly one track record example with a number attached. - End with a specific statement of what the next dollar of support enables. </constraints> <format> A structured case for support document, 2 to 3 pages. </format>

Builds a reusable case for support document with problem scale, track record, and what the next dollar enables.

๐Ÿ’ก

Pro tip: Cite the source for every statistic used, this document gets copied into grant applications where an unsupported number becomes a real credibility risk.

Quarterly Program Evaluation Summary

15/30

You are a program evaluation manager at a nonprofit. <context> A program's quarterly data has come in and needs to be turned into an evaluation summary for internal program staff, not external funders. </context> <inputs> - Quarter's activity data and outcome metrics against targets: [PLACEHOLDER] - Any known implementation challenges from the quarter: [PLACEHOLDER] </inputs> <task> Write an internal evaluation summary comparing actual results to targets, naming challenges plainly, and recommending adjustments for next quarter. Invent realistic sample data if none are given. </task> <constraints> - Show actual versus target for each metric side by side. - Name at least one challenge honestly, without softening language. - End with exactly 3 recommended adjustments for next quarter. </constraints> <format> A structured internal evaluation summary. </format>

Compares quarterly results to targets and recommends 3 specific adjustments for program staff, not funders.

๐Ÿ’ก

Pro tip: Write this one for internal eyes only and say so at the top, staff report challenges more honestly when they know it isn't going straight to a funder.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Volunteer Communications & Management

5 prompts

Volunteer Recruitment Email

16/30

You are a volunteer coordinator at a nonprofit. <context> A program needs more volunteers for an upcoming season and a recruitment email needs to go out to the community list. </context> <inputs> - Volunteer role, time commitment, and required skills (if any): [PLACEHOLDER] - Start date and how to sign up: [PLACEHOLDER] </inputs> <task> Draft a recruitment email describing the role, the time commitment, and why it matters, with a clear single call to action to sign up. Invent realistic sample role details if none are given. </task> <constraints> - State the exact time commitment in the first two sentences. - Include one sentence on what a volunteer in this role actually does day to day. - End with a single, clear call to action and link placeholder. </constraints> <format> A recruitment email. </format>

States the exact time commitment upfront and closes with one clear sign-up call to action.

๐Ÿ’ก

Pro tip: Lead with the time commitment, not the mission, vague time asks are the top reason interested volunteers never actually sign up.

Volunteer Onboarding Welcome Packet

17/30

You are a volunteer manager at a nonprofit. <context> A new volunteer has signed up and needs a welcome packet before their first shift. </context> <inputs> - Volunteer role and first shift date and location: [PLACEHOLDER] - Who they'll report to and what to bring or wear: [PLACEHOLDER] </inputs> <task> Produce a welcome packet covering what to expect on the first shift, who to contact with questions, and any required forms or preparation. Invent realistic sample details if none are given. </task> <constraints> - State the exact first shift date, time, and location at the top. - Name a single point of contact with how to reach them. - List anything the volunteer needs to bring or complete before arriving. </constraints> <format> A one-page welcome packet document. </format>

Gives a new volunteer the first-shift logistics, a named contact, and any prep needed before day one.

๐Ÿ’ก

Pro tip: Put the exact address and a parking or entry note in the first line, new volunteers who can't find the entrance often just leave.

Volunteer Shift Reminder and Confirmation Email

18/30

You are a volunteer coordinator at a nonprofit. <context> Volunteers are scheduled for an upcoming shift and need a reminder email a few days before, with an easy way to confirm or cancel. </context> <inputs> - Shift date, time, and location: [PLACEHOLDER] - What volunteers should bring or wear, if anything: [PLACEHOLDER] </inputs> <task> Draft a short reminder email confirming the shift details and giving a clear way to cancel or reschedule if they can no longer make it. Invent realistic sample details if none are given. </task> <constraints> - State date, time, and location in the first sentence. - Include a specific instruction for how to cancel, not just "let us know". - Keep the email under 100 words. </constraints> <format> A short reminder email. </format>

Confirms shift logistics in the first sentence and gives a specific cancel path to reduce no-shows.

๐Ÿ’ก

Pro tip: Make canceling as easy as a one-line reply, volunteers who feel bad about a hard cancel process often just no-show instead.

Volunteer Appreciation Letter

19/30

You are a volunteer manager at a nonprofit. <context> A long-serving volunteer needs a personal appreciation letter recognizing their specific contribution, not a generic thank-you. </context> <inputs> - Volunteer name, role, and how long they've served: [PLACEHOLDER] - One specific contribution or moment worth calling out: [PLACEHOLDER] </inputs> <task> Draft an appreciation letter that names the volunteer's specific contribution and its concrete impact on the program. Invent a realistic sample contribution if none are given. </task> <constraints> - Reference one specific moment or contribution, not a general "thanks for everything". - State how long they've volunteered as a specific number. - Keep the letter to one page. </constraints> <format> A one-page appreciation letter. </format>

Recognizes a volunteer's specific contribution and tenure with a concrete example, not generic thanks.

๐Ÿ’ก

Pro tip: Ask their direct supervisor for the one moment they'd call out, the specific detail is what makes this land instead of reading as a form letter.

Volunteer Role Description for a New Program

20/30

You are a volunteer program manager at a nonprofit launching a new initiative. <context> A new program is launching and needs a formal volunteer role description before recruitment can start. </context> <inputs> - Program name and the tasks volunteers in this role will do: [PLACEHOLDER] - Time commitment, required skills, and any training provided: [PLACEHOLDER] </inputs> <task> Write a volunteer role description covering responsibilities, time commitment, required and preferred skills, and training provided. Invent realistic sample responsibilities if none are given. </task> <constraints> - List responsibilities as bullet points, not a paragraph. - Separate "required" from "preferred" skills clearly. - State the exact training commitment before the role starts, if any. </constraints> <format> A structured volunteer role description document. </format>

Documents a new volunteer role's responsibilities, required versus preferred skills, and training before recruitment starts.

๐Ÿ’ก

Pro tip: Cut the required skills list to what's truly non-negotiable, an overloaded requirements list is the fastest way to scare off willing volunteers who'd learn on the job.

Event Planning & Promotion

5 prompts

Fundraising Gala Event Plan

21/30

You are an events director at a nonprofit. <context> The organization is planning its annual fundraising gala and needs a full event plan to align staff and vendors. </context> <inputs> - Event date, venue, and expected attendance: [PLACEHOLDER] - Fundraising goal and planned revenue streams (tickets, sponsorships, auction, appeal): [PLACEHOLDER] </inputs> <task> Produce an event plan covering timeline, revenue streams and targets, staffing and vendor needs, and key milestones leading up to the event. Invent realistic sample details if none are given. </task> <constraints> - Break the timeline into milestones with dates counting down from the event. - Show each revenue stream with its own target amount that sums to the fundraising goal. - List staffing and vendor needs as a separate checklist section. </constraints> <format> A structured event plan document. </format>

Plans a fundraising gala with a countdown timeline, per-stream revenue targets, and a staffing checklist.

๐Ÿ’ก

Pro tip: Build the timeline backward from the event date, not forward from today, it surfaces which milestones are already at risk before it's too late to fix them.

Event Sponsorship Pitch Email

22/30

You are a corporate partnerships manager at a nonprofit. <context> The organization is seeking sponsors for an upcoming event and needs a pitch email to send to prospective business sponsors. </context> <inputs> - Event name, date, and expected audience: [PLACEHOLDER] - Sponsorship tiers and what each tier includes: [PLACEHOLDER] </inputs> <task> Draft a sponsorship pitch email introducing the event, the audience it reaches, and the available sponsorship tiers with their benefits. Invent realistic sample tiers if none are given. </task> <constraints> - State the audience size and type in one specific sentence. - Present sponsorship tiers as a short list with the benefit of each. - End with a specific next step and a deadline to commit. </constraints> <format> A sponsorship pitch email. </format>

Pitches event sponsorship tiers with specific audience numbers and a clear deadline to commit.

๐Ÿ’ก

Pro tip: Give a real audience number, not "hundreds of supporters", sponsors are comparing this against other sponsorship offers that do state a number.

Event Save-the-Date and Invitation Copy

23/30

You are a communications coordinator at a nonprofit. <context> An upcoming event needs a save-the-date announcement followed later by the full invitation copy. </context> <inputs> - Event name, date, and location: [PLACEHOLDER] - Event purpose and any notable speaker or honoree: [PLACEHOLDER] </inputs> <task> Write both a short save-the-date announcement and a longer formal invitation with RSVP details. Invent realistic sample event details if none are given. </task> <constraints> - Keep the save-the-date under 50 words. - Include a clear RSVP deadline in the full invitation. - Name any speaker or honoree in the invitation, not the save-the-date. </constraints> <format> Two pieces of copy, labeled "Save the Date" and "Invitation". </format>

Writes a short save-the-date and a full invitation with an RSVP deadline, ready to send separately.

๐Ÿ’ก

Pro tip: Send the save-the-date at least 8 weeks out and the full invitation 3 to 4 weeks out, sending both close together loses the early calendar hold.

Post-Event Thank-You and Recap Email

24/30

You are an events coordinator at a nonprofit. <context> A fundraising event just wrapped and attendees need a thank-you email with a quick recap of what was raised. </context> <inputs> - Amount raised and attendance number: [PLACEHOLDER] - One specific highlight moment from the event: [PLACEHOLDER] </inputs> <task> Draft a post-event email thanking attendees, sharing the amount raised, and highlighting one specific moment from the event. Invent a realistic sample highlight if none are given. </task> <constraints> - State the amount raised in the first two sentences. - Include exactly one specific highlight, not a full recap of the evening. - End with what the funds raised will go toward next. </constraints> <format> A short, client-ready email. </format>

Announces the amount raised upfront, shares one highlight, and states what the funds go toward next.

๐Ÿ’ก

Pro tip: Send this within 24 hours while the event is still fresh, momentum from a good result fades fast if the recap arrives a week later.

Event Day-Of Run Sheet

25/30

You are an events manager at a nonprofit finalizing logistics for an event. <context> An event is happening soon and staff and volunteers need a minute-by-minute run sheet for the day. </context> <inputs> - Event start and end time, and the program agenda (speeches, dinner, auction, etc.): [PLACEHOLDER] - Staff and volunteer roles for the day: [PLACEHOLDER] </inputs> <task> Produce a minute-by-minute run sheet from setup through breakdown, with a named owner for each block. Invent realistic sample timing if none are given. </task> <constraints> - Give every time block a start time and a named or role-based owner. - Include setup and breakdown as their own time blocks, not just the program itself. - Flag any block with a hard external dependency (caterer, AV, venue staff). </constraints> <format> A minute-by-minute run sheet table. </format>

Builds a minute-by-minute day-of run sheet with a named owner for every block, including setup and breakdown.

๐Ÿ’ก

Pro tip: Add a 10 minute buffer after any block with an external vendor dependency, catering and AV are the two most common places a run sheet slips.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Board Updates & Governance

5 prompts

Board Meeting Briefing Memo

26/30

You are an executive director at a nonprofit preparing for a board meeting. <context> A board meeting is coming up and members need a briefing memo before the meeting summarizing what will be discussed and decided. </context> <inputs> - Meeting date and agenda items: [PLACEHOLDER] - Any decisions the board needs to make at this meeting: [PLACEHOLDER] </inputs> <task> Draft a briefing memo summarizing each agenda item, the background needed to discuss it, and any decision the board is being asked to make. Invent realistic sample agenda items if none are given. </task> <constraints> - List agenda items in the order they'll be discussed. - Mark each item requiring a board vote or decision explicitly. - Keep the memo to 2 pages. </constraints> <format> A structured briefing memo. </format>

Briefs board members on each agenda item and flags exactly which ones require a vote before the meeting.

๐Ÿ’ก

Pro tip: Send this at least 5 days before the meeting, not the night before, decisions go smoother when board members had time to actually read it.

Executive Director Report to the Board

27/30

You are an executive director at a nonprofit writing a regular update to the board. <context> The board expects a regular written report from the executive director covering organizational performance and key issues. </context> <inputs> - Key organizational metrics since the last report (programs, fundraising, staffing): [PLACEHOLDER] - Any significant risks, opportunities, or decisions pending: [PLACEHOLDER] </inputs> <task> Write an executive director's report covering organizational highlights, key metrics, and any risks or decisions the board should be aware of. Invent realistic sample metrics if none are given. </task> <constraints> - Open with the single most important update, positive or negative. - Present key metrics as a short table, not embedded in paragraphs. - Flag any risk or pending decision in its own clearly labeled section. </constraints> <format> A structured board report document. </format>

Opens with the most important update, then a metrics table and a clearly flagged risks section for the board.

๐Ÿ’ก

Pro tip: Lead with bad news as readily as good news, boards that only hear good updates get blindsided later and start double-checking everything.

Board Recruitment Pitch for a New Member

28/30

You are a board development committee chair at a nonprofit. <context> The board has identified a promising candidate and needs a recruitment pitch to invite them to join. </context> <inputs> - Candidate's background and why they're a fit for a board gap: [PLACEHOLDER] - Board expectations (meeting frequency, giving expectation, committee needs): [PLACEHOLDER] </inputs> <task> Draft a recruitment pitch, as an email or talking points, explaining why this candidate specifically is being asked, the organization's work, and what board service involves. Invent realistic sample details if none are given. </task> <constraints> - State the specific skill or connection gap this candidate would fill. - List board expectations explicitly, including any giving expectation, not vaguely. - End with a specific next step, such as a coffee meeting or a board meeting observation. </constraints> <format> A recruitment pitch, as an email plus talking points. </format>

Pitches a specific board candidate on the exact gap they'd fill and states expectations plainly upfront.

๐Ÿ’ก

Pro tip: State the giving expectation as a real number during recruitment, not after they've joined, surprising a new board member with it later damages trust fast.

Strategic Plan Progress Update for the Board

29/30

You are a director of strategy at a nonprofit reporting on a multi-year strategic plan. <context> The organization has a multi-year strategic plan and the board wants a progress update against its stated goals. </context> <inputs> - Strategic plan goals and their target dates: [PLACEHOLDER] - Progress made on each goal so far: [PLACEHOLDER] </inputs> <task> Write a progress update comparing each strategic goal to actual progress, using a clear status label for each. Invent realistic sample progress if none are given. </task> <constraints> - Give each goal a status label (on track, at risk, behind, complete). - Explain any "at risk" or "behind" goal with a specific reason and a proposed fix. - Present the goals as a table with goal, target date, and status. </constraints> <format> A table plus a short narrative summary. </format>

Status-labels every strategic plan goal against its target date and proposes a fix for anything at risk.

๐Ÿ’ก

Pro tip: Propose a specific fix for every at-risk goal in the same document, a status update without a fix just restates the problem back to the board.

Board Meeting Minutes Template

30/30

You are a board secretary at a nonprofit. <context> A board meeting just happened and formal minutes need to be drafted from the discussion notes for board approval. </context> <inputs> - Meeting date, attendees, and agenda items covered: [PLACEHOLDER] - Key discussion points, motions made, and votes taken: [PLACEHOLDER] </inputs> <task> Draft formal board meeting minutes recording attendance, each agenda item discussed, and any motions with the vote result. Invent realistic sample discussion points if none are given. </task> <constraints> - Record every motion with its exact wording, who moved it, who seconded, and the vote result. - Keep discussion summaries factual and neutral, not editorializing on who said what. - Note the time the meeting was called to order and adjourned. </constraints> <format> A formal board minutes document. </format>

Records attendance, agenda items, and every motion with its exact vote result in formal minutes.

๐Ÿ’ก

Pro tip: Write the motion wording down verbatim during the meeting if possible, reconstructing exact motion language afterward is where minutes most often get disputed.

Frequently Asked Questions

Copy a prompt, fill in the bracketed placeholders with your program, donor, or grant details, and paste it into Claude. Leave a placeholder blank and Claude fills in realistic sample data so you can see the output format first.
Claude can draft a strong first-pass narrative, budget explanation, or report section from the details you give it, but your program lead should always review the final version before it's submitted to a funder.
The prompts ask Claude for specific, concrete language tied to your actual program details rather than generic filler, but you should still edit in your organization's voice and any donor-specific history before sending.
Yes. Most prompts need only a few details filled in, they're built so a single staff member wearing multiple hats can produce a donor letter, report, or board memo without starting from a blank page.
Yes. The impact dashboard prompt returns a single self-contained HTML file you can open in a browser, screen-share on a call, or project directly in a board meeting.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.