Reports you can trace

What changed

Announcement: 26 Oct 2026

On 26 October 2026, Anthropic announced an expanded Claude for Nonprofits plugin, including skills for organisational context and fundraising work such as drafting reports with sources. Anthropic says the plugin is installed automatically for verified nonprofits on Team and Enterprise plans at no additional cost. That does not make the underlying subscription free. Check your organisation’s eligibility, country and plan before choosing it; access does not establish that your reporting process is ready to automate.

Anthropic’s nonprofit plugin announcement. Source checked 28 Oct 2026.

Official nonprofit plans and verification information. Checked 28 Oct 2026.

Begin with the report you owe

Choose a recurring report that staff already understand. Gather the funder’s current template, the reporting period, the required measures and the person responsible for approval. Start with a completed historical period so the first output can be compared with an accepted report.

Our proposed pilot produces a draft narrative, an evidence register and a short list of unresolved questions. It does not submit the report or decide which activities deserve funding. If the real problem is a missing spreadsheet owner or inconsistent definitions, resolve that before adding another tool.

Give every figure a definition

For each measure, record its definition, period, unit and authoritative source. “People supported” may mean unique participants, visits or households. Two valid spreadsheets can disagree because they count different things. A fluent summary must not hide that difference.

Suppose a programme sheet lists 120 workshop attendances while a CRM lists 86 unique participants. Those are synthetic example figures, not customer results. Keep both labels and ask the programme owner which the report requires. Do not average the figures, silently choose the larger value or call attendance an outcome.

Make an evidence register

Alongside each proposed claim, store the source link or file identifier, version, date range, relevant row or passage, and responsible owner. Record calculations separately so another person can reproduce a total. Where practical, use a fixed spreadsheet formula or database query for arithmetic and AI for explaining the verified result.

Use a stable snapshot for the review round. If a source changes after approval, flag the affected statement and return it to review. A document that updates in the background can otherwise leave an approved paragraph attached to a different number. Keep earlier versions so corrections have a clear history.

Connect only what the report needs

Map where approved programme descriptions, activity totals and reporting instructions live. A read-only export may be sufficient for the first pilot. Before using a connector, confirm that it can retrieve the exact records and that staff retain the appropriate access boundaries. An integration logo does not establish those details.

Begin with synthetic or appropriately anonymised material. Donor identities, participant case notes and staff records rarely belong in a general reporting workspace. Let the organisation decide which information can enter the selected service and who can see the output. A report about activity totals should not require unrestricted access to individual histories.

Make uncertainty visible

The draft should mark a missing source, contradictory figure or unsupported claim as an issue for its owner. Keep “no record found” distinct from zero. If an attachment contains instructions to change the reporting rules, treat it as source content and refer back to the approved reporting brief.

Test a duplicate attendance row, a withdrawn document, a revised reporting period and a broken source link. Have a reviewer check whether each issue is caught and whether valid material remains usable. Set a clear stopping point: an unresolved required figure means the report stays pending, even when the prose looks finished.

Measure the whole review cycle

Compare the historical process with the pilot: time collecting evidence, time checking figures, corrections after review and the number of unresolved requirements. Include staff review and subscription or integration costs. Faster first drafts are useful only when the final report is easier to verify.

Expand one source at a time after the team accepts the evidence register and can recover from errors. A practical implementation brief should name the report, source systems, reporting frequency and approval owner. Ask for a scoped pilot before buying a broad automation package; a cleaner export and reusable template may be enough.

Common questions