Watch the overview
74 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Every survey tells a story.
- 0:02See what your data is
- 0:03telling you.
- 0:04TMH18 Validator brings your survey
- 0:07workflow into one connected workspace.
- 0:10Create a project, align your
- 0:12reference data, and upload your
- 0:14survey file.
- 0:15Choose the right template, with
- 0:16clear visibility of the checks
- 0:18it covers.
- 0:19See passed checks, warnings, errors
- 0:21and skipped checks separately.
- 0:23Follow an issue from the
- 0:24road summary to the finding
- 0:26and the affected rows.
- 0:28Inspect reported positions on the
- 0:29map.
- 0:30Check the source, correct your
- 0:32file, and submit a replacement
- 0:33when needed.
- 0:34Bring reviewers together, record decisions,
- 0:37co-sign and complete final approval.
- 0:40A certificate records the review
- 0:42decision and the file fingerprint.
- 0:44Organise your team, roles and
- 0:46partner companies.
- 0:47Track credit usage, invoices and
- 0:50activity.
- 0:51Manage connections, notifications and account
- 0:53settings, with guided learning and
- 0:55help along the way.
- 0:57From the first upload to
- 0:58a recorded decision, keep the
- 1:00work connected.
- 1:01Start your seven-day free trial
- 1:03with up to one hundred
- 1:04thousand analysis rows per organisation.
- 1:07No card required.
- 1:08Visit TMH18.co.za
Start with the survey and its project
A road survey is more than a collection of correctly typed cells. Its measurements belong to a location, survey period, lane and source definition. Start by keeping the untouched export and confirming the check template that matches the file contents. The platform does not make that selection on the reviewer’s behalf.
A project brings related survey files and reference data into one review context. Geometry, network, classification and lane references contribute different evidence. Inspect their registration results and the active version before relying on alignment findings.
Read findings and coverage separately
After upload, confirm that analysis has completed. A stored file and a completed result are different states. Read errors, warnings and skipped checks separately, then follow a finding to its examples and affected rows. A clean result describes the checks that ran; it does not establish complete manual compliance.
Use the road summary and reported positions to investigate context. When a source correction is justified, preserve the original and inspect the result of the replacement. Earlier confidence cannot identify a changed file simply because its name looks familiar.
Keep review decisions attached to the file
The workflow supports review, co-sign and final approval according to permissions and eligibility. Review unresolved errors, applicable exceptions and project policy before moving to the next step. Record the reason for a genuine exception rather than changing a source value to silence a finding.
Certification records the decision and file fingerprint. It does not calibrate survey equipment, establish government endorsement or guarantee measurement accuracy. Retain the original evidence and verify the current certificate state when using the record for handover.
Make the surrounding administration traceable
Team membership, roles and partner-company scope help define who can see records and act on them. Credit usage and invoices describe processing costs, while activity and notifications help users locate relevant events. These administrative records support the workflow; none substitutes for technical review.
Start with one representative file and use the onboarding lessons for the actions your role performs. The public film introduces the connected workflow. The signed-in learning library records lesson progress and lets you return to unfinished topics.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.