AUTHORITY
Client mandate, jurisdiction, roles, objectives, and system-of-record ownership are defined first.
SPECIAL INVESTIGATIONS PROGRAMS
Investigation, referral, evidence, and program governance under one controlled model.
MODLAN can support individual SIU matters, overflow investigative capacity, or broader program operations while findings, claim authority, legal judgment, and intelligence remain distinct.
OPERATING LANES
Different disciplines. One governed program.
01
Investigations
Suspicious, complex, staged, organized, or unresolved claim fact development.
Explore →02Program Support
Assignment governance, vendor oversight, training, procedures, and trend context.
Explore →03Evidence
Digital preservation, authentication, submitted-media review, and secure evidence exchange.
Explore →04CST Intelligence
Protected MODLAN-owned fraud intelligence can add approved pattern, relationship, and claims context.
Explore →PROGRAM LIFECYCLE
Control the handoffs, not just the tasks.
- 01
Refer
Capture the objective, authority, jurisdiction, indicators, and relevant program instructions.
- 02
Investigate
Develop facts through licensed field, statement, public-source, records, or technical work as authorized.
- 03
Preserve
Keep evidence provenance, custody, source attribution, and investigative findings separable and reviewable.
- 04
Escalate
Return findings, referral-ready context, exceptions, and approved intelligence to the accountable program owner.
ENTERPRISE PROGRAM DEPLOYMENT MODEL
Services, evidence, integration, and CST can connect without collapsing their boundaries.
Program architecture scales only after authority and control are explicit. The carrier or client remains the source of business authority while MODLAN supplies the approved operating capability.
OPERATIONS
Claims, adjusting, SIU, private investigation, vehicle, or technical work runs inside the authorized lane.
EVIDENCE
Matter evidence moves through controlled ingress, provenance, access, custody, exchange, retention, and disposition.
INTEROPERABILITY
Approved adapters normalize and reconcile authorized data without replacing the client core platform.
CST BOUNDARY
Only approved context crosses into MODLAN-owned CST Protocol™; protected mechanics remain undisclosed.
ASSURANCE
Access, exceptions, reconciliation, control evidence, and program decisions remain reviewable.
ILLUSTRATIVE GOVERNANCE MATRIX
Accountability should remain visible as the program becomes more integrated.
This public matrix illustrates a common control pattern. Final responsibility, approval, consultation, and notification are defined by contract, jurisdiction, professional role, and the client operating model.
A AccountableR ResponsibleC ConsultedI Informed
| CONTROL AREA | CLIENT / CARRIER | MODLAN PROGRAM OPS | SERVICE SPECIALIST | PLATFORM / INTEGRATION |
|---|---|---|---|---|
| Business authorityThe client defines the mandate, authority limits, program objectives, and system-of-record ownership. | A/R | C | I | I |
| Program configurationMODLAN configures the approved operating model; client approval remains visible. | A | R | C | C |
| Claim decisionCoverage, settlement, and claim authority remain with the authorized client function unless expressly delegated by contract and law. | A/R | C | C | I |
| Investigative findingQualified investigators develop and report facts; findings do not automatically become coverage or legal conclusions. | I | A | R | I |
| Evidence custodyCustody responsibilities are matter- and program-specific and must be documented before evidence moves. | A | R | C | C |
| Integration mappingMappings, tenant boundaries, checkpoints, and reconciliation operate only inside the approved integration scope. | A | C | I | R |
| CST intelligence outputCST returns approved decision-support context; protected mechanics remain inside MODLAN. | A | C | C | R |
| Assurance & exceptionsControl evidence, exceptions, access, and reconciliation remain reviewable by the accountable program owner. | A | R | C | C |
PROGRAM LAUNCH GATES
Production should begin only after the operating model can explain who may do what, with which data, under which controls.
These are design gates, not public service-level promises or a substitute for customer-specific security, legal, licensing, or compliance review.
- 01DEFINE BEFORE LAUNCH
AUTHORITY
Program sponsor, permitted services, jurisdictions, decision rights, escalation, and system-of-record ownership are defined.
- 02DEFINE BEFORE LAUNCH
ROLE SEPARATION
Claims, investigative, technical, counsel-directed, and intelligence roles are separated where law, contract, or defensibility requires it.
- 03DEFINE BEFORE LAUNCH
DATA MINIMIZATION
Only the information necessary for the authorized purpose is identified, classified, and approved for use.
- 04DEFINE BEFORE LAUNCH
EVIDENCE LIFECYCLE
Ingress, integrity, custody, participant access, retention, legal hold, and disposition responsibilities are documented.
- 05DEFINE BEFORE LAUNCH
INTEGRATION CONTROL
Tenant boundaries, credentials, mappings, checkpoints, idempotency, retry/replay, and reconciliation are validated before production sync.
- 06DEFINE BEFORE LAUNCH
CST BOUNDARY
Approved context and approved outputs are defined without exposing protected algorithms, scoring logic, schemas, or internal orchestration.
- 07DEFINE BEFORE LAUNCH
ASSURANCE
Access review, control evidence, exceptions, vendor dependencies, incident paths, and audit requirements have accountable owners.
- 08DEFINE BEFORE LAUNCH
LAUNCH AUTHORITY
The accountable client and MODLAN owners approve launch criteria, unresolved exceptions, rollback/stop conditions, and production scope.
AFTER LAUNCH
The program lifecycle continues after implementation.
Review access, evidence, integrations, exceptions, vendors, controls, material changes, renewal, and eventual closeout against the approved operating model.
CONTROL BOUNDARIES
Enterprise breadth only works when authority stays visible.
- Regulated work is performed only where appropriately authorized and licensed.
- Investigative findings do not become coverage or legal conclusions by default.
- Fraud-bureau or agency referral decisions remain with the authorized carrier, counsel, or responsible program function.
- CST output supplements human investigative review and remains behind a protected technology boundary.
- Open-ended monitoring and deceptive collection are not program features.
ENGAGEMENT MODELS
Scale the relationship without changing the control model.
Matter
A defined suspicious or complex claim investigation.
Overflow
Extend an in-house SIU while the client retains program ownership.
Outsourced Program
Operate approved SIU functions under documented governance, separation, evidence, and escalation rules.
MODLAN PROGRAM OPERATIONS
Start with one assignment. Scale only when the operating model is ready.
Program architecture is defined around authority, jurisdiction, data, evidence, role separation, integration, and client guidelines before production scope expands.