1---2name: client-advisory3description: Drafts client advisory memoranda translating legal developments into actionable guidance with impact analysis, Bluebook citations, and compliance recommendations. Use when preparing client alerts, regulatory updates, legal bulletins, or proactive advisory summaries.4license: Apache-2.05---67# Client Advisory Summary89Produces a professional advisory memorandum that translates recent legal developments into tailored client guidance with impact analysis and numbered action items.1011## Prerequisites1213- **Legal development(s)** — case law, statutory amendments, regulatory updates, agency guidance, or pending legislation14- **Client profile** — industry, jurisdiction(s), operations, and specific legal concerns15- **Client materials** (if available) — contracts, policies, prior advisories, compliance frameworks16- **Effective dates and deadlines** — time-sensitive compliance windows1718## Quick Start19201. Gather inputs (developments, client profile, deadlines)212. Draft header and executive summary223. Analyze each development using the body framework below234. Build the recommendations summary table245. Run the drafting checklist before delivery2526## Output Structure2728### Header2930| Field | Content |31|-------|---------|32| To | Client name / matter ID |33| From | Attorney / firm |34| Date | Date of preparation |35| Re | Concise subject line identifying development(s) |3637### Executive Summary (2–3 paragraphs)3839- Lead with the most critical development and its immediate implication40- Write for a non-lawyer audience while preserving legal precision41- State the bottom line: what changed, who is affected, what to do4243### Body Sections (one per development)4445For each development, address:4647| Component | Content |48|-----------|---------|49| **Development** | What changed — statute, rule, holding, agency action |50| **Citation** | Full Bluebook citation; mark unverified cites `[VERIFY]` |51| **Effective Date** | When it takes effect |52| **Context** | Brief origin/purpose (1–2 sentences) |53| **Substantive Changes** | Bullet list of new requirements, standards, or rights |54| **Client Impact** | Effect on this client's operations, obligations, or rights |55| **Impact Horizon** | Immediate / Short-term / Long-term |56| **Impact Type** | Compliance obligation / Strategic opportunity / Risk exposure |57| **Recommendations** | Numbered action items with deadlines where applicable |5859### Recommendations Summary Table6061| # | Action Item | Deadline | Priority | Type |62|---|------------|----------|----------|------|63| 1 | ... | ... | High/Med/Low | Compliance/Strategic/Risk |6465### Closing6667- Note assumptions or limitations in the analysis68- Flag areas requiring further fact-gathering69- Include specific contact information for follow-up7071## Drafting Checklist7273- [ ] Every factual assertion tied to a cited source74- [ ] All citations Bluebook-formatted; uncertain cites marked `[VERIFY]`75- [ ] Cross-referenced client contracts/policies against new requirements76- [ ] Jargon defined on first use or replaced with plain language77- [ ] Concrete examples illustrating impact on client's actual operations78- [ ] All deadlines and effective dates explicitly stated79- [ ] Recommendations are specific and actionable (not "consider reviewing")8081## Pitfalls8283- **Speculation**: Distinguish enacted law from proposed/pending changes; label each clearly84- **Jurisdiction**: Default US; flag state-specific variations where federal and state law diverge85- **Unconfirmed facts**: If analysis depends on unverified client facts, state assumptions explicitly86- **Length**: Target 2–5 pages; bias toward concision87- **Visual aids**: Use comparison tables for before/after changes and timelines for phased implementation