Insurance

How AI Helps Seattle and Chicago Underwriters Process Submissions

Seattle and Chicago carriers and MGAs can use AI to prepare source-linked submissions while meeting Washington and Illinois AI bulletins and MGA contract rules.

In this guide

For a carrier or MGA writing Washington or Illinois business with underwriters in Seattle or Chicago, AI can help by assembling a submission into a reviewable file: identify the documents, extract specified fields, compare conflicting values, flag missing information, and prepare a handoff into the underwriting workbench. The useful outcome is less reconstruction before a person can assess the risk. Whether it saves time depends on the quality of the incoming material, the effort to check the output, and the connection to existing systems.

Submission processing is a sensible first candidate when staff repeatedly reopen attachments or rekey the same information. It is a weaker candidate when most of the delay comes from broker responses, limited underwriting capacity, or unresolved appetite decisions. Those constraints need their own changes.

The time is there to recover. In Accenture's P&C underwriting survey with The Institutes, conducted in 2021, the average underwriter spent 40% of working time on administrative tasks and another 30% on negotiation and sales support, leaving about 30% for underwriting itself. Submission preparation is where much of that administrative time sits.

Explore an illustrative submission handoff with missing-document and identity checks.

The two states shape the design alike at the core and differently at the edges. Both adopted the NAIC bulletin on insurers' use of AI, and both require an MGA's contract to carry the same eight underwriting guidelines. Illinois expects a written AI program, makes the insurer file each MGA contract for approval, and allows far larger MGA penalties.

Give the underwriter a file they can interrogate

A useful submission view should show the named insured, requested coverage and effective date, document inventory, material extracted values, unresolved questions, and the next owner. Every material value needs a route back to its source. A polished narrative without that evidence makes review harder: the underwriter has to locate the original fact before deciding whether to trust the summary.

Cytora's intake lesson describes combining submission, internal, external, and inferred data before routing a file. That is a vendor description of a design pattern, not evidence of performance on your submissions.

Keep those categories distinct: a broker's address, the current policy's address, a third-party property attribute and a model's inferred occupancy are different kinds of evidence, and showing all four as supplied facts hides the disagreement the underwriter must resolve.

Separate reading, checking, and deciding

The following is a proposed operating design for submission preparation. Adapt the fields and controls to the line of business and your underwriting authority.

WorkUseful machine outputAcceptance boundary
Identify documentsApplication, loss history, schedule, supplemental form, and correspondence linked to one submissionAmbiguous entity matches stay unassigned for intake staff to resolve.
Extract fieldsValues with document, page or sheet, and version referencesMissing or unreadable values stay missing; the system does not supply a plausible answer.
Check completenessRequirements met, missing, or needing review against an approved checklistPresence of a document does not establish that it covers the required entity, period, or scope.
Prepare routingSuggested team and reasons based on current written rulesUnknown appetite conditions go to an authorized reviewer rather than becoming an automatic decline.
Support the risk assessmentSource-linked facts and open questionsRisk selection, pricing, terms, and binding stay within the organization's separately approved authority process.

A checklist, date comparison, or duplicate check may need ordinary software rules rather than AI. Use document AI where variable layouts make extraction difficult, and never ask a model to invent a rule your underwriting team has not agreed.

A conflicting property schedule is a better test than a clean application

This fictional example illustrates the review design; it is not a client case or a measured result. A property submission includes an application listing 12 locations, a spreadsheet listing 13, and a broker message saying one site has been sold. The loss runs cover an earlier period than the intake checklist requests.

A weak output silently removes a location, reports 12 as the confirmed total, and calls the submission complete. A useful output preserves the discrepancy: application count 12, schedule count 13, disposition of the sold site unconfirmed, loss-history period incomplete. It links the broker's message and both documents without deciding which is authoritative.

The intake coordinator requests the intended schedule; the underwriter decides whether the available loss history is sufficient. After clarification, the accepted schedule becomes a new version and the earlier one stays in the record. The handoff is ready when the reviewer can see the accepted facts, the unresolved issues, and who owns each one.

What regulators expect when AI supports underwriting

Using AI in underwriting is permitted, but the insurer remains accountable for it. The NAIC's Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, adopted December 4, 2023, says decisions or actions made or supported by AI must comply with all applicable insurance laws and regulations, and it sets expectations for how insurers govern their use of AI. As of April 1, 2026, 24 states and the District of Columbia had adopted the bulletin, and California, Colorado, New York and Texas had issued their own insurance-specific AI regulation or guidance.

Washington adopted it on April 22, 2024 as Technical Assistance Advisory 2024-02, addressed to all insurers licensed to do business in Washington: a policy statement that is advisory only and that encourages insurers to keep a written AI systems program. Illinois adopted it on March 13, 2024 as Company Bulletin 2024-08, which says insurers are expected to develop, implement and maintain that written program. Both ask that contracts with third-party AI vendors include, where appropriate, audit rights and a duty to cooperate with regulatory inquiries, so put both clauses in a submission-preparation vendor agreement in either state.

Managing general agents in Washington and Illinois

Both states built their MGA laws on the same model. In each, the MGA's written contract with the insurer must include underwriting guidelines covering at least the maximum annual premium volume, the basis of rates, the types of risks that may be written, maximum limits of liability, applicable exclusions, territorial limitations, cancellation provisions and the maximum policy period. The insurer reviews the MGA's underwriting and claims operations on site at least every six months, and the MGA's acts count as the insurer's.

In Seattle

Washington's act covers risks located in the state, including risks in Seattle, for an insurer authorized there, and requires the MGA to hold a Washington producer license and the insurer's appointment (RCW 48.98.010). It applies to an MGA as RCW 48.98.005 defines it: one that produces and underwrites at least five percent of the insurer's policyholder surplus in any quarter or year and also adjusts or pays claims above a set amount or negotiates reinsurance. The contract guidelines are in RCW 48.98.015, which also gives the commissioner access to the MGA's records in a usable form. The insurer's semiannual on-site review and its duty to notify the commissioner within 30 days of appointing or terminating an MGA are in RCW 48.98.020, and the examination rule in RCW 48.98.025. The commissioner may order a penalty of up to $1,000 for each violation (RCW 48.98.030).

In Chicago

Illinois sets its rules in 215 ILCS 5/141a. Its MGA threshold is five percent of policyholders' surplus in a quarter or eight percent in a calendar year, with authority to settle claims above $500 or to negotiate reinsurance. The insurer must file each MGA contract for the Director of Insurance's approval within 45 days, and it is approved if not disapproved in that time; a replacement contract goes back for approval when the old one expires. The insurer notifies the Director within 30 days of an appointment or termination, and the Director may order a penalty of up to $100,000 for each separate violation.

MGA ruleWashingtonChicago (Illinois)
Premium threshold5% of policyholder surplus in any quarter or year5% in a quarter or 8% in a calendar year
Contract approvalNo approval filing in chapter 48.98 RCWFiled for the Director's approval within 45 days
Penalty per violationUp to $1,000Up to $100,000
Shared coreEight minimum underwriting guidelines, semiannual on-site review, regulator access to MGA records, examination as the insurer

For an MGA writing Washington or Illinois business, build the completeness checklist and routing rules from those contract guidelines, send a submission outside a stated limit, territory or risk type to an authorized reviewer, and keep a record of which rule raised each flag for the insurer's semiannual review. In Illinois, tie each rule version to the contract the Director approved, so a changed guideline and its approval travel together.

Connect to the workbench without creating a second book

Start with the inbox or portal, document repository, clearance process, rating inputs, and policy administration system you already use. Identify the authoritative record for each field before mapping data between them. A submission identifier should survive a broker follow-up, a revised attachment, and a reassignment to another underwriter.

At first, place proposed changes in a staging view and let staff accept them into the working record. A failed write should show a pending handoff with an owner, and retries should not create duplicate submissions. Review how the provider retains documents, uses them for model training, and supports deletion and export.

Measure the review burden as well as the extraction

Compare representative files under the current and proposed process, including scanned loss runs, unfamiliar broker templates, corrected schedules, multiple named entities and incomplete submissions, and keep a test set that was not used for tuning.

  • Preparation effort: total staff minutes to produce an accepted handoff, including corrections and follow-up drafting.
  • Material errors: wrong entities, dates, location counts, amounts, or periods that would change the next action.
  • Missed gaps: files called ready despite a missing requirement, including a sample of apparently clean outputs.
  • Queue performance: time from receipt to an assigned reviewer, with time waiting on brokers reported separately.

Have the underwriting owner set acceptable errors and stop conditions before the trial. A high average field-accuracy score can hide a wrong insured or a material schedule omission, and faster preparation does not prove better risk selection or lower losses.

The broader insurance operations guide connects submission work with service and renewal queues. Within underwriting, the first question is narrower: can staff accept a source-linked preparation output with less total effort?

Quick answers

Can insurers in Washington and Illinois use AI in underwriting?

Yes, within existing insurance law. Both states adopted the NAIC model bulletin, which says decisions or actions made or supported by AI must comply with all applicable insurance laws; Washington's version is advisory, and Illinois expects a written AI program.

What should AI do first in underwriting?

Prepare the submission: identify documents, extract fields with links to their source, flag conflicts and missing items, and route the file, while risk selection, pricing and binding stay with authorized underwriters.

How do MGA rules differ between Washington and Illinois?

Both require the same eight underwriting guidelines and a semiannual on-site review. Illinois also requires the insurer to file each MGA contract for approval and allows penalties up to $100,000 per violation, against up to $1,000 in Washington.

Sources

  1. Accenture's P&C underwriting survey with The Institutes · insuranceblog.accenture.com
  2. Cytora's intake lesson · cytora.com
  3. NAIC's Model Bulletin on the Use of Artificial Intelligence Systems by Insurers · content.naic.org
  4. 24 states and the District of Columbia had adopted the bulletin · content.naic.org
  5. Technical Assistance Advisory 2024-02 · insurance.wa.gov
  6. Company Bulletin 2024-08 · idoi.illinois.gov
  7. RCW 48.98.010 · app.leg.wa.gov
  8. RCW 48.98.005 · app.leg.wa.gov
  9. RCW 48.98.015 · app.leg.wa.gov
  10. RCW 48.98.020 · app.leg.wa.gov
  11. RCW 48.98.025 · app.leg.wa.gov
  12. RCW 48.98.030 · app.leg.wa.gov
  13. 215 ILCS 5/141a · ilga.gov

Revision note · October 6, 2026: Headline simplified; the article body is unchanged.

How we research and review these guides

AI transformation with Clairvance

Put the ideas to work in your business.

We provide AI consulting and implementation for insurance agencies and brokers. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.

Discuss your project →

Still exploring? Explore the Workflow Opportunity Workbook →