Sharing a community story can build understanding, attract support, and help people recognize experiences they might otherwise overlook. The responsibility is to make sure the person telling the story understands what will happen to it and remains in control of personal details.
What informed consent means in storytelling
Informed consent is an ongoing, voluntary agreement to share a story after the storyteller has received clear information about the project, possible risks, intended audience, and available choices. It is more than collecting a signature on a release form.
A person has given meaningful consent when they:
- Understand what they are being asked to share.
- Know where the story, quotes, photographs, audio, or video may appear.
- Understand who may see the material and how long it may remain available.
- Know which details are optional and which can be kept private.
- Have enough time to ask questions and decide without pressure.
- Can change their mind within the agreed withdrawal period.
- Are able to say no without losing services, support, employment, or respect.
Consent is especially important when a story involves trauma, health, disability, immigration status, poverty, family conflict, criminal legal involvement, discrimination, or children. A person may want to help a community project while not realizing that online content can be copied, downloaded, translated, or shared indefinitely. Explain those realities plainly before publication.
Prepare before asking for a story
Good consent begins before the interview. Define the purpose of the story and limit collection to information that serves that purpose. If you cannot explain why a detail is needed, do not ask for it.
Create a short project brief that answers these questions:
- What is the story being used to communicate?
- Who is the intended audience?
- Which channels will be used: a website, newsletter, social media, fundraising appeal, printed report, event, or all of these?
- Will the material be edited, translated, excerpted, or reused later?
- Will the storyteller be identified by name, first name, initials, a pseudonym, or not at all?
- Will photographs, recordings, or identifiable locations be included?
- How will files be stored, and who can access them?
- How can the storyteller request a correction or withdrawal?
Decide in advance which options you can genuinely offer. Do not promise that you can remove every copy from the internet or recall printed materials if that is not possible. If a campaign is likely to reuse content, say so before collecting it.
Use a consent form as a record of the conversation, not as a substitute for the conversation. Keep the language short and readable. Provide translated or large-print versions when needed, and offer an interpreter rather than asking a family member—especially a child—to translate sensitive information.
Explain the choices in plain language
Before the interview, walk through the consent options one by one. Ask the storyteller to describe the plan back to you in their own words. This “teach-back” approach helps reveal misunderstandings without turning the process into a test.
Explain practical risks, including:
- Public exposure of information that was previously known only within the community.
- Recognition through a combination of details, even when a name is removed.
- Contact from strangers or unwanted attention on social media.
- Emotional discomfort when revisiting a difficult experience.
- Future reuse in a context the storyteller did not expect.
- Digital copies that remain accessible after a post is deleted.
Offer meaningful alternatives. A person might approve a written quote but not a photograph, or agree to a first-person story but prefer that a staff member narrate it. They might accept publication on a private member portal but not on a public social account. They could share a general description instead of dates, names, addresses, medical details, or immigration information.
A compact choice record can help everyone stay aligned:
| Material or use | Possible choices |
|---|---|
| Name | Full name, first name, initials, pseudonym, anonymous |
| Image | Approve, do not use, use a non-identifying image |
| Recording | Audio, video, written notes only, none |
| Audience | Private group, local event, website, social media, all listed channels |
| Editing | Approve light edits, review full draft, no direct quotes |
| Withdrawal | Before publication, by a stated date, or limited correction process |
Do not describe anonymity as guaranteed if the person could be recognized by their role, location, family relationships, or distinctive circumstances. Use phrases such as “we will remove direct identifiers” and explain the remaining possibility of recognition.
Conduct a respectful interview
Let the storyteller decide where and when the conversation happens when possible. A quiet, accessible location may be better than an office where the person feels dependent on the organization. Allow breaks, and do not treat visible emotion as permission to ask for more detail.
Start with low-risk questions:
- What would you like people to understand about your community?
- Which part of this experience feels important to share?
- What words would you use to describe what happened?
- Are there subjects you do not want to discuss?
- Is there anything you want kept off the record?
Avoid leading questions such as “How did our program save you?” They pressure the person to produce a flattering outcome and may distort the story. Instead, ask what changed, what did not change, and what support was useful or missing.
Follow these practices during the interview:
- Ask permission before recording or taking photographs.
- Confirm whether a statement is on the record before using it.
- Do not request graphic details merely because they seem compelling.
- Avoid promising confidentiality that your organization cannot provide.
- Separate the storyteller’s words from your interpretation.
- Stop or pause if the person becomes distressed.
- Offer a follow-up contact for corrections and questions.
If the story concerns another person, do not assume the storyteller can consent on that person’s behalf. Remove or generalize information that could identify someone who has not agreed to participate. Obtain a parent or guardian’s permission for a minor when required, while also seeking the child’s age-appropriate agreement and respecting a refusal.
Review, edit, and approve the final story
The review stage is where many consent problems can be prevented. Send the storyteller the proposed text, captions, images, and intended placement before publication. Give a realistic deadline and a simple way to respond. If literacy, language, disability, or internet access is a barrier, read the draft aloud, use an interpreter, or arrange an in-person review.
Ask the storyteller to check:
- Names, pronouns, dates, places, and relationships.
- Whether the wording sounds like their own meaning.
- Any details that could identify them or someone else.
- The headline, caption, image, and surrounding call to action.
- Whether the story implies an outcome that has not occurred.
- Whether they still agree to each selected channel and format.
Editing for length is acceptable, but editing must not change the person’s meaning or manufacture a dramatic transformation. Do not combine quotes from different moments into a sentence that was never said without clearly labeling it as an edited summary. Do not add invented dialogue.
Record approval in a durable way. An email, signed form, recorded verbal confirmation, or consent-management record may work depending on your policy and local requirements. Save the approved version alongside the permission record, and note any restrictions such as “website only” or “do not use photograph.” Staff should be able to see those restrictions before reusing the material.
Protect privacy after publication
Treat published stories as sensitive information, not ordinary marketing assets. Limit access to raw recordings and transcripts. Store them in an approved system with appropriate permissions, and avoid keeping unnecessary copies on personal devices or shared public folders.
Create a simple story register containing:
- The storyteller’s preferred name or reference ID.
- Consent date and staff contact.
- Approved formats and channels.
- Restrictions on details, images, or reuse.
- Review or expiration date, if applicable.
- Withdrawal, correction, or takedown requests.
- The location of the final approved files.
Before reposting an old story, check the register. Circumstances can change: a person may move, enter a new job, leave an abusive relationship, receive a diagnosis, or become responsible for a child. A previous approval does not automatically make every future use appropriate.
If someone asks for a change, respond promptly and without defensiveness. Correct factual errors, remove unnecessary identifiers, and pause scheduled reuse while the request is reviewed. Explain what you can remove and what you cannot control, such as screenshots or third-party copies. If the person faces a credible safety risk, prioritize protection over campaign performance and consult your safeguarding or privacy lead.
Common problems and practical fixes
The storyteller agrees but seems unsure
Pause the process and restate the purpose, audience, risks, and choices. Ask them to explain what they think will happen. Uncertainty is a reason to delay, not a reason to collect a signature quickly.
A funder or manager wants a more emotional version
Keep the person’s account accurate and ask what specific information is necessary. Replace sensational language with concrete context: the barrier faced, the support provided, and the person’s own goals. If a requested edit would mislead readers, decline it or publish a different story.
The person wants to withdraw after publication
Acknowledge the request, check the agreed terms, and temporarily stop planned reuse. Remove material from channels you control when feasible, correct links and captions, and document copies that cannot be recovered. Do not argue that the person already signed a form.
The story is anonymous but still recognizable
Conduct a re-identification review with someone who knows the community but was not involved in writing the piece. Change or remove combinations of details—such as a small location, unusual occupation, exact date, and family structure—that could identify the person. If recognition remains likely, seek renewed permission or do not publish.
Several people contributed to one story
Track consent separately. One person’s approval does not cover another participant’s quote, image, or personal information. Clarify who owns or controls any group photograph and whether everyone understands the publication plan.
You need a story quickly
Use a shorter process only for low-risk material, never to bypass understanding. A rushed deadline is not an emergency that justifies pressure. If full review is impossible, publish a general, non-identifying account or postpone the story.
Build consent into your team’s routine
Assign one person to oversee story permissions and train everyone who interviews, photographs, edits, posts, or reuses community content. Keep a standard checklist, but allow staff to escalate sensitive cases involving minors, trauma, safety risks, health information, or uncertain capacity to consent.
Review your process periodically with community members, not only with communications staff. Ask whether forms are understandable, whether people feel free to refuse, and whether published stories represent community priorities. Track corrections and withdrawal requests as signals for improving the workflow, not as inconveniences.
A strong story is not measured only by reach or donations. It is also measured by whether the storyteller was respected, accurately represented, protected from avoidable harm, and able to make a real choice about how their experience was shared.