You’ll notice that many of the fields have fairly long names. This is intentional, as it helps us capture more detail and be more precise. There are a few common patterns with our field names:

(e.g., business exception count): Fields with the word “count” in them represent “counts” of values. For example, if there are 3 missed pickups in a given week, “missed pickup exception count” will equal 3.

Fields with the word “percent” in them represent proportion or percentages. For example, if there are 3 missed pickups out of 50 shipments in a given week, “missed pickup exception percent” will equal 6%.

Fields with the appendix “CR” indicate that the carrier is the responsible party. All KPIs should have a percentage field and a percentage “CR” field. Remember that only exceptions for which the carrier was responsible are counted against carrier scorecards. Accordingly, if you want to compare KPIs on ISO scorecard pages to KPIs in ISO's analytics tool, you’ll want to use the “CR” field. For example, if there are 3 missed pickups out of 50 shipments in a given week, but only 1 was the carrier’s fault, then “missed pickup exception percent CR” will equal 2%, while “missed pickup exception percent” will equal 6%.

There are certain fields that are worth highlighting.

ISO has two types of dates--reporting dates and shipper weeks.

are representative of when an event occurred, such as a tender decline or a successful pickup. When you filter on specific dates in ISOs carrier scorecard, you’re using the reporting date. When comparing data from ISOs carrier scorecard and ISOs analytics tool, make sure you’re filtering on the right date field.

In addition to reporting date, ISO offers shipper weeks and shipper years. These fields map directly to the shipper weeks that your company uses internally. Shipper weeks are normalized across all carriers. When you’re filtering on weeks in ISO's carrier scorecard, you’re using shipper weeks and years.

ISO's carrier scorecard also offers the ability to filter by Delivery and/or Transfer. In ISO, this field is called “fulfillment type.” When comparing data from ISO's carrier scorecard and ISO's analytics tool, make sure you’re filtering on the correct fulfillment type.