eo-tracker
Design E&O (Errors and Omissions) exposure tracking and mitigation workflows for insurance agencies. Use when building systems to document client interactions, track coverage recommendations, and reduce E&O liability exposure.
What this skill does
# E&O Exposure Tracking and Mitigation Workflow Design Design a systematic E&O risk management framework for an insurance agency, covering documentation standards for client interactions, coverage gap tracking, renewal follow-up, certificates of insurance, complaint handling, and staff training. The goal is to create a defensible record that demonstrates the agency acted professionally and in the client's best interest. ## Why E&O Documentation Matters An E&O claim arises when a client alleges the agency made an error or failed to provide coverage the client expected. The agency's defense depends almost entirely on documentation. If it is not documented, it did not happen. The most common E&O triggers: - Client claims they requested coverage that was not placed - Client claims they were not told about a coverage gap or exclusion - Agency failed to timely place, renew, or endorse coverage - Certificate of insurance issued with inaccurate coverage information - Agent gave advice that turned out to be incorrect --- ## Component 1: Client Interaction Documentation **Required documentation by interaction type:** **At every client contact (phone, email, in-person, portal):** - Date, time, and duration of contact - Contact method (phone / email / in-person / portal) - Client name and policy number(s) discussed - Summary of what was discussed (minimum: key topics, any requests made, any advice given) - Next action items and who is responsible - Logged in AMS activity notes within [N] hours of the interaction **At quote/application stage:** - Coverage options presented to client (what was offered) - Coverage options declined by client (what the client chose not to buy) - Client declination documented: date, coverage declined, reason given by client, how documented (signed form / email confirmation / verbal with note) - Premium quoted for declined coverage (shows client understood the cost) - Agent recommendation documented (did the agent recommend the declined coverage?) **At bind:** - Confirmation of coverage selections (what was bound) - Confirmation that coverage not purchased was discussed and offered - Written bind confirmation sent to client with coverage summary **At annual review / renewal:** - Coverage review checklist completed (see renewal workflow) - Any life changes disclosed by client (new vehicle, new property, business change, new employees) - Coverage recommendations made based on changes - Client decisions documented (accepted / declined for each recommendation) **Documentation standards:** - Notes must be contemporaneous — entered at time of interaction, not reconstructed later - Avoid jargon; write notes as if a jury will read them (because in an E&O claim, they might) - Never delete or alter AMS notes — append clarifications as new entries --- ## Component 2: Coverage Gap Tracking **Uninsured/underinsured exposure documentation:** For every client, identify and document known coverage gaps. A gap exists when the client has an insurable exposure that is either uninsured or insured for less than the recommended limit. **Coverage gap log — per client:** | Gap ID | Coverage Type | Exposure | Current Coverage | Recommended Coverage | Gap | Offered Date | Client Decision | Documentation | |--------|-------------|---------|-----------------|---------------------|-----|--------------|----------------|---------------| | [G001] | Umbrella | Personal liability above auto/home limits | None | $1M umbrella | $1M uninsured above primary | [Date] | Declined | Signed declination form | | [G002] | Business interruption | Home-based business operations | None | $100K BOP | $100K uninsured | [Date] | Will consider | Follow-up scheduled | **Coverage gap review triggers:** - Annual policy review (all clients) - Client reports a life change (new business, major purchase, new household member, significant income change) - Agency learns of a client's new exposure through third-party information - Claim filed that reveals an uninsured exposure **Coverage declination documentation:** When a client declines recommended coverage, obtain written confirmation using one of these methods (in order of preference): 1. **Signed declination form** — Client signs a form stating they were offered the coverage, understand the gap, and decline. Best documentation. 2. **Email from client** — Client sends written reply declining. Forward to AMS with note. 3. **Email to client confirming verbal decline** — Agency sends email summarizing the conversation: "Per our discussion today, you have declined to add [coverage] at this time. This means [consequence]. Please contact us if you change your mind." No reply from client is acceptable documentation of receipt. 4. **AMS note with specific detail** — Minimum acceptable: "Called client [name] on [date] at [time]. Offered [coverage] for [premium estimate]. Client declined, stating [reason given]. I recommended the coverage for the following reason: [reason]." --- ## Component 3: Renewal Follow-Up Workflows **Renewal pipeline automation (tiered by client value and complexity):** | Tier | Criteria | Renewal Outreach | |------|---------|-----------------| | A | Premium > $[X] or complex accounts | Personal call 90 days out; detailed review meeting | | B | Premium $[X]–$[X] | Email 90 days out; phone call 60 days out | | C | Premium < $[X] | Automated email sequence; phone only if no response | **Standard renewal outreach sequence:** | Day Before Expiration | Trigger | Channel | Content | |----------------------|---------|---------|---------| | 90 days | Auto | Email | Renewal notification; request updated information | | 60 days | Auto | Email | Quote ready (if auto-renewed) or quote request | | 30 days | Auto | Email + phone attempt | Confirm renewal decision; gap review reminder | | 14 days | Manual | Phone call required | Confirm bind or non-renewal decision | | 7 days | Auto | Email | Final reminder; lapse warning | | Expiration | Auto | Email | Policy lapsed (if not renewed); consequences notice | **Non-response documentation:** If the client does not respond to renewal outreach, document each attempt. If the policy lapses due to non-response, document: - All outreach attempts (date, method, result) - Any response received (even "I'll get back to you") - Final notice of impending lapse sent - Confirmation that lapse occurred and client was notified **Non-renewal by carrier:** If the carrier is non-renewing the policy: - Confirm receipt of non-renewal notice (date received, period covered, reason) - Client notified immediately upon receipt (not at 60 days) — lapse protection requires early notification - Begin re-marketing immediately - Document timeline of carrier non-renewal, client notification, and re-marketing efforts --- ## Component 4: Certificates of Insurance Tracking **Certificate issuance workflow:** 1. Request received (from client, additional interest, or insured's contract counterparty) 2. Requestor verified: is the requestor entitled to a certificate? (Generally: certificate holder must have an insurable interest) 3. Coverage verified against current policy before certificate is issued 4. Certificate content reviewed for accuracy: - Named insured exactly matches policy - Coverage limits and types exactly match current policy - Effective and expiration dates correct - Additional insured endorsed on policy (if box is checked on certificate) - Certificate holder information correct 4. Certificate issued — never add coverage, language, or endorsements on the certificate that are not reflected on the actual policy 5. Certificate stored: linked to client record and policy in AMS; copy to certificate holder if requested **Certificate accuracy rules (critical E&O risk area):** - NEVER check the "Additional Insured" box on a certificate unless the additional insured endorsement has been issued on the actual policy - NEVER list a cancellation notice period longer than what is
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.