6205C17 SHSpec-146  Auditing Errors

     There are two types of auditing activity in which you engage:

          1. Rudiments type of activity.  You are trying to straighten
             something out right now, not to dig something up.  Done against
             the needle.

          2. Auditing activity.  Done against the tone arm.  Long, wide sweeps
             of the needle may count as TA motion.  Here you are trying to dig
             something up.

You have to get good at sliding from one type of activity to the other.  Say
the PC suddenly declares that the list is complete.  You have to shift fast to
middle ruds and check for missed withholds.  There are also negative middle
ruds, e.g., "In this session, have you tried not to withhold anything?" or "In
this session, have you tried not to invalidate anything?  Suppress anything?",
etc.  There are two reasons why your PC keeps picking up more and more missed
withholds.  One is that you have missed a withhold and the other is that the
PC is strenuously and attentively keeping his ruds in, running the session,
And being very careful not to withhold, etc.  It doesn't matter what you use
as a middle rudiment.  It could be an end-type rud [half-truths, untruths,
etc.] or whatever seems to be needed to keep the body of the session going.
The faster you get the rud in, the better.  You are not looking for more than
a clean needle, even if it only stays clean for ten seconds.  If you want a
rudiment to stay in, you get your session ruds in and use the body of the
session to prepcheck a particular rudiment so it will stay cleaned up.

     You can drive yourself and the PC nuts by not acknowledging everything
the PC says in answer to your questions, even if what the PC says doesn't
actually answer up.  You have to be clever in prepchecking to probe around and
actually help the PC to find out things he didn't know about.  It is possible
that there will be no chain and that the overt will blow after he tells it to
you.

     When you are doing rudiments, don't go into a process to handle an
out-rud until you have given it several chances to blow by inspection.  If you
do run a process, get in and out fast; treat it as lightly as possible.  The
best ruds process is the one that gets the ruds in fastest.  Time spent on
ruds is time robbed from the session, so don't get started handling ruds [if
you can avoid it].  Just dust them off.  Pc's will obligingly get rid of
things that you don't seem to think are very important.  When you are in the
body of a prepcheck, you want to give some importance to the overts you are
searching for.  By apparently taking responsibility for the PC's overts, just
to the degree of being very interested and thorough about getting them, you
throw an element of responsibility into the session, and the PC will come up
with more data.