Claude Project: Build a Persistent Program Operations Assistant

What This Builds

Right now, every time you ask Claude for help, you re-explain your program, your funders, your team structure, and your reporting formats from scratch. That setup tax adds up across a week of board updates, case note summaries, evaluations, and SOPs. This build puts all of that context in one place, permanently. You create a Claude Project, load it once with your program's real structure and reference documents, and every conversation inside it starts already knowing your organization instead of starting from zero.

Prerequisites

• Pro subscription ($20/month total ongoing cost)
• A short written description of your program (mission, population served, funders, team)
• Copies of 2-3 recent documents you already produce: a board update, a funder report, an SOP, or evaluation notes
• 1-2 hours to set up; a few minutes per use afterward

The Concept

A Claude Project works like a case file you hand a new staff member on day one, except this staff member reads the whole file before every conversation and never forgets it. You write standing instructions that describe your program and how you like things written. You upload a handful of real documents as reference material. From then on, every chat inside that Project starts already knowing your funders' names, your program's structure, and your organization's voice, so you spend your time on the actual writing task instead of the fifteen minutes of context you'd otherwise type out first.

Build It Step by Step

Part 1: Set Up the Project

1. Go to claude.ai and click Projects in the left sidebar.
2. Click New Project and name it something specific to your role, for example "[Your Program Name] Operations."
3. Click Edit Project Instructions and write your standing instructions using the template below.

Project instructions template:

You are a program operations assistant for [Program Name], a
[youth mentoring / housing stability / after-school / food access]
program run by [Organization Name], a nonprofit serving [population/area].

## Program Profile
- Population served: [description]
- Program size: [number] participants per [year/quarter]
- Team: [number] staff, [number] regular volunteers
- Funders: [list the 2-4 funders you report to most often]
- Case management system: [system name, e.g. Salesforce Nonprofit Cloud,
  Bloomerang, or "paper/spreadsheet based"]

## My Role
I am the Program Manager. I write: funder reports, board updates, case note
summaries, staff and volunteer evaluations, training materials, and SOPs.

## How to Help Me
- Summarize case notes or meeting notes into the sections I ask for
- Draft board updates and funder reports matching the tone of documents I
  upload as examples
- Draft performance evaluations from notes I paste, using our four-category
  format: quality of work, reliability, teamwork, growth areas
- Draft SOPs from a plain description of a process
- Ask clarifying questions when a request is ambiguous rather than guessing

## Tone
- Board and funder writing: professional, warm, concise, never inflated
- Staff and volunteer writing: direct and specific, growth-oriented
- Default to short paragraphs and plain language over jargon

## Data Handling
- I will never paste a client's full name, date of birth, or other
  identifying detail into this Project. Treat any note I share as
  de-identified unless I say otherwise.
- If something I paste looks like it might contain identifying information,
  point it out before responding.

Click Save.

Part 2: Upload Reference Documents

Click Add Content and upload:

1. A recent board update or funder report, so Claude has a real tone reference
2. Your program's rough outline or an existing SOP, if one exists
3. A blank version of your most common evaluation form or template

What you should see: the documents listed under the Project's knowledge panel. Claude reads them at the start of every conversation inside this Project, not just once.

Part 3: Test and Refine

Start a new chat inside the Project and run three real tests.

Test 1, case note summary:

Test 2, board update:

Test 3, evaluation draft:

Check each output against two things: does it use your program's real terminology (funder names, team roles, program name) without you having to add it, and does the tone match what you uploaded. If either is off, go back to the instructions and add the missing detail near the top, Claude weighs earlier instructions more heavily than later ones.

Real Example: A Monday Morning Batch

Setup: You built the Project with your program profile, your funders, and one sample board update.

Monday, inside your Program Operations project:

You: "Here are eight de-identified case notes from last week. Summarize into common needs, urgent flags, and follow-ups for today's 10am staffing meeting."

Claude: produces a three-section summary that flags two families needing a referral follow-up, without you having to explain what your intake process looks like, because that context is already in the Project.

You (same conversation): "Now turn last week's numbers, 31 families served, 4 new referrals sent, into two sentences I can drop into this month's board update."

Time saved: The case note summary that used to take 45-60 minutes of manual reading takes about 10 minutes to review. The board update sentences that follow it take another 5, because the Project already knows your program's voice and doesn't need re-explaining mid-conversation.

What to Do When It Breaks

• Claude doesn't reference your uploaded documents → Remove and re-upload them. Files over roughly 30MB or in unsupported formats sometimes fail silently on upload.
• Output ignores your instructions → Move your most important rules (data handling, tone, format) to the very top of the instructions field. Length dilutes emphasis.
• Responses feel generic despite setup → Add more specific detail: your actual funder names, your real program size, a sentence about what makes your population served different from a generic description. Specific detail is what separates a Project from a plain chat.
• You forget the Project exists and default back to a blank chat → Bookmark the Project's URL or pin it, whichever your routine actually sticks to. A Project that gets bypassed saves nothing.

Variations

• Simpler version: Use Claude's account-level Custom Instructions (Settings menu) for lightweight standing context without managing a full Project. Less powerful, but zero ongoing maintenance.
• Extended version: Build a second Project scoped to one specific funder if that funder's reporting requirements are complex enough to deserve their own space, separate from your general operations Project.

What to Do Next

• This week: Set up the Project with your program profile and one reference document; run one real case note summary through it.
• This month: Add your evaluation template and SOP examples. Make the Project your default starting point for any board or funder writing.
• Advanced: Pair this with a funder-specific Custom GPT in ChatGPT (see the "Custom GPT: Build a Reusable Funder Report Writer" guide) so this Project handles the broader drafting work and the Custom GPT handles final funder-specific formatting.

Advanced guide for Nonprofit Program Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.