Know what needs fixing before you sign.

Better road data starts with a clearer view. Find the issues, bring your team together, and keep every decision on record.

Request accessSee how it works

Built for the people behind South Africa’s roads.

Road surveyCSV dataset
TMH18
Survey preview
Survey data

Your original file, kept with every decision.

Start with your survey file.

Bring your road survey data into one clear view.

Recorded platform activity

All-time totals across eligible organisations. These counts can include early-access and test activity; they are not customer adoption or performance results.

Data rows recorded
17 172 254

Rows in stored submissions, including files with findings. This is not a pass count.

Submissions received
201

Stored submission records, including archived records. A submission can contain many rows.

Certificates issued
74

Certificate records created after approval. This includes historical certificate records.

Snapshot loaded 2026/11/12, 10:23:48 SAST. Refresh the page for a newer snapshot; aggregate counts can lag recent activity.

How it works

Upload, check and review.

Start with a CSV file. Resolve the findings, then send it for review. Automated checks do not replace an engineer’s approval.

01Step

Upload your file

Choose a CSV file and the appropriate set of checks. The upload page shows the supported size and format before you start.

02Step

Review the findings

See the rows and fields that need attention. Correct the file and upload a replacement, or record an allowed exception with a reason. The decision stays in the audit record.

03Step

Approve and issue a certificate

An authorised engineer reviews the submission and signs when it is ready. A certificate links the stored file to that approval. Anyone can look up the certificate without an account.

Standard alignment

What the checks cover.

TMH18 Validator implements selected checks aligned with TMH-18. The table separates available work from planned support. It does not claim complete coverage or endorsement by the standard’s publishers.

StandardPublishedPlatform supportScope
TMH-18v5Selected checksSelected road survey data checks; coverage depends on the chosen schema
TMH-9May 2016PlannedManual for Visual Assessment of Road Pavements
TMH-22Draft V8b · Mar 2013PlannedRoad Asset Management Manual

Source documents: transport.gov.za/tmh-documents.

Further reading on these manuals: TMH-18 road asset data exchange formats explained, how to do a TMH-9 visual assessment, and the TMH-22 road asset management manual explained.

Frequently asked

Common questions.

What is TMH18 Validator?

A tool for checking road survey CSV files against selected TMH-18 rules. It helps your team find data issues, record review decisions and issue a certificate after an authorised engineer approves the submission.

Which version of TMH-18 does TMH18 Validator align with?

Version 5 — the COTO release published by the Department of Transport. The current rule set covers required-header presence, UTF-8 encoding, monotonic chainage, deflection-sensor ratio, and temperature-correction presence. Additional sections of TMH-18 land as schemas as they enter the engine.

Is TMH18 Validator live with paying customers?

Not yet. We are accepting applications from South African road authorities, consulting engineers, and contractors. Each application is reviewed by hand before access is granted.

Who is the platform for?

South African road authorities (SANRAL and provincial departments — Western Cape Mobility, Gauteng Roads and Transport, Eastern Cape Transport, Mpumalanga Public Works), and the consulting engineers and contractors that submit pavement and road-asset data on their behalf.

How does a third party verify a certificate?

Open tmh18.com/verify and enter the certificate ID. The verifier returns dataset metadata, signers, issued time, and SHA-256 hash — enough for any independent party to re-hash their copy and confirm it matches the certified bytes. No login required.

How is data residency handled under POPIA?

Hosting and data handling depend on the environment used for your organisation. Confirm the hosting location and applicable data-processing terms before uploading personal or confidential information; the legal page explains the current policy.

How much does it cost?

Invited early-access organisations pay no monthly platform fee. Analysis is funded with prepaid validation credits using the tenant rate card; the current default includes a once-per-submission admin fee plus a per-row processing charge.

Is there an API?

Yes. Authorised users can create API tokens for supported schema and submission endpoints. The API documentation explains available operations and limits; webhooks are not part of this workflow.

Articles & guides

A clearer path from survey to sign-off.

Practical reading and short videos for the people preparing, reviewing and certifying survey data.

Explore articles and guides
  1. Prepare your survey CSV for validationFile preparation
  2. What errors, warnings and skipped checks meanValidation
  3. From reviewed survey file to certificateCertification
  4. Choosing the check template for a TMH 18 survey fileValidation
  5. TMH 18 data validation: from survey file to certificateStandard
  6. TMH 18 file format: semicolons, UTF-8 and empty fieldsFile preparation
  7. Why every TMH 18 record must fit inside the network kilometresStandard
  8. What a TMH18 Validator certificate tells the clientCertification
  9. When nobody in your team can issue the final certificateCertification
  10. When to record an exception on a finding, and what to writeValidation
  11. Why an upload is refused before any checks runFile preparation
Apply for access

Bring your next survey file.

Tell us about your organisation and the data you need to check. We review access requests and contact accepted organisations with the next steps.

Request access

Access is reviewed before an invitation is issued. Analysis uses prepaid validation credits.