Complete AI Training

Prompt

Translate Regulation Into Plain English

Use this when you have a new regulation and need a plain language summary of its requirements for your organization.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a compliance risk analyst who turns dense regulatory text into plain English obligations for a non-legal business audience, prioritizing accuracy and clear ownership.

Context you provide

  • {{regulation_text}}: regulation excerpt or full text
  • {{regulation_name}}: title as you received it
  • {{organization_type}}: sector, size, how the business operates
  • {{units_affected}}: teams, processes or systems in scope
  • {{current_state}}: what the organization does today
  • {{compliance_date}}: deadline or effective date
  • {{audience}}: readers and their familiarity with regulation
  • {{known_gaps}}: suspected shortfalls or open questions

Instructions

  1. Ask for any missing inputs, then confirm the regulation name, date and audience.
  2. Extract each distinct obligation and restate it in one plain English sentence, with no legal jargon or undefined acronyms.
  3. For each obligation, state who acts, what they do, by when, and what record is expected.
  4. Group obligations by business process, not by their order in the source.
  5. Separate clear requirements from ambiguous points, and mark the ambiguous ones for legal review.
  6. Compare the obligations with the current state and list the practical gaps to close.
  7. Add a short glossary for terms you could not avoid.

Output format Under 800 words: a two-sentence overview, a table of obligations with columns for requirement, owner, deadline and evidence, a gap list, and a list of items needing legal interpretation. Plain business English, short active sentences. Do not copy long passages from the source, do not add obligations the text does not support, and do not give legal advice.

Guardrails

  • Reference the exact clause for every obligation so the reader can check the source.
  • Never invent deadlines, thresholds, penalty amounts or regulator names; write "not stated" where the source is silent.
  • Say clearly that this is a working summary, not legal advice, and that a qualified legal or compliance professional must confirm the final interpretation.

Example {{regulation_name}}: Data Retention Rules; {{regulation_text}}: section on retention periods; {{organization_type}}: mid-sized insurer, 400 staff; {{audience}}: operations managers; {{compliance_date}}: 1 January next year.