Sensitive Message Language Reviewer
Review difficult messages for factual clarity, accountability, dignity, privacy, and actionable next steps without hiding bad news.
Leaders, HR teams, support teams, and communicators preparing messages about disruption, denial, error, change, or other sensitive outcomes.
You are a sensitive communications editor who specializes in clear, humane language for difficult or high-impact messages.
Inputs:
1. Draft message: {{draft}}
2. Audience, relationship, and likely concerns: {{audience_context}}
3. Verified facts, decisions, and unresolved information: {{facts}}
4. Desired action, support, and follow-up process: {{response_plan}}
5. Legal, HR, privacy, cultural, and tone constraints: {{constraints}}
Do the following:
1. Separate verified fact, decision, rationale, uncertainty, empathy, responsibility, instruction, and support, flagging claims or promises that exceed supplied authority.
2. Review the draft for euphemism, blame, defensiveness, false reassurance, emotional manipulation, unnecessary detail, hidden bad news, privacy exposure, and language that removes the reader’s agency.
3. Reorder the message so the material fact appears early, its effect is concrete, accountability is clear, and the reader can identify what happens next and where to get help.
4. Rewrite in direct, respectful language matched to the audience, preserving required wording and avoiding apology language that admits liability unless approved.
5. Produce the revised message, risk notes, sentence-level rationale for major changes, alternative subject lines or openings, and a pre-send verification checklist. Do not invent support, compensation, timelines, or outcomes.How to use
- Provide verified facts and unresolved questions separately.
- State what support is actually authorized.
- Include required legal or HR wording.
- Verify dates, contacts, and promises before sending.
Example input
Draft: Email to 74 applicants explaining that a funded training cohort will start six weeks late after a venue contract failed. Facts: new start date is September 28; all places remain reserved; travel reimbursements already booked will be honored; childcare arrangements are not yet resolved. Response: applicants must confirm availability by August 5 and may withdraw without penalty. Constraints: do not identify or blame the venue, German and English versions will be sent, and legal must approve reimbursement language.
Example output
The revision states the six-week delay and new date in the opening, confirms that places remain reserved, and distinguishes approved travel reimbursement from unresolved childcare support. It removes blame and the phrase “minor scheduling adjustment,” acknowledges practical disruption without false reassurance, and provides confirmation and withdrawal steps. Risk notes flag reimbursement wording for legal approval and require a named contact before sending.
Customization tips
- — Put the material impact in the opening.
- — Avoid euphemisms for negative outcomes.
- — Preserve the reader’s options and agency.
- — Translate after the source message is approved.
Tags
FAQ
What is this prompt for?
How should I customize it?
Are there any limitations?
How is it different from a basic prompt?
Related Prompts
All Writing & Editing prompts →Reading Level Adapter
Rewrites a piece of text to a specific target reading level or grade level while preserving accuracy, nuance, and key terminology where appropriate.
Brand Voice Style Guide Builder
Derive a practical writing system from real samples, defining voice principles, language rules, examples, exceptions, and review criteria.
Inclusive Language and Bias Editor
Review writing for unnecessary stereotypes, exclusion, coded assumptions, accessibility barriers, and imprecise group references while preserving relevant meaning.
Related Skills
Sensitive Communication Risk Editor
Review sensitive communications for clarity, empathy, privacy, escalation risk, legal sensitivity, blame, promises, and unintended harm.
Sensitive Data Field Classification and Handling Reviewer
Classify data fields by sensitivity, necessity, access, retention, masking, transfer, and review requirements without claiming legal compliance.