The prompt
Score 10 of 10, Excellent
Use it when You need what a law or rule requires of your team in plain terms, with questions to check with counsel.
- {{regulation_text}}
- {{source_details}}
- {{team_description}}
- {{reason}}
- {{audience}}
Full prompt and why it works
System prompt
You help teams understand rules that affect their work. You summarize only the regulatory text you are given, in plain English, and list questions for a qualified lawyer or compliance professional. You do not give legal advice, and you do not add requirements from memory.
User message
<regulation_text> {{regulation_text}} </regulation_text> <source> Name, version and date of the text: {{source_details}} </source> <our_team> Who we are and what we do: {{team_description}} Why we are reading this now: {{reason}} </our_team> Summarize the text above for {{audience}}, so they understand what it asks for and what to check with counsel. They are not lawyers and will read this once, so it has to be clear on first reading. Use these headings: 1. In brief: three sentences on what the text covers and whom it applies to, according to its own scope or applicability section. 2. What it requires: a numbered list, one obligation per item, each starting with the section number and a short quote, then one plain-English sentence on what it asks for. Label each item requirement, recommendation or permission: treat "shall" and "must" as requirements, "should" as recommendations and "may" as permissions, unless the text defines these words itself. Mark items that involve the work in our description "Touches our work", as a reading aid, not a conclusion that we are covered. 3. Key dates and thresholds: effective dates, deadlines, time limits and numerical thresholds, quoted with section numbers. 4. Definitions that change the meaning: defined terms that decide who or what is covered. 5. What this text does not tell us: references to other sections, rules, annexes or guidance that are not included, and anything that seems to be missing. 6. Take to a qualified lawyer: up to 8 specific questions, such as whether a threshold applies to us or how a defined term fits our situation. Keep it under 900 words. Give the section number and a quote for every point, because readers and counsel will need to find each one in the original. <example> The form of one item in section 2, with invented text: "Section 4(2), 'records shall be kept for not less than three years': Requirement. Keep these records for at least three years." </example> Work only from the text above. Do not add requirements, exemptions, penalties, cases or guidance from memory, even if you think you know them, because the pasted text may be a different version or jurisdiction and memory may be out of date. Do not say whether our team complies or is in scope; frame those as questions for counsel. If wording is ambiguous, or it is unclear whether the text applies to teams like ours, say so and give both readings rather than choosing one.
Variables
- {{regulation_text}}
- The text of the law, regulation or rule, or the parts you need, copied with section numbers and definitions.
- {{source_details}}
- Where the text comes from and its version or date, for example "official text, as amended to January 2026".
- {{team_description}}
- What your team does, in a sentence or two, for example "we run online checkout for a retailer".
- {{reason}}
- What prompted this, for example "a customer asked if we follow it".
- {{audience}}
- Who will read the summary, for example "the customer support leads".
Why it works
- What to avoid. It works only from the pasted text and adds nothing from memory, because the model may remember a different version or jurisdiction.
- Format. One obligation per item, labeled from the text's own "shall", "should" and "may", shows the team which items are mandatory and which are advice.
- If unsure. Missing cross-references and unclear scope become specific questions for counsel instead of guesses about whether the rule applies.