Endorsement requests, drafted for your account manager to review.

Today an insured emails something like "we bought a truck, add it Monday" with a photo of the bill of sale. An account manager works out which policy it touches, collects what the carrier needs, sends the change, and later checks the endorsement the carrier returns.

During the test, AI reads that same request and drafts the change: the policy and coverage line, the requested effective date, the details the carrier will ask for, and the questions still open for the insured. It also reads the endorsement the carrier issued and lists anything that differs from what was asked. Nothing goes to a carrier. Your reviewer compares both drafts with what your team did.

Each kind of change has its own checklist, and requests rarely arrive complete. A vehicle add needs the 17-character VIN, year, make and model, the garaging address, a stated amount or cost new for physical damage, and any lienholder or loss payee. A new location needs construction, occupancy, protection and exposure details plus building and business personal property values. Contractor's equipment needs serial numbers and values for the inland marine schedule. Often the most useful part of a draft is the short list of what to ask the insured.

The paperwork depends on the system and the carrier. ACORD 175 is the standard Commercial Policy Change Request, and AMS360 can build it in eForms from the policy's change and comparison details, with the underwriter and master certificate holders among its recipients. In Applied Epic, the account manager endorses the policy line from Policy Detail, then marks the endorsement issued or not issued once the carrier's version comes back. Some carriers want changes keyed into their own portal instead, so the draft has to match what that carrier asks for, not a generic form.

Not every request is a change the agency can simply make. A new operation, a vehicle outside the policy's usual class, a newly formed company added as a named insured, or a change dated before the request may need the underwriter, and some carriers won't backdate a change at all. The draft marks these as underwriting questions. It never says a change is covered and never gives an insured a coverage date.

The check on the way back is where errors hide. Commercial lines download works carrier by carrier, so some endorsements arrive in your system by download and others as a PDF in an email. Your reviewer looks for a wrong VIN digit, an effective date that moved, an additional insured spelled differently from the contract, and the additional or return premium. One endorsement can also start more work: an auto ID card for the new vehicle, an invoice on an agency-billed account, and new certificates for holders who rely on the changed line.

Once your reviewer says yes, new change requests run through the same job for about 30 days.

Each change waits for an account manager to confirm it, send it to the carrier and decide anything that needs underwriting. The AI never sends a change, never binds one, and never tells an insured a change is in place.

When endorsements come back, the check runs again, and your reviewer keeps the same score sheet.