Endorsement requests: by hand or software?

Published 17 October 2026. Updated 17 October 2026.

Every agency handles mid-term change requests somehow: a client emails that a van was bought, a crew was hired or a location opened, and someone turns it into a request for the carrier. Some agencies do it by hand each time. Some keep a template. Some use software. This guide compares the three honestly, including the cases where doing it by hand is the right call.

The three ways of doing it

1. By hand. Someone reads the email, opens the carrier portal or writes an email, and types the values in.
2. By hand with a template and a checklist. The same, but with a standard request layout and a short list of things to confirm.
3. With software that drafts the request. The email goes in, a draft with the fields filled comes out for you to read before sending.

Where mistakes enter

The errors in this job are small and repetitive, and they all have the same cause: a value is retyped, or assumed, without being compared with its source.

• Retyping. A VIN with a transposed pair of characters, a street number typed twice, a payroll figure with a missing zero.
• Assumed dates. The client says "next Tuesday" or "the 15th". The month or year gets assumed.
• Total or increase. A payroll figure that is the amount being added is entered as the new total, or the reverse.
• Missing details. No suite number, no garaging address, no class description.
• Version confusion. The request is drafted from an older copy of the email or from an old declarations page.
• Nobody checks the second time. The person who typed it is the person who checks it, and they see what they meant to type.

The guides on adding a vehicle to a commercial auto policy and mid-term workers comp payroll changes go through what the carrier needs for each of the common changes.

Comparison table

When by hand is enough

By hand, with a good template and a checklist, is the right answer for many agencies:

• you handle a few change requests a week, and the same careful person handles them;
• most requests are simple and the checklist covers them;
• your requests are unusual, with many different forms and carriers, so a fixed layout would not fit;
• you would rather write a checklist once than change how the work flows.

If you go this way, make the checklist do real work: a VIN check, a rule that dates are written in full, a rule that a payroll figure is always asked as "total or increase", and a rule that the original email is saved with the request.

When software starts to pay for itself

Look at software when:

• several people draft requests and the quality depends on who picked it up;
• a request has gone out wrong in the last year and it took weeks to find out;
• emails arrive messy, with several changes in one paragraph;
• you want each value traced to its source so that the second look means reading one line, not the whole email.

Weigh these against what software cannot do. It does not know your client's situation, it does not decide coverage questions and it does not replace a call to the carrier when something is unusual.

A short checklist for either approach

1. Save the client's email with the request.
2. List every change in the email, one per line, before filling anything.
3. Write every date in full, with the year.
4. Run the VIN check digit and compare the VIN with a document.
5. Compare addresses and payroll classes with the declarations page.
6. Mark anything missing as a question to the client.
7. Send, then log the date and the carrier's reply.

How EndorseDesk does this step

You upload the client's change email (text, PDF or Word, or pasted) and, if you have it, the declarations page as a text-based PDF, Word or text file. The email can hold up to 6 changes such as a vehicle added or removed, a location added or a payroll change. You get back one zip: a pre-send check listing what to look at first, a portal field sheet with the email line behind each value, a carrier email to copy, and the field sheet as JSON.

Code checks the VIN, the date, the address and the required fields, and compares the change with the declarations page. A missing value is listed as missing, not guessed; only the insured's name (when the email gives none) and the year of a day-and-month date (when the policy period leaves no doubt) are taken from the declarations page. A second, stronger AI model reviews every result and lists what is left for you to decide; the drafting model corrects the serious problems the review finds, and code checks every correction. Results are not verified by a person.

A request costs 6 credits, $6.00 on the starter pack, with no subscription. EndorseDesk sends nothing to the carrier and does not write to your agency management system, and it does not read scanned declarations pages. You read the result and send it yourself. Sign up to try one.

Questions

How many change requests a month justify software?

There is no fixed number. The better question is how often a request goes out with a wrong or missing value, and how long it takes someone to find out. If that has happened more than once this year, a more careful process is worth looking at.

Will our agency management system do this for us?

Some systems include assistants for drafting emails or filling forms, and what they do varies by system and by version. Ask your vendor three things: does it cite where each value came from, does it check the VIN and date, and does it compare the request with the policy on file.

Is a template enough?

A template fixes the layout and reminds you what to ask. It does not read the client's email for you or check anything you type into it. For low volumes with a careful person, it is often enough.

Who should check a drafted request before it goes out?

Whoever sends it is responsible for it. Whatever drafts the request, read the values against the client's email and the declarations page once before you send.