On this page
A rate or form filing is mostly research, drafting and checking: finding what the state requires, gathering support, building exhibits and forms, answering the reviewer and keeping track of where everything stands. A general AI assistant can draft fluent text, but on its own it does not know the state's filing rules, cannot see other carriers' filings and has nowhere to keep the filing's record. Its answers come from the model's memory.
An AI filing desk closes that gap. Evermont connects your assistant (Claude, ChatGPT or Codex) to state filing research, public SERFF filings, calculation modules and your organization's own filing records. The assistant does the reading and drafting; Evermont supplies the sources and keeps the record; your team reviews and decides.
One filing, start to finish
Requirements
Create the filing, answer the intake questions and build a checklist of what the state requires, each row with its authority.
Research
Search other carriers' public SERFF filings for precedent and read the documents behind them.
Build
Run calculations, fill the state's official forms and draft documents, saved to the filing.
Objections
Record the reviewer's letter, gather cited evidence for each item and draft a response for review.
Record
Every change an agent makes is kept in the filing's history, with the person or key that made it.
Requirements
Each filing in Evermont has a state, line of business and filing type. From those and your answers to a short set of intake questions, Evermont builds a requirements checklist: what applies to the filing, the authority behind each row, and which rows are ready, blocked or need review. Your assistant can explain any row, search the state guidance behind it (statutes, regulations, bulletins and the state's own instructions, with sources) and list the official state forms and templates that apply. State filing requirements and checklists explains where these requirements come from.
Exhibits, forms and documents
For the actuarial side, Evermont runs deterministic calculation modules, such as a rate indication, loss development, credibility or on-leveling, with quality checks and an audit record you can cite. For the paperwork, the assistant can fill an official PDF form and save the completed copy to the filing, or build a Word or Excel document from your inputs. Each output is saved as a new document on the filing; originals are not overwritten.
Precedent comes from public SERFF filings: the assistant can find how other carriers supported a similar change and read their memoranda and exhibits. SERFF filing search covers that part.
Objections
When the department sends an objection letter, the assistant records it on the filing and splits it into items, gathers cited evidence for each one (SERFF precedent, your documents and matching requirement rows) and drafts a response as a Word document for your review. Evermont tracks each objection's status and response date. SERFF objection responses describes the workflow.
The filing record
Filings, their documents, requirement rows and objections live in your Evermont organization, visible in the web app and to your assistant. Ask what changed on your filings this week or which deadlines are coming up, and the assistant answers from that record. Every change an agent makes through Evermont is recorded with the person or API key behind it, which also helps when a state asks whether AI was used; see AI-use disclosure in SERFF filings.
What stays with your team
AI speeds up the research and the first drafts. It does not take responsibility for the filing, and Evermont is built around that:
- People sign off on requirements. Only a person can mark a requirement row satisfied, in the web app.
- Your team files. Evermont does not submit to SERFF. A filing is marked submitted only after someone confirms it was filed.
- Drafts are drafts. Responses and documents are saved for review; nothing is sent to a regulator.
- Sources are named. Answers cite the filing, document and page they came from, so a reviewer can check them before anything goes out.
Watch the demo to see a filing go from SERFF research to requirements and an objection response in Claude and Codex, or read the docs for every tool your assistant gets.
Questions and answers
Does Evermont submit filings to SERFF?
No. Your team files in SERFF as it does today. Evermont keeps the filing record, and an agent can mark a filing submitted only after you confirm it was filed outside Evermont.
Who decides that a requirement is met?
A person. Your assistant can add rows to the requirements checklist and update their status and notes, but only a person can mark a row satisfied, in the Evermont web app.
Does it overwrite our documents?
Filled forms and drafted documents are saved to the filing as new documents, so the originals stay as they were. When you ask for find-and-replace edits to a Word document, they are saved over that document, or to a separate copy if you ask for one.
What does Evermont see from our conversations?
Only the arguments your assistant puts in each tool call, plus connection details. It does not receive your conversation history, your assistant's memory or the files in your chats, and a connection reaches only the organization you approved.
Which assistants can use it?
Claude, Claude Code, Cowork, ChatGPT and Codex, connected to Evermont's MCP server with an OAuth sign-in or an API key.
See it work: watch the 75-second demo or read the docs for setup, the tool list and coverage.
General information, not legal or actuarial advice. Requirements differ by state, line and filing; check the current rules with the department of insurance before you file.