Statute Summarizer
When you encounter an unfamiliar statute or need to break down complex statutory language for a memo or client advice.
Statutes are written for precision, not readability, and a single provision can fold in cross-referenced definitions, exceptions, effective dates, and penalty structures spread across an entire code chapter. Before you can advise a client or draft a memo, you have to decompose that language into its operative elements and spot the ambiguities courts have fought over. Done by hand, that parsing is slow and easy to get partly wrong.
Claude is well suited to this decomposition. Paste the full statutory text and your context, and it returns a plain-English summary, an element-by-element breakdown of what must be satisfied, the defined terms that control meaning, the exemptions and carve-outs, penalties, interacting statutes, and the phrases that invite competing interpretations. It turns a dense block of code into a structured working outline you can build analysis on top of.
Use the summary as a first-pass analytical aid, not a definitive reading. Claude can misstate effective dates, overlook a controlling definition, or miss how courts have construed a phrase, and it can describe statutes that have since been amended or repealed. Confirm the current text and every element against the official code and primary authority. The output is a draft for the attorney to verify, not legal advice.
The Prompt
Analyze the following statute and provide: Statute: [PASTE THE FULL TEXT OR CITE THE STATUTE] Context: [WHY YOU'RE ANALYZING THIS — what issue are you trying to resolve] 1. Plain-English summary — what does this statute do in one paragraph 2. Element breakdown — list each element/requirement that must be satisfied 3. Key defined terms — note any terms defined elsewhere in the code 4. Exceptions and exemptions — who or what is excluded 5. Effective date and any sunset provisions 6. Penalties or consequences for violation 7. Related statutes that interact with this provision 8. Ambiguities — language that courts have interpreted differently 9. Practical application — how this applies to the context described above
Example Output
A 1-2 page analysis breaking the statute into its elements, noting ambiguities, and applying it to your specific situation.
Illustrative example — names, figures, and facts are fictional.
STATUTE ANALYSIS (DRAFT — VERIFY AGAINST CURRENT CODE) Statute: Model Data Protection Act § 12-409 (illustrative placeholder) Context: Does a 40-employee SaaS client owe breach-notification duties? 1. PLAIN-ENGLISH SUMMARY Requires covered businesses to notify affected residents "without unreasonable delay" after discovering a breach of unencrypted personal data. 2. ELEMENT BREAKDOWN (each must be met) (a) Entity is a "covered business"; (b) "Personal data" as defined in § 12-401(7); (c) Data was unencrypted or key was also compromised; (d) A "breach of security" occurred; (e) Notice given without unreasonable delay (<= 45 days, § 12-409(c)). 3. KEY DEFINED TERMS: "Covered business" (§ 12-401(3)) — excludes entities with < 25 employees AND < $5M revenue. 4. EXEMPTIONS: Good-faith acquisition by an employee; encrypted data with secured key. 5. EFFECTIVE DATE: Jan. 1, 2025; no sunset noted. 6. PENALTIES: Civil penalty up to $7,500 per violation; AG enforcement only (no private right). 7. AMBIGUITY: "Without unreasonable delay" vs. the 45-day outer limit — courts split on whether 45 days is safe harbor. 8. APPLICATION: 40-employee client likely "covered" (exceeds headcount threshold); confirm revenue and encryption status.
Tips
- •Paste the full text rather than just citing it — Claude works better with the actual language.
- •Ask about legislative history if the plain text is ambiguous.
- •Cross-reference with the definitions section of the same code chapter.
Frequently Asked Questions
When is this prompt most useful?
Use it whenever you encounter an unfamiliar statute or need to break dense statutory language into its operative elements for a memo, a compliance assessment, or client advice. It is especially helpful for new or amended provisions where you need a fast, structured orientation before diving into annotations and case law.
Can I treat the summary as an authoritative reading of the statute?
No. AI can misstate elements, miss a controlling definition, or rely on a superseded version of the law. Always confirm the current statutory text in the official code and validate the analysis against primary authority and annotations on Westlaw or Lexis before relying on it. The summary is an analytical starting point, not a legal opinion.
How do I get the most accurate breakdown?
Paste the full statutory text rather than just a citation, since the model reasons better from the actual language. Add the definitions section of the same chapter, state your specific factual context, and ask it to flag ambiguities and interacting provisions. Cross-referencing definitions yourself catches the carve-outs that change the answer.
What about accuracy and the duty of competence?
Under Model Rule 1.1 and ABA Formal Opinion 512, competent use of AI requires understanding its limits and verifying its output. Statutory analysis turns on exact text and current effective dates, both of which AI can get wrong, so independent confirmation against the official code is essential before the analysis informs advice or filings.
Related Prompts
Get New Prompts Like This Every Week
Join the free Claude for Lawyers newsletter — weekly prompts, tutorials, and practice-specific guides.