They Said You Can't Track Equipment. Thanks for Holding Our Coffee.

Back in April we published "They Say Strivie Is for Mid Carriers. We Say: Hold Our Coffee." That coffee has been sitting on the counter. We'd like it back.

Because the thing people kept telling us wasn't about fleet size or pricing. It was this:

"Nobody actually tracks equipment. Every software says it does. Open it up and it's a spreadsheet."

They were right about the industry. Thanks for holding our coffee.

The Argument Nobody Wins

Here's the scene. A driver quits in November. The truck comes back with a cracked bunk window and a scrape down the passenger side. When did the scrape happen? March? July? Nobody photographed the truck at handover. The only evidence is a dispatcher who "pretty sure remembers" it was clean.

Now somebody has to decide: charge the driver or eat the cost. Charge him and he fights it — there's no proof. Eat it and nothing changes, because next time it'll be the same missing photos and the same argument.

This isn't a technology problem. It's a record problem. Every system that promised to track equipment gave carriers an upload button and a spreadsheet and called it solved. So the honest ones gave up tracking, and the dishonest ones never started.

A Map You Tap

Every truck and trailer in Strivie has a damage map — a drawing of the unit you tap to mark. Two views, side and top, because a scratch on the passenger panel and a dent on the roof are different problems that look the same from one angle. Body panels, glass, tires, bumpers, frame rails. Alongside the drawing are the mechanical systems that don't belong on a silhouette: engine, transmission, brakes, suspension, exhaust. Every mark carries a severity, a photo, and a timestamp.

Here is the one decision that makes all of it work: damage is recorded against the unit, not the driver.

Marks don't get wiped when a driver leaves and a new one climbs in. They accumulate on the truck through every reassignment, every maintenance visit, every inspection. A scratch marked in March by one driver is still there in November when the next driver returns the truck — and the record knows when it appeared, who was assigned, and what it looked like.

That cracked bunk window? It's in the map with a date, a photo, and a name. The argument is over before it starts.

From Handover to Settlement

The day a driver gets the keys, the truck's condition is documented — every existing mark photographed and mapped. That's the baseline. Everything that appears after this belongs to their tenure.

The day the truck comes back, new damage gets marked on the same map. The system knows the difference between what was already there and what wasn't. At offboarding, return photos sit side by side with the hire photos — not in separate folders, not in someone's email. Same screen, same unit, side by side. New damage becomes a charge that posts into the driver's final settlement on its own.

That charge is gated to terminated drivers only. Nobody can quietly bill a working driver for a dent while they're still hauling freight. And the gear you issue — chains, binders, straps — gets tracked the same way. Items handed out on a fuel-card money code land as pending until confirmed against a receipt. Unreturned items are counted by the offboarding completion gate, so a driver's file won't close while the company is still owed a set of chains.

Records That Don't Bend

A record whose job is to survive a dispute between a carrier and a former driver should be the hardest thing in the building to rewrite. So we made it exactly that.

The damage map has no general API door. Most records in Strivie can be reached through a generic endpoint with the right permission. Damage annotations cannot. The only path in or out is a single audited function. There is no back door, no admin override, no "well, the API technically allows it." One door. It's watched.

That's part of a bigger pattern. More than twenty record types are append-only — the API refuses to edit or delete them outright. PSP reports. Random-testing outcomes under §382.401. Employment verifications under §391.23. Medical-certificate history. Onboarding and offboarding records. These aren't guarded by permission levels. They're guarded by code that has no path for the request.

And the audit log doesn't become the leak. It records that a sensitive field changed, never what it changed to. You can prove somebody edited a driver's banking on Tuesday without the log holding the account number. That sits on top of the masking and server-side gating we built in July.

From the Parking Lot, Not the Desk

Equipment inspections happen next to the truck. Not at a desk three hours later, trying to remember which side the scratch was on.

Strivie CRM is a phone app for recruiters and onboarders — the two roles that run the front of the driver lifecycle. The damage map is on the phone. Tap where the scratch is, attach the photo, done. Standing next to the unit, ninety seconds, and the record is permanent.

Recruiters get their lead queue, the full call and text history, notes, and document photos from the camera. They can order an MVR or a PSP — the PSP behind a consent confirmation, because it's a consumer report and the law is specific. Calls go through the office phone system: the server dials, and the driver's number never touches the recruiter's phone.

Onboarders get the seventeen-step checklist live — what's done, what's blocking, and the ability to mark a step complete, waive one with a note, or reset. A driver cannot be activated while a required step is unsatisfied — enforced on the server, not by a greyed-out button someone could get around. They can send the application and contract for signature. And push notifications deep-link straight into a lead's file when a call or text comes in.

The app is built and heading to both the App Store and Google Play. If you're already a customer, you sign in with the account you have.

What We Won't Say

A damage map is only as honest as the person holding the phone. If nobody photographs the truck at handover, the system has nothing to compare against in November. What Strivie does is make the honest version take ninety seconds and make the record permanent once it exists. When "do it right" is faster than "skip it," the incentive structure changes on its own.

A few things aren't on the phone yet. Drug tests and DOT physicals still go through the office app — those flows need clinic search and site codes, and we'd rather ship them right than thin.

And under all of this — the damage map, the equipment tracker, the append-only records, the phone app — is the thing that makes the rest work: in Strivie, a driver is one continuous record from the first recruiter call to the day they hand the keys back. No retyping, no handoffs between systems, no history dying in a migration. The same file, getting fuller. The equipment is tracked the same way — one unit, one history, every driver who ever sat in it.

That's what we did with the coffee. There's a short walkthrough if you'd rather watch than read.