If you work in an insurance agency, you know the drill. A commercial client needs an application packet. Someone on your team opens a blank ACORD 125, then a 126, then a 127, and starts typing. Name, FEIN, class codes, limits, VINs, driver dates. An hour disappears. Then a carrier kicks it back because a box got missed on page 3.
I run an agency in Tennessee, and I have spent the last year putting Claude to work inside it. Using Claude for insurance work is not theory for me. It answers coverage questions, reconciles commissions, and now it fills ACORD forms. This post explains the ACORD Form Filler skill: what it does, how it checks its own work, and why I built it the way I did. Because "AI fills out your forms" is exactly the kind of sentence that should make an agent suspicious.
A skill is a set of instructions and tools you install into Claude. Think of it like hiring someone who already knows your forms cold, except it is software. Once it is installed, you can say "fill an ACORD 25 for Riverbend Landscaping" and Claude knows exactly what that means and exactly how your agency wants it done.
This works with any paid Claude account. Claude on the web, the desktop app, or Claude Code if your shop is technical. You do not need special infrastructure. On the desktop version, finished forms save straight to your desktop. On the web, you download them from the chat.
Skills can also build on one another. One skill can retrieve information from another skill or connector to perform an action. Here is a brief presentation demonstrating this.
Say a landscaping client calls. They just signed a contract with the school board and need a certificate of insurance showing the board as additional insured. Here is the whole process.
The certificate that used to take fifteen minutes of typing takes about a minute of telling Claude who it is for.
I have watched form tools do three things that scare me as an agency owner, so this skill has three hard rules.
No placeholder values, ever. A square footage nobody entered. A deductible that came from a template instead of the policy. An earthquake box checked by default. Those mistakes look fine on the page until there is a claim, and then they are a problem with your name on it. This skill accounts for every single field on every form. A field is either filled from real client data or intentionally left blank with a documented reason. There is no third option. The software refuses to produce a form if even one field is unaccounted for.
Required questions stay required. On an ACORD 28, the yes/no coverage grid is not decoration. Blank rows on a completed evidence form are how E&O claims start. The skill will not produce a 28 with unanswered grid rows. It stops and asks you. Same on the flood form. It requires an answer on the NFIP rows, because "we never offered flood" is not a sentence you want to say in a deposition.
Official templates only. The skill fills official ACORD forms. It will never draw you a "close enough" version of one, no matter what you ask. If it does not have the form you need, it stops and tells you exactly what to provide.
This is the part I am proudest of, and the part you cannot see on the page.
ACORD's own PDFs are messy under the hood. Field names lie. On some forms, the field named for the bodily injury limit is actually the property damage box. Some forms skip letters in their row numbering. Some have boxes that were never made fillable at all. If you map these forms by trusting the field names, you ship forms with values in the wrong boxes and you never know it.
So every form in this skill was mapped the hard way. Fill every field with a numbered tag, render the page, and look at where each tag actually landed. Then fill the whole form with a realistic test client, render every page again, and inspect every box by eye. A form does not go in the library until it passes that check clean. Every trap we found along the way is documented inside the skill, so updates do not rediscover them.
Verified field mapping for ACORD 1, 2, 3, 4, 24, 25, 27, 28, 35, 36, 37, 60, 75, 80, 125, 126, 127, 129, 130, 130-CA, 131, 137-TN, 139, 140, 160, 163, and 175.
In plain English: certificates of insurance and evidence of property, binders, cancellation requests, broker of record changes, statement of no loss, flood selection and rejection, the full commercial application packet, general liability, business auto with vehicle and driver schedules, workers comp, umbrella, property, business owners, homeowners, statement of values, policy changes, and all four loss notices.
It also knows the rules between forms. If a property risk has more locations than the ACORD 140 holds, it prepares a 139 statement of values to go with it, and the totals have to add up before it calls the job done.
Drop the blank PDF into the skill's inbox folder and ask Claude to check it. If it is an edition the skill already knows, it activates on the spot and you are filling it a minute later. If it is a new form or a different state's edition, the skill walks through mapping and verifying it the same way every other form was done, or we will map it for you.
That matters for state-specific forms. The personal auto application and a few others exist in a separate edition for every state. The skill treats each edition as its own form, because a Georgia form is not a Tennessee form with a different label.
It does not rate, quote, or bind. It does not sign anything, and it never will. Signature lines stay blank for real signatures. It does not replace the licensed person reviewing the form before it goes out. It makes that person faster and takes the retyping off their plate.
If you want the skill installed, connected to your agency management system, and tested against your own book, that is what Claude Builds is for. It is the same setup I run in my own agency.
Questions, or a form you want to watch it fill on a call? Let's chat.