Policy to Plain-Language Translator
Category writing
Subcategory policy-communication
Difficulty beginner
Target models: gpt, claude-opus, gemini-pro
Variables:
{{source_policy_text}} {{target_audience}} {{must_keep_terms}} {{reading_level_goal}} policy plain-language communication compliance clarity
Updated February 26, 2026
The Prompt
You are a plain-language editor. Rewrite policy text so non-specialists understand it without losing legal or operational accuracy.
SOURCE POLICY TEXT:
{{source_policy_text}}
TARGET AUDIENCE:
{{target_audience}}
MUST-KEEP TERMS:
{{must_keep_terms}}
READING LEVEL GOAL:
{{reading_level_goal}}
Deliver:
1. Plain-language version.
2. "What changed" notes (jargon removed, structure simplified).
3. Glossary for unavoidable technical/legal terms.
4. FAQ section (5 likely user questions).
5. "Still ambiguous" section where original text remains unclear.
Rules:
- Preserve obligations, prohibitions, deadlines, and exceptions exactly.
- Do not introduce new policy meaning.
- Use short sentences and active voice.
When to Use
Use this when internal policies, legal notices, or compliance instructions are technically correct but difficult for teams or customers to act on confidently.
Variables
| Variable | Description | Example |
|---|---|---|
source_policy_text | Original policy content | ”Data retention policy v4” |
target_audience | Who needs to understand this | ”Customer support team” |
must_keep_terms | Terms that must remain verbatim | ”GDPR, data controller, SLA” |
reading_level_goal | Simplicity target | ”General business audience” |
Tips & Variations
- Request “before/after side-by-side” for legal review workflows.
- Add “convert to training handout” for onboarding use.
- Ask for “manager briefing version” if leadership needs a short summary.
Example Output
- Plain-language key line: “Delete customer files 30 days after account closure unless legal hold applies.”
- FAQ: “What happens if a customer asks for immediate deletion?”