Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes after, if at all. - One idea per sentence. Aim for an average of 15 words, and vary length so it does not read like a form. - Use everyday words: "start" not "commence", "use" not "utilize", "if" not "in the event that". - Use active voice with a named actor: "We will refund you within 10 days", not "A refund will be issued". - Turn conditions into a short bulleted list. Turn sequences into numbered steps. - Keep every technical or legal term the reader will meet again elsewhere, but define it in parentheses the first time. What must survive unchanged: - Every number, date, deadline, dollar amount, percentage, and named party. - Every obligation, exception, and right. If simplifying a sentence would drop a condition, keep the condition and split the sentence instead. - The legal effect. If you are unsure whether a simplification changes meaning, keep the original wording for that clause and flag it as [CHECK: why you are unsure]. Return: 1. The rewrite. 2. A glossary of any terms you kept, one line each. 3. Your [CHECK] flags, or "None" if there are none. Text to rewrite: """ [PASTE TEXT] """
How to use
The whole prompt turns on the 'what must survive unchanged' block. Plain-language rewrites fail in one direction only: a condition or exception quietly disappears because it made the sentence long. The [CHECK] flag gives the model a way to admit that instead of guessing, which is much better than a confidently smooth rewrite that has changed what you owe someone. For anything with legal effect, have a human compare the flagged clauses against the original before publishing.
More writing prompts
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.
Create the metadata package for this YouTube video. Video transcript or outline: """ [PASTE TRANSCRIPT WITH TIMESTAMPS IF YOU HAVE THEM, OR THE OUTLINE] """ Channel and audience: [WHO WATCHES, WHAT THEY EXPECT FROM YOU] What someone would search to find this: [1-3 PHRASES, OR "you tell me"] Produce: 1. **Titles**: 8 options under 60 c
YouTube Metadata Pack
Generate ranked title options, a search-optimized description, and accurate timestamp chapters from a transcript or outline.