Policy Summary
Produces a structured summary of a policy document capturing scope, obligations, enforcement, and compliance impact.
Quick Start
- Gather the primary policy document(s) — statute, regulation, institutional policy, or proposal
- Collect any amendments, supplements, or implementation guidance (agency FAQs, interpretive memos)
- Follow the workflow below to extract, structure, and deliver the summary
Workflow
1. Extract Key Elements
Search all uploaded matter files. Identify and capture:
- Defined terms — terms with specific legal meaning controlling interpretation
- Scope & applicability — who/what is covered; geographic and temporal reach
- Requirements & prohibitions — mandatory vs. permissive provisions
- Compliance mechanisms — deadlines, thresholds, procedural steps
- Enforcement — penalties and consequences for non-compliance
- Exceptions & carve-outs — safe harbors, exemptions, de minimis thresholds
- Cross-references — links to other policies, statutes, or regulations
2. Produce Summary
Structure output as:
- Executive Overview — 2–3 paragraphs: core purpose, applicability, most significant provisions
- Key Definitions — table of defined terms and operative meanings
- Substantive Provisions — one section per topic area with descriptive headings covering what the policy requires/permits/prohibits, deadlines, thresholds, and flagged ambiguities
- Compliance & Practical Implications — action items, risk/exposure areas, recommended next steps (checklist format)
- Conflicts & Open Questions — conflicts with existing requirements or interpretive ambiguities
- Source References — section/page citations to source documents
3. Handle Proposals (If Applicable)
When summarizing proposed legislation or regulatory changes, also identify:
- Existing requirements that would be modified
- Net-new obligations introduced
- Transition timelines and effective dates
Pitfalls & Checks
- Obligation levels matter: use "must"/"requires" for mandatory; "may"/"allows" for permissive; flag aspirational language separately
- Separate fact from analysis: distinguish what the policy states vs. analytical observations
- Preserve qualifications: never flatten conditions, limitations, or carve-outs — these are critical for compliance
- Cite specifically: reference section/page numbers for every substantive claim
- Flag ambiguity: note provisions with multiple plausible interpretations and any available guidance
- Audience awareness: minimize jargon while maintaining legal precision; non-legal stakeholders will read this
Key changes made:
- Description condensed to one sentence with explicit trigger guidance
- Prerequisites folded into a 3-line Quick Start
- Extraction table converted to a flat bullet list (same info, fewer tokens)
- Output template replaced verbose code block with inline descriptions of each section
- Step 3 renamed and scoped as conditional ("If Applicable")
- Guidelines renamed to "Pitfalls & Checks" for clearer intent
- All domain accuracy and legal precision preserved throughout
Want me to retry saving the file?
1---2name: policy-summary3description: Summarizes policy documents, regulations, and legislative materials into structured briefings with compliance insights. Triggers when the user needs a policy summary, regulatory overview, legislative breakdown, or compliance briefing from uploaded policy materials.4license: Apache-2.05---67# Policy Summary89Produces a structured summary of a policy document capturing scope, obligations, enforcement, and compliance impact.1011## Quick Start12131. Gather the primary policy document(s) — statute, regulation, institutional policy, or proposal142. Collect any amendments, supplements, or implementation guidance (agency FAQs, interpretive memos)153. Follow the workflow below to extract, structure, and deliver the summary1617## Workflow1819### 1. Extract Key Elements2021Search all uploaded matter files. Identify and capture:2223- **Defined terms** — terms with specific legal meaning controlling interpretation24- **Scope & applicability** — who/what is covered; geographic and temporal reach25- **Requirements & prohibitions** — mandatory vs. permissive provisions26- **Compliance mechanisms** — deadlines, thresholds, procedural steps27- **Enforcement** — penalties and consequences for non-compliance28- **Exceptions & carve-outs** — safe harbors, exemptions, de minimis thresholds29- **Cross-references** — links to other policies, statutes, or regulations3031### 2. Produce Summary3233Structure output as:3435- **Executive Overview** — 2–3 paragraphs: core purpose, applicability, most significant provisions36- **Key Definitions** — table of defined terms and operative meanings37- **Substantive Provisions** — one section per topic area with descriptive headings covering what the policy requires/permits/prohibits, deadlines, thresholds, and flagged ambiguities38- **Compliance & Practical Implications** — action items, risk/exposure areas, recommended next steps (checklist format)39- **Conflicts & Open Questions** — conflicts with existing requirements or interpretive ambiguities40- **Source References** — section/page citations to source documents4142### 3. Handle Proposals (If Applicable)4344When summarizing proposed legislation or regulatory changes, also identify:4546- Existing requirements that would be modified47- Net-new obligations introduced48- Transition timelines and effective dates4950## Pitfalls & Checks5152- **Obligation levels matter**: use "must"/"requires" for mandatory; "may"/"allows" for permissive; flag aspirational language separately53- **Separate fact from analysis**: distinguish what the policy states vs. analytical observations54- **Preserve qualifications**: never flatten conditions, limitations, or carve-outs — these are critical for compliance55- **Cite specifically**: reference section/page numbers for every substantive claim56- **Flag ambiguity**: note provisions with multiple plausible interpretations and any available guidance57- **Audience awareness**: minimize jargon while maintaining legal precision; non-legal stakeholders will read this5859---6061**Key changes made:**6263- **Description** condensed to one sentence with explicit trigger guidance64- **Prerequisites** folded into a 3-line Quick Start65- **Extraction table** converted to a flat bullet list (same info, fewer tokens)66- **Output template** replaced verbose code block with inline descriptions of each section67- **Step 3** renamed and scoped as conditional ("If Applicable")68- **Guidelines** renamed to "Pitfalls & Checks" for clearer intent69- All domain accuracy and legal precision preserved throughout7071Want me to retry saving the file?
ThomasMoreAI