To find slivers in our network-wide data we have been using the Check Events tool within RCE (we do not have data reviewer or workflow manager implemented yet). This returns Gaps, Overlaps, and Invalid Measures on the events selected. Currently our workflow to fix this has been to reassign to a bogus Route ID then reassign back to the original Route ID, however we are experiencing a separate issue with that workflow.
My question is how are other R&H users fixing invalid measures on events?