Stops served
- Planned
- 329 dispatched
- Measured
- 325 made
- Billed
- no charge
- Variance
- 4 stops not made
P5 route completion · manifest reconcile against the dispatch plan
Reconciliation read
The seller's system holds what was planned. The position trace holds what was driven. This is the ledger between the two, set beside what was actually charged, and it states how much of the window it could read before it states anything else.
Reconciliation read
OTR trucking Flat service Additive service Rail carload
Mon 15 Jun – Sun 21 Jun 2026
Modeled sample data
Detention on this book billed $9,513.87 against $9,952.85 of operating cost on the same 149 hours, a $438.98 shortfall, read across the 93.8% of duty hours the position trace could place.
P5 route completion · manifest reconcile against the dispatch plan
P3 detention · free_time_s=7200, rate=per_hour, $63.71/h recovered against $66.65/h of cost
P6 off-route · sustained deviations only, persistence_s=300, priced at $2.34 per mile
P7 utilization · idle_threshold_s=300, 186 gal at 0.82 gal/h, priced by the engine's two-rate idle burn
Bar is measured. Tick is billed. Caret is planned. The rule under the bar is the span between what happened and what was charged, and hatching is quantity the read could not determine.
Stated before the rates above, not after them. A rate without a denominator is an assertion.
93.8% of the 1,680 duty hours in this window are placed by the position trace. The remaining 6.2%, roughly 104 hours, carries no segment at all. It is excluded from every rate above rather than assumed idle.
5 of 9 KPIs. P3 detention, P5 route completion, P6 off-route, P7 utilization, P8 speeding.
4, each with a reason. P1 dwell, because over-the-road uses P3 for the same physical fact with the other polarity. P2 unauthorized stop, because this trace has no unknown-class stops to fire on. P4 after-hours, because no authorized-window schedule is modeled here. P9 perimeter, because the trace holds no geofence exit events. A blank is an unfired KPI, never a clean score.
25 events. Brief off-corridor excursions that did not clear the 300-second persistence floor, carrying 66 of the 784 observed deviation miles. They are reported as uncounted, with the count, and never as zero.
P8 speeding, 8 of 329 moves. The threshold is absolute while the published band is measured against posted limits, so the two are not the same measurement. The row stays in the ledger and carries no dollar.
Idle here is measured against engine hours from a real engine feed, so it is comparable to a telematics idle figure. On the two service books it is a proxy against the paid shift and is discounted on their own coverage panels.
Modeled evidence. One row from this run, not a client record.
Rule P6 off-route, sustained deviations only, persistence_s=300. A deviation that does not hold for 300 seconds is suppressed and counted as not determinable, never as zero. The mileage ledger behind this row is fleet-cleaning grade, not survey grade, and the read says so before the number is used.
Modeled evidence. One row from this run, not a client record.
Rule P7 utilization, idle_threshold_s=300. Idle is engine on and stationary within the stop radius, so it is not the complement of moving time and the two are not summed. The denominator on this book is engine hours, taken from a real engine feed.
Modeled evidence. One row from this run, not a client record.
Rule P3 detention, free_time_s=7200, rate=per_hour. This stop is also one of the 19 that ran past four hours. The comparison figure is computed the same way the engine computed the billed side, per detained stop with half-away rounding, so the shortfall is not a rounding artifact.
Modeled evidence. One row from this run, not a client record.
Rule P5 route completion, manifest reconcile against the dispatch plan. The stop is in the manifest and absent from the segment stream, so this is a reconciled absence rather than an estimate from a miss rate. A miss cites only the manifest identity, because there is no observed segment to point at. This book's tariff carries no charge for a stop that was not made, so the row carries no dollar.
Modeled evidence. One row from this run, not a client record.
Rule P8 speeding, threshold_mps=31.29. The threshold is absolute and the published band is measured against posted limits, so the two are not one measurement and must not be presented as one. The read is directional and the row carries no dollar. There is no driver score anywhere in this read.
This book holds 316 visits on contract and the crews made 301, leaving $1,191.39 charged against work that was never delivered, read across the 85.8% of the paid shift this trace accounts for.
P5 route completion · manifest reconcile against the designed route, priced at the book's own per-visit rate
Designed against driven · an account with no scheduled visit anywhere in the window, cross-checked against the visit history
P2 unauthorized stop · min_dwell_s=900. Five of the nine fell under the floor, so total off-book labour is $210.30 against $134.45 captured
P1 dwell · threshold_s=3600, roles.whitelist=[known_customer], priced by the engine at $84.00 per crew-hour
P7 utilization · idle_threshold_s=300. A proxy, not an engine fact: the denominator is the paid shift, so this is not comparable to a telematics idle percentage
Bar is measured. Tick is billed. Caret is planned. The rule under the bar is the span between what happened and what was charged, and hatching is quantity the read could not determine.
Stated before the rates above, not after them. A rate without a denominator is an assertion.
85.8% of the paid shift on this book is placed into a measured state. The remaining 14.2% is unaccounted, and on a book with no engine feed that span is both the idle proxy and the coverage gap at once. It is reported as unaccounted rather than resolved into one of the two.
4 of 9 KPIs. P1 dwell, P2 unauthorized stop, P5 route completion, P7 utilization.
5, each with a reason. P3 detention, because no customer-side free-time clock exists in grounds maintenance. P4 after-hours, because all modeled movement sits inside the shift, which is not evidence of a clean fleet. P6 off-route, because no planned corridor is modeled and there is nothing to deviate from. P8 speeding, because the trace holds no per-hop speed. P9 perimeter, because it holds no geofence exit events.
5 stops. Off-book stops that fell under the 15-minute dwell floor and did not fire. That is a threshold choice hiding real unbilled work, $75.85 of it, and it is stated as a choice rather than reported as a clean result.
Idle on this book is a proxy. There is no engine-on signal in the trace, so the denominator handed to P7 is the paid shift and not engine hours. It is a weaker fact than the trucking book's and is not comparable to a telematics idle percentage.
Modeled evidence. One row from this run, not a client record.
Rule P7 utilization, idle_threshold_s=300. This book has no engine-on signal, so what P7 receives is unaccounted paid shift time and the denominator is the shift. The row is reported at proxy grade and the coverage panel above discounts it accordingly.
Modeled evidence. One row from this run, not a client record.
Rule P5 route completion, manifest reconcile against the designed route. The stop is in the manifest and absent from the segment stream. On a flat-price book the contract charges for it either way, which is why the charge column here is contracted revenue for work not delivered and not a penalty.
Modeled evidence. One row from this run, not a client record.
Rule P1 dwell, threshold_s=3600, roles.whitelist=[known_customer]. The rate is $28.00 an hour across a crew of three, and the charge is the sum of the processor's own amounts rather than a figure this page multiplied out.
Modeled evidence. One row from this run, not a client record.
Rule P2 unauthorized stop, min_dwell_s=900, alertable=[unknown]. Same primitive as P1 with the opposite polarity and a separate class-role map, priced at the book's own $84.00 per crew-hour. Five further off-book stops sat under the floor and did not fire, so $75.85 of real unbilled work is outside the captured figure. That is a threshold choice, and it is on the coverage panel rather than in a footnote.
Modeled evidence. One row from this run, not a client record.
Rule An account carried on the book with no scheduled visit in the window. The read stops there. What is invoiced against those accounts is in the billing system, not in the position data, so this row names the accounts and refuses to price them. A page that priced them would be modeling the invoice rather than measuring it. There were also 107 stops served out of the planned sequence, which is a routing observation and not a charge.
Crews performed 47 extras on this book and 32 reached an invoice, leaving $3,735.00 of work delivered and never billed on $783.89 of labour already spent, read across the 84.8% of the paid shift this trace accounts for.
P5 route completion · manifest reconcile against the dispatch board
P2 unauthorized stop · min_dwell_s=900, alertable=[upsell_unbilled]. Capture came out at 68.1% on 47 extras against a modeled parameter of 63.0%
Effort split against the same engine counters · time on a property doing work that never reached an invoice
P1 dwell · threshold_s=5400, whitelist=[upsell_billed, upsell_unbilled]. The base visit cannot trip this row by construction
P7 utilization · idle_threshold_s=300. Measured and not an artifact: the board schedules a drawn number of jobs against a fixed 8.5-hour shift, so some days finish early and some overrun
Bar is measured. Tick is billed. Caret is planned. The rule under the bar is the span between what happened and what was charged, and hatching is quantity the read could not determine.
Stated before the rates above, not after them. A rate without a denominator is an assertion.
84.8% of the paid shift on this book is placed into a measured state. The remaining 15.2% is unaccounted, and with no engine feed here that span is both the idle proxy and the coverage gap. Idle minutes per crew-day ranged from 4 to 266, which is why an average would have been the wrong figure to publish.
4 of 9 KPIs. P1 dwell, P2 unauthorized stop, P5 route completion, P7 utilization.
5, each with a reason. P3 detention, because there is no customer-side free-time clock in this vertical. P4 after-hours, because movement is confined to the shift. P6 off-route, because no planned corridor is modeled. P8 speeding, because the trace holds no per-hop speed. P9 perimeter, because it holds no geofence exit events.
None on this sample, which is a measurement and not a clean bill. Every unbilled extra cleared the 15-minute dwell floor, so the floor hid nothing here. On a book with shorter extras it would, and the count would appear on this line.
A week is a thin sample for a capture rate. The observed 68.1% is one realization of a modeled 63.0% parameter, so the parameter and the finding are what to quote, never the last digit of the observed rate.
Idle on this book is a proxy against the paid shift, because a service van carries no engine feed here. It is not comparable to a telematics idle percentage.
Modeled evidence. One row from this run, not a client record.
Rule P2 unauthorized stop, min_dwell_s=900, alertable=[upsell_unbilled]. Labour is priced at $56.00 per crew-hour, $28.00 across a crew of two. The leak concentrates by service: storm cleanup $2,050.00, shrub pruning $720.00, mulch refresh $555.00, weed treatment $285.00, irrigation check $125.00. That is 37.4% of upsell revenue on this book.
Modeled evidence. One row from this run, not a client record.
Rule The cost side of the same 15 extras. It is separated from the revenue row deliberately: the revenue is what a buyer could recover, and the labour is what the seller already paid whether or not anyone recovers it. Summing the two would double count the same event.
Modeled evidence. One row from this run, not a client record.
Rule P1 dwell, threshold_s=5400, whitelist=[upsell_billed, upsell_unbilled]. The class-role map whitelists only the two upsell classes, so the denominator is every performed extra and nothing else, and the overage is priced at the same $56.00 per crew-hour. The base visit never trips this row and cannot.
Modeled evidence. One row from this run, not a client record.
Rule P5 route completion, manifest reconcile against the dispatch board. A job the crew could not reach before the shift ended is in the manifest and absent from the stream, so the miss is reconciled rather than estimated. What that costs depends on the contract, which is in the billing system and not in this data, so the row carries no dollar.
Priced against the published per-day tariff these 180 car holds owe $8,800.00. Priced at a linear per-hour rate they compute $11,909.33, an overstatement of $3,109.33, and the linear rate agrees with the tariff on none of the 91 cases that carry a charge. That is the one question of nine this record can answer.
P3 detention · free_time_s=172800, rate=per_day_step, exclude_weekends=true. Free time counted in whole days, a partial chargeable day billed as a full one
P3 detention · same population, same free time, rate=per_hour at each tier's nearest integer hourly expression of its daily rate
One scale, the linear total. The bar is the tariff-correct charge and the tick is what the hourly rate computes, so the span between them is the mispricing rather than a difference of opinion about the facts.
Stated before the rates above, not after them. A rate without a denominator is an assertion.
1 of 9 KPIs fired on this book. A placement and release record is a narrow instrument: it answers whether the charge is right and it answers nothing else, and the bar above is the honest picture of that. Eight KPIs did not fire and each carries a reason.
P3 detention, in both rate modes. Run twice over one population under two configs, which is what makes the divergence below a measurement rather than an argument.
8, each with a reason. P1 dwell, because a car hold is a dwell question and P3 is the dwell KPI with a price attached. P2 unauthorized stop, because every hold is at a known place. P4 after-hours, because a placed car does not move. P5 route completion and P6 off-route, because a car on a siding has no manifest and the shipper sees no planned corridor. P7 utilization, because a freight car has no engine. P8 speeding, because line-haul speed is the carrier's fact and not the shipper's. P9 perimeter, because a placement record holds no geofence exit events.
None. This book is not regenerated: it replays a 180-case reference corpus that was authored by an independent day-walk before the per-day step mode existed, so the figures are exact rather than sampled. 89 of the 180 holds carry no charge at all, which is a result and not a gap.
No published band exists for a demurrage rate, so nothing here is scored against one. The mechanism is documented in Norfolk Southern tariff 6004-D, Railinc RIC 6004 and Surface Transportation Board reporting. The per-day rate levels are trade press and are marked as the weaker source they are.
Modeled evidence. One row from this run, not a client record.
Rule P3 detention, rate=per_day_step, exclude_weekends=true. The error has three independent sources and only the first runs one way. Whole-day billing means a three-hour overage bills a full day. Free time is counted in whole days, so the boundary sits on the day grid and not on the second. Weekends do not accrue against free time, which makes an identical hold cost a different amount depending on the weekday it began. The third source makes the charge not a function of duration alone, and an hourly rate is a function of duration alone, so no price fixes it. That the linear rate both overstates and understates on one population is the visible signature: a scale error can only go one way.
Modeled evidence. One row from this run, not a client record.
Rule P3 detention, free_time_s=172800, rate=per_day_step. Half of the difference between the two columns is not a price at all: the linear rate fires on 91 holds where the step fires on 52, so it invents 39 charges the tariff does not carry. A row that reads zero here is a hold that cleared its free time, which is a measurement and not an absence of data.
Two visuals, one selection
The same week, the same book, drawn twice. Select a zone on the map and the ledger beside it filters to that zone. Select a zone or a rule in the ledger and the map redraws to match. Both are views of one selection, and either one clears it.
Corridor read
OTR trucking · Newark–Elizabeth terminal area
Modeled sample data
Circle area is the dollars that zone carries. It is drawn on our own basemap, from our own tile archive.
This map needs JavaScript. The zone figures beside it do not, and they are the same numbers.
© OpenStreetMap contributors · rendered from our own tile archive, no third-party map service
Bar length is the zone total. Within it, off corridor, idle and detention in that order.
Kearny–Meadowlands
$170.71
Port Newark–Elizabeth
$158.89
Linden–Carteret
$122.06
Jersey City–Bayonne
$117.68
Secaucus–North Bergen
$72.98
Newark Airport south
$57.00
Selected $699.32 all six zones, of the book's $2,843.34
Off corridor is P6, idle is P7, detention is P3, in that order along every bar. P5 route completion carries no dollar on this book, so the two stops dispatched and not made are counted on their zones and priced nowhere.
61 of the 325 stops in this window fall inside this terminal area and carry $699.32 of the book's $2,843.34. Zone figures sum to that subtotal exactly. They are a part of the read above, never a restatement of it, and like every figure on this page they are modeled.
How to read this
The coverage panel sits above the exception list on every book, because a rate whose denominator is unstated is an assertion. On the trucking book the coverage figure and the utilization figure are the same number, and that is not a coincidence: an hour the trace cannot place is an hour we do not count as worked.
Rows marked not determinable or not priced stay in the ledger with their counts. A KPI that did not fire is an unfired KPI and never a clean score, and a threshold that hid work says how much work it hid.
There is no live vehicle position on this screen, by design. Live position answers where a truck is now. This page answers what already happened and whether it was charged correctly, so a map appears only where the question is genuinely spatial: inside an evidence panel, and in the corridor read above, which draws a closed week rather than a moving fleet. Two of the evidence panels say plainly that they do not need one.
Money is exact because the engine holds it in integer cents and every dollar is the sum of the processor's own charges. Physical quantities are not carried past what a ping cadence supports, which is why there is no score, no index, and no figure invented to fill a column.
The four books share no operating model. An industry here is a configuration file, not a code path, so the same processors run over all four and a threshold change moves every book at once. Ratios cross the books. Absolute figures do not, and they are never summed across them.
Published figures are attributed and never rehosted. Everything else is modeled output from our own generators, run against those published bands, and it is labelled inside the ledger chrome rather than under it.
Send us a book you are looking at. We will tell you what the position data can and cannot settle before anyone commits to anything.
Talk about a deal