User Guide
A reference for every page in the FreightMath Dashboard — what it shows, how to use it, and how segment-level costing powers the underlying analytics.
Every page in the FreightMath platform — what it shows, the business questions it answers, how to read it correctly, and where it fits in your analytical workflow. Pages marked SLC draw directly from the segment-level cost allocation engine, meaning profitability figures are load-level and allocation-aware — not simple averages.
Start high-level, move to diagnosis, then action. Users who follow structured workflows consistently extract more value than those who navigate dashboards independently. The sequence above mirrors how experienced FreightMath users approach a weekly performance review.
Filter the list by role, expand any page for its screenshot, key questions, what to look at, watch-fors, and an example scenario. Related-page links open the matching entry below.
Methodology reference
Core OR tells you how a single load performed on its own merits. IB OR and OB OR bring the market context behind every load — the area-level profitability conditions that surround each pickup and delivery. Together they form FMOR.
IB OR is the average profitability of all loads delivering into a specific market area — including loads from nearby areas where the driver then deadheaded in for a reload. It reflects how efficiently freight flows into that market.
Assigned to each load based on its origin market. A favorable IB OR at the origin means the market is an efficient source of freight — loads pick up at good rates with manageable positioning cost.
How it's built. Direct deliveries to the area + loads from nearby areas connected via deadhead, weighted by load count into a single blended area average. Empty miles use only intra-area deadhead for direct loads, and the actual cross-market deadhead cost for loads drawn from neighboring markets.
OB OR is the average profitability of all loads picking up from a specific market area — including loads in neighboring markets that drivers deadheaded into after leaving this area. It reflects how efficiently freight originates from that market.
Assigned to each load based on its destination market. A favorable OB OR at the destination means the driver reloads well after delivery — the market generates efficient outbound freight.
How it's built. Direct pickups from the area + loads from nearby areas connected via outbound deadhead, weighted by load count. For direct loads, only pre-haul intra-area deadhead is used. For drivers who crossed a market boundary to reach a pickup, the full cost of that deadhead leg — and the revenue it generated — belong to this area's outbound picture.
Together, Core OR, IB OR, and OB OR form FMOR — the primary load-level profitability metric. It captures what the load cost, the conditions it came from, and the conditions it delivered into.
Two loads with identical Core OR can have very different FMOR depending on which markets they touch. A load running between two efficient, well-balanced markets will carry a FMOR close to its Core OR. A load delivering into a market where outbound freight is scarce or expensive will see its FMOR pulled significantly higher — the OB OR at the destination is reflecting the true cost of positioning the driver for the next move. IB OR and OB OR make this market context visible in every number.
Platform reference
Every measure on these pages is defined in the FreightMath Glossary — plain-language definition, how it is calculated, and why it matters — searchable by term, abbreviation, category, and tag.