AI for community nonprofits
Prepare a funder-update evidence map for community nonprofits: three administrative tasks, a synthetic worked example, and a complete reviewed brief.
Quick answer
For community nonprofits, start with a funder-update evidence map for the program and development lead. Connect each drafted statement to an approved measure so narrative preparation does not invent program outcomes. Righthand can help prepare the administrative draft from inputs you authorize; staff review its evidence and decide the next action.
Three desk tasks
1. Map reporting evidence
List the figures available for the requested period, preserving units and measure definitions.
2. Prepare narrative gaps
Show what cannot yet be supported and ask the program owner for missing evidence.
3. Draft a reviewable update
Write from approved material only, excluding beneficiary details not cleared for the audience.
Who owns each handoff?
| Input | Proposed assistant deliverable | Responsible person |
|---|---|---|
| approved program figures and reporting brief | funder-update evidence map with record references | program and development lead |
| Missing or contradictory fields | Exception and source-linked question | Named source owner |
| Approved next step | Reviewable coordination draft | Staff authorize external action |
Worked example: three records, three outcomes
The following inputs and outputs are synthetic, not customer results. Read them as a test packet for this desk.
| Illustrative source row | Useful worked output |
|---|---|
| Program N-81: approved figure is forty attendances, while draft says forty unique participants. | Correct the label and retain the underlying program count; do not invent a unique-person total. |
| Program N-82: staff note covers September, but the funder draft asks about October. | Mark the reporting-period gap and request the current approved figure. |
| Program N-83: beneficiary story is supplied without an approved public-use record. | Keep it out of the funder-facing draft and ask staff for an authorized alternative. |
Correction check: Recheck period and unit labels before describing impact. Attendance counts, distinct people, and outcomes should remain separate; the assistant cannot manufacture evidence simply to finish the narrative.
Complete first-run brief
Prepare a funder-update evidence map from approved program figures and reporting brief. Cover October 12–16, 2026; use America/Los_Angeles for date cutoffs. Include these source fields: program reference, reporting period, measure, unit, approved value, source owner. Trigger: Monday at 9 AM. Output: a source-linked Markdown draft in my private review thread, grouped by next action and owner. Reviewer: the program and development lead. Flag missing fields or conflicting versions. Keep impact claims, funder commitments, financial sign-off, and personal-information release with staff. Do not send messages, change source records, or spend money. Result check: Check every quantitative or outcome statement against its period, unit, and approved source.
Replace the illustrative dates and source locations before running this task. Use an approved extract when a native connection and its exact actions have not been verified; the extract remains a snapshot, not live synchronization.
First-week check and failure boundaries
Pilot one upcoming funder update and compare the draft with the program lead’s approved figures before review. Attendances and distinct beneficiaries are different measures. A compelling anecdote still needs the organization’s public-use approval. Keep impact claims, funder commitments, financial sign-off, and personal-information release with staff. When an input changes, rerun the affected comparison and retain its source reference; do not overwrite the authoritative operational record with a draft.
The Righthand documentation explains setup. Consult source-record guidance for the underlying system, and use Features to check the proposed task fit. Review Pricing against the actual pilot workload before expanding.