Claude Project Prompt Chain: Assemble the Monthly Board Packet

For Nonprofit Executive Directors

Tools: Claude Projects | Time to build: 45 minutes to 1 hour | Difficulty: Advanced Prerequisites: Comfortable creating a Claude Project with custom instructions and uploaded files. See the Level 3 governance-assistant guide for this role.

What This Builds

Instead of opening a blank document and writing the whole board packet narrative in one sitting, you run four source updates through a chain of prompts inside a Claude Project, one per area of the organization, and review each section before the next one gets added. The packet assembles itself section by section, with you checking the work at every handoff instead of proofreading one long draft at the end.

Prerequisites

• Comfortable creating a Claude Project with custom instructions and uploaded files (see the Level 3 governance-assistant guide for this role)
• A Pro subscription ($20/month): Sign up
• The month's four source updates ready to paste in: a finance summary, program dashboard notes, a development update, and HR items
• Total ongoing cost: $20/month for the Claude plan this build needs, assuming you already have the governance-assistant Project set up

The Concept

A prompt chain is a relay race instead of a single long sprint. Each prompt hands off a finished section to the next one, and you inspect the baton before it moves on. The finance section gets written and checked, then the program section, then development, then HR, and only after all four are approved does a final prompt stitch them into one packet. If one section needs a rewrite, you catch it before it's buried inside a fifty-page document instead of after.

Build It Step by Step

Part 1: Set Up the Chain Inside Your Governance Project

Use the Claude Project you already built for board governance (bylaws, policies, past minutes). Start a new conversation inside that Project each month rather than reusing last month's thread, so old numbers don't bleed into the new packet.

Part 2: Run the Four Section Prompts, One at a Time

Each prompt below produces one section. Read and edit the output before moving to the next prompt. Do not paste all four source documents into one prompt. Running them one at a time is what makes each section checkable on its own.

Prompt 1: Finance section

Here is this month's finance summary: [paste budget-vs-actual notes, cash position,
any variance explanations from your bookkeeper or treasurer, with donor names and
specific gift amounts removed or aggregated].

Write the Financial Update section of a board packet. Plain language, no jargon
the board would need explained. Flag any line item more than 10 percent off budget
and note whether that's a timing issue or a real variance. Two to three paragraphs.

Checkpoint: Read it. Does the variance explanation match what your treasurer actually told you? Fix anything before continuing.

Prompt 2: Program section

Here is this month's program dashboard: [paste program manager notes, outcome
metrics, any service-delivery issues, with client or participant names removed].

Write the Program Update section of a board packet. Cover what happened, what's
on track, and anything that needs board awareness or a decision. Two paragraphs.

Checkpoint: Confirm the metrics match your dashboard exactly. Claude summarizes what you give it; it doesn't verify numbers against a source system.

Prompt 3: Development section

Here is this month's development update: [paste high-level fundraising progress,
pipeline status, upcoming events, with individual donor names and gift amounts
aggregated into totals or ranges].

Write the Development Update section of a board packet, framed for board members
who may be asked to make an introduction or attend an event. Two paragraphs.

Checkpoint: This section reports fundraising progress from the ED's seat. It is not the appeal letter or thank-you note the development director sends to donors directly.

Prompt 4: HR and people section

Here is this month's HR update: [paste staffing changes, open roles, anything
the board needs to know, with performance or disciplinary specifics left out
unless the board must act on them].

Write the People and HR Update section of a board packet. Note any item that
needs board approval (a new senior hire, a policy change) separately from
items that are informational only. One to two paragraphs.

Checkpoint: Personnel matters are sensitive even in summary form. Read this one twice before it goes anywhere near the full packet.

Part 3: Assemble the Final Packet

Once all four sections are approved, run the assembly prompt in the same conversation so Claude has the full chain in context:

Combine the four approved sections above into one board packet narrative,
in this order: Financial Update, Program Update, Development Update, People
and HR Update. Add a short opening paragraph from me as executive director
that highlights the one or two items the board most needs to focus on this
month. Use clear headers for each section, board-ready tone throughout.

This assembly step is long-document work, combining four separate sections plus your opening paragraph in one pass, so it benefits from a model built for handling extended context well. If your Project lets you pick a model for the conversation, choose Sonnet 5 before running this prompt.

Checkpoint: This is the version that goes in front of the board. Read the whole thing start to finish, not just the new opening paragraph, since combining four separately written sections can leave a rough transition or repeated point between them.

Part 4: Optional Fifth Prompt: One-Page Highlights

If your board prefers a highlights page ahead of the full packet:

Write a one-page summary of the packet above: the two or three decisions or
discussion items the board needs to prioritize, in plain bullet points, no
more than half a page.

Real Example: A February Board Meeting Packet

Setup: The governance Project already holds the bylaws, board policies, and January minutes.

Input: A finance summary showing program-service revenue running 8 percent under budget due to a delayed grant payment, program notes on a new after-school cohort launch, a development update on spring gala planning, and an HR note about an open case-manager role.

Output: Four checked sections, then one assembled packet with an opening paragraph flagging the revenue timing issue and the open role as the two things the board should focus on, plus a one-page highlights sheet for board members who only read the summary.

Time saved: What used to take a full evening writing from a blank page now runs as five short review passes across about 45 minutes, most of it spent checking facts rather than drafting sentences.

What to Do When It Breaks

• A section reads generically, like it could belong to any nonprofit → Add a specific number, name of a program, or actual quote from your notes into the prompt. Claude writes to the specificity of what you give it.
• The assembled packet repeats the same point in two sections → This happens when the finance and program updates both mention the same grant. Tell Claude in the assembly prompt which section should own that point and to cut it from the other.
• You start skipping the checkpoints because you're behind schedule → That defeats the reason to chain the prompts instead of writing one long one. If you're short on time, cut to two prompts (finance and program only) rather than skipping review on all four.
• Claude states a program metric that doesn't match your actual dashboard → Always paste the real numbers into the prompt rather than asking Claude to recall last month's figures from memory. It only knows what's in this conversation.

Variations

• Simpler version: Run one prompt with all four updates pasted together and a single assembly instruction. Faster, but you lose the per-section checkpoint that catches errors early.
• Extended version: Add a fifth source, a brief compliance or risk note, as its own prompt and checkpoint when there's a filing or audit item the board needs to see that month.

What to Do Next

• This week: Run the chain once with real numbers for your next board meeting and time how long each checkpoint actually takes.
• This month: Save the four prompts as a note you can copy from each cycle instead of retyping them.
• Advanced: Pair this with the compliance-deadline Zapier automation and paste that week's deadline digest into the extended version's compliance prompt, so filing items reach the board from a list that has already been checked.

Advanced guide for nonprofit executive director professionals. Board packets carry financial detail, personnel matters, and sometimes executive-session material. Strip donor names and specific gift amounts, aggregate client or program participant details, and leave out anything from an active personnel investigation before pasting notes into any chatbot, free or paid.