managing-insurance-fraud-detection
Structures insurance fraud detection with red flag identification, investigation protocols, and SIU referral documentation. Use when detecting insurance fraud, investigating suspicious claims, or documenting fraud indicators.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- managing-insurance-fraud-detection
- tags
- [ "management", "insurance" ]
- source
- https://github.com/CaseMark/skills
- license
- Apache-2.0
- language
- en
- metadata
- { "author": "casemark", "skill_modes": [ "Management", "Coordination" ], "document_types": [ "Management Report" ], "practice_areas": [ "Insurance", "Actuarial Science", "Reinsurance" ] }
- description
- Structures insurance fraud detection with red flag identification, investigation protocols, and SIU referral documentation. Use when detecting insurance fraud, investigating suspicious claims, or documenting fraud indicators.
- imported_at
- 2026-09-20
- source_path
- skills/finance/managing-insurance-fraud-detection/SKILL.md
- source_repository
- CaseMark/skills
03 SKILL.md 正文
Managing Insurance Fraud Detection
Structures insurance fraud detection programs covering red flag identification, investigation protocols, SIU referral documentation, and cross-functional coordination across claims, underwriting, and compliance teams.
When To Use
- Standing up or auditing a fraud detection program for a carrier or MGA
- Triaging suspicious claims against known fraud indicator patterns
- Building or refining SIU referral criteria and escalation workflows
- Documenting fraud investigation findings for regulatory reporting or litigation support
- Evaluating analytics/model outputs that flag anomalous claim or policy activity
- Coordinating between claims adjusters, SIU investigators, legal counsel, and law enforcement
Inputs To Gather
- Line of business: Auto, property, health/medical, workers' comp, life, disability, or commercial liability
- Claim file or policy data: Claim number, policy details, loss description, claimant/insured information, payment history
- Red flag triggers: What prompted suspicion (adjuster referral, analytics alert, tip, pattern match)
- Prior investigation history: Past SIU referrals, prior claims by same claimant/provider, related party flags
- Jurisdictional context: State fraud reporting statutes, mandatory referral thresholds, immunity protections [VERIFY]
- Internal thresholds: Company-specific scoring models, referral criteria, authority limits for SIU action
- Regulatory obligations: State fraud bureau reporting deadlines, NICB membership requirements, federal program fraud considerations (e.g., crop insurance, flood insurance) [VERIFY]
Workflow
-
Classify the fraud type
- Distinguish hard fraud (staged accidents, arson, fabricated claims) from soft fraud (inflated damages, misrepresented facts, premium evasion)
- Identify the scheme pattern: provider fraud, policyholder fraud, agent/broker fraud, organized ring activity
- Map to the relevant line of business — red flags differ materially between auto PIP fraud, property water-loss fraud, and workers' comp malingering
-
Catalog red flags
- Document each indicator with specificity: financial pressure signals, timeline inconsistencies, claimant behavior anomalies, medical treatment patterns, policy inception-to-loss timing
- Cross-reference against established indicator libraries (NICB, ISO ClaimSearch, Coalition Against Insurance Fraud resources)
- Score or weight indicators — a single flag rarely warrants SIU referral; accumulation of 3+ correlated indicators typically triggers escalation
-
Assess investigation viability
- Determine whether the claim reserve and potential recovery justify investigation costs
- Identify available evidence sources: surveillance feasibility, social media intelligence, EUO/statement under oath opportunities, medical record audits, financial record subpoenas
- Evaluate statute of limitations and reporting deadlines for the jurisdiction [VERIFY]
-
Structure the SIU referral package
- Prepare a referral memo with: claim synopsis, enumerated red flags with supporting evidence, recommended investigation actions, preliminary fraud type classification
- Attach supporting documentation: indexed claim file excerpts, analytics output, prior claim history, public records search results
- Assign priority tier (routine, elevated, urgent/ring activity) based on dollar exposure and scheme complexity
-
Define investigation protocol
- Outline specific investigative steps: recorded statements, surveillance windows, scene inspections, canvass interviews, financial analysis, expert retention
- Set milestone checkpoints (30/60/90-day reviews) with go/no-go decision criteria
- Establish chain-of-custody procedures for physical and digital evidence
- Coordinate with claims on reservation of rights letters and EUO scheduling
-
Manage regulatory and law enforcement coordination
- Prepare state fraud bureau referral forms per jurisdictional requirements [VERIFY]
- Determine whether to file a Suspicious Activity Report (SAR) if federally regulated program is involved [VERIFY]
- Coordinate with NICB for organized fraud or multi-carrier schemes
- Document all law enforcement contacts and information-sharing with appropriate privilege protections
-
Produce the management report
- Summarize open investigations by status, priority, and estimated exposure
- Track key metrics: referral-to-resolution time, denial/recovery rates, investigation ROI
- Highlight emerging scheme trends and recommend adjustments to detection models or adjuster training
- Flag cases approaching regulatory reporting deadlines or litigation hold triggers
Output
The deliverable is a Fraud Detection Management Report containing:
- Executive summary: Total referrals, open investigations, recoveries, and denial savings for the reporting period
- Red flag analysis: Cataloged indicators by scheme type with frequency and correlation data
- Active investigation tracker: Case-by-case status with priority tier, assigned investigator, next action, and target dates
- SIU referral packages: Completed referral memos with supporting documentation indices
- Regulatory compliance log: Filed reports, upcoming deadlines, and outstanding obligations by jurisdiction
- Trend analysis and recommendations: Emerging patterns, model tuning suggestions, training needs, and resource allocation proposals
Quality Checks
- Every red flag cited is tied to a specific, documented data point — no conclusory assertions without evidentiary support
- Fraud type classification aligns with NICB/ISO standard taxonomy
- SIU referral memos distinguish between confirmed facts, adjuster observations, and analytical inferences
- Jurisdictional reporting requirements are verified against current statutes — mark with [VERIFY] if not independently confirmed
- Investigation protocols include chain-of-custody requirements and privilege preservation steps
- Management metrics use consistent definitions (e.g., "recovery" includes subrogation, denial savings, and restitution separately)
- No accusatory language in documentation — use "indicators consistent with" rather than "fraud" until adjudicated
- All timelines account for applicable statutes of limitation and regulatory filing windows [VERIFY]
04 同仓库更多 Skills
dei-assessment
Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.
dei-action-plan
Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.
culture-fit-assessment
Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.
cowork-to-code-bridge
Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.
counter-offer-response
Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.
continuous-feedback-system
Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.