Watch the overview
About 3 minutes. A narrated explainer; the same words are below.
Read the video text
- 0:00Sometimes a check flags a value that is actually correct.
- 0:06If it is an error, the file cannot move on, even though the road data is fine.
- 0:12In TMH18 Validator, an exception is a note that says: I looked at this, and it is fine.
- 0:20On an error, it lets the file move on. It does not change the data.
- 0:26Among findings, only an error without an exception blocks Send for review and co-sign, co-signing and certification.
- 0:34Warnings never block those steps. An exception can be recorded on either.
- 0:42An exception does not correct the data, and it does not make the measurements right.
- 0:47The stored error count keeps its raw number, so the original result stays readable.
- 0:53Recording an exception needs the findings override privilege.
- 0:58No reason box on an error you can accept? Ask an administrator about the privilege.
- 1:04Open the file with Review findings. Each finding that can be accepted has a reason box and a Record exception button.
- 1:11Write your reason, then press the button. The finding now shows EXCEPTION RECORDED.
- 1:18The form refuses an empty reason, but a single word will pass. So write for the engineer who signs after you.
- 1:27Say which value, why it is acceptable, and what evidence you checked, such as the field notes.
- 1:34Say a reading looks far too high, but your field notes show a bridge joint there.
- 1:40A good reason names that record, that evidence, and why the value stands. It never just repeats the rule.
- 1:48There is no undo for one exception. If unsure, leave it open, fix the source data, and check again.
- 1:57Some processing notes, like the comma delimiter note, have no reason box and cannot be dismissed.
- 2:05A Reupload, or Run checks again, deletes the old findings and builds new ones.
- 2:12Earlier exceptions do not carry over, so keep a copy of each reason and record them again.
- 2:20So: an exception clears the gate, not the data. Write a reason another engineer can check, and treat it as final for this run.
- 2:28The full guide is at TMH18 dot com, slash articles.
What Record exception does to a finding
When you open a file with Review findings, each finding that can be accepted has a reason box and a Record exception button. After you use it, the finding shows EXCEPTION RECORDED. An exception works on both errors and warnings. This guide is part of our TMH 18 data validation series; for what Error, Warning and Skipped mean, read the guide on understanding validation findings first.
Exceptions matter because only an Error without an exception blocks the next steps. While one remains, you cannot send the file for review and co-sign, and it cannot be co-signed or certified. Warnings never block those steps. An exception clears the block. It does not correct the data, and it does not make the measurements right.
Who can record an exception, and what to write
Recording an exception needs the findings.override privilege. If you cannot see the reason box on a finding, ask an administrator in your organisation whether your account holds it.
The form refuses an empty reason, but it does not check how long the reason is. A single word will be accepted, so do not rely on the form to make you write something useful. Your reason is shown on the finding afterwards. Write it for the engineer who signs after you.
- Say which record or value the finding is about.
- Say why the value is acceptable, in your own words.
- Name the evidence you checked, such as the field notes.
- Do not write a reason that only repeats the rule message.
Findings you cannot dismiss, and what stays on record
Some notes have no reason box. The comma delimiter note and the note that empty rows were ignored describe how the file was read, so they cannot be dismissed. They stay visible as part of the record of the check.
Recording an exception also does not change the count stored for the check run. That count keeps its raw number of errors. The exception clears the gate only; the original result is still there to read.
There is no undo for a single exception
No action reverses a single recorded exception. The only way exceptions go away is when the checks run again or the file is reuploaded, which rebuilds all findings and drops every exception. Treat the button as final for this check run. If you are unsure, leave the finding open, correct the source data, and check the file again instead.
Running the checks again (Run checks again) sets the file back to Under review and, like a Reupload, deletes the old findings and builds new ones. Earlier exceptions do not survive it, so record them again for any finding that still deserves one.
A Reupload starts the findings again
Reupload replaces the file after a correction. It needs the permission to reprocess files, and it is not available once the file is Certified or Rejected. The new file is checked in a queue, and the old file stays the file of record until that analysis finishes.
When it finishes, the old findings are deleted and rebuilt from the new file. Earlier exceptions do not carry over, so record them again for any finding that remains and still deserves one. Be ready to repeat your reasons.
- Keep a copy of each reason outside the product.
- Reupload only after the correction is complete.
- Review every rebuilt finding before you send the file on.
Put it into practice
Open your survey filesSign-in and the relevant account permissions are required.