JaredMake the work easier to move forward.
Nonprofit teams balance program delivery, fundraising, volunteers, and a long list of organizational commitments. Jared is an AI coworker in Slack that prepares work from team conversations and connected context. A focused update can bring approved program milestones and outstanding questions together for the person responsible for communicating with supporters.
An enthusiastic update can outrun the evidence. Plans can sound like completed outcomes, preliminary figures can look final, and a moving story may contain details that should stay private. Useful preparation grounds each claim in approved material, distinguishes progress from ambition, and gives the reviewer a clear view of what still needs verification.
What to bring to the task
- The intended audience, purpose, and reporting period for the draft.
- Approved program updates, published impact information, and permitted organizational context.
- The communication owner, approved messaging, and relevant donor contact preferences.
- Clear exclusions for beneficiary information and private donor details.
From context to a useful result.
Choose the audience and purpose
Specify whether the draft is a donor update, volunteer briefing, or internal project summary. Different audiences need different context and different levels of detail.
Gather approved evidence
Use organization-approved milestones and figures. Keep pending activities separate from completed work. Mark missing evidence instead of inventing an outcome or a success story.
Prepare a clear draft
Explain what changed, what comes next, and any specific approved request. Use aggregate, approved information and leave out beneficiary sensitive data or identifying stories.
Review claims and recipients
The communication owner verifies accuracy, tone, permissions, and commitments. Sending a message or changing a connected record waits for explicit human approval.
The human review checkpoint
Every external write waits for human approval. Your team controls donor contact, fundraising commitments, grant representations, spending, and publication of impact claims. Keep sensitive beneficiary information out of this workflow. Access to an internal conversation does not authorize sharing its contents with supporters.
Before you make it a routine
- Verify that program claims match approved source material.
- Label future activities and unconfirmed dates clearly.
- Exclude beneficiary sensitive data and unnecessary donor information.
- Check contact preferences and the intended recipients.
- Confirm any fundraising request or organizational commitment.
A few useful questions
Can Jared write a personal donor message?
It can prepare a draft from the context your team authorizes. Review contact preferences, the purpose of the message, and any commitment before approving a send.
What if our impact figures are still preliminary?
Mark them as unverified review items and keep them out of the public draft until the responsible person approves a supported statement.
Can we include a beneficiary story?
This workflow excludes sensitive beneficiary data and personal stories. Use organization-approved, non-sensitive aggregate information to explain program progress instead.