6307C10 SHSpec-282 Auditing Skills for R3R

[Some of the material in this tape is also to be found in HCOB 9Jul63 "A
Technical Summary: The Required Skills of Processing and Why".]

We have the exact number of skills necessary to make an OT.
Unfortunately they are not simple and they are numerous. But they break down
to about five skills, which must be perfect. They are:

1. The ability to follow an auditing cycle.

2. The ability to give it repetitively.

3. The ability to read a meter very well.

4. The ability to read, understand, and follow the procedure of a
bulletin.

5. The ability to get and keep a PC in session.

Any time an auditor cannot handle an upper-level procedure, it is because of
the fact that he cannot do one of these five basic things. As an auditing
supervisor, knowing this will enable you to get auditing done. If the auditor
cannot get results with a process, it is one of these skills, not the process,
is awry. No amount of persuasion will overcome the lack of one of these
skills.

You like to think that you are up against case level in training an
auditor. Low case level does make it harder to teach some people, but if you
make that a criterion of whether you can train someone, you will lose. There
is no case requirement for training. You mustn't Q and A with the "I can't"
of someone. If you make him do it, you make him right, not wrong. To agree
with the "I can't" is Q and A'ing with his aberration. The D of T must never
be permitted to refuse a student, because getting into the practice of doing
so leads to limiting who can be trained to the point where no auditing gets
done. When the instructor says, "Yes, you can't," The instructor is
invalidating the reactive mind, and the student's ability to audit
deteriorates rapidly. It takes some people a little longer to get towards
those basics and just do them, but if you keep at it, they will get there.

A complex technology like R3R will show up the weak points in any of your
five basics. For instance, given what you are handling in R3R, if you Q and
A, you get major bad reactions. 2 and A occurs when the auditor doesn't make
his intention stick in the session. He tends to become the effect of the PC.

The level of error is always stupidly elementary and has nothing to do
with what process you are running or how complicated that is. R3N and R3R
look very complicated. They have a lot of steps and lots of doingness. But
if you can do the basics of auditing, you will have no trouble. It is
fantastic to have a process that runs engrams by rote. All that can give you
real trouble in R3R is wrong date and wrong duration, which can result from
faulty meter reading, or faulty dating procedure. It is difficult for an
expert meter reader to get dates and durations of engrams. If the auditor
can't read the meter, well!! "Wrong date doesn't mean a minor wrongness. It
is something grossly wrong which rapidly snarls up the time track. Wrong date
produces bypassed charge and a grouped track. The BPC is fantastic. If a
person has his attention on a date or something, it will tick, once, on the
meter, even if it isn't the right date. Hence you can Q and A. You might say
that a dub-in case is just someone who has his dates mixed up. You could
probably cure dub-in by accurate dating.

Nothing drives the PC battier than to have a wrong duration. Say the
incident is really a trillion years long and you give him a duration of two
days. The PC tries in vain to find the beginning of the incident. He can't,
because he is looking at something that happened two days before, so it stays
all black and gruesome. When you get that phenomenon, you re-duration the
incident. What made R3R workable is that "a PC has perception on any incident
that is properly dated and durationed." That is where perceptics lie. There
are only three reasons for no perception:

1. Wrong date.

2. Wrong duration.

3. It has a GPM in it.

Wrong assessment and overrun (chain already flat) give you no TA, but not
necessarily no perception. The incident can get obscured if it has a GPM in
it because black energy goes up and obscures the engram. This was caused by
the PC's protest in the incident. When lights go off in an incident, look for
a GPM. If that happens, you have to get the PC to straighten out the GPM, by
taking him to the first pair of items in it. Get the motion out, pick up
another pair of items, get the TA motion off that pair, etc. Just clean it up
rapidly, then run it as an engram. It is never very long or very difficult to
run.

There is a point where R3R and R3N cross. Start the case on R3R and pick
up any implants that turned up while running R3R. Check for an implant on
the duration step. If you get onto the Helatrobus implant, clean them up!
Get the first pair of items and discharge them with rocket reads, etc., then
go back to R3R. Use R3N as the adjunct it is.

There are some technical details that you have to know. These include:

1. How to assess an ARC break.

2. What list(s) one should use.

3. Ability to do an accurate and thorough L and N, to a complete, but not
overlisted list.

The source of ARC breaks on lists is incompleteness of lists. You can,
however, assess a prepared, arbitrary list without fear of having the
"incomplete list phenomena" turn on, because the PC never started the list, so
it isn't complete. But in a regular list, in order to get the items, you do
have to be able to do L and N, which includes metering.

If you are having trouble with R3R, be sure that your difficulties do not
stem from troubles with getting in ruds or, say, writing while watching the
meter. Learn to audit by fundamentals, and you will have no trouble with a
procedure that just combines the fundamentals. Your main danger as an auditor
is being too complicated. Recognize that the simplicities of the game are
what make it hang together and work.

Wrong date and wrong duration are the only things that give you trouble.
Wrong assessment is very junior and generally just gives you no TA. Because
wrong date and wrong duration are such lies, it is difficult for the PC to
as-is them. And what happens to the track when you move to a wrong date?

It is very hard to get the right date and duration to read, even when the
PC is in session and you are on the right chain. Date is easier than
duration, because the beginning of the incident is so hard for PCs to see,
especially at the beginning. One source of a wrong assessment is overrun,
when you try to go earlier than basic.

Case Levels 5, 6, and 7 [See pp. 414-415, above.] all have a channel
through the bank on which the PC has reality, where he can be run on engrams
without dub-in, using R3R. So if you find that channel and run the PC in it,
the PC wins and can go on up.