Chainage · Road construction quality assurance
Road quality assurance, mapped along the alignment.
Raise inspection requests by chainage, 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.
- Status
- In trial with Harsh Constructions
- Used by
- Site and QA/QC engineers, approvers, project managers
- Runs on
- Any browser, on phone or desktop
- Every stretch opens to
- Its inspection, tests and limits
Illustrative project · 120+000 – 120+480 · 10 m cells
LHS · Dry lean concrete
120+120 – 120+160
Rejected · 40 m
The newest inspection of this ground was rejected, so it stays red. Approvals either side never repaint it; only a newer, approved re-test can.
Inspection 1034raised 19 Jul
Rejected
- Cube compressive strength, 7 day8.6 MPa · limit ≥ 10 MPaFAIL
- Thickness151 mm · limit 150 mm, −0 / +10PASS
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 board is computed from the inspections every time it is drawn. Nobody maintains it, so it cannot drift from the register.
- Sequencing is checked, not remembered
- Chainage refuses to raise a layer over ground whose prerequisite is not approved, and names the metres 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, in the words of your specification.
The evidence comes first. There is no override.
An inspection carries the tests its layer requires. It cannot reach an approver until every due test has evidence: a value keyed in, or a field sheet read and confirmed. The moment the last one lands, it submits itself.
A failed result is evidence too. Submitting it is how a rejection happens, and the stretch stays red until a newer re-test is approved. Tests marked “as required” never hold the gate.
The meter the engineer sees is the same count the server enforces. Try it.
Inspection 1188 · Granular sub-base · RHS
120+300 – 120+360
Status: Raised
Field dry density
IS 2720 (Part 28) · limit > 98%
Gradation
IS 2720 (Part 4) · limit Grading III envelope
Atterberg limits
IS 2720 (Part 5) · limit LL < 25% & PI < 6%
Ten per cent fines valueas required · never gates
IS 2386 (Part 4) · limit ≥ 50 kN
It cannot reach an approver until every due test has a result. A fail counts as a result.
A layer goes down only on approved ground.
Each layer carries its own requirements: the layers or structure stages that must be approved beneath it, optionally within a chainage window. A request is accepted only where every requirement that touches the stretch is met. When it is not, Chainage says exactly where.
From an empty stretch to an approved layer.
Step 1: Set up the project
Define the road’s extent, its layers and sides, and the structures, drains and junctions along it. Load your test catalogue with its acceptance limits, and the people who raise and approve. Setup recipes cover common configurations.Step 2: Raise an inspection
Select a stretch of road, or a structure and its stage. Chainage attaches the tests the layer requires and checks that the work beneath is already approved.Step 3: Record the evidence
Enter results for each due test; they are judged against the acceptance limits as your specification writes them. When the last due result is in, the inspection submits itself for approval.Step 4: Approve and report
Approvers decide from their queue. Each decision updates the road straight away, and reports across projects export to CSV or Excel.
A road QA register, and a map of it.
- The road board and its lenses
- Every cell of the road, on both sides and in every layer, coloured by the inspection that controls it. Lenses lay information over it without changing it: ready ground, what needs attention, and the road as it stood on a past date, read-only.
- Ready ground
- For each layer and side, the ground its sequencing rules would accept that nothing has been raised on yet, with a proposed stretch that continues the latest work.
- Named re-tests
- Select rejected ground and Chainage names the rejection that controls it, the day it was decided and the approver’s remarks. Re-inspection is a right: every earlier attempt stays on record.
- Construction front
- A time–chainage chart for each layer: where its longest continuously approved stretch ends, how far it moved in 30 days, its lead over the layer above, and what holds it.
- An assignee that follows the work
- A new inspection proposes the engineer already working that stretch or layer, and says why, before falling back to the default.
- A work queue
- Engineers and approvers each see the inspections waiting on them.
- Reports and exports
- Organization-wide reports on inspections and tests across projects, with saved report definitions and CSV or Excel exports.
- Field sheets, where enabled
- Photograph a field density sheet and Chainage reads its values, recomputes the arithmetic and puts both in front of a reviewer. Nothing counts as evidence until a person confirms it.
- An API
- A documented REST API (OpenAPI 3.1, with public reference docs) and read-only API keys for inspections and their results, so reporting systems can follow the work. Webhooks for state changes are built but not yet switched on.
Built for the audit, not just the site.
Accounts are provisioned for your organization and signed in through single sign-on, and roles are checked on the server. How we handle security · Our approach
- 01Rules frozen when the work is raised
- An inspection keeps the acceptance limits it was raised under. Activated configuration cannot be edited; a change makes a new version and never re-judges past work.
- 02Logs that refuse a rewrite
- Append-only logs record who changed each record and who opened each inspection. The database refuses a rewrite; they cannot be edited from the product.
- 03One rule, two places
- The status, evidence and sequencing rules are one package run by both the browser and the server, so what the screen shows is what the server will enforce.
- 04Writes that cannot double
- Requests that create or move a record carry an idempotency key, so a retry is answered from the first attempt instead of being applied twice.
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.
How does Chainage decide the colour of a stretch?
From the inspections covering it, every time the road is drawn. The newest attempt controls; if two were raised together, a rejection wins, so a tie can never hide a failure. Approving the ground next to a failure never repaints it, and a rejection clears only under a newer, approved re-test of the same ground.
Which test standards does Chainage support?
Chainage does not ship a fixed standard. Your test catalogue holds each test 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 test 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 connection to load. If the connection drops, inspections raised and decisions taken wait on the device and send when it returns.
Can it connect to our ERP or reporting tools?
Reporting systems can read inspections and their results over a documented REST API with read-only API keys, and reports export to CSV or Excel. Webhooks for state changes are built but not yet switched on. The developers page has the details.
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.