Chainage, for road and highway construction
Road quality assurance, mapped along the alignment.
Raise inspection requests by chainage range, layer and side. Record the tests each one needs. Approve or reject from a queue. Chainage turns every inspection into the status of the road, so the map is never typed in by hand.
Why Chainage
The status of a road usually lives in five places
Inspection requests on paper or in chat groups, lab results in a workbook, approvals in someone’s inbox, and a progress chart updated by hand. When a layer goes down over ground that was never approved, it is found late and fixed at cost. Chainage keeps the request, the evidence, the decision and the map in one record.
- Status is derived, not typed
- The road map is computed from inspections every time it is drawn. Nobody maintains it, so it cannot drift from the register.
- Sequencing is checked, not remembered
- The system refuses to raise a layer over ground whose prerequisite is not approved, and says where the gap is.
- Evidence travels with the request
- Results sit on the inspection they belong to, next to the acceptance limit they were judged against.
How it works
From an empty stretch to an approved layer
Set up the project
Define the road's extent, its layers and sides, and the structures, drains and junctions along it. Add your test catalogue with frequencies and acceptance limits, and the people who raise and approve. Setup recipes cover common configurations.Raise an inspection
Select a stretch of road, or a structure and its stage. Chainage attaches the tests the frequency plan requires and checks that the work it depends on is already approved.Record the evidence
Enter results for each due test. They are checked against the acceptance limits as your specification writes them. When the last required result is in, the inspection submits itself for approval.Approve and report
Approvers decide from their queue. Each decision updates the road map straight away, and reports across projects export to CSV or Excel.
What is in Chainage
Everything a road QA register needs, and a map of it
- The road board
- Every cell of the road, on both sides and in every layer, colored by the inspections that cover it: approved, awaiting approval, rejected or not yet inspected. The worst result governs, so a failed stretch cannot hide between approved ones.
- An evidence gate
- An inspection carries the tests its layer requires and cannot reach an approver until every one has evidence. The progress you see is the same rule the server enforces.
- Layer sequencing
- Each layer can depend on the layers or structure stages beneath it. It can only be raised where those are approved across the whole stretch.
- Acceptance limits as written
- Test definitions hold the acceptance criteria word for word from your specification, and results are evaluated against them strictly. Past inspections keep the rules they were raised under.
- Structures, drains and junctions
- Culverts, bridges, drain runs and junctions are tracked as features along the alignment, each with its own stage plan.
- Ready ground
- For each layer and side, Chainage lists the ground its sequencing rules would accept that nothing has been raised on yet, and proposes the stretch that continues the latest work. Pick it and raise it.
- Named re-tests
- Select rejected ground and Chainage names the rejection that controls it, the day it was decided and the approver's remarks. The re-test's result sets the status; every earlier attempt stays on record.
- The road on any date
- Lenses lay information over the road without changing it: status, ready ground, what needs attention, and the road as it stood on a past date, read-only.
- Construction front
- A time–chainage chart for each layer, with its approved length, its advance over the last 30 days and how much cover it leaves the layer above.
- An assignee that follows the work
- A new inspection proposes the engineer already working that track or layer, and says why, before falling back to the default.
- A work queue
- Engineers and approvers each see the inspections that are waiting on them.
- Reports and exports
- Organization-wide reports on inspections and tests across projects, with saved report definitions and CSV or Excel exports.
- Audit trail
- Append-only logs record who changed each record and who opened each inspection. They cannot be edited from the product.
- API and webhooks
- A REST API with idempotent writes and signed webhooks on state changes, so an ERP or reporting system can raise inspections and read results.
- Field sheets, where enabled
- Photograph a field density sheet and Chainage reads the values, recomputes the arithmetic and puts it in front of a reviewer before it counts as evidence. Available where document reading is switched on for your organization.
- Configuration you control
- Project settings are versioned. Activating a change never re-judges inspections that were raised under the previous version.
Who uses it
One record for the people on the road and the people answering for it
- Site and QA/QC engineers
- Raise inspections on stretches and structures, and record results from the field or the lab.
- Approvers
- Accept or reject submitted inspections from a queue, with the evidence and acceptance limits in front of them.
- Project managers and leadership
- Follow progress on the road board and in reports across every project.
- Administrators
- Configure projects, the test catalogue and the people who can raise and approve.
Chainage runs in the browser on phones and desktops. It is readable in the field and dense enough for the site office, and it needs a network connection.
Access and security
Invitation-only, organization-scoped, fully recorded
Accounts are provisioned for your organization and signed in through single sign-on. Roles decide who can raise, approve and administer, and every change is logged. Read how we handle security.
Questions
Chainage FAQ
What is chainage?
Chainage is the distance along a road's alignment from a fixed starting point, usually written in kilometres and metres, such as 120+450 for 120.45 km. Chainage the product uses it as the address of every inspection, so a request, its tests and its approval all refer to the same stretch of road.
Which test standards does Chainage support?
Chainage does not ship a fixed standard. Your test catalogue holds each test, its frequency and its acceptance criteria as your contract specification writes them, and results are evaluated against that text. During onboarding we set the catalogue up from your existing lab formats.
Which pavement layers can it track?
Layers are configured per project, on each side of the road, so the stack matches your pavement design. Dependencies between layers, and between layers and structure stages, are configured the same way.
Does it work on a phone?
Yes. Chainage runs in the browser on phones, tablets and desktops, with no app to install, and photos can be taken straight from a phone's camera. It needs a network connection; there is no offline mode.
Can it connect to our ERP or reporting tools?
Yes. A REST API with idempotent writes lets other systems raise inspections and read results, signed webhooks report state changes, and reports export to CSV or Excel.
How does a rejected stretch get cleared?
After rework, raise a re-inspection over it. The newest attempt sets that stretch's status once it is approved, and the rejected attempt stays in the record.
How do we get started?
Book a demo. We configure a first project with you from your contract's specification and test formats, and accounts are set up for your team by invitation.
See your own road in Chainage
Bring a project's specification and test formats. We will show you the road board, the evidence gate and the reports on work like yours.