6310C17 SHSpec-314 Levels of Auditing

     Getting TA motion is a common denominator of all scientology activities.
The state of case of the PC has practically nothing to do with your ability to
get TA motion on him.  Some day you will cognite that if you don't yank the
PC's attention off of his case, and if you give him something to itsa, and if
you don't stop him, he will get TA motion.  You can reduce TA motion by being
unpredictable as an auditor, e.g. by varying the form of model session.  Keep
the session drill constant and predictable from session to session, or the PC
will start running a whatsit on the auditor.  Then the auditor runs itsa on
the PC, and you get no TA.

     The auditor, not the PC, is in complete control of the bank.  The bank
always does what you tell it to do.  The PC sometimes does and usually tries
to.

     When a new style of auditing is released, like "listen style", auditors
at first go to pieces.  They will start introducing some listen-style into
formal auditing.  You should let the PC itsa the item or goal, but that's
all.  If you let the PC itsa the bank, you will have a sick PC on your hands.
The TA might move for awhile, but the over-restimulation that the PC could get
into will lock up the TA pretty soon.  The things that you are handling in the
bank are the things that prevent itsa, so letting the PC itsa around in the
bank isn't effective.  The PC will restimulate that which prevents him from
itsa-ing, so he won't be able to itsa.  Level IV is all sub-itsa, but when you
give the PC an item, do let him cognite and itsa on it, or you will stack up
missed withholds, BPC, and high and stuck TA.  This presents a bit of a
problem, since, e.g., when the auditor stops the PC from wandering into the
wrong GPM, there is BPC, which can produce a fierce ARC break.  What you have
to do is to audit fast enough and positively enough, so that the PC never gets
a chance to wander.

     The two great dangers in Level IV auditing are:

     1. The tendency for a goals list to be underlisted.

     2. The tendency for an item list to be overlisted.

     When you fumble a command, you are not in control of the PC's itsa-ing of
his bank.  But you are in absolute control of the bank, so if you fumble a
list, the bank will fumble.  So the bank fumbles, unseen to you.  The PC's
attention line is on the point where you fumbled.  Therefore, the bank has
shifted under that scanner, and the PC's attention goes off onto other things,
because you have shifted other things into his view with your fumbling.  Soon
after such a fumble, the PC will add something to the session -- some kind of
yip-yap, not necessarily critical.  You did something that showed that you did
not have control of the PC's bank.  You distracted the PC's itsa-maker line
and shifted the bank underneath it with this goof.  So you are going to get
some other stuff.  It isn't neat and clean.  The PC's attention will now be
somewhere you don't want it.  If there is any BPC lying around, the goof, or
cutting the itsa line, will key it in, and you will get an ARC break.  You
will get a dispersal of attention.  The itsa goes all over the time track.
There is always BPC in a session.  You can't avoid it.  The BPC is either from
past auditing or from this session.  "The key-in of BPC is always some
communication failure", e.g. cut comm or refuted itsa, on the part of the
auditor.  You could even get a wrong goal, and if you audited very smoothly,
you could audit without giving the PC a single ARC break, because it takes a
cut comm line to restimulate any BPC, even when it is there.  The fact that
there is BPC does not mean that there has to be an ARC break, but the fact
that there is an ARC break does mean that there was some BPC.  BPC, via a
rough spot in auditing, via a session key-in -- cut comm, etc. -- gives rise
to an ARC break.  A wrong goal may cause a very uncomfortable PC, but need not
cause an ARC break.  Whether there is an ARC break from BPC is entirely
dependent on the auditor.  Of course, the more BPC there is in the session,
the tinier the mistake could be, that could key it in.

     The cycle of any ARC break is:

     1. Bypassed charge.

     2. A rough spot that gives the PC a little dispersion.

     3. A cut line on the rough spot.

     4. The ARC break.

Dead on the ARC break, you will find a little misdemeanor, but ten minutes to
1 1/2 hours earlier, you will find a nice nasty misdemeanor.  For instance,
you might find that some sort of forcingness was going on.

     Guide the PC's attention; don't force it.  The bank does move to whatever
the auditor says.  Running an engram is like developing a picture.  Just have
the PC look at it.  You can move his attention over it repetitively.  This
procedure will develop his picture of whatever was there.  LRH did this with a
PC who was dead in his head.  LRH moved the PC to a non-significant date and
moved him through the next half hour, over and over.  The PC got to where he
was reading the mail that he had read at the time that LRH moved him to, word
for word.  If you get the date and duration of any picture on the back track,
the picture will turn on.  The only thing that fouls this up is:

     1. The comm line is too lousy for the PC to report that he has done it.
        There are several ways to prevent a PC from reporting what he sees.
        You can also foul up the comm line by refusing to take the PC's data.
        You could fail to believe that you were moving the date under the PC's
        attention.

     2. The track is stuck in something.

     You can demonstrate the above phenomenon by taking some non-significant
date and getting the PC to pick up everything in it by moving him through it
enough.  This is even easier than getting aberrated incidents, since there is
no charge debarring it.  Running a chargeless incident is a test of an
auditor's tech, because there is nothing there but the auditing.  If you don't
go goofy and demand more than the PC has, you can get the picture.  You may
not get the PC's state of consciousness [in the incident], unless you spend a
long time on it.  It would be a good test of auditing.  There is no upset
present, except what the auditor introduces.  If your auditing is rough, you
will find that when you are trying to get the PC's attention on the rough
stuff of Level IV, his confront will be lowered, his confidence will suffer,
and his ability to itsa will be lessened.  The PC will only have difficulty on
what he can confront and do if you make difficulty for the PC.  Additions to
the comm cycle do make trouble for the PC.

     So keep itsa where it belongs.  When you've got a nice long item list (20
items long), give the PC his item.  Let him look at it and cognite.  When he
has done so, you can show him the list and ask him how the other items
relate.  Now you will get more TA and more confusion blowing off.

     Once you have learned how to audit Level IV, it will seem easy.  The fast
way to arrive at that point is to do it.