Follow a record
In development
Follow a finding.
Keep the thread.
You are reviewing a road-centerline issue before the next data delivery. See what the GIS analyst examines, what a manager can follow, and what remains available when the issue returns.
01 / Source record
Start with the value on the record.
A fictional road centerline has ZZ in its left-side state field. Its source identifier is RCL-0147@example.test.
The source record
| Field | State_L |
|---|---|
| Value supplied | ZZ |
| Data handling | Read locally. Results written separately. |
One fictional record, domain checks only. Selected output fields; no operational data. Example details.
What if the value is corrected?
The GIS editor makes the correction in a separate source copy. The Workbench checks that newly supplied value.
The condition returns.
A new Critical finding starts Unreviewed. The earlier Reviewed decision is linked as history.
An exception with a precise scope
Approve a convention.
Keep its boundaries.
An Approved Local Convention is a documented exception for an exact value, field, layer, and rule. Recognition changes the attention queue. The original finding remains in the record.
Lowercase or
The domain check recognizes the state value but reports nonstandard capitalization as Watch. A fictional reviewer approves this exact lowercase value for local review.
| Rule | DOM-010 |
|---|---|
| Layer / field | RCL / State_L |
| Exact value | or |
Local approval does not alter an external standard or decide interchange acceptance.
The Watch finding remains Unreviewed in the full record. It is excluded from the active queue because the approved scope matches.
The active queue is the set of findings needing attention; it is separate from the review status named Active. Marking a finding Reviewed does not remove its underlying condition.
All three outcomes are captured from the same development candidate. These controls do not approve a real exception.
Inspect the evidence
Inspect the result.
These excerpts come from recorded output for the fictional domain-check example. They preserve the finding and review values needed to inspect the workflow; internal build and matching metadata are omitted.
After human review
See the original Critical assessment alongside Reviewed status and the finding’s source identifier.
Open the report excerpt (new tab)When the value returns
See a new Unreviewed occurrence for the same source record. The machine assessment is still Critical.
Open the next-run excerpt (new tab)Inspect the finding record
Rule, layer, value, identifier, severity, and review context in a machine-readable file.
Download the JSON excerptSee the source values
The example begins with one road-centerline identifier and one deliberately invalid state value.
Download the input excerptLook beyond this one example.
Explore the check families and what their results help a practitioner examine.