A library of participant stories you can use with confidence, because consent, review, and approval are recorded on every one. Describe your programs and Taskade Genesis builds the collection pipeline: the interview prompts, the consent record, the review stage, the approved quote, and the usage log that tells you where each story has already appeared.
The app embedded on this page is Testimonial Portal App, a real Taskade Genesis build that collects first-person stories and moves them toward publication. Move a story through the stages, open a record, then clone it in about ten seconds and add the consent and permission fields described above.
Each story record holds the participant, the program, the interview date and interviewer, the raw notes or transcript, the consent form with its scope and expiry, whether the person wants their name or a pseudonym, an approved short quote, an approved long version, any photo and its separate permission, and a log of every place the story has been used. Linked records connect a story to the program and outcome it illustrates, so finding the right story for a proposal takes a filter rather than a memory.
Workspace DNA is what makes this safe as well as useful. Memory holds the consent scope and the usage history, so a story approved for a newsletter never quietly turns up in a fundraising ad. Intelligence, using 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, turns a rough interview into a clean draft in the person's own voice, suggests where the language slips into pity rather than dignity, and flags identifying details that should be removed. Execution routes the draft back to the participant for approval and records the response.
Work the library in whichever layout you need:
- Board view, stories moving from invited to interviewed to consented to approved
- Table view, every story with program, consent scope, expiry, and usage count
- List view, the approved stories in readable form for a writer
- Calendar view, consent expiries and re-approval dates
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations protect the process. With Taskade automations, a story cannot be marked publishable until consent is attached, an approaching consent expiry creates a re-approval task, and an approved story notifies the communications lead in Slack. Across 100+ bidirectional integrations, your form tool and Gmail pull consent responses in while Slack pushes approvals out to the people who need them.
The AI agents carry 34 built-in tools including file analysis and persistent memory, so an agent can transcribe an interview recording, draft the story, and produce a short quote and a long version without a staff member retyping anything.
Clone it, invite your communications lead and your program staff, and the stories, the consents, and the usage history stay under your control.
Browse other builds in the Community Gallery, start a new one at Taskade Genesis, or learn approval workflows in Learn. Use the approved quotes in the quarterly impact report, in a grant proposal narrative, and in the supporter newsletter.
Frequently Asked Questions
How is consent recorded?
As a linked record on the story with the scope of permitted use, the date, the expiry if you set one, whether a real name may be used, and a separate permission for photographs. A story without an attached consent cannot be marked publishable.
Can someone withdraw consent later?
Yes, and the app is built for it. Mark the withdrawal and every use of that story is listed so you can remove it, with the record retained showing when consent ended.
Does the AI write the story for the participant?
No. It cleans up a transcript into readable prose in the person's own words and flags anything that changes their meaning. The participant reviews and approves the version that gets used, which is both ethical practice and better writing.
How does it help avoid harmful framing?
The agent flags language that emphasizes deficit over agency, removes unnecessary identifying details, and suggests alternatives. The judgment stays with your team, but the first pass catches a lot.
Can we anonymize a story?
Yes. Set the record to pseudonym and the agent rewrites identifying details while preserving the substance, keeping the real identity in the restricted record only.
Where does this fit with our participant data?
Keep stories in their own project with tighter permissions than your general program records. Communications staff need the approved quote, not the case file.
How many stories should we collect?
A handful per program per year, kept current, beats a large archive that has gone stale. The app shows you which programs have no recent story, which is usually where the next interview should be.
