Five rules for software used from a truck cab

I assume our users have about ninety seconds and an unreliable connection. A driver photographing a bill of lading at a receiver's dock should finish in four taps, see each page stored on the phone, and know which pages are still waiting to upload. We do not ask drivers to interact with the app while the truck is moving; anything that needs attention waits for a stop or goes to the dispatcher. My researchers test new screens in poor light, with gloves, with a weak signal and in Spanish as well as English. A feature passes when a driver can complete it without calling the office. I also watch dispatchers, who may be the owner's spouse working from a kitchen table, because a screen that saves the driver a minute can cost the dispatcher five if it hides the exception they must resolve.

Small carriers live on the interval between delivering a load and being paid for it. Brokers often pay on terms of thirty days or longer, while fuel, insurance and truck payments do not wait. An advance against an approved invoice can be the right choice, and it always has a cost. I insist that the cost appears in dollars on the button, beside the date the money will arrive, and that the free option on the broker's own terms is never harder to choose. Our account home shows each carrier the total paid in advance fees this year. I work with our finance, risk and partner-bank colleagues on eligibility and disclosures, and with support on the complaints we receive. The product's job is to make a timing choice visible, not to make it for the carrier.

Federal hours-of-service rules limit driving and on-duty time, and drivers record that time on electronic logging devices. Ostervane is not the legal record and does not decide compliance. Where a fleet connects its logging device, we read the driver's remaining hours and compare them with the appointment times on a load offer. If the hours cannot reach the appointment, the offer shows the shortfall and how old the reading is, and a dispatcher who accepts must record why. I learnt from logging products that drivers distrust any number they cannot trace, so every figure on these screens names its source device and the time it was received. When the data is stale or missing, the screen says so rather than presenting a guess as a fact.

A driver's phone knows where the driver sleeps, eats and visits family. Brokers and shippers have legitimate reasons to know where a load is between pickup and delivery, and our product supports that. Outside that window, the location belongs to the driver. Sharing starts when the driver arrives for pickup, stops thirty minutes after delivery is confirmed, and is shown on the driver's screen the entire time, with the same map the broker sees. Off-duty and personal time are never shared. A driver who wants a reload can send a city-level availability signal. I review every new data request from partners against these limits with our privacy counsel, and I report exceptions and requests we declined to our audit and risk committee twice a year.

Our customers range from an owner-operator with one truck to a family business with twenty-five. In 2020 I moved our subscription from seats to trucks, so that adding a dispatcher or a bookkeeper costs nothing and the bill grows only when the fleet does. A truck costs US$34 a month and a single-truck account US$22, with no setup fee and no annual contract. Advance fees are separate and optional, and we publish them. I resist bundling features that most small carriers will not use, because each bundle raises the price for the smallest customers to fund the needs of the largest. Price changes go to carriers sixty days ahead with a calculation of their own new bill, and I review cancellations by fleet size after every change.