TR Zero exists so an auditor is not ducking the session but can sit there relaxed, doing his job.
TR One must be done so the pc can hear and understand the auditor (without blowing the pc’s head off either).
TR Two must be done so that the pc gets acknowledged. This can be so corrupted that the auditor doesn’t ack at all but gives the pc meter reads! Instead of acks! Or keeps saying, “I didn’t understand you,” etc.
TR Three basically existed so that the auditor would continue to give the pc commands and not squirrel off or pack up with total silence.
TR Four exists so that the pc’s origins are accepted and not Qed and Aed with or invalidated.
And, surprise, surprise, TRs are for use in the session itself, not just a drill. They are how one runs a session.
Metering can miss “F/Ns” with high or low TA. And one never feeds meter data to the pc: “That read,” “That didn’t read,” “That blew down,” just must not exist in session patter. “Thank you. That F/Ned,” is as far as an auditor goes. And that’s the end of the cycle and says so.
Floating needles can be overlooked by an auditor. In Dianetics this fault is fatal.
Auditor’s Code must be in on all points and particularly invalidation. Pc says, “That’s so and so.” An auditor who says, “I’m sorry. You are wrong,” or any other invalidation is going to wreck a pc’s case. A full knowledge of the Auditor’s Code and actually applying it saves endless troubles. It is an auditing tool, not just a nice idea.