RAILSPIKE-RIG

Know the fleet.
Back the decision.

Dispatch, shop, parts, crew, hours, border and cost in one carrier record. Every unit promised once. Every driver cleared before the call. Every repair you’re owed, recovered.

Long-haul, regional, expedite, cross-border and specialised bulk. Canada and the US. Pricing is being finalised; talk to us about early access.

A Tuesday, with Railspike-Rig
Governed workflow
01
A load comes in

The board shows which units are free for the whole window — not the ones in the shop or out on rent.

02
Dispatch picks a driver

Tickets and hours are checked for the day the run starts, before anyone is called — and for a run that crosses the line, dispatch asks for one border answer that binds the whole trip.

03
The run gets done

Fuel, parts and the settlement land against the unit that did it — and a failed part becomes a warranty claim, not a write-off.

One record, from the dispatch desk to the shop floor to the office.
What a normal week costs you

The problems are ordinary. That is what makes them expensive.

None of these are rare. They happen because dispatch, the shop, safety and the office each keep their own version of the fleet, and the versions disagree in the yard.

01

The trailer you promised was already in the shop.

Rig: a load, a shop visit, a rental and downtime are all claims on the same unit, on one board. Ask what is free for Thursday and you get one answer, not three.

02

Your best driver ran out of hours two hundred kilometres from home.

Rig: hours and tickets are checked for the hour the run starts — before dispatch picks up the phone, not at the roadside — and a run that crosses the line has one border answer for the whole trip, asked at the desk.

03

You ate a five-figure repair that was under warranty.

Rig: every service is recorded against the unit at a reading, the notice deadline is on the calendar the day the failure is logged, and the claim carries its own file.

04

The part was “in stock” — and promised to another job.

Rig: on hand, promised and available are three numbers. A quantity reserved for one job cannot be reserved for another, and what is on order is never counted as stock.

One record, every desk

Dispatch, shop, safety and the office, working from the same fleet.

Each desk keeps doing its job in its own screens. What changes is that they are looking at one set of facts about one set of units.

DS

Dispatch a unit once

Run the board. See what is free for every hour of a window. Claim a unit for a load, a shop visit or a rental, put a cleared driver on it, and release it with a reason that stays on the record.

The dispatch desk →
SH

Keep the shop ahead of the road

Set service cadences in your own words. See what is due, what is overdue, and which units nobody has read the gauge on. Book the bay against the same board dispatch uses, so a truck cannot be in two places.

The shop and stores →
CL

Clear a driver before you call

File tickets, write the rules once, and ask whether somebody is eligible for the day the work runs. Judge hours under the rules where the work is, and cross the border with one answer.

Crew and compliance →
PT

Promise a part to one job

Stock by yard, reserved against the work that needs it, issued once when it is fitted. Order without pretending the order is on the shelf, and reorder without buying what is already coming.

WR

Recover what the warranty owes

Raise a claim against the actual repair, track the notice deadline, and keep what you asked for, what was agreed and what actually arrived as separate figures — so recovery means received.

CU

Know what a unit costs and a rental earns

Fuel, tires, tolls and repairs land against the unit that incurred them. Cost per kilometre says how much of the fuel it rests on. A rental’s margin comes from what it settled at.

Built for the way you run

Long-haul, regional, expedite, cross-border, bulk.

A commitment is a claim on a unit over a window, and that holds for a three-thousand-kilometre run and a two-hour shuttle. So one product covers lanes that usually need three.

Long-haul and OTR

Multi-day cycles, hours judged under each jurisdiction the run touches, and a border check that binds the whole trip rather than the departure.

Regional and dedicated

Repeat lanes, home-time patterns, and the cycle position that decides whether somebody can take tomorrow’s run. Shop work planned against the board, not around it.

Expedite and time-critical

Free means free for every hour of the window, not free on average. Eligibility is checked for the hour the work starts. That is the answer you need before you promise a truck.

Cross-border

Your authority in each jurisdiction, the combinations you are qualified to run there, whether a driver’s papers are accepted across the line, and anything that expires mid-trip — as one answer.

Bulk and specialised

Where the trailer is the constraint and a unit turns several times a day. Pneumatic, tank, deck, B-train — you name the configuration, and it is checked against where you are qualified to run it.

Equipment you rent out

Surplus trailers on rent to a third party are claims on your units like any other, so they cannot be promised twice. What each earned is a recorded settlement.

Who sees what

Driver files are not the dispatch floor’s business.

Access is per person, not per login. A yard hand can see that 412 is spoken for from six until two without seeing who it is for or what it is paying. The shop sees the shop. Qualification files, duty records and settlements are their own grants, separate from the board.

Separate three things.

What somebody may touch. What the system is for. What they actually did. Most operations software conflates the three, which is how a dispatch system ends up with every driver’s file open to everyone who can log in — and why carriers buy a second system just to lock the first one down.

How governance works →
Why you can trust the answer

It tells you what it knows, and what it does not.

An operations product earns trust by the answers it declines to invent. Four you will notice.

It is not an ELD, and it says so.

Your certified hours system stays the authority. Rig is the cross-check: when the two disagree, the stricter answer stands and the difference is surfaced — usually a data problem worth finding before an inspection finds it.

Unknown never clears a driver.

No duty record, no reviewed rule package, no recognised medical — each is a named open question, not a pass. And a break that restarted the cycle under one country’s rules is checked again under the next.

There is no compliance score.

A border check returns the conditions by name and the worst one governs. A single percentage is what gets dispatched against, and it cannot say which condition failed.

Missing is unknown, not zero.

Fuel economy is not published from a window where nobody wrote the odometer down. Every cost figure says how much of the record it rests on, or says why it cannot be given.

Start Monday with the list you already have.

Paste the yard list as it is. Rows that cannot be placed come back as questions instead of rejecting the file, and nothing is guessed onto the register. A setup page then says which parts of the product work yet, what would close each gap, and who can close it. Your team is included — the point is that everyone works from the same record.