How to Decide Which Nonprofit Workflows Should Be Approved for AI First

Many nonprofits are already using AI in small, unofficial ways, but the rules around donor data, confidential notes, public statements, and staff review often lag behind. This workflow helps you turn real internal material into a usable governance artifact instead of starting from a generic template. It is for nonprofit executives, operations leads, development leaders, board administrators, and policy owners who need something practical that staff can actually follow.

Editorial guardrail: Use AI to sort and score possible workflows, not to make the final governance decision by itself. A human reviewer should approve the scoring criteria and the final priority list.

What you need

• A list of candidate workflows such as donor emails, grant draft support, board summaries, volunteer scheduling, meeting notes, or spreadsheet cleanup
• A short scoring rubric that covers data sensitivity, public risk, time savings, review burden, and source quality
• Claude in a regular chat or Project
• One reviewer who can confirm whether the suggested priority order matches real organizational risk

How to capture or gather the source material

• Start with a simple spreadsheet or pasted list of workflows. For each workflow, note who does it, what input it uses, what output it creates, and whether sensitive data is involved.
• Draft a small rubric before you ask Claude to score anything. Good columns are data sensitivity, public exposure, repeat frequency, time saved, human review ease, and source grounding.
• If your organization already has privacy or confidentiality rules, keep them nearby so you can sanity-check the scoring afterward.
• Do not start with every workflow in the organization. A list of 10 to 20 common tasks is enough for a first pass.

The fastest workflow

1. Paste the workflow list and scoring rubric into Claude.
2. Ask Claude to score each workflow against the rubric and sort them into approve first, pilot later, or do not approve yet.
3. Review the output and change any scoring that feels disconnected from real operational risk.
4. Ask for a final checklist that names the first three workflows to pilot, the controls each one needs, and the workflows that should wait.
5. Use that list as your governance starting point instead of trying to approve everything at once.

Tool-specific instructions

Primary path: Claude

• Claude is a good fit here because the job is structured reasoning and ranking rather than file-heavy source synthesis.
• Give the scoring rubric first. Models produce better prioritization when the scoring logic is explicit.
• Ask for one short justification per score so you can spot when the model is overweighting time savings and underweighting risk.
• Keep the final output short enough to act on. A one-page prioritization list is more useful than a long strategy memo.

Fallback options

ChatGPT fallback

• Use ChatGPT if you want the scoring turned into a clean table or a quick visual prioritization matrix.
• Ask for the output in a sortable table so you can copy it into Sheets.

NotebookLM fallback

• If the scoring needs to be grounded in several policy documents, use NotebookLM first to pull the relevant constraints, then run the prioritization in Claude.
• That two-step path is helpful when your rules are scattered across several internal files.

Copy and paste prompt blocks tailored to the workflow

Primary prompt

{
  "task": "Score nonprofit workflows for AI approval priority.",
  "score_from_1_to_5": [
    "Data sensitivity",
    "Public or reputational risk",
    "Time savings",
    "Ease of human review",
    "Source grounding",
    "Operational repeatability"
  ],
  "required_output": [
    "One scoring table",
    "Approve first list",
    "Pilot later list",
    "Do not approve yet list",
    "Top three controls needed for the first pilots"
  ],
  "instructions": [
    "Explain each score briefly.",
    "Prefer low-risk, high-frequency, easy-to-review workflows in the approve first group.",
    "Do not assume the organization has enterprise contracts or special integrations unless the source list says so."
  ]
}

Fallback prompt

{
  "task": "Turn this nonprofit workflow list into a pilot-priority checklist for AI adoption.",
  "instructions": [
    "Use plain English.",
    "Keep the final priority list to one page.",
    "Name the tasks that are safest to approve first and explain why."
  ]
}

Quality checks

• Check that the highest-ranked workflows are actually easy to review and do not involve sensitive data by default.
• Make sure the scoring rubric is visible in the final output so leadership understands why a task was ranked where it was.
• Verify that the final short list is small enough to pilot within the next quarter.

Common failure modes and fixes

• Claude ranks flashy tasks too high: Tighten the rubric and increase the weight on data sensitivity and review burden.
• Too many workflows land in the middle: Force a distribution by asking for only three tasks in the approve first group.
• Leadership does not trust the scoring: Show the rubric and justification beside each task instead of just the final order.
• The list is too broad to act on: Split the workflow set by department and rank one team at a time.

Sources Checked

• Anthropic Help Center, How can I create and manage projects?. https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects. Accessed 2026-03-27.
• Anthropic Help Center, Uploading files to Claude. https://support.claude.com/en/articles/8241126-uploading-files-to-claude. Accessed 2026-03-27.
• OpenAI Help Center, File Uploads FAQ. https://help.openai.com/en/articles/8555545-file-uploads-faq. Accessed 2026-03-27.
• Candid, Getting started on a responsible AI use policy for nonprofits. https://candid.org/blogs/how-to-create-responsible-ai-use-policy-for-nonprofits/. Accessed 2026-03-27.
• BoardEffect, Nonprofit leaders share their thoughts on AI. https://www.boardeffect.com/blog/leaders-thoughts-ai/. Accessed 2026-03-27.

Quarterly Refresh Flag

Review this article by 2026-06-25. Re-check product features, upload flows, and nonprofit workflow references before updating or republishing.