Lines of business
ISO commercial auto rating, one vehicle at a time
Commercial auto rates per unit. Class, radius of operation and where the vehicle is garaged are facts about that vehicle, while the liability limits apply across the whole schedule, so a quote is a set of units that each rate individually and then roll up. In SelectRate's configuration model, bureau content sits underneath and your carrier and program configuration sits on top.
The unit of rating is the vehicle
A general liability risk is a business activity. A commercial property risk is a list of places. A commercial auto risk is a list of machines, and each machine carries its own rating facts.
Two trucks parked at the same yard, owned by the same insured, on the same policy, can rate differently because they are used differently. One runs local, one runs long haul. One is a light truck, one is not. The rate follows the unit.
That makes commercial auto the line where the schedule is most obviously the risk. A fleet of forty is forty rating problems that share a policy, not one rating problem with a count attached.
Per-vehicle facts and policy-level limits
| Input | Belongs to | What it drives |
|---|---|---|
| Class | The vehicle | How the unit is used, which is a property of that unit and not of the account. |
| Radius of operation | The vehicle | Where the unit runs. Two identical trucks in the same yard can sit in different radius bands. |
| Garaging territory | The vehicle | The territory follows where the vehicle is kept, so one policy can span several territories without the insured having several offices. |
| Liability limits | The policy | Limits apply across the schedule, which means the schedule rates per unit and the limits then sit on top of all of it. |
That split is the design constraint. Per-unit facts fan out, policy-level terms fan in, and the rating engine has to do both in one pass and keep the two straight in the output. In the published general liability payload, limits sit on the risk and the exposures sit underneath it. Commercial auto needs the same split, with the schedule made of vehicles rather than classifications. The commercial auto payload is not published, so ask to see it against a real fleet before you design intake around an assumed shape.
A quote is a schedule of units that roll up
The consequence at the top of the funnel is that a commercial auto submission is never small. Getting a fleet quoted means getting forty rows of vehicle detail correct, and the difference between a platform you can build on and one you cannot shows up in three places.
Per-unit resolution. Each vehicle has to resolve from its own facts, not from an account-level assumption applied uniformly.
Visible roll-up. The path from unit premiums to policy premium has to be readable, because the first question anyone asks about a fleet quote is which vehicles are driving the number.
Consistency across the schedule. The carrier deviation and program pricing you released have to apply the same way to unit one and unit forty. You set one multiplier for the whole program and override the single state that differs, and every unit on the schedule resolves from that one released version.
Fleets change mid-term
Fleets change constantly. A unit is added in March, two are sold in June, a driver moves a truck to a different yard.
In SelectRate a mid-term change is an endorsement: it is rated from the policy's current state, on the rating versions locked at the term's effective date, and recorded in the policy's transaction ledger with its own calculation. Cancellation, reinstatement and renewal follow the same model.
SelectRate rates and records every transaction on the policy term. Billing, invoicing, commissions and accounting stay in your systems.
Where a changed fleet actually gets re-priced
Renewal is the transaction where a commercial auto schedule is put back together. On SelectRate, a renewal is seeded from the policy as it stands after every accepted change, then rated fresh on the new term.
Two platform behaviors carry most of the weight here.
Rate a risk as of any date, and prior versions stay callable for audit. A quote from three years ago re-rates on the version and edition it was written under, which is what makes a renewal comparison honest: the expiring risk can be re-rated on the version it was written under and again on the released version, so the delta is measured rather than estimated.
And a program that is not effective for the quote date returns no premium. On a renewal that lands either side of a version change, silence is safer than a premium from the wrong version.
A rating run resolves the version in force for the policy’s effective date. There is no version to pin and no way to rate on one that was not in force.
What a per-vehicle worksheet has to show
SelectRate captures every rating step as the engine executes it, with the governing value and where that value came from, and every intermediate value is shown at the precision the engine used. Provenance records which filed mapping was selected, why it governed, and the document and page it came from.
A general liability worksheet for a single risk is one sequence of steps. A fleet worksheet is that sequence once per unit, then the steps that apply across the schedule, then the roll-up. So a commercial auto worksheet has to answer questions a monoline general liability worksheet never faces. Use them as the checklist when you review a fleet worksheet in a demo:
- Which vehicle a step belongs to.
- Which per-vehicle fact governed that step rather than an account-level input.
- Where the policy-level terms entered, and against what they applied.
- How forty unit results became one policy premium.
The full step-by-step reading of a worksheet sits on the general liability rating page. Commercial auto is the same discipline, repeated per unit.
Configuring a commercial auto program
The configuration model is the same one every line runs on. ISO rating content is the base layer, maintained by SelectRate against circulars as they issue. Carrier-approved deviations sit above it, by state. Your program pricing and rules sit above that. The final rate is explainable line by line.
When a circular issues, the base layer moves underneath you and your configuration stays intact. Creating a change never disturbs what is live, and a version is published with an effective date rather than on a release night, with the change live in Workbench and the Rating API at once.
Every change is tested in Program Studio before it can go forward: rate complete test risks against the draft version and against what is published, and read the worksheet behind each result. A version cannot be submitted for release until at least one test has rated, and the review step shows exactly what it changes against the published configuration, state by state. A published version takes effect on its effective date and never changes afterwards. Test with a fleet of a realistic size. A program that behaves on three vehicles tells you very little about one with forty.
Distribution
One endpoint serves every rating channel you authorize, all on the version you released. Each API client has its own credential and is granted the specific programs it may rate. Scopes decide which operations a credential can call. Grants decide which programs. There is no wildcard at request time, and a client never sees another client's quotes or policies.
The Rating API is synchronous JSON on the same engine as Workbench, so identical inputs, program and effective date produce an identical premium and worksheet. Products are discovered rather than hard-coded: GET /products/{productCode}/schema returns field metadata, types, options, required fields and conditional visibility, and new lines of business appear through discovery without a contract change. For a line whose risk payload is as field-heavy as commercial auto, discovery is the difference between a schema change and a contract negotiation.
The rest of the book
Commercial auto runs on the same configuration model as general liability, commercial property, businessowners and the ten AAIS products: governed bureau content underneath, your carrier and program configuration on top. A carrier that also needs cargo on the same account writes it on the AAIS Motor Truck Cargo product in the same place.
Questions buyers actually ask
Can we add a vehicle mid-term through the API?
In SelectRate a mid-term change is an endorsement, available in Underwriter Workbench and through the Rating API, rated from the policy’s current accepted state on the versions locked at the term’s effective date. Ask us to walk through it for the fleet program you are planning.
Do we send a territory for each vehicle?
On general liability you do not: territory is derived from the filed mapping and reported in the worksheet provenance. Ask to see the same behavior demonstrated for garaging territory on a multi-state fleet, because it decides how much your intake has to know.
Can one fleet submission be shopped across several carrier programs?
Yes. Leave the program code out and a single request rates every program you are entitled to for that product, state and date, each as an independent result, which is how you compare a fleet across your markets in one call.
How do we defend a fleet premium at audit?
Every rating step is captured as the engine executes it, with governing values and source references, and the run stays retrievable and byte-identical. Prior versions stay callable, so the quote re-rates on the version and edition it was written under.
Bring a fleet, not a sample
The honest test of a commercial auto rater is a real schedule with mixed units, more than one garaging territory and a couple of vehicles that should not be on it. Bring a program you write today and we will configure it live with you on the call, then talk your fleet through with you.