OdosMark Request Access
Automated Onboarding

Winter roads. Treated. Documented. Visible to everyone.

OdosMark keeps every treatment run efficient and accounted for — live speed guidance keeps salt on the road instead of in the ditch, every mile is documented as it happens, and the public sees progress during the storm, not after.

Built for the regions where major winter weather is rare — and dedicated tracking has never been cost-justifiable. Until now.

The full loop · five steps · one record
STEP 01
Jurisdiction Code
Five digits → routable map
01081
STEP 02
Dispatch
Assign routes from the map
STEP 03
Treat
Speed-guided; confirmed from the cab
Live
STEP 04
Hash-Chain Log
Tamper-evident record
7af3…c91e
STEP 05
Public Map
Residents see what's done
LIVE
01Jurisdiction Code
02Dispatch
03Treat
04Hash-Chain Log
05Public Map
BUILT FOR PUBLIC ROAD AGENCIES SHA-256 APPEND-ONLY LOG OPEN STANDARDS DATA INGEST MATERIAL & LABOR CAPTURED PER EVENT
Section 01 · The Problem

Every winter, your crew treats the roads under pressure.

Hours later, someone asks about a road your team treated at 3 a.m. The commission wants records. The auditor wants numbers. And the salt budget quietly pays for every mile spread too heavy.

Can you show what was done — and what material was used?

PAIN 01
No verifiable record

Spreadsheets, radio logs, and paper ride-alongs aren't documentation. When questions arise — from officials, residents, or auditors — there is nothing to show.

PAIN 02
No real-time visibility

Who is treating what, right now? Without a live operational picture, every status update is a phone call — and every phone call is a gap in the record.

PAIN 03
Wasted dollars on inefficient treatment

On manually controlled spreaders, application rate rises and falls with truck speed — and the error is money. Published research puts recoverable salt over-application at roughly 20–37% when speed-induced error is corrected.

Sources: Clear Roads / WisDOT Project 06-21 (spreader calibration accuracy) · MassDOT / UMass Amherst spreader-controller study (USDOT ROSAP)

Section 02 · Speed Control

More on the road.
Less in the ditch.

Spreader output is calibrated for a speed. Drive faster and salt bounces off the roadway; the application rate drifts off target. OdosMark gives the operator live, glanceable speed guidance in the cab — a calibrated band, a simple in-band indicator, and a clean stopped state at lights — so the material goes where the budget intended.

Every run records time-in-band, material, and labor per segment.

SALT LOST TO BOUNCE AND SCATTER · BY TRUCK SPEED
9%
at 25 mph
32%
at 35 mph
45%
at 45 mph

Treated salt, conveyor discharge; loss varies by material and discharge method. Source: Michigan DOT Salt Bounce & Scatter Study (2012).

speed control · 79s ▶ VIDEO
Automated Onboarding Section 03 · Onboarding

From a five-digit jurisdiction code to a full, routable road network — no GIS staff required.

You enter your federal jurisdiction code (FIPS). OdosMark does everything else. No GIS department. No shapefiles. No IT ticket. Just a five-digit code.

DELIVERED AT ONBOARDING
Your road network, loaded

Every public road in your jurisdiction, on a live, routable map — one validated onboarding brought in 13,259 road segments.

DELIVERED AT ONBOARDING
Federal classifications assigned

Primary, secondary, and local — every segment carries its federal road classification from day one. No GIS staff required.

DELIVERED AT ONBOARDING
Every bridge flagged

Bridges in your jurisdiction are identified and marked before your first dispatch — 442 in that same onboarding. Cold decks freeze first.

We stand your jurisdiction up with you — network loaded, verified, and ready before your first winter event.

No GIS department needed No shapefiles to upload No IT ticket
Section 04 · Dispatch

Your dispatcher sees the network. Your crew sees their route.

Map-driven route building. Click roads. Assign. The driver's device lights up with the segments, the priority, and the bridges on the way.

01
Route selection on the map

Select road segments straight on the live map. No polygon math. No drawing tools required.

02
Priority & classification

Primary and secondary segments surface first. Bridges are called out visually — cold decks freeze first.

03
Dispatch ticket

A single tap sends routing, priority, and segment list to the assigned driver's device.

dispatch · event #2026-014 ● LIVE
JURISDICTION · 01081 ZOOM 11 ⚑ BRIDGE ⚑ BRIDGE
ROUTE
14 segments
BRIDGES
3 flagged
ASSIGN TO
Truck 04 · Driver ID
7:42 ●●●●● LTE
ROUTE · R-2026-014-04
North Loop
Event #2026-014 · 03:42 EST
CURRENT ⚑ BRIDGE
CR-142 · Main St.
PRIMARY · 03:22
River Bridge
BRIDGE · Priority
CR-88 · Ridge Road
SECONDARY
Mill Road
LOCAL
Section 05 · Field confirmation

When the salt hits the road, OdosMark knows.

The driver's device is built for a glove at 3 a.m. One tap confirms a segment. Bridges are called out before the truck gets to them. Every action is a record.

More trucks treating. Less setup.

The driver app runs on any phone or tablet with a browser. Open a link, log in, add to home screen — no app store, no device management, no IT project, and it is always the latest version. A new hire, a seasonal operator, or a contractor crew is running the same day.

WHAT GETS RECORDED · PER EVENT
TIMESTAMP
2026-02-18T03:42:17Z
ROUTE GEOMETRY
LINESTRING(…)
USER ID
driver@agency
EVENT TYPE
TREAT_BRINE
BRIDGE AUTO-TAG
bridge:nbi#10482 · flagged on dispatch

Every segment. Every pass. Every timestamp.

Section 06 · The Record

A record built not to be quietly rewritten.

Every treatment event is added to an append-only SHA-256 hash chain — a sequence of records where each entry locks in the one before it. Change one byte anywhere in the log, and every link after it breaks. The math is the proof. And the same record that answers the auditor shows you where the salt went — material and labor, storm over storm.

treatment-log.chain · 2026-02-18
SHA-256 · append-only
BLOCK · 02174
03:22:04Z
CR-142 Main St. · TREAT_BRINE
prev: 7af3…c91e
hash: b091…41a7
BLOCK · 02175
03:42:17Z
River Bridge · BRIDGE
prev: b091…41a7
hash: e4c2…8db0
BLOCK · 02176
04:01:52Z
CR-88 Ridge Road · TREAT_BRINE
prev: e4c2…8db0
hash: 9a17…fe33
BLOCK · 02177 · HEAD
04:18:03Z
Mill Road · TREAT_BRINE
prev: 9a17…fe33
hash: 1c80…22b5
chain integrity VERIFIED · 02,177 / 02,177
Tamper-evident

Change a timestamp, a route, or a user ID anywhere in the log — every link downstream of the edit is mathematically broken. There is no silent edit.

Time-ordered

The sequence is provable. Not "the computer says so" — the hashes say so, in the order they were written.

One-click audit report

Export the full event log as a PDF — time-ordered, hash-linked, with material and labor totals per event. Ready for your leadership, your commission, or your county auditor.

SAMPLE · REDACTED
Request a sample audit PDF
See what an event log looks like when it leaves OdosMark.
Section 07 · Public map

Show the public what you've done.

As treatment events are confirmed, a public-facing map updates in near-real-time. Residents pull it up on their phone. Your leadership gets a live, public accountability tool.

1 URL
One public link answers residents, officials, and your department — during the event, not after it.
< 30s
From driver confirmation to visible update on the public map.

When residents wonder if their road was treated, give them an answer.

roads.jurisdiction.gov ● UPDATED 04:18
LIVE TREATMENT MAP TREATED · LAST 12H NOT YET TREATED
TREATED
178 mi
BRIDGES
18 / 63
CREWS OUT
7
Event #2026-014
Section 08 · Who this is for

Built for the agencies the record falls on.

Winter events don't check your headcount before they arrive. Whether you run four trucks or forty, the questions start the moment the first flake lands — and the auditor, the commission, and the resident ask the same question of every agency, regardless of size.

OdosMark gives every public road agency the same verifiable record, in the same format, from the same five-digit code.

Road & bridge engineers
The ones who get the call at 2 a.m.
Public works directors
Accountable to residents and commissions alike.
DOT district offices
Coordinating a winter event across jurisdictions.
Traffic management centers
Seeing the regional picture in real time.
Section 09 · Access

One jurisdiction. One code. One clean record.

OdosMark is rolling out to select public road agencies ahead of the 2026–2027 winter season. Tell us where you are and what you run today. We'll come back with a short conversation and a stand-up plan.

Treated roads, remembered.