"proper training" won't work. There has to be accurate feedback from an automated source, preferably one written and distributed for free by the relevant agency as the sole source of "truth."
The reason "proper training" won't work is that GD&T (sic) is a programming language and people suck at programming unless there is a compiler to examine the validity and a computer to run the code. The compiler and computer have no opinions to manipulate. No one does "code reviews" line by line anymore independent of compilation and running the code. But that is still tolerated in GD&T (sic.) Even then the better programmers run extensive tests on varied inputs to ensure the outputs are what is expected.
In software, a programmer might write 10-50,000 lines of code a year**. A drafter/detailer might put down 50-1000 FCFs a year. Which one is likely to truly understand the subject when the drafter/detailer never sees all the possible variations his code might produce? Feedback is how one gets experience. Sitting in training doesn't produce experience.
That's why I want Y14.5 to be a picturebook, so that no one has to think about the outcome to typical cases at all. And ASME to provide a software tool to generate variations that are acceptable per the GD&T (sic) so that users have immediate feedback and can push those variations to tolerance analysis software and to FEA software.
**Most are rewrites when the software doesn't work as expected. Many more are deleted when a better solution comes up. Still, the programmer has considered each line and what it will do and they still need the compiler to verify their understanding is correct.