Explain a Policy Issue Simply
Must brief your legislator or staff on a complex topic in plain language.
Prompts for your job
Must brief your legislator or staff on a complex topic in plain language.
Need to turn a department policy or procedure into a clear, respectful explanation for residents.
Need to reply to a client who asks why their insurance premium increased at renewal.
Need to calm a frightened patient by explaining an upcoming procedure in simple, honest words.
Need to describe a surgical procedure to a patient without medical jargon.
Need to describe a procedure in simple terms for a patient who is anxious or has low health literacy.
Use this when a customer asks how a specific feature works and you need a plain-language answer.
Use this when a key product metric moved and you need plausible drivers to investigate before committing to a cause.
Are unsure how your service sequences a treatment and want it spelled out in order.
Have an EXPLAIN output and need to understand what the database is doing and where the time goes.
Use this when a new rule, notice or letter affects your business and you need a simple summary of what it requires before you act.
Have a new rule, notice, or lease clause and need to know what it actually requires of you day to day.
Need to communicate a regulatory requirement clearly to a supplier.
Need to tell a customer what failed, why it matters, and what you will do to fix it without jargon.
Need to tell a customer what's wrong and what it costs without jargon.
Use this when a tenant or building user asks what broke, how long it will take, and what it means for them day to day.
Need to justify a risk score in plain language to a non-risk audience.
Need a plain-English explanation of an OSHA, fire code, or ADA rule for staff or vendors.
Need a working summary of what a standard like FMVSS 208 or Euro NCAP actually requires.
Need to know what an OSHA, NFPA, or local code clause actually requires of your site and your crew.
Need to explain what a sales metric means and why it moved to a non-technical stakeholder.
Use this when someone asks what a long, nested formula actually does and you need a plain-English walkthrough.
Need to teach a new skill and want a step-by-step explanation your athletes can follow.
Have EXPLAIN output you cannot read and need the bottleneck and the fixes spelled out.