The Perilarc UW Workbench
ACORD-native ingestion, configurable appetite rules, ISO/Verisk risk signals, and decision routing — integrated into your existing policy system.
Three-tier data flow — submission to decision
Perilarc sits between your submission channel and your policy system, adding the appetite screen and risk score layer that manual UW workflows typically lack.
Everything in the submission lifecycle
From ACORD ingest to decision output, Perilarc handles each step with configurable logic and full audit trail.
ACORD XML/AL3 ingestion at carrier scale
Perilarc parses ACORD 125, ACORD 126, and ACORD 140 submissions natively — no manual rekeying into spreadsheets or intermediate transformation scripts. Direct carrier upload, REST API, or Guidewire/Duck Creek connector.
- ACORD 125 / ACORD 126 / ACORD 130 / ACORD 140
- AL3 EDI and ACORD XML both supported
- Required field completeness scoring at intake
ACORD Field Map
Configurable appetite matrix — your rules, your thresholds
UW directors configure appetite rules by line of business, territory, class code, TIV band, and CAT zone. Rules version-control and audit trail included. Appetite changes take effect immediately at intake — no code deployment required.
Appetite Modeling detailAppetite Rule Sample
TERRITORY: FL, LA, TX
CLASS: ISO 6311–6399
TIV_MAX: $5,000,000
CAT_ZONE: Tier 1 → DECLINE
Composite 0–100 risk score with signal attribution
Verisk PolicyAnalytics, LexisNexis C.L.U.E. Commercial, and ISO PolicyServices signals assembled into a single composite score. Every score includes a signal breakdown — no black-box decisions for your underwriters.
Risk Scoring detailScore Breakdown
Auto-route before the underwriter opens the file
Configurable thresholds determine whether a submission auto-declines, auto-refers to a specific UW queue, or enters manual review. Routing rules are per line of business and can be adjusted by UW operations without engineering involvement.
Submission Triage detailRouting Thresholds
Decision explainability and full audit trail
Every routing decision — and the data signals behind it — is logged. Underwriters can review the appetite rule that flagged a submission, the risk score breakdown, and the routing threshold applied. Supports UW operations review and regulatory inquiry response.
Audit Entry
Fits into your stack — no rip-and-replace
Perilarc connects to Guidewire PolicyCenter, Duck Creek Policy, and Insurity Policy via documented integration points. Submission data flows in; routing decisions and enriched risk data flow back. No workflow re-engineering for your UW team.
Full integrations catalogPolicy System Support
Platform specifications for technical buyers
| Specification | Value | Notes |
|---|---|---|
| API Latency | <2s per submission triage | Measured from ACORD ingest to routing decision. Verisk/LexisNexis lookups run concurrently. |
| Uptime Target | 99.5% monthly | Pilot SLA. Production SLA defined during carrier contract. |
| ACORD Versions | ACORD 125 (2014.1+), 126 (2016.1+), 130 (2014.1+), 140 (2014.1+) | AL3 and XML both supported. Version tolerance for common carrier variants. |
| Data Retention | Submission data: 7 years | Configurable per carrier data governance policy. PII handling per Perilarc DPA. |
| Encryption at Rest | AES-256 | All submission data and appetite configuration at rest. |
| Encryption in Transit | TLS 1.3 | All API calls and integration connectors. |
| Tenant Isolation | Per-carrier data isolation | Appetite rules and submission data are not shared across carrier tenants. |
| Authentication | OAuth 2.0 / API key | SAML 2.0 SSO available for carrier enterprise deployments. |
Ready to see the workbench configured for your lines?
Talk to our team about a structured pilot. We'll review your ACORD submission volume, lines of business, and policy system before recommending a configuration.