6207C26 SHSpec-179  Prepchecking

     [Some of the data in this lecture is found also in HCOB 30Ju162 "A Smooth
HGC 25 Hour Intensive". See also page 254, above, for history of
prepchecking.]

     "I've just found a way to use middle rudiments and make them double in
brass and get the job done much better, in prepchecking." Suppress, suggest,
careful of, invalidate, and fail to reveal are powerful prepcheck buttons.
They should be used in the above order.  Used in this order, you have the
mid-ruds as a complete prepcheck.  The middle rudiments were carefully sorted
out of a great number of buttons that could be used.  You could add another
fifteen or twenty buttons.  The Chart of Attitudes [See Handbook for
Preclears] has a lot of them.  Ruds are buttons that consist of just those
things that can keep one of the other buttons from reading and which, if
present, can keep a goal or item from reading.  They are pretty powerful:

   SUPPRESS:        If you got suppress off the case, nearly everything would
                    blow.  If suppress is alive, you don't get a read on the
                    remainder of the buttons, so run suppress before adding
                    another series of anything.

   SUGGEST:         This button could be and sometimes has to be translated as
                    "Is-ness".  That is evaluation, per the Auditor's Code
                    (No. 1).  It says that something is.  It is a powerful
                    button, because you say something is, it will now read,
                    even though it wasn't reading before.  You say something
                    reads which doesn't, and the PC can jam on it, and it will
                    now read.  It will at least read on disagreement.
                    "Suggest needn't be used in mid-ruds, since auditors don't
                    do it much.  Save it for prepchecks."

   INVALIDATE:      If a goal or item is invalidated, it will read, even when
                    it is not the goal or item.  Get the inval off and it will
                    no longer read.  Suppress on top of inval keeps the inval
                    from showing up.  That is why suppress goes first as a
                    button.

   FAIL TO REVEAL:  This button is off the line.  It gives you the dirty
                    needle, a minute rockslam.

   CAREFUL OF:      This is another suppress, with an added
                    characteristic: After the person has been having something
                    a little off-beat done for a little while, he can hang up
                    in the thing, if he becomes too careful of something or
                    other.  He can also make an item read by a reverse
                    suppression, by carefully not suppressing it, i.e. by
                    making sure it reads

The order of the buttons would be.:

     Suppress

     Suggest

     Careful of

     Invalidate

     Fail to reveal.

This is an optimum arrangement.  That puts the most important button last, as
far as session foul-ups are concerned.  This also gives you two cracks at
suppression.

     If these buttons are so strong, they must have some value.  They make
great prepcheck zero questions, as LRH found more or less by accident, while
cleaning up a PC who had been feeling poorly.

     The procedure for the Problems Intensive is as follows [See also p. 134
above and HCOB 9Nov61 "The Problems Intensive -- Use of the Prior Confusion",
as well as the current HCOB of 30Jul62].

     1. Sort out the chief self-determined change the PC has made, using
        assessment by elimination or greatest read.  For purposes of
        assessment, each change should be expressed in a few words plus a
        date.

     2. Get the confusion that preceded the change and date it.  Keep the PC
        to the just prior confusion.  This should be anywhere from five
        minutes to two weeks earlier.  Don't let the PC go "way back on the
        track.

     3. Go a month earlier, in case he didn't remember the overt that started
        the confusion.

     4. Prepcheck "Since (the above date)...."

When you use the above procedure, PCs are very willing to tell you things they
have suppressed.  Somatics come off also.  Don't also check mid-ruds on the
period you are prepchecking!

     You might think that you wouldn't reach basic on any chain by using the
above method of prepchecking, but since you are taking up the buttons in this
sequence and they seem like such innocent buttons, they clear away a lot of
track without your having to worry about fundamentals and basic.  Omitting the
withhold system left us with no way to get to basic.  It appears that, with
this system, you don't have to bother.  You could start in all over again, if
the PC had given It a shallow pass on the first time through, and pick up
deeper fundamentals.  However, the hazard in doing so is that you might be
cleaning a clean.  Also, be very sure not to leave a question unflat.  That is
very important, since in so doing you could give him missed withholds, and he
could blow or create a big storm and feel terrible.

     For a fifty-hour intensive, you could also do a prepcheck "In this
lifetime...."

     This system gets the PC's withholds easily and voluntarily.  Just be sure
to follow the rules.  And don't be an idiot: make sure the PC understands the
question!  To audit a small child, you might have to reword it to get it to
communicate.  On any PC, you want to be sure to communicate.  Know what you
are trying to communicate.  If you find the PC unable to answer or with very
few answers, don't blame it on the PC's caginess or unwillingness.  You have
to more the communication so it does bite.  If you do that, the prepcheck will
unstack the bank in its natural sequence, which is always desirable in sec
checking and prepchecking.  It is a very repetitive action.

     There is another way to use repetitive prepchecking:

     1. Sort out by assessment the person's self-determined decisions.  Get
        the most charged, old-time Problems Intensive style.  Make sure it is
        self-determined.

     2. Date the problem.

     3. Date the confusion prior to the decision found in (1).  The PC will
        slide away from the prior confusion if You don't keep him looking for
        it.  Don't let him find one five years before.  It is a just-prior
        confusion.

     4. Date the beginning of the prior confusion and go a month
        earlier.

     5. Prepcheck it "Since (date found in (4)...."

     A PC tends to see himself as a pawn on the board of life.  The liability
of taking an other-determined chain is that you will get into a chain of
engrams.  This system doesn't handle engrams, so watch it!  It is ok, however,
to get sometimes coming off.  On dating the prior confusion if you let the
date he a few years earlier, you will Miss it.  The prior confusion is the
period when he was creating the problem for which the decision is a solution.
The sequence for this

this mechanism is:

     1. The PC commits overts all over the place and has withholds missed on
        him like mad.

     2. This causes a problem for him.

     3. He makes a decision to solve the problem.  This is the self-determined
        change. [For more details, sec pp. 128-130, above.]

     All this is part of an effort to make prepchecking beefier and more
effective and far-reaching.  You might feel shy of doing a prepcheck if you
weren't pretty sure of getting a good result.  Somatics and conditions like
post-partum depression will blow, without your having to run engrams and getting the PC stuck in the incident. The success you will have will depend on the excellence of your meter reading, how thoroughly the PC is in session, and how well you clean up each question. Prepchecking is a relatively permissive system that gradiently lets the PC get himself into confrontable soup.  It doesn't overwhump the PC, but it must be
metered right.

