Background
The insurer received submissions from brokers across several product lines. Each package could contain questionnaires, policy information, risk documents, pricing inputs, and supporting communication.
The information arrived in inconsistent formats and at different levels of completeness. Underwriters therefore spent part of their time checking documents, extracting risk parameters, identifying missing information, and following up with brokers before substantive assessment could begin.
Submission status was also distributed across CRM, policy administration, document tools, and broker communications, limiting visibility into pipeline progress and workload.
Approach to solution
Computools began by mapping broker submission workflows, underwriting queues, document requirements, and dependencies across existing insurance systems.
The team identified which information brokers needed to provide, which risk parameters had to be available before review, where incomplete submissions created delays, and how cases moved into underwriting queues.
A structured broker journey was then designed around questionnaire completion, document upload, data extraction, completeness validation, follow-up tasks, submission prioritization, and routing.
OCR and AI converted relevant document content into structured risk data. Validation rules identified missing information before submission handoff, while task creation supported follow-up with brokers.
REST-based integrations connected submission data with CRM, policy administration, and document management systems. Pipeline dashboards provided visibility into submission status, broker activity, pending actions, and workload distribution.
Computools role
Computools was responsible for:
- analyzing broker submission workflows;
- mapping underwriting queues and system dependencies;
- defining broker and underwriter user journeys;
- designing structured submission questionnaires;
- implementing document intake and classification;
- configuring risk-data extraction and validation;
- defining missing-information checks;
- creating automated follow-up tasks;
- building submission queues and prioritization logic;
- integrating CRM, policy administration, and document systems;
- implementing pipeline dashboards;
- adding submission history, override logs, and role-based access
Key decisions and outcomes
Submission completeness became an explicit part of the underwriting workflow, allowing teams to identify missing documents and risk information before a case reached substantive assessment. Structured questionnaires and document processing reduced variation across broker submissions and created a more consistent information set for underwriters.
Automated preparation remained separate from underwriting authority. OCR and AI-supported extraction and validation, while pricing, eligibility, overrides, and approvals remained under human control.
Submission priority, pending actions, and readiness were consolidated into a single underwriting view. Integrations kept CRM, policy, and document information connected to the submission record, giving operations teams clearer pipeline visibility without creating another isolated data source.