For Nonprofit Executive Directors ·
What you'll accomplish
Right now, every time you draft a committee charter or a board policy, you retype the same context: your bylaws, your existing committee structure, how your board actually operates. A Claude Project fixes that. Upload your governance documents once, and every conversation inside that Project already knows your organization. You ask for a draft, and it comes back sounding like your board, not a generic template.
What you'll need
Gather digital files (PDF or Word) for your bylaws, any standing board policies, existing committee charters, and a handful of recent board packets or approved minutes. If any of these only exist on paper, scan them or export them from wherever your board stores files.
What you should see: A folder on your computer with 5 to 10 documents in it.
Troubleshooting: If your bylaws only exist as a scanned image, Claude can still read most scanned PDFs, but double-check the extracted text once it's uploaded rather than assuming it read every clause correctly.
Before you upload anything: Board packets and minutes can carry personnel matters, donor names and gift details, or notes from an executive session. Pull those pages out, or swap in a version with names and figures replaced by role labels, before a packet goes into this Project. Anything genuinely executive-session should stay out entirely unless the board chair has said otherwise.
Go to claude.ai and sign in. Look for Projects in the left sidebar and click it. Then click the button to start a new project. Name it something clear, like "Board Governance."
What you should see: A new, empty project workspace with a place to add a project description and a knowledge base panel on the side.
In the project's instructions field, describe what this Project is for. Use something like:
This project supports governance writing for a small nonprofit. I am the executive director. When I ask for a draft (a committee charter, a policy update, board meeting talking points), write it consistent with the uploaded bylaws and existing committee structure. Flag anywhere a draft would conflict with the bylaws or an existing policy instead of quietly overriding it.
What you should see: Your instructions saved to the project. Claude will apply them to every conversation you start inside this Project.
In the same project, find the option to add files to the project's knowledge base and upload your bylaws, board policies, and committee charters first. Add 2 to 3 recent board packets or minutes sets after that.
What you should see: Your files listed in the knowledge base panel, usually with a short processing delay before each one is ready to reference.
Troubleshooting: On the free plan, a project can hold a limited amount of content before older or larger files start getting less attention in answers. If you have many years of packets, start with just the bylaws, policies, and charters. Add packets a few at a time after that rather than dumping in everything at once.
Click into the Project and start a new conversation (this is separate from a regular Claude chat: it stays inside the Project and keeps its knowledge base). Ask a question that should draw on the uploaded documents.
Example prompt to copy-paste:
Based on our bylaws and current committee structure, draft a one-page charter for a new Finance Committee: purpose, membership (who serves and how they're appointed), meeting frequency, and what it reports back to the full board.
What you should see: A draft that references your actual board size, your actual committee-appointment process (not a generic "the board shall appoint" placeholder), and language that reads consistent with your other charters.
Read the draft next to your actual bylaws. Confirm it did not invent a committee-appointment process or a quorum rule that isn't in your governing documents.
Troubleshooting: If a draft contradicts your bylaws, tell Claude directly: "Section 4.2 of the bylaws says committee members are appointed by the board chair, not elected. Redo the membership section." It will correct the next draft using that correction.
Copy the finished draft into your board's actual document system (wherever you store approved governance documents), not just into your Claude history. Add a genuinely new or updated policy back into the Project's knowledge base later so future drafts stay current.
What you should see: Your governance document library growing over time, with each new addition making future drafts more accurate.
Board policy first draft:
Draft a first version of a [conflict-of-interest / document-retention / whistleblower] policy section, consistent with our existing board policies in tone and structure. Note anywhere this needs counsel's review before adoption.
Board packet cover memo:
Using the attached rough notes, draft the cover memo section of this month's board packet: a short overview of what's on the agenda and what decision, if any, the board needs to make at each item.
Bylaws or policy consistency check:
Read the attached draft policy against our bylaws. Point out anything that conflicts with or duplicates an existing bylaw provision, and anywhere the draft is silent on something the bylaws require.
Board recruitment matrix starter:
Based on our current board roster and committee structure, draft a skills-and-representation matrix template for board recruitment: the categories we should be tracking (skills, sector connections, lived experience, giving capacity) and a short description of each.