plugins/lobbi-insurance-domain/skills/eo-tracker/SKILL.md
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.
npx skillsauth add markus41/claude plugins/lobbi-insurance-domain/skills/eo-trackerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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:
Required documentation by interaction type:
At every client contact (phone, email, in-person, portal):
At quote/application stage:
At bind:
At annual review / renewal:
Documentation standards:
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:
Coverage declination documentation:
When a client declines recommended coverage, obtain written confirmation using one of these methods (in order of preference):
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:
Non-renewal by carrier:
If the carrier is non-renewing the policy:
Certificate issuance workflow:
Certificate accuracy rules (critical E&O risk area):
Certificate log:
| Certificate ID | Issue Date | Client | Policy # | Certificate Holder | Issued By | Accuracy Verified | Copy Stored | |---------------|------------|--------|---------|-------------------|----------|------------------|------------| | [CRT-001] | [Date] | [Name] | [Pol #] | [Holder] | [Agent] | ✓ | ✓ |
Certificate holder management:
Complaint intake:
A complaint is any written or verbal expression of dissatisfaction from a client regarding the agency's services. Complaints must be logged even if resolved immediately.
| Field | Description | |-------|-------------| | Complaint ID | Unique identifier | | Date received | | | Complainant name and contact | | | Policy number(s) involved | | | Complaint channel | Phone / Email / Written letter / State DOI complaint | | Complaint description | Verbatim or detailed paraphrase | | Alleged error or failure | What did the client allege the agency did wrong? | | Assigned to | Who is handling the investigation | | Priority | Standard / Escalated (state DOI complaint = always escalated) |
Investigation workflow:
State DOI complaint regulatory reporting:
If a formal state DOI complaint is received:
Required E&O training by role:
| Role | Required Training | Frequency | Minimum Hours | |------|-----------------|-----------|--------------| | Licensed agent | E&O risk management (agency-specific) | Annual | 2 hours | | Licensed agent | State CE requirements (includes E&O topics in most states) | Per CE cycle | Per state | | CSR (unlicensed) | E&O documentation practices | Annual | 1 hour | | New hire (any role) | E&O onboarding — documentation standards | Within 30 days of hire | 2 hours | | Principal/agency owner | E&O program management | Annual | 1 hour |
Training completion log:
| Employee Name | Role | Training Module | Completion Date | Score (if tested) | Attestation Signed | |--------------|------|----------------|-----------------|------------------|--------------------| | | | | | | |
E&O training curriculum topics (minimum):
Deliver four artifacts:
tools
Managing project and task state in .claude/projects/{id}/ with atomic writes and session continuity
tools
Deep research before task execution using 4-source protocol: codebase→Perplexity→Context7→Firecrawl
tools
Validating task completion against acceptance criteria with per-type automated checks
tools
Using and creating project templates for webapp, API, ML pipeline, mobile, and infrastructure projects