Write Safe, Survivor‑Centered Content About Physical Assault

Core contents

What’s in the free toolkit

Practical, ready-to-use prompt templates and editorial tools designed for drafting survivor‑centered material. Outputs are intentionally editable and meant to be reviewed by clinicians, legal counsel, or survivor advocates before publication.

• Trauma‑informed prompt library (first‑person statements, guides, intake scripts, media statements)
• Anonymization and redaction guidance built into every template
• Content‑safety checks that flag graphic detail, instructions for harm, or requests for illegal advice
• Publication checklist prompting trigger warnings, helpline placement, and stakeholder review
• Localization notes for adding local helpline names safely and verifying contact details

Prompt clusters

Selected prompt examples you can copy

Use these exact prompt patterns as a starting point. Each prompt is written to prioritize safety, non‑sensational language, and options for anonymity and review.

Editorial safety steps

Publication checklist — before you publish

A short, repeatable checklist to reduce harm and legal risk for any public-facing content about assault.

• Add an explicit content warning or trigger notice at the top of the page or post.
• Redact or replace names, locations, employers, and other identifiable details with [ANONYMIZED].
• Remove graphic sensory detail that could retraumatize or be used to sensationalize the incident.
• Insert referral language and placeholders for verified local helplines and clinics (do not publish unverified numbers).
• Flag any legal or medical claims and route the draft to legal counsel or a clinician for review.
• Obtain and document explicit consent from the survivor for any first‑person material; include a process to withdraw consent.
• Consider accessibility and translation needs; mark culture‑specific references with [LOCALIZE].

Protecting survivors

Anonymization, consent, and privacy

Guidance intended to reduce reidentification risk and respect survivor agency. Use edit rules and consent scripts from the toolkit rather than publishing AI output verbatim.

• Default to the most protective redaction: remove names, exact dates, addresses, workplaces, and unique identifiers.
• When collecting consent, explain who will see the piece, how it will be used, and the process to revoke permission.
• Store drafts and identifying metadata separately from published text; restrict access to staff with a need to know.
• If a survivor requests anonymity, avoid publishing syndicated snippets or social posts that could include identifying context.

Making content safe in other languages

Localization and translation guidance

Tools and prompt patterns to produce copy that’s easier to translate and culturally adapt without losing trauma‑informed intent.

• Use short sentences, plain language, and avoid idioms to simplify translation.
• Mark culture‑specific items with [LOCALIZE] and add editorial notes for local reviewers.
• Provide placeholders for local resource names; never auto‑populate phone numbers or legal processes without local verification.
• Ask bilingual clinicians or community partners to review translations for tone and cultural safety.

Intended audiences

Who this helps — concrete use cases

Examples of how different teams can use the toolkit and what to review before publishing.

Practical workflow

How to use the prompts responsibly

A short recommended workflow that centers survivor safety and appropriate review.

• Step 1 — Draft: Run a chosen prompt to produce a first draft with embedded redaction tags like [ANONYMIZED].
• Step 2 — Edit: A clinician, survivor advocate, or legal reviewer should edit for safety, accuracy, and consent.
• Step 3 — Verify resources: Replace helpline placeholders with verified local contacts during publication; do not auto‑share numbers in public snippets.
• Step 4 — Record consent: Document written consent and any conditions (anonymity, withdrawal timeline) before publishing.
• Step 5 — Monitor: After publication, monitor for unintended identifiers or safety concerns and be prepared to remove content quickly if requested.

Suggested review contexts

Source ecosystems and where to test

Draft outputs should be reviewed and adapted for the following real‑world ecosystems before publication.

• Shelter and crisis center resource pages and intake forms
• Healthcare patient‑education materials and discharge instructions
• Legal‑aid 'what to expect' guides and intake paperwork
• Nonprofit outreach toolkits, blog posts, and email resources
• Press releases, media statements, and social safety posts
• Training modules and internal SOPs for frontline staff