Prototype, sample imagery is illustrative
by IntelliMass

BackRoadIntel for First Nations · Territory Intelligence Platform

Their trucks. Your road. Your numbers.

A working brief: how a Nation holds its own record of a road through an industrial project.

Who holds the record of the land after the project? Right now, the proponent does. This page is the practical version of changing that — what gets collected, when, by whom, what the comparison can settle at the end, and what it cannot. It is written for the person who would have to run it.

A pilot is complete with a British Columbia First Nation, with further work under way alongside First Nations and regional districts across the province.

A single-lane timber-deck bridge carrying a gravel resource road over a creek, steel culvert and riprap at the bank below

In this brief

The problem in one paragraph

When the only record is someone else's.

The proponent builds the access road. Their consultant writes the condition report. Their photographs are the evidence, taken on the days they chose and framed the way they framed them. Two years on, the culvert at the crossing is crushed, the staging ground was never pulled back, and the only thing anybody can point at is a file the other side assembled.

None of that requires bad faith. It is simply what happens when one party documents and the other remembers. A dated record held by the Nation does not make the proponent wrong; it makes the question answerable. The rest of this brief is how you get one.

Do not ask them to pay for it. A record the Nation commissions is the Nation's to produce, or not. A record the proponent commissions is theirs. That independence is the whole value of it at the referrals table, in a negotiation, and on the day a contractor says the road was fine when they left.

Step one

The baseline is the only part you cannot collect later.

Everything else in this brief can be started mid-project and still be worth having. The condition of the road before the first loaded truck cannot. If the work has already started, the honest position is that your baseline is "as of today" — which is still far better than nothing, and worth starting this week.

Drive the route before work begins

The whole length, in one pass, in a vehicle with the kit in it. On a 19 km access road that is about twenty-five minutes. The road is divided into 200 m segments automatically — roughly 94 of them on that length — and every segment gets a condition reading, a position and a frame of video.

Do it more than once

A single pass is a true record of that road on that day and it is evidence the moment it exists. What repeated passes buy is the ability to tell a real change from ordinary scatter. Roughness is sensed through a moving vehicle, so no two passes land identically even on a road that did not move. The smallest change a comparison can resolve falls with the square root of the number of passes — which is why a dozen passes before the trucks is worth far more than one.

Name the things the agreement commits someone to

Culverts, crossings, bridges, cattle guards, gates, signs, the right-of-way itself, the staging grounds and the reclamation sites. Each becomes a watch — a standing question attached to a place, answered again on every drive that passes it, rather than a note in somebody's inbox.

Practically: if a project is six months out, you have time to build a baseline out of trips that were happening anyway. If it starts next month, drive the route deliberately a handful of times. If it started last year, start now and say plainly what your record does and does not cover.

Step two

While the work is going on.

Nobody is hired to go and look. The kit rides in vehicles your people already drive — Guardians, public works, the emergency coordinator, anyone with a reason to be on that road — and the record accrues out of trips that were happening regardless. Capture is driver-started: one action at the beginning of a drive.

01The running surface

The hitch-mounted sensor scores the ride continuously. Every pass lands on the same road axis, so the same 200 m of road lines up across dates and you can watch it move.

Scout sensor
02The roadside

Dated, geolocated video of the whole way through — ditches, cut slopes, culvert inlets and outlets, fence lines, approaches, cleared right-of-way, staging areas, and what was dumped or left behind. On a project, beside the road is where most of the obligations live.

Dashcam device
03What the driver saw

A spoken field report, tapped on the wheel, stamped with where it was said. "They've widened the pull-out past the creek again." Transcribed and catalogued by what it describes. The thing a photograph cannot tell you.

Voice field reports

One drive returns all three. There is no separate inspection programme to staff, and no month in which somebody forgot to do it.

Step three

At closeout, the comparison does the arguing.

When the contractor says the work is done, the record already holds the answer. The comparison runs segment by segment along the road's own line: the window before the trucks against the window after the remediation, the same 200 m against itself.

What comes out is not an opinion about whether the road looks alright. It is a count. How many segments came back to where they started, how many did not, where those sit, and whether they sit together — because a contiguous run of worse segments is what a real local problem looks like, and scattered ones are usually noise. Alongside it sits the thing a community actually feels: how long the drive takes now compared with before.

The headline

Minutes, not levels

A roughness level is an internal unit. "A twenty-three minute drive became forty-two, and the remediation gave back all but five minutes" needs no explanation at a table.

The finding

Where it did not come back

The segments still reading worse than before the trucks, and whether they form one run. That is the ask: a location, a date range and a direction.

The guard rail

What the comparison could resolve

Every comparison carries the smallest change it could have detected. A movement below that figure is not a finding, however much it looks like one.

Scope

What the record settles, and what it does not.

Being clear about this before a project starts is worth more than any feature. A record that is oversold once is not trusted again.

It settles what the road was like, and when. A dated, located condition reading and a frame of video for any point on the route, on any day it was driven. Nobody has to rely on recollection.

It settles the direction and size of a change. The same stretch against itself across windows, with the resolution of the comparison stated alongside it.

It settles where to look. The stretches that moved most, so an engineer, a crew or a negotiator spends their time in the right kilometre.

It does not establish cause. The record shows a road got worse between two dates. It does not prove which vehicle, which operator or which rainfall did it. What it removes is the argument about whether anything changed at all.
It does not price the repair. Scoping and costing a rebuild is an engineer's work. This is the evidence they start from, and the reason you knew to call them.
It is not real-time. A record is published after the drive. It is a dated record of a road on a day, captured on your interval — not a live feed and not an alerting system.
The score is comparative, not calibrated. The same road against itself, drive to drive. It is not a profilograph and not a pavement condition index.
Industrial remediation timeline

What it did, and what came back.

A hauling season on an access road under an agreement, measured before, during and after. Every reading lands on the same road axis, so the windows stack and the same stretch lines up down the page. The road was fine in March, the loaded trucks doubled its roughness by May, and the remediation took most of that back out — except in one place. None of it was a measurement campaign, and none of it was commissioned by the proponent: it is drives the Nation was making anyway, on a road the Nation was already using.

The road on the map

The same segments, where they actually are. The haul reddens the whole line; the remediation takes it back to green — except at the creek crossing, where it does not. Each chip is the average speed over that 8 km stretch and the minutes it adds against before the trucks — the 2 km detail runs under each strip below.

before the trucks48 km/h49 km/h59 km/h
after the haul26 km/h+8.7 min26 km/h+8.7 min36 km/h+1.9 min
after remediation40 km/h+2.1 min39 km/h+2.5 min51 km/h+0.5 min
Access road under agreement 18.8 km · 94 segments · 200 m each
05 km11 km · creek15 km18.8 km
pre-industrial traffic01 – 14 Mar · 14 passes · roughness p90 5 · worst 5 · 0 % at 7+
54km/h—53km/h—45km/h—43km/h—60km/h—49km/h—43km/h—47km/h—58km/h—61km/h—
50 km/h · 23 min end to end
Hauling begins · 15 March
under haul17 – 29 Mar · 12 passes · roughness p90 9 · worst 11 · 37 % at 7+
38km/h+1.0min35km/h+1.2min31km/h+1.2min29km/h+1.4min47km/h+0.5min32km/h+1.3min30km/h+1.2min32km/h+1.2min45km/h+0.6min52km/h+0.1min
35 km/h · 32 min · +10 min · 30 % slower
haul finished26 Apr – 09 May · 13 passes · roughness p90 10 · worst 11 · 56 % at 7+
29km/h+1.9min27km/h+2.1min24km/h+2.2min23km/h+2.4min35km/h+1.4min24km/h+2.5min23km/h+2.4min25km/h+2.3min35km/h+1.4min39km/h+0.5min
27 km/h · 42 min · +19 min · 46 % slower
Remediation · 12 May
after remediation18 – 31 May · 15 passes · roughness p90 7 · worst 9 · 12 % at 7+
44km/h+0.5min44km/h+0.4min37km/h+0.6min36km/h+0.6min52km/h+0.3min35km/h+1.0min35km/h+0.6min39km/h+0.6min50km/h+0.4min53km/h+0.1min
41 km/h · 28 min · +5 min · 18 % slower
Change · before the trucks → after remediation0 improved · 87 about the same · 7 worsened
-10km/h+0.5min-9km/h+0.4min-8km/h+0.6min-7km/h+0.6min-8km/h+0.3min-14km/h+1.0min-8km/h+0.6min-8km/h+0.6min-8km/h+0.4min-8km/h+0.1min
50 → 41 km/h · +5 min end to end · 18 % slower
Roughness · level 1 (smooth) → 11 (severe) has video Changebetter  ·  about the same  ·  worse Speed · km/h per 2 km block, over the minutes it adds (on the change row, km/h lost)
Hover or click a 200 m segment — on a map or on any strip — to compare that same stretch across all three windows.

Basemap © OpenStreetMap contributors. The road line and its condition readings are constructed for this example; in the platform these are live maps that pan and zoom together.

Read across the windows: the road was in good shape before the trucks, roughness p90 5. Under haul it reached 9; by the time the trucks stopped it was 10 — double where it began. The remediation brought almost all of it back — except the creek crossing: one continuous 1.2 km run from km 10.6 to 11.8, and the only stretch anywhere on the road still reading worse than it did in March. That is the tell for a problem that is not a surface problem: water, or what is under the road. In minutes — the lane under each strip — a 23-minute drive became 42 under the worst of it, and still runs 28 after the repair: five minutes added to every trip anybody makes, each way. The rest was restoration the contractor owed; that one is a drainage repair, and now you can show why.

Illustrative — the shape of a real comparison, with constructed readings. The score is comparative: the same road against itself, window to window, so a stretch that degrades is visible. It is not calibrated, not a profilograph, and not a pavement condition index; an engineer's measurement is still an engineer's measurement.

What it takes

What running this actually costs you.

Not money — effort. The money question is at the bottom of the page and the answer is "ask us". This is the part people underestimate in both directions.

1A vehicle, not a programme

The kit goes in a truck that was already driving the route. No crew, no survey window, no scheduling against anybody's availability.

2One action per drive

The driver starts capture at the beginning of the trip. Field reports are optional and take a tap and a sentence. There is no form.

3Somebody who owns it

This is the real cost. One person who knows which routes matter, which assets are under agreement, and who looks at the record when a watch fires. A few hours a month, not a role.

The failure mode is not technical. It is a kit that lives in a vehicle nobody drives on the route that matters, or a record nobody opens until the week of the dispute.

Whose data it is

The community holds the record.

The record of a project on the territory is the Nation's. It is collected by the Nation's own people, on the Nation's own drives, and held under the Nation's own control — OCAP®-aligned in how it is handled: ownership, control, access and possession stay with the community. OCAP® is a registered trademark of the First Nations Information Governance Centre, and there is no such thing as OCAP certification; we do not claim one.

Nothing is shared by default

No proponent, ministry or neighbouring authority sees a project record because they asked us. They see it because the Nation decided they should.

Sovereign hosting, if you want it

The platform can run on infrastructure the Nation controls. That is a real deployment we sell, not a compliance badge — and it is the difference between policy and architecture.

The Nation can license its record

A regional district, a wildfire agency or a utility may want what the Nation has already collected on these roads. The Nation decides whether that happens, on what terms, and gets paid for it.

What it costs

Pays for itself on the first claim.

Priced to the size of the territory, or per project. A line item Council can approve from the Nation's own revenue — with no proponent in the room and no grant cycle in the way. One restoration obligation met because there was a dated baseline to measure it against is usually the whole year.

Funding help is available for this kind of work and we prepare most of the materials with your team — see the funding section on the First Nations page.

Start with the route you would argue about.

The project will end. The road will still be there, and so will the question of what state it was left in. The only thing that decides that argument is whether somebody was holding a dated record of the land — and whether that somebody was you. Tell us which route you would document first.

Sample analysis · constructed data

Industrial remediation timeline — sample record

Three months on 18.8 km of access road under an agreement — 1 March to 31 May, 54 passes — through a hauling season and the remediation that followed. Measured by the Nation's own Scouts, compared segment by segment along the road's own line.

RemediatedHigh confidence

The haul turned a 23-minute drive into a 42-minute one. The remediation gave back all but five minutes of it.

Before the trucks, not one reading on this road came back rough — zero out of 1,316. Under haul and after it, 649 of 1,222 did: more than half of every drive. After remediation it is 141 of 1,410, about one reading in ten. Average speed ran 50 km/h, then 27, and now 41.

Recommendation. The restoration obligation is substantially met on the running surface. It is not met between km 10.6 and 11.8 at the creek crossing — seven consecutive segments, and the only stretch on the road still reading worse than it did before the first loaded truck. At km 11.0 not one of the 14 drives before the trucks read rough; all 15 after the remediation do. That is a drainage repair, and it is now a dated, measured ask rather than an opinion.

Resolution

This comparison could have detected a change of 0.56 levels or more. The haul moved it 4.1.

Segment scatter

Standard deviation 1.48 levels across 94 paired segments — the spread when nothing has happened.

Coverage

94 of 94 segments measured in every window; 54 passes over the three months, about 14 a month.

Comparability

These windows were not driven at the same speed — 50 km/h before the trucks, 27 after the haul. That gap is the road forcing the change rather than a difference in how it was driven, but roughness is sensed through a moving vehicle, so the two are not independent: a slower pass over the same ground registers less. If anything that understates what the haul did.

Video

Every window carries linked video on at least 89 of 94 segments, so any reading can be looked at rather than argued about.

Method

200 m segment · statistic mode · trusted devices · Scout units only — driver-app phones are excluded by device class, so no phone reading reaches a road number.

The road, window by window

Each strip is the whole road, south to north, at roughly 200 m a segment, averaged across every pass in that window. On the change row, grey is no move at all and the palest tints are a one- or two-level drift — real, but inside what a single 200 m segment scatters by between passes, so not a finding on its own. A blue underline marks a segment with linked video, and under each strip is that window's average speed 2 km at a time, with the minutes it adds. Below, all 54 individual passes that sit behind these four windows are shown unaveraged.

05 km11 km · creek15 km18.8 km
pre-industrial traffic01 – 14 Mar · 14 passes · roughness p90 5 · worst 5 · 0 % at 7+
54km/h—53km/h—45km/h—43km/h—60km/h—49km/h—43km/h—47km/h—58km/h—61km/h—
50 km/h · 23 min end to end
Hauling begins · 15 March
under haul17 – 29 Mar · 12 passes · roughness p90 9 · worst 11 · 37 % at 7+
38km/h+1.0min35km/h+1.2min31km/h+1.2min29km/h+1.4min47km/h+0.5min32km/h+1.3min30km/h+1.2min32km/h+1.2min45km/h+0.6min52km/h+0.1min
35 km/h · 32 min · +10 min · 30 % slower
haul finished26 Apr – 09 May · 13 passes · roughness p90 10 · worst 11 · 56 % at 7+
29km/h+1.9min27km/h+2.1min24km/h+2.2min23km/h+2.4min35km/h+1.4min24km/h+2.5min23km/h+2.4min25km/h+2.3min35km/h+1.4min39km/h+0.5min
27 km/h · 42 min · +19 min · 46 % slower
Remediation · 12 May
after remediation18 – 31 May · 15 passes · roughness p90 7 · worst 9 · 12 % at 7+
44km/h+0.5min44km/h+0.4min37km/h+0.6min36km/h+0.6min52km/h+0.3min35km/h+1.0min35km/h+0.6min39km/h+0.6min50km/h+0.4min53km/h+0.1min
41 km/h · 28 min · +5 min · 18 % slower
Change · before the trucks → after remediation0 improved · 87 about the same · 7 worsened
-10km/h+0.5min-9km/h+0.4min-8km/h+0.6min-7km/h+0.6min-8km/h+0.3min-14km/h+1.0min-8km/h+0.6min-8km/h+0.6min-8km/h+0.4min-8km/h+0.1min
50 → 41 km/h · +5 min end to end · 18 % slower
Roughness · level 1 (smooth) → 11 (severe)has videoChangebetter  ·  about the same  ·  worseSpeed · km/h per 2 km block, over the minutes it adds (on the change row, km/h lost)
Every one of the 54 passesthe four windows above, unaveraged

The road runs left to right — the same 18.8 km as the strips above. Time runs down the page, oldest at the top, one row for every drive, and every drive covered the whole road. You can watch the haul arrive, spread and sit there; you can watch the remediation take it out again; and you can see the one column at the creek crossing that never comes back.

Fifty-four drives over three months, every one of them a trip somebody was making anyway. This is what a record looks like when nobody is running a measurement campaign — and it is a picture no single inspection could produce.

Weather between the windows

Thirteen weeks, 1 March to 31 May. The haul ran through the spring freshet — the worst time to put loaded trucks on an unpaved road, and the reason the creek crossing moved as far as it did.

Rain / melt
Freeze–thaw
MarAprMay

What more readings buy you

A single pass is not a guess — it is a true record of that road on that day, and it is evidence the moment it exists. What repetition buys is the ability to tell a change from the ordinary scatter between passes. Roughness is sensed through a moving vehicle, so no two passes land identically even on a road that did not move. The smallest change a comparison can resolve falls with the square root of the number of passes.

Smallest change this road can resolve
0.5123±3.371 pass±1.694±0.9712±0.5735levelsOne pass can only tell you something moved if it moved more than three levels. Twelve passes and a single level is readable. Thirty-five and you can see half a level — which is the difference between "something happened" and "the haul did this".
The same stretch, clustered by week
4567wk 1n=2wk 2n=3wk 3n=1wk 4n=4wk 5n=5wk 6n=3wk 7n=6wk 8n=5Each dot is one pass. The line is the week's mean, the band is its confidence. Early weeks sit on one or two readings and the band is wide — a dot outside it proves nothing. By week 7 the band is tight enough that the downward drift is the road, not the driving.

This is the argument for capture that rides along with drives people were already making: nobody schedules a measurement campaign, and the confidence accumulates for free. It is also why the verdict at the top of this report carries a resolution figure — a change smaller than the resolution is not a finding, however much it looks like one.

Where to look

The segments the haul moved most, read all the way through to the remediation. Four came back to exactly where they started — that is the restoration working, and it is why the verdict is what it is. Seven did not, and they are not scattered: they are one unbroken run from km 10.6 to 11.8, which is what a real local difference looks like as opposed to a measurement artefact. The video is how you tell those apart, so every row opens its clip.

Roughness level · 1 (smooth) → 11 (severe)Drives that read rough · level 7+Peak vertical acceleration · m/s²
AtBefore the trucksAfter the haulAfter remediationStill outstandingbefore → after remediationbefore → after remediation
2.40 km15100/14 → 0/150.8 → 0.8 0.0▶ clip
3.60 km48400/14 → 0/153.1 → 3.1 0.0▶ clip
4.80 km48400/14 → 0/153.1 → 3.1 0.0▶ clip
7.20 km510500/14 → 0/154.8 → 4.8 0.0▶ clip
10.60 km174+30/14 → 0/150.8 → 3.1 +2.3▶ clip
10.80 km3117+40/14 → 8/152.1 → 10.6 +8.5▶ clip
11.00 km5119+40/14 → 15/154.8 → 23.8 +19.0▶ clip
11.20 km5118+30/14 → 15/154.8 → 15.8 +11.1▶ clip
11.40 km4118+40/14 → 15/153.1 → 15.8 +12.7▶ clip
11.60 km4117+30/14 → 15/153.1 → 10.6 +7.4▶ clip
11.80 km3106+30/14 → 0/152.1 → 7.1 +5.0▶ clip

Drives that read rough counts the individual passes that came back at level 7 or worse on that segment — level 7 is the product's own threshold for rough. It is a count over the drives, not a restatement of the window average, which is why km 11.00 reading 15 of 15 after remediation says something the level alone does not. Peak vertical acceleration is what a level means in physical units: the midpoint of that level's band on the published log ramp, gravity removed. It is the scale rather than a second instrument — two segments on the same level necessarily show the same figure, which is why it sits beside the levels and not apart from them.

Illustrative. Readings are constructed to show the shape of a real comparison. Roughness is comparative — the same road against itself, window to window. It is not calibrated, not a profilograph, and not a pavement condition index; an engineer's measurement is still an engineer's measurement.