Larkfield Intake: Submission Intake for Specialty Insurance by Ali ShanLarkfield Intake: Submission Intake for Specialty Insurance by Ali Shan

Larkfield Intake: Submission Intake for Specialty Insurance

Portfolio project
Ali Shan
SKILLS
Product Design, Web App Development, Front-End Development, UI/UX Design, Internal Tools, Dashboard Design, Data Visualization, React, TypeScript, Insurtech
TOOLS
React, TypeScript, Vite, Tailwind CSS, Radix UI, Motion, D3.js
Overview
Larkfield Intake is a production-ready internal platform for the submission desk at a specialty MGA writing excess and surplus (E&S) commercial property. When a broker sends an email with an application, statement of values and loss runs, the platform turns those documents into one checked submission file. It extracts application data, maps every insured location, summarizes loss history, identifies missing information, drafts requests back to the broker and routes the file to an underwriter with sufficient signing authority.
I designed and built the platform end to end, including the workflow, interface, design system and front end.
The problem with MGA submission intake
On an E&S property desk, an underwriting assistant traditionally opens every broker email by hand. They review the application, statement of values and loss runs, then manually transfer the information into the rating system. When something is missing, they chase the broker over email and the file remains on hold until a response arrives. Someone also has to determine which underwriter has the authority to sign off on the file’s total insured value, often using a spreadsheet or relying on memory.
The result is a slow intake process. Underwriters wait for complete files, while brokers wait for decisions.
How the submission desk works
A renewal moves through the platform from initial receipt to underwriting readiness. A wholesale broker submits a file for a refrigerated warehousing company with 14 locations across Georgia, South Carolina, North Carolina and Tennessee, representing $18.4M in total insured value.
Email intake. The submission enters the queue, displaying the broker, insured and current status.
Application processing. The platform reads the application and extracts its fields. Each field on the submission card is populated and validated as the document is processed. A timestamped run timeline records each step.
Location mapping. The statement of values is translated into an interactive geographic view of all 14 locations across the four states. Each location is represented by a column sized according to its insured value. Locations missing sprinkler details are highlighted in amber.
Automated checks. Appetite, duplicate, completeness and authority checks run against the submission. The resulting summary identifies that the file fits appetite, has two outstanding items and requires senior underwriting authority.
Broker follow-up. The platform prepares an email identifying the missing information: loss runs for 2022 and 2023, along with sprinkler details for two locations. The assistant reviews and sends the request from their own mailbox.
Authority-based routing. Because the $18.4M submission exceeds the assigned underwriter’s $10M authority, it is routed to a senior underwriter with a $50M limit. The senior underwriter accepts it for review, with the hand-off recorded in the audit log.
Completeness verification. When the broker responds, the two PDFs are attached to their corresponding outstanding items. The missing loss years are populated, both locations are marked complete, and the submission moves to Ready for Underwriting.
Design decisions for an underwriting tool
Underwriters make the decisions. The platform does not calculate premiums, generate rates, issue quotes or bind coverage. Its role is to prepare and validate the submission so an underwriter can make the decision.
The assistant remains in control of broker communication. The platform drafts follow-up emails, but the assistant reviews and sends them from their own mailbox. The broker relationship stays with a person.
Rules reflect existing underwriting processes. Appetite by class, required documents, authority limits and broker lists are imported from the spreadsheets the team already maintains. Updates to the authority table are reflected in routing decisions.
Every action is auditable. Document reads, validation checks, email drafts and hand-offs are recorded with timestamps and the name of the person or system responsible.
Color has a functional purpose. Amber indicates that something requires attention. The aubergine accent is reserved for active states and primary actions, keeping the interface focused on the next required decision.
Technical build: React, TypeScript and D3
Application architecture. React 19, TypeScript and Vite, with Tailwind CSS v4 and a token-based design system. Radix UI primitives handle dialogs, menus and popovers, providing keyboard and screen reader accessibility. Lucide icons and Geist typography complete the interface.
Interactive 3D location map without WebGL. The statement-of-values map is rendered entirely in SVG. d3-geo projects US states from us-atlas TopoJSON. An orthographic camera, applied through an affine transform, tilts the four states into a raised perspective. Each location is represented by a cylinder, depth-sorted so foreground columns overlap those behind them. The SVG rendering remains sharp at any zoom level.
Seamless screen transitions. Opening a submission from the queue uses the View Transitions API with React’s flushSync. The selected row’s title transitions into the file header rather than cutting abruptly to a new screen.
Synchronized document processing. The document viewer’s scan line and text reveal remain synchronized. A scrambled copy of the text is clipped at the scan line’s live position, with the actual text settling into place from left to right as the line passes.
Unified submission state. Submission fields, validation chips, routing information, outstanding items and audit records all derive from a shared submission state. When new broker documents arrive, the relevant views update together.
Motion and accessibility. Animations use critically damped springs without bounce. Attachment hand-offs run on the Web Animations API, and all motion respects prefers-reduced-motion.
Thirteen functional application pages. Inbox, My Queue, Waiting on Broker, Referred, Ready for Underwriting, Insureds, Locations, Brokers, Rules, Authority, Audit Log, Imports and Settings. Each page has its own URL.
Integration architecture. The platform supports spreadsheet imports for underwriting rules and authority limits, with file-based exports for the rating system. It operates alongside the MGA’s existing systems without writing directly to the policy administration system.
What changes for the desk
Underwriting assistants review extracted and validated information instead of manually retyping it. Brokers receive clear, consolidated requests for outstanding information. Underwriters receive complete, checked submissions routed according to their authority. The head of underwriting gets a centralized audit trail of every action taken on every file.
The result is a more structured, traceable submission process that reduces manual handling and gives the underwriting team better visibility from intake to review.

0 likes · 0 views · Nov 17, 2026

An internal underwriting tool that turns broker emails into checked, routed submission files for E&S commercial property. Product design and front-end build.

Tags