The way you collect risk information is part of the underwriting model
Ask any experienced underwriter what makes a submission good and they will not describe a form. They will describe a conversation: the right questions, in the right order, shaped by answers as they arrive. Facio treats the intake journey as the first act of underwriting.
The operational problem
Commercial risks are not uniform, and neither is the information needed to understand them. Which questions apply depends on the product, the binder, the class, and frequently on the answers already given. When that logic lives in an underwriter's head, every submission requires their attention. When it lives in a generic form, submissions arrive incomplete, and the real underwriting happens in the email thread that follows — undocumented, unassigned and invisible to management.
How it works
Facio provides adaptive data collection, eligibility rules, referral routing, and authority-aware workflow progression with complete decision history behind every risk.
Dynamic & conditional data collection
Journeys present questions relevant to the specific risk at the exact point they become relevant. An answer can open a section, require evidence, or route the case.
Product- and binder-specific journeys
Each product and binder defines its own journey, questions, required evidence, and validation rules.
Eligibility and validation
Rules evaluate risk as information arrives. Required information is validated before the workflow advances.
Referrals on proposed policy forks
Conditions trigger human referral. Where a referral concerns a policy change, it operates on a proposed policy fork so the active contract remains untouched.
Follow-ups and operational SLAs
Missing information becomes a structured, assigned follow-up connected to the risk with governed operational SLAs.
Authority-aware progression
What each participant may do — submit, quote, approve, bind — follows from their configured roles and authority limits.
Complete decision history
Questions asked, answers changed, referral triggers, approvals, and timestamps form an audit-ready transaction record.
Configuration and control
Journeys, questions, validation rules, referral conditions and authority boundaries are configured per product and binder — and versioned, so a change to the question set does not orphan the submissions collected under the previous version.
The boundary between what the workflow executes automatically and what requires a person is a configuration decision, made deliberately, per programme.
Design Your Underwriting Journey
In a working session, we map one of your products' actual information requirements into an adaptive journey, including where referrals and human decisions belong.