Impact Stories
Bring the story behind your mission into every donor conversation.
Give field updates a home your fundraising team can use. Collect stories and media, review permission to share, and bring approved content into newsletters, mailings, and donor follow-up.
Available on Scale and Network.
Explore Gratona Impact Stories
A field update becomes a story ready to share
Gratona Impact Stories
Interactive example · sample recordsStep 1 of 4
Collect the update
Bring a contribution, image and program context together instead of losing the story across messages and folders.
- Record
- Learning program update
- Status
- Submitted
- Owner
- Field contributor
Tali’s part in the work
Summarize the contribution without inventing missing details.
Try this step with the sample record. No real records or messages are changed.
A contribution can no longer be used in the same way.
Review restrictions and update the story before further use.
Read the full walkthrough
Collect the update
Bring a contribution, image and program context together instead of losing the story across messages and folders.
Review permission
Keep consent and publication restrictions with the story so reviewers understand what may be shared.
Prepare the story
Connect approved program details and images into a draft for the intended audience.
Share and retain context
Reuse an approved story in relevant updates while retaining its origin, permissions and review history.
Explore the steps with sample records, then see your team’s workflow in a live demo.
Make field updates easier to find
Keep stories, photos, source links, and program context together in a searchable Story Bank. Start with the story your team already has instead of requesting it again.
Know what is ready to share
Review story status, privacy, consent, and supporting releases before reuse. Keep internal updates distinct from stories intended for donors or the public.
Give approved stories more reach
Use a reviewed story in newsletter drafts, mailing templates, and Journey messages. Keep the source connected so staff can return to the story behind the message.
From a field update to a donor-ready story
A shared path for the people collecting stories and the people telling them.
Step 1
Collect the update
Use a story intake form or add a story in the workspace. Capture the title, update, date, media, and relevant program so reviewers have a clear starting point.
Step 2
Add context and permission
Attach source material and releases. Record privacy and consent, connect relevant records, and request missing context before approving a story.
Step 3
Review for the intended audience
Review the narrative and supporting evidence. Approve stories for reuse with the privacy and consent appropriate to the audience.
Step 4
Prepare the communication
Choose an eligible story for a newsletter, mailing, or Journey draft. Review the resulting message before sending and return to the story’s reuse history later.
Inside the story record
The context travels with the story.
A useful Story Bank holds more than a finished paragraph. It helps the next person understand where the story came from and how it can be used.
- Source and context
Story date, program, linked records, and media
Keep the narrative alongside the files, links, and relationships that support it.
- Review and consent
Review status, privacy level, consent, and releases
See what is ready for review and whether the story is intended for internal, donor, or public use.
- Reuse history
Publication handoffs and connected drafts
Trace a story into the communications prepared from it without losing the original source.
Explore a story’s intake, review, and communication draft in a demo.
Set up a story workflow your team will use
- Choose who can contribute, review, approve, and publish stories.
- Set the intake fields and program context your reviewers need.
- Agree on consent and release practices for each audience.
- Choose the communication channels included in your plan.
Common questions
Can field teams submit stories?
Yes. Story intake forms collect updates and supporting context for review. Your team can also create stories in the workspace and connect them to program records.
Does approving a story send it to donors?
No. Story approval makes content eligible for the appropriate reuse workflow. Your team still prepares and reviews the communication before sending it.
Can we keep some stories private?
Yes. Stories carry privacy and consent settings, and the story picker filters content for the intended use. Record releases and review the audience before sharing.
Choose the right fit
Compare nonprofit storytelling platforms around your work.
Collect field updates, review consent and turn approved stories into relevant communication.
Open the comparison guide- 01Field contribution experience
- 02Consent and privacy controls
- 03Editorial review and source context
- 04Reuse across relationship communication
Getting started
Start with one complete workflow.
Choose one program and its contributors. Agree on consent fields, review ownership and approved channels, then carry a contribution through to a usable update.
What should we bring to a demo?
Bring the people who own this workflow, an example of how it runs today and the decision you need to make. Walk through collect the update, review permission, prepare the story, share and retain context with your team.
How does Tali fit into the work?
Highlight missing consent information for review. Your team keeps responsibility for the review and the next action. Tali works with the context and permissions behind the workflow.
Can we connect this to the rest of Gratona?
Yes. Gratona Impact Stories connects to the shared relationships, information and work in Gratona. Start with the workflow your team needs and use the same platform as more teams participate.
Explore Gratona by fundraising goal