   
   CLASS VIII CONFIDENTIAL COURSE PACK PART 6/16


CLASS VIII COURSE PACK

CONTENTS:

Part 6

60. HCOB   6 SEP 78 FOLLOWING UP ON DIRTY NEEDLES
61. HCOB  30 NOV 78 CONFESSIONAL PROCEDURE
62. HCOB  11 AUG 63 ARC BREAK ASSESSMENTS
63. HCOB  19 AUG 63 HOW TO DO AN ARC BREAK ASSESSMENT
64. HCOB   7 SEP 64 PTPs, OVERTS AND ARC BREAKS
65. HCOB  29 MAR 65 ARC BREAKS
66. HCOB   4 APR 65 ARC BREAKS AND MISSED WITHHOLDS
67. HCOB  19 JAN 66 DANGER CONDITIONS, TECHNICAL DATA FOR REVIEW AUDITORS
68. HCOB   1 AUG 68 THE LAWS OF LISTING AND NULLING
69. HCOB  23 SEP 68 VIOLATION OF THE LAWS OF LISTING AND NULLING
70. HCOB  15 OCT 73 NULLING AND F/Ning PREPARED LISTS
71. HCOB  13 SEP 67 REMEDY B
72. HCOB   9 NOV 67 REVIEW AUDITORS, BOOK OF CASE REMEDIES
73. HCOB   3 JUL 71 AUDITING BY LISTS REVISED


**************************************************

CLASS VIII CONFIDENTIAL COURSE PACK PART 6/16

**************************************************

60. HCOB   6 SEP 78 FOLLOWING UP ON DIRTY NEEDLES


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 6 SEPTEMBER 1978

Remimeo
Tech Staff
Qual Staff
HCOs
Confessional Courses
Level II Checksheets
All Auditors.
Supers. C/Ses

FOLLOWING UP ON DIRTY NEEDLES

(Ref: HCOB 3 Sep 78 DEFINITION OF A ROCK SLAM
HCOB 28 Jun 62 DIRTY NEEDLES
HCOB 17 May 69 TRs AND DIRTY NEEDLES
E-Meter Drills 17, 20, 21: THE BOOK OF E-METER DRILLS
TAPE: 6205C23 SH TVD-7 FISH &amp; FUMBLE, CHECKING DIRTY NEEDLES.)

_________

The only valid definition of a dirty needle is given in
HCOB 3 September 78, DEFINITION OF A ROCK SLAM, as:

&quot;DIRTY NEEDLE: AN ERRATIC AGITATION OF THE NEEDLE WHICH IS

RAGGED, JERKY, TICKING, NOT SWEEPING, AND TENDS

TO BE PERSISTENT. IT IS NOT LIMITED IN SIZE.&quot;

It is caused by one of three things: 1) the auditor's TRs
are bad or 2) the auditor is breaking the Auditor's Code or
3) the pc has withholds he does not wish known.

The definitions are pointed up in the above HCOB because it
is vital not to confuse a dirty needle with an R/S. They
are distinctly different reads. The difference is in the
character of the read: it has nothing to do with size.

Auditors, supervisors and C/Ses must understand the
difference between these two reads and must be able to
recognize each instantly when they occur.

Because of the underlying causes of these two different
types of reads they are both most apt to appear when
Confessionals are being done or when areas of O/Ws are
being addressed.

But they are different and the auditor must know the
difference cold.

A dirty needle must not be ignored especially when doing
any type of Confessional action.

If the auditor's TRs are in and he is maintaining the
Auditor's Code, a dirty needle, taken up, will either clean
or turn into an R/S. It is not to be overlooked.

The dirty needle is your hottest string to pull in finding
and turning on an R/S. Whatever is behind it, ignoring it
will cut the comm line between auditor and pc and wreck the
auditing comm cycle.

The area that is producing a dirty needle, when questioned
to get full data, will either clean or go into an R/S.

The area is considered clean when you can go over the area
that gave the dirty needle and it no longer produces a
dirty needle.

If it still produces a dirty needle then there is more to
the withhold itself or something the pc isn't voicing about
the withhold or how he feels about the withhold, or the
auditor's TRs are terrible, but-pursued and taken up with
auditor's TRs in- this dirty needle will either turn into
an R/S or it will fully clean. Until it does, however, it
is still a dirty needle.

The procedure for fishing a read is covered in AUDITING
DEMO TAPE 6205C23 SH TVD-7, &quot;FISH AND FUMBLE, CHECKING
DIRTY NEEDLES.&quot; Cleaning a dirty needle is covered in
E-Meter Drills 17, 20 and 21 as well, and Class II auditors
and above should be very adept at this.

The rule is: DON'T IGNORE DIRTY NEEDLES. ALWAYS FOLLOW THEM UP.

L. RON HUBBARD
Founder

LRH:mf
Copyright  1978
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

61. HCOB  30 NOV 78 CONFESSIONAL PROCEDURE


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 30 NOVEMBER 1978

(Cancels BTB 31 Aug 72RB,
Auditors Confessional Procedure)

C/Ses
Tech/Qual 
HCOs
Confessional Courses Checksheets 


CONFESSIONAL PROCEDURE


(Ref: 
HCOB 5 Aug 78 INSTANT READS
HCOB 28 Feb 71 C/S Series 24 IMPORTANT, METERING READING ITEMS
HCOB 8 Feb 62 URGENT, MISSED WITHHOLDS
HCOB 12 Feb 62 HOW TO CLEAR WITHHOLDS AND MISSED WITHHOLDS
HCOB 3 May 62R ARC BREAKS, MISSED WITHHOLDS Rev. 5.9.78
HCOB 11 Aug 78 I RUDIMENTS, DEFINITIONS &amp; PATTER
HCOB 20 Sep 78 AN INSTANT F/N IS A READ Rev. 9.10.78
HCOB 14 Mar 71R F/N EVERYTHING Corr. &amp; Rev. 25.7.73
HCOB 3 Sep 78 URGENT, URGENT, URGENT, DEFINITION OF A ROCK SLAM
HCOB 10 Aug 76R R/Ses, WHAT THEY MEAN Rev. 5.9.78
HCOB 17 May 69 TRs AND DIRTY NEEDLES
HCOB 6 Sep 78 FOLLOWING UP ON DIRTY NEEDLES
BTB 8 Dec 72RC CONFESSIONAL REPAIR LIST Re-rev. 4.6.77 (LCRC)
HCOB 10 Nov 78R PROCLAMATION: POWER TO FORGIVE
HCOB 10 Nov 78R-I PROCLAMATION: POWER TO FORGIVE-ADDITION Add. 26.11.78 
HCOB 28 Nov 78 AUDITORS WHO MISS WITHHOLDS, PENALTY
BOOK: THE BOOK OF E-METER DRILLS. 
SEC CHECKING HCOBs.
SEC CHECKING TAPES and TAPE DEMOS since 1961.)

___________

&quot;Sec Checking,&quot; &quot;Integrity Processing&quot; and &quot;Confessionals&quot;
are all the exact same procedure and any materials on these
subjects is interchangeable under these titles (HCOB 24 Jan
1977 TECH CORRECTION ROUND-UP )

Withholds don't just add up to withholds They add up to
overts, they add up to secrecies, they add up to
individuations, they add up to games conditions, they add
up to a lot more things than O/W.

You are straightening out somebody on a moral code, the
&quot;Now I'm supposed to's.&quot; They've transgressed on a series
of &quot;Now I'm supposed to's.&quot; Having so transgressed, they
are now individuated. If their individuation is too
obsessive, they snap in and become the



terminal. All of these cycles exist around the idea of the
transgression against the &quot;Now I'm supposed to's.&quot; That is
what a Confessional clears up and that is all it clears up.
It's a great deal more than a withhold. (HCOB 1 March 77,
Iss III, FORMULATING CONFESSIONAL QUESTIONS.)

PROCEDURE

A Confessional must be done by someone who is a well
trained auditor, skilled in TRs, basic auditing and
metering, who can make a prepared list read, and who has
been fully checked out and drilled on these techniques.

Every reading question of a Confessional is F/Ned. The
original question must be taken to F/N, not some other
question.

Here is the basic procedure for a Confessional:

1. Set up the room with the auditor seated closer to the
door than the pc, so that he can gently put the pc back in
his chair if he tries to blow the session. Ensure all the
necessary materials are to hand, per HCOB 4 Dec 77,
CHECKLIST FOR SETTING UP

SESSIONS AND AN E-METER.

2. Make sure the person is well fed and well rested, that
his hands are not too dry or moist, that the cans are the
correct size and that the person knows how to hold them.
Include all the steps of HCOB 4 Dec 77, CHECKLIST FOR
SETTING UP SESSIONS AND AN

E-METER. (Also ref: FALSE TA HCOBs.)

3. Start the Confessional. Model Session and rudiments are
used. Ref: HCOB 11 Aug 78, Iss II, MODEL SESSION. If the TA
is high or low, do a C/S Series 53RL, assess and handle. If
you are not trained in doing a C/S Series 53, end off for
C/S instruction.

4. Put in any needed R-Factor on doing the Confessional.
Briefly explain the meter and the procedure to the person
if they are not already known to him or her.

The term &quot;I am not auditing you&quot; only occurs when a
Confessional is done for justice reasons. Otherwise the
procedure is the same. (By &quot;justice reasons&quot; is meant when
a person is refusing to come clean on a Comm Ev, B of I,
etc., or as part of a specific HCO investigation when the
person is withholding data or evidence from such HCO
personnel.)

A Confessional done for justice reasons is not auditing and
the data uncovered is not withheld from the proper
authorities. Any other Confessional is auditing and is kept
confidential.

By F/Ning each question that reads, and by the use of
Examiner and review, there is a great deal of case gain in
a Confessional. It permits the person to again feel a part
of his group.

5. Clear the procedure and the use of the buttons
&quot;Suppress&quot; and &quot;False&quot; etc. If necessary as an example run
a non-significant question to demonstrate the procedure
(e.g. &quot;Have you ever eaten an apple?&quot;).

6. Take up the first question and clear the words
backwards. Then clear the full command, noting any instant
read that occurs on the command while clearing, as this is
valid. See HCOB 9 Aug 78 Iss II, CLEARING COMMANDS, HCOB 28
Feb 71, C/S Series 24,

IMPORTANT, METERING READING ITEMS, and HCOB 5 Aug 78, INSTANT
READS.

Ensure the pc fully understands the question and what it
encompasses.

7. With good TR 1 give the person the first question,
keeping an eye on the meter and noting any instant read,
i.e. SF, F., LFBD. (Ref: HCOB 5 Aug 78, INSTANT READS.) A
tick is always noted and in some cases becomes a wide read.
(Ref: HCOB 28 Feb 71, C/S Series 24, IMPORTANT, METERING
READING ITEMS.) But don't assume you

have a read because you get a tick. Put in Suppress and it
will either read or the tick will vanish. In a
Confessional, even the smallest change of needle
characteristic, if it is instant, is checked into before
you go on. But NOTE: YOU DON'T TAKE A RISE AS A CHANGE OF
CHARACTERISTIC IN SEC CHECKING.

8. Take up each reading question, getting the what, when,
where, all of every overt. Find out who missed it or who
nearly found out, and what that person did to make the pc
wonder if he knew. Get specifics, not general or vague
answers. If no F/N, take the overt E/S to F/N. And ensure
that the original question that read is taken to F/N before
you leave it.

9. For security investigation purposes, get all the exact
names, dates, addresses, phone numbers, and any other
information that might be helpful in investigating the case
further, should this be needed.

10. If the pc gives you three or four overts at once in
reply to a reading question, you note them and ensure you
take each separate reading overt or withhold to an F/N, or
E/S to F/N.

11. Some people you have to ask the exact question. If your
question is even faintly off they F/N. Low responsibility
of the pc does this.

12. If the person gives off another's overt, ask if he ever
did something like that. You want what the person himself
has done.

13. DO NOT TAKE UP UNREADING QUESTIONS.

a) If a question does not read and does not F/N you can put
in the buttons Suppress and Invalidate, asking:

&quot;On the question________ has anything been suppressed?&quot;

&quot;On the question________ has anything been invalidated?&quot;

But don't require it to be answered and don't look up at
the pc expectantly either. If it's not reading, tell him so
and go on.

b) If Suppress or Invalidate reads, it means the read has
transferred exactly from the Confessional question to the
button. (Ref: HCOB 1 Aug 68, THE LAWS OF

LISTING &amp; NULLING.) Put in the button (simply get what the
pc has to say and acknowledge), then take up the question.
Fully clean the question, as in No. 8 above. Then go on to
the next question.

c) Or, if the question reads and the pc is trying to answer
it and is groping, puzzling, baffled and doesn't have any
answer, then check False. Ask: &quot;Was that a false read?&quot;, in
which case it will read and on indication that it was a
false read will now F/N. If no F/N, E/S to F/N.

14. FOLLOW UP FULLY ON ANY DIRTY NEEDLE. A dirty needle
will either clean or turn into an R/S. It is your hottest
string to pull in finding and turning on an R/S. Thus it is
not to be overlooked. The area that is producing a dirty
needle when questioned for full data will either clean or
go into an R/S. The area that gave the dirty needle is
considered clean when you can go over it and it no longer
produces a dirty needle. If a dirty needle still persists
then there is more to the withhold itself or something the
pc isn't voicing about the withhold or how he feels about
the withhold. But, pushed. with auditor's TRs in, this
dirty needle will turn into an R/S or it will fully clean.

(Ref: HCOB 6 Sept 78, FOLLOWING UP ON DIRTY NEEDLES, and 
HCOB 17 May 69, TRs AND DIRTY NEEDLES.)

The auditor MUST know COLD the difference between an R/S
and a dirty needle. The difference is in the character of
the read NOT the size. (Ref: HCOB 3 Sept 78, URGENT,
URGENT, URGENT, DEFINITION OF A ROCK SLAM.)

A Confessional is not a rote procedure. Your job is to get
the data and help the pc.

Sometimes you will be thrown curves or may encounter
attempts to be led off in the wrong direction. This is
simply a sure indicator the subject is withholding and that
the withhold is in restimulation. One has to ignore the
volunteer misdirections of the pc as the pc is of course
misdirecting, and simply get the read E/Sed or the W/H
F/Ned. You must use your tools as given in HCOBs, Sec
Checking tapes and tape demonstrations since 1961.

15. TAKE THE ORIGINAL READING QUESTION TO F/N. Not some
other question.

This all comes under the heading of completing cycles of
action and getting one auditing question answered before
you ask a second question.

In going earlier similar to take the question to F/N,
always repeat the Confessional question as part of the
earlier similar command to keep the person on that question.

Example: &quot;Is there an earlier similar time you ate an apple?&quot;

16. On each question be sure you get all the overts. When
you have taken a specific chain of overts earlier similar
to F/N, then re-check the original question for any read.
If it F/Ns, fine. It's clean.

If it reads you have another overt or overt chain to clear
to F/N on that question. Use False and Protest buttons as
needed.

Example:

Question A: &quot;Have you committed any overts against apples?&quot;
Meter reads. Auditor gets an overt, takes it E/S to F/N.
Auditor then re-checks Question A. Meter reads. Pc finds
another overt against apples. Auditor takes it E/S to F/N.

You clean it, getting all, until the original question F/Ns.

(Ref: HCOB 14 Mar 71R Corr &amp; Rev 25 Jul 73, F/N EVERYTHING
HCOB 19 Oct 61, SECURITY QUESTIONS MUST BE NULLED HCOB 10
May 62, PREPCHECKING

AND SEC CHECKING.)

17. If the person gets critical, realize you have missed a
withhold and pull it. It is no light thing to miss
withholds and mess up a pc when doing a Confessional. So be
alert for any of the 15 manifestations of missed withhold
and handle fully should any of these crop up.

(Ref: HCOB 8 Feb 62, URGENT, MISSED WITHHOLDS, HCOB 12 Feb 62, HOW
TO CLEAR WITHHOLDS AND MISSED WITHHOLDS, HCOB 3 May 62R Rev 5 Sep
78, ARC BREAKS, MISSED WITHHOLDS, HCOB 11 Aug 78 Iss I, RUDIMENTS,
DEFINITIONS AND PATTER.)

It is wise, particularly when doing a Confessional of any
length, to periodically check the question, &quot;In this
session has a withhold been missed?&quot; or &quot;Have I missed a
withhold on you?&quot;.

18. At the first sign of any trouble in doing a
Confessional check for: missed withholds, false reads and
ARC breaks, in that order, and fully handle what you get.
In the majority of cases the above buttons should resolve
the difficulty.

If not, handle with an LCRC (BTB 8 Dec 72RC, CONFESSIONAL
REPAIR LIST).

Use of the above buttons first, however, before resorting
to the LCRC, avoids the possibility of getting into an
&quot;overrepair&quot; situation.

19. If the pc consistently immediately dives whole track on
Confessional questions, use the preface &quot;In this lifetime .
. .&quot;, with good R-Factor. This should not be used to
prevent him going whole track on the earlier similar
command to F/N the question.

20. ONE MUST ALWAYS REPORT A ROCK SLAM IN THE AUDITING REPORT,
NOTE IT WITH SESSION DATE AND PAGE INSIDE THE LEFT COVER OF THE
PC'S FOLDER AND REPORT IT TO ETHICS INCLUDING THE QUESTION OR
SUBJECT WHICH ROCK SLAMMED, PHRASED EXACTLY. (HCOB 10 Aug 76R,
Rev 5 Sep 78, R/Ses, WHAT THEY MEAN.)

As the R/S is probably the single most important and
dangerous read on the meter, it is important that they are
carefully noted when doing a Confessional.

For a pc to be branded as an R/Ser is a very serious thing.
Also for a real R/Ser to be overlooked by an auditor is a
catastrophe both to the pc and to those around that
particular person. (Ref: HCOB 24 Jan 77, TECH CORRECTION
ROUND-UP. )

Valid R/Ses are not always instant reads. An R/S can read
prior or latently. (HCOB 3 Sep 78, URGENT, URGENT, URGENT,
DEFINITION OF A ROCK SLAM.)

21. If you want a pc to stop fiddling with the cans you
make them put their hands on the table and keep them there.

22. HCO or executives may request a Confessional be done
but neither Tech nor Qual are bound by such requests as an
FES could reveal that the trouble stems from &quot;out-lists&quot; or
other matters needing correction. They should however take
cognizance of such requests and do all possible to get the
person handled.

23. If a reading question does not go to F/N and bogs or
the TA goes high, take up an LCRC (Confessional Repair
List, BTB 8 Dec 72RC), assess and handle per instructions.

24. End off any Confessional session and the entire
Confessional itself, when complete, with the rudiments
which would pick up anything which might have been missed:
Half Truth, Untruth, Missed Withhold, Told All, etc. Use
the prefix &quot;In this session . . .&quot; or &quot;In this Confessional
. . .&quot;. Take any reading rudiment E/S as needed to F/N.

25. When the Confessional is fully completed, the auditor
who has administered the Confessional informs the person he
is forgiven for the overts and withholds he has just
confessed, using the following statement:

&quot;By the power invested in me, any overts and withholds you
have fully and truthfully told me are forgiven by
Scientologists.&quot;

The usual response of the pc is instant relief and VGIs. On
any adverse reaction to the Proclamation of Forgiveness,
get the rest of the withhold or repair the Confessional
session at once.

(Ref: HCOB 10 Nov 78 R. PROCLAMATION: POWER TO FORGIVE HCOB 10 Nov
78R-1, Addition of 26 Nov 78, PROCLAMATION: POWER TO FORGIVE-
ADDITION.)

26. All worksheets are routed to Tech Services so they can
be included in the person's pc folder. (Ref: HCOB 28 Oct
76, C/S Series 98, AUDITING FOLDERS, OMISSIONS IN
COMPLETENESS.)

27. EXAMINER. All Confessionals must be followed
immediately by a standard pc examination. The folder is
then routed to the C/S.

The C/S looks for any nonsequitur F/N on some other
subject. It's the primary thing he inspects.

If a person falls on his head after a Confessional session
an LCRC is given. However, an FES to find missing questions
that F/Ned on something else is done. Standard C/S rules
apply to Confessionals.

28. On any bad Exam Report (non-F/N, BIs or nonoptimum
statement) after a Confessional, or on any person who gets
sick or upset or does not do well or has a high or low TA,
give an LCRC as the very next action.

The 24-hour red tag rule must be strictly enforced.

AUDITOR ATTITUDE AND TRs

If the pc is not in session you won't get the withholds.
TRs play a large part in the pc being willing to talk to
the auditor. A wrong or challenging auditor attitude can
throw the scene off as there is a destroyed comm cycle. If
TRs are rough or choppy the pc feels he's being accused.

A poor or comm lag TR 2, hidden from the view of the C/S,
can also mess up a person in a Confessional. It invalidates
his answers and makes him feel he hasn't gotten it off. If
suspected, this could be checked by D of P interview or
person to the Examiner for: &quot;What did the auditor do?&quot;
(Also see HCOB 16 Aug 71R Iss II, Rev 5 Jul 78, TRAINING
DRILLS REMODERNIZED.)

So TRs must be polished and the auditor, while maintaining
good ethics presence, takes the role of confessor when
handling the pc's answers and makes it safe for the pc to
get off his overts and withholds. Similarly, an auditor who
is certain of his tech and does not miss withholds will
build the pc's confidence in him.

Anyone doing a Confessional should be fully trained and
interned by doing a course and interneship in the handling
of Confessionals.

You had better determine to become an expert in it, since
an auditor's inability to handle this is a fast route to
&quot;how to win enemies and wrongly influence people.&quot; (HCOB 24
Jan 77, TECH CORRECTION ROUND-UP.)

But even more important is the fact that, in knowing and
applying Confessional tech correctly, you are helping the
individual to face up to his responsibilities in his group
and the society and putting him back into communication
with his fellow man, his family, and the world at large.

L. RON HUBBARD
Founder

LRH:jk/clb
Copyright  1978
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

62. HCOB  11 AUG 63 ARC BREAK ASSESSMENTS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 11 AUGUST 1963

Central Orgs
Franchise

ARC BREAK ASSESSMENTS

In a session don't ever do an ARC Break Assessment until
the pc has given up trying to untangle it. This
particularly applies to R3R and 3N.

DATES R2H

Don't ever date anything for the pc until the pc has
completely given up trying himself.

DON'T USE METERING, ARC BREAK ASSESSMENTS, DATING, or

incomprehensible or new commands to CUT THE ITSA LINE. Let
it run. Help only when it's stopped.

L. RON HUBBARD

LRH :dr jh
Copyright  1963
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

63. HCOB  19 AUG 63 HOW TO DO AN ARC BREAK ASSESSMENT


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 19 AUGUST AD13

Central Orgs
Franchise

SCIENTOLOGY TWO

STAR RATED HCO BULLETIN

HOW TO DO AN ARC BREAK ASSESSMENT

(HCO Secs: Check out on all technical Executives and
Personnel. Tech Dir: Check out on HCO Secs and Assn Org Secs.)

The successful handling of an ARC Break Assessment is a
skilled activity which requires: 1. Skill in handling a Meter.

2. Skill in handling the Itsa Line of the Auditing Cycle.

3. Skill in Assessment.

The lists given in HCO Bulletin of July 5, AD13 &quot;ARC BREAK
ASSESSMENTS&quot;, are used, either from that HCO Bulletin or
amended.

There are several uses for ARC Break Assessments.

1. Cleaning up a session ARC Break.

2. Cleaning up auditing in general.

3. Cleaning up a pc's or student's possible ARC Breaks.

4. Cleaning up a member of the public's possible or actual
ARC Breaks.

5. Regular use on a weekly basis on staff or organization members.

There are others. Those above are the chief uses.

For long time periods the standard 18 button prepcheck is
faster, but an ARC Break Assessment is still useful in
conjunction with it.

The drill is simple. If complicated by adding in R2H
material, dating, and other additives, the ARC Break
Assessment ceases to work well and may even create more ARC
Breaks.

If used every time a pc gets in a little trouble in R3N or
R3R the ARC Break Assessment is being used improperly. In
R2H, R3N, R3R sessions it is used only when the pc shows
definite signs of an ARC Break. To use it oftener
constitutes no auditing.

Unnecessary use of an ARC Break Assessment may ARC Break
the pc with the Assessment.

The ARC Break Assessment may be repaired by an 18 Button
Prepcheck &quot;On ARC Break Assessments ......&quot;.

ARC BREAK ASSESSMENT BY STEPS

STEP ONE:

Select the proper list. This is done by establishing what
the pc has been audited on. If more than one type of
by-passed charge is suspected, do more than one list. If
the ARC Break is not completely cured by one list, do another 
kind of list. (All lists have been in HCOBs as &quot;L&quot;.)

STEP TWO:

Inform the pc that you are about to assess for any charge
that might have been restimulated or by-passed on his or
her case. Do not heavily stress the ARC Break aspect.

Right: &quot;I am going to assess a list to see if any charge
has been by-passed on your case.&quot; Wrong: &quot;I'm going to try
to cure (or assess) your ARC Break.&quot;

STEP THREE:

Without regard to pc's natter, but with quick attention for
any cognition the pc may have during assessment as to
by-passed charge, assess the list.

Phrase the question in regard to the reason for the
Assessment-&quot;In this session........&quot; &quot;During this week
......&quot; &quot;In Scientology ........&quot; etc. Call each line once
to see if it gives an instant read.

The moment a line gives a reaction, stop, and do Step Four.

STEP FOUR:

When a line reacts on the needle, say to the pc, &quot;The line
.......reacts. What can you tell me about this?&quot;

STEP FIVE:

Keep Itsa Line in. Do not cut the pc's line. Do not ask for
more than pc has. Let pc flounder around until pc finds the
charge asked for in Step Four or says there's no such charge.

(If a line reacted because the pc did not understand it, or
by protest or decide, make it right with the pc and
continue assessing.)

STEP SIX:

In a session: If pc found the by-passed charge, ask pc &quot;How
do you feel now?&quot; If pc says he or she feels OK, cease
assessing for ARC Breaks and go back to session actions. If
pc says there's no such charge or gets misemotional at
Auditor, keep on assessing on down the list for another
active line, or even on to another list until the charge is
found which makes pc relax.

In a routine ARC Break check (not a session but for a
longer period), don't stop assessing but keep on going as
in Step Five, unless pc's cognition is huge.

END OF STEPS

Please notice: This is not R2H. There is no dating. The
auditor does not further assist the pc with the meter in
any way.

If the pc blows up in your face on being given a type of
charge, keep going, as you have not yet found the charge.
Typical response to wrong charge found: Pc: &quot;Well of course
it's a cut communication! You've been cutting my
communication the whole session. You ought to be retreaded
. etc.&quot; Note here that pc's attention is still on auditor.
Therefore the correct charge has not been found. If the
by-passed charge has been found the pc will relax and look
for it, attention on own case.

Several by-passed charges can exist and be found on one
list. Therefore in cleaning up a week or an intensive or a
career (any long period) treat a list like rudiments,
cleaning everything that reacts.

Blow down of the Tone Arm is the meter reaction of having
found the correct by-passed charge. Keep doing Steps One to
Six until you get a blow down of the Tone Arm. The pc
feeling better and being happy about the ARC Break will
coincide almost always with a Tone Arm Blow Down.

You can, however, undo a session ARC Break Assessment by
continuing beyond the pc's cognition of what it is.
Continuing an assessment after the pc has cognited,
invalidates the pc's cognition and cuts the Itsa Line and
may cause a new ARC Break.

Rarely, but sometimes, the ARC Break is handled with no TA
blow down.

PURPOSE OF ASSESSMENT

The purpose of an ARC Break Assessment is to return the pc
into session or into Scientology or into an Org or course.
By-passed charge can cause the person to blow out of
session, or out of an Org or a course or Scientology.

WITH A SESSION (formerly &quot;in&quot;): Is defined as &quot;INTERESTED
IN OWN CASE AND WILLING TO TALK TO THE AUDITOR&quot;. AGAINST
SESSION: Against session is defined as &quot;ATTENTION OFF OWN
CASE AND TALKING AT THE AUDITOR IN PROTEST OF

AUDITOR, PT AUDITING, ENVIRONMENT OR SCIENTOLOGY&quot;.

WITH SCIENTOLOGY: With Scientology is defined as
&quot;INTERESTED IN SUBJECT AND GETTING IT USED&quot;. AGAINST
SCIENTOLOGY: Against Scientology is defined as &quot;ATTENTION
OFF SCIENTOLOGY AND PROTESTING SCIENTOLOGY BEHAVIOUR

OR CONNECTIONS&quot;.

WITH ORGANIZATION: With organization can be defined as
&quot;INTERESTED IN ORG OR POST AND WILLING TO COMMUNICATE WITH
OR ABOUT ORG&quot;. AGAINST

ORGANIZATION: Against organizationness is defined as
&quot;AGAINST ORGANIZATION OR POSTS AND PROTESTING AT ORG
BEHAVIOUR OR EXISTENCE&quot; .

The data about ARC Breaks can be expanded to marriage,
companies, jobs, etc. Indeed to all dynamics-With Dynamic,
Against Dynamic.

What it boils down to is this: There are only two
conditions of living, but many shades of grey to each one.

These conditions are:

1. LIFE: NOT ARC BROKEN: Capable of some affinity for, some
reality about and some communication with the environment; and

2. DEATH: ARC BROKEN: Incapable of affinity for, reality about and

communication with the environment.

Under One we have those who can disenturbulate themselves
and make some progress in life.

Under Two we have those who are in such protest that they
are stopped and can make little or no progress in life.

One, we consider to be in some ARC with existence.

Two, we consider to be broken in ARC with existence.

In a session or handling the living lightning we handle,
people can be hit by a forceful charge of which they are
only minutely aware but which swamps them. Their affinity,
reality and communication (life force) is retarded or cut
by this hidden charge and they react with what we call an
ARC Break or have an ARC Broken aspect.

If they know what charge it is they do not ARC Break or
they cease to be ARC Broken.

It is the unknown character of the charge that causes it to
have such a violent effect on the person.

People do not ARC Break on known charge. It is always the
hidden or the earlier charge that causes the ARC Break.

This makes life look different (and more understandable).
People continuously explain so glibly why they are acting
as badly as they are. Whereas, if they really knew, they
would not act that way. When the true character of the
charge (or many charges as in a full case) is known to the
person the ARC Break ceases.

How much by-passed charge does it take to make a case? The
whole sum of past by-passed charge.

This fortunately for the pc is not all of it in constant
restimulation. Therefore the person stays somewhat in one
piece but prey to any restimulation.

Auditing selectively restimulates, locates the charge and
discharges it (as seen on the action of a moving Tone Arm).

However, accidental rekindlings of past charge unseen by pc
or auditor occur and the pc &quot;mysteriously&quot; ARC Breaks.

Similarly people in life get restimulated also, but with
nobody to locate the charge. Thus Scientologists are lucky.

In heavily restimulated circumstances the person goes OUT
OF. In such a condition people want to stop things, cease
to act, halt life, and failing this they try to run away.

As soon as the actual by-passed charge is found and
recognized as the charge by the person, up goes Affinity
and Reality and Communication and life can be lived.

Therefore ARC Breaks are definite, their symptoms are
known, their cure is very easy with this understanding and
technology.

An ARC Break Assessment seeks to locate the charge that
served, being hidden, as a whip-hand force on the person.
When it is located life returns. Locating the actual
by-passed charge is returning life to the person.

Therefore, properly handling ARC Breaks can be called, with
no exaggeration &quot;Returning Life to the person&quot;.

One further word of caution: As experience will quickly
tell you, seeking to do anything at all with an earlier
by-passed charge incident which led to the ARC Break
immediately the earlier incident is found will lead to a
vast mess.

Let the pc talk about it all the pc pleases. But don't
otherwise try to run it, date it or seek to find what
by-passed charge caused the earlier incident. In assessing
for ARC Breaks, keep the Itsa Line in very well and keep 
the What's It out in every respect except as contained in 
the above Six Steps.

SUMMARY

An ARC Break Assessment is simple stuff, so simple people
are almost certain to complicate it. It only works when
kept simple.

Old auditors will see a similarity in an ARC Break
Assessment List and old end rudiments. They can be handled
much the same but only when one is covering a long time
period. Otherwise assess only to cognition and drop it.

The trouble in ARC Break Assessments comes from additives
by the auditor, failure to keep on with additional lists if
the type of charge causing the ARC Break isn't found on the
first list chosen, failure to read the meter, and failure
to keep the Itsa Line in.

Doing ARC Break Assessments to cure ARC Breaks is not the
same drill as R2H and confusing the two leads to trouble.

Handled skillfully as above, ARC Break Assessing cures the
great majority of woes of auditing, registraring, training
and handling organization. If you find you aren't making
ARC Break Assessments work for you check yourself out on
this HCO Bulletin carefully, review your meter reading and
examine your handling of the Itsa Line. If you want live
people around you, learn to handle ARC Break Assessments.

Don't worry about pcs getting ARC Breaks. Worry about being
able to cure them with assessment until you have confidence
you can. There's nothing so uplifting as that confidence,
except perhaps the ability to make any case get TA motion.

Don't ever be &quot;reasonable&quot; about an ARC Break and think the
pc is perfectly right to be having one &quot;because ......&quot;. If
that ARC Break exists, the pc doesn't know what's causing
it and neither do you until you and the pc find it! If you
and the pc knew what was causing it, there would be no
further ARC Break.

L. RON HUBBARD

LRH:dr.cden 
Copyright  1963
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

64. HCOB   7 SEP 64 PTPs, OVERTS AND ARC BREAKS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 7 SEPTEMBER 1964
Issue II

Remimeo
Franchise
Sthil Students

ALL LEVELS

PTPs, OVERTS AND ARC BREAKS

Just to remind you, other auditing is not possible in the
presence of Present Time Problems and Overts. No auditing
is possible in the presence of an ARC Break.

These are data like &quot;Acknowledge the pc&quot;, &quot;An auditor is
one who listens&quot; etc. These belong in the ABCs of Scientology.

PRESENT TIME PROBLEMS

When a pc has a PTP and you don't handle it, you get no
gain. There will be no rise on a personality test graph.
There will be little if any TA action. There will be no
gain in the session.

The pc will not make his session goals. Etc. Etc. So you
don't audit pcs who have PTPs on anything but the PTPs the
pc has.

And you don't audit PTPs slowly and forever. There are
numerous ways of handling PTPs. One of them is &quot;What
communication have you left incomplete about that problem?&quot;
A few answers and poof! no PTP. Another is &quot;What doesn't
(that person or thing pc is having PTP with) know about
you?&quot; Other versions of overts and withholds can be used.
These are all fast PTP handling methods and they get rid of
the PTP and you can audit what you started to audit.

The mark of a ruddy amateur in auditing is somebody who can
always do successful assists but can't do a real session.
The secret is: in an assist you are handling the PTP,
aren't you? So you never audit over the top of (in the
presence of) a PTP!

Another circumstance is &quot;can't get down to real auditing
because the pc always has so many PTPs&quot;. This is only a
confession that one can't handle a PTP and then get on with
the session. One fumbles with the PTPs so badly as an
auditor one never really handles the pc's PTPs so of course
one never gets on with the job at hand-auditing the pc.

The pro, in a real session, just handles the PTPs quickly,
gets the pc into session and gets on with whatever should
be run.

OVERTS

Overts are the other principal source of getting no gain.

Here we really can tell the goony birds from the eagles
professionally.

No pro would think of auditing a pc on other processes in
the presence of overts.

1. The Pro would recognize by the pc's natter, or lack of
previous gain, that the pc had overts;

2. The Pro would know that if he tried to do something else
besides pull these overts, the pc would eventually get
critical of the auditor; and

3. The Pro wouldn't (a) fail to pull the real overts or (b)
ARC Break the pc in getting the overts off.

If one gets &quot;reasonable&quot; about the pc's condition and
starts agreeing with the motivators (&quot;look at all the bad
things they did to me&quot;), thus ignoring the overts, that's
the end of gains for that pc with that auditor.

If one is clumsy in recognizing overts, if one fails to get
the pc to give them up, if one fails to properly
acknowledge the overt when given, or if one demands overts
that aren't there, overt pulling becomes a howling mess.

Because, then, getting the pc overts off is a tricky
business auditors sometimes become shy of doing it. And
fail as auditors.

Sometimes pcs who have big overts become highly critical of
the auditor and get in a lot of snide comments about the
auditor. If the overt causing it is not pulled the pc will
get no gains and may even get ARC broken. If the auditor
doesn't realize that such natter always indicates a real
overt, when pcs do it, eventually over the years it makes
an auditor shy of auditing.

Auditors buy &quot;critical thoughts&quot; the pc &quot;has had&quot; as real
overts, whereas a critical thought is a symptom of an
overt, not the overt itself. Under these critical thoughts
a real overt lies undetected.

Also, I love these pcs who &quot;have to get off a withhold
about you. Last night Jim said you were awful ........&quot; An
experienced auditor closes the right eye slightly, cocks
his head a bit to the left and says, &quot;What have you been
doing to me I haven't known about?&quot; &quot;I thought .....&quot;
begins the pc. &quot;The question is&quot;, says the old pro, &quot;What
have you been doing to me that I don't know about. The word
is doing. &quot; And off comes the overt like &quot;I've been getting
audited by Bessy Squirrel between sessions in the Coffee Shop.&quot;

Well, some auditors are so &quot;reasonable&quot; they never really
learn the mechanism and go on getting criticized and
getting no gains on pcs and all that. I once heard an
auditor say &quot;Of course he was critical of me. What he said
was true. I'd been doing a terrible job.&quot; The moral of this
story is contained in the fact that this auditor's pc died.
A rare thing but a true one. The pc had terrible overts on
Scientology and the auditor, yet this auditor was so
&quot;reasonable&quot; those overts were never cleaned up. And that
was the end of those auditing sessions.

It's almost never that drastic, but if an auditor won't
pull overts, well auditing gets pretty unpleasant and
pretty pointless too.

A lack of grasp of the overt-motivator sequence (when
somebody has committed an overt, he or she has to claim the
existence of motivators-the Ded-Dedex version of
Dianetics-or simply when one has a motivator he is liable
to hang himself by committing an overt) puts an auditor at
a very bad disadvantage. Howling pcs and no pc wins.

ARC BREAKS

You can't audit an ARC Break. In fact you must never audit
in the presence of one.

Auditing below Level III, the best thing to do is find an
auditor who can do ARC Break Assessments.

At Level III and above, do an ARC Break Assessment on the
pc. An ARC Break Assessment consists of reading an ARC
Break list appropriate to the activity to the pc on a
meter and doing nothing but locate and then indicate the
charges found by telling the pc what registered on the needle.

That isn't auditing because it doesn't use the auditing
comm cycle. You don't ack what the pc says, you don't ask
the pc what it is. You don't comm. You assess the list
between you and the meter, same as no pc there. Then you
find what reads and-you tell the pc. And that's all.

A by-passed charge assessment is auditing because you clean
every tick of the needle on the list being assessed. The pc
is acked, the pc is permitted to Itsa and give his
opinions. But you never do a by-passed charge assessment on
an ARC Broken pc. You do an ARC Break Assessment as per the
paragraph above this one.

These two different activities unfortunately have the word
&quot;assessment&quot; in common and they use the same list.
Therefore some students confuse them. To do so is sudden death.

You can really clobber a pc by doing a by-passed charge
assessment on an ARC Broken pc. And also you can ARC Break
a pc by doing an ARC Break Assessment on a pc who isn't (or
has ceased to be) ARC Broken.

So unless you have these two separate and different
actions-the ARC Break Assessment and the by-passed charge
assessment-clearly understood and can do both of them well
and never get too rattled to know which one to use, you can
get into plenty of trouble as an auditor.

Only auditing over the top of an ARC Break can reduce a
graph, hang the pc up in sessions or worsen his case. So
it's the next to the most serious blunder that an auditor
can make. (The most serious error is to deny assistance
either by not trying to get the pc into session or not
using Scientology at all.)

Auditing an ARC Broken pc and never realizing it can lead
to very serious trouble for the auditor and will worsen the
pc's case-the only thing that will.

SUMMARY

It is elementary auditing knowledge that no gains occur in
the presence of PTPs or overts and that cases worsen when
audited over the top of an ARC Break.

There aren't &quot;lots more conditions that can exist&quot;. Given
an auditing session there are only these three barriers to
auditing.

When you do Clay Table auditing or any other kind of
auditing the rules all still apply. A change of process or
routine doesn't change the rules.

In doing Clay Table auditing off a meter one still handles
the elements of a session. One puts the pc on the meter to
start off and checks for PTPs, overts, withholds, even ARC
Breaks, handles them quickly and then goes into the body of
the session. Much the same as the oldest model session
rudiments. One doesn't use Mid Ruds or buttons to get
started. One just knows the things that mustn't be there
(PTPs, overts, ARC Breaks) and checks for them, handles if
found and goes on with the main session activity. If a PTP
or an overt or an ARC Break shows up one handles them,
putting the pc back on the meter if necessary. When they
are handled, the pc is put back into the main activity of
the session.

It's true of any auditing that gets done. It isn't likely
to alter and actually no new data is likely to be found
that controverts any of this. The phenomena will still be
the same phenomena as long as there are pcs. Ways of
handling may change but not these basic principles.

They're with the auditor in every session ever to be run.
So one might as well stay alert to them and be continuously
expert in handling them.

They are the only big reefs on which an auditing session
can go up high and dry, so their existence, causes and
cures are of the greatest possible importance to the
skilled auditor.

L. RON HUBBARD

LRH jw.cden 
Copyright  1964
by L. Ron Hubbard
ALL RIGHTS RESERVED


**************

65. HCOB  29 MAR 65 ALL LEVELS - ARC BREAKS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 29 MARCH 1965

Remimeo
Students 

ALL LEVELS

ARC BREAKS

Great News!

I've found the basis of ARC Breaks!

As you know, only a PTP (Present Time Problem) can hold a
graph unchanging and only an ARC Break can lower one.
Therefore the Anatomy of an ARC Break is more vital to
know, as it can worsen, than the anatomy of a PTP. But both
are very important and with the overt act and misunderstood
words in study form the vital four things anyone should
know in auditing Pcs.

The average student has a hard time getting rid of ARC
Breaks in others, mostly because he never really finds the
ARC Break. One Auditor was sure a Pc had been ARC Broken by
&quot;the last few inches of a lecture tape&quot; and was madly
calling Washington to borrow the tape so the poor Pc could
&quot;listen to it again to cure his ARC Break&quot; ! Well I don't
mind being cause, but my tape never ARC Broke the Pc. The
Auditor just didn't locate the Charge.

The whole trick is to keep cleaning up the ARC Break until
the Pc is happy again and then quit. When you find it,
that's it. You don't find it and still have an ARC Broken
Pc! No, the terribly simple truth is that

1. The Pc is ARC Broken because something happened.

2. The Pc will continue to be ARC Broken until the thing is found.

3. The ARC Break will vanish magically when the source is found.

Finding the ARC Break and indicating it clears the ARC
Break. If it doesn't clear on what you find, then you
haven't found it !

You must not continue to run a Pc on some process when the
Pc is ARC Broken. You must find the ARC Break and clear it.

The Pc will go into a sad effect if you don't find the ARC
Break but instead, continue the process. If you think you
have found the ARC Break (and haven't) and then go on
auditing, the Pc will go into a sad effect.

ARC Broken Pcs are easy to identify. They gloom and
mis-emote. They criticise and snarl. Sometimes they scream.
They blow, they refuse auditing.

If you can read a lighted neon sign at 10 feet on a dark
night, you can detect a Pc who has an ARC Break. Some
Auditors can detect them sooner than others. I can see one
coming in a Pc 1 1 / 2 hours of auditing before the Pc
starts to get misemotional in earnest. Some newcomer in the
business might not detect one until the Pc wraps a chair
around the auditor's head. As I say, the ability to
perceive one varies. The better you are the sooner you see
one. If an auditor's Pc isn't bright and happy, there's an
ARC Break there with life or the bank or the session.

The thing to do is find it and clean it up.

And now all is revealed: This is what makes an ARC Break occur:

AN ARC BREAK OCCURS ON A GENERALITY OR A NOT THERE.

The Generality

Example of a Generality

&quot;They say you are cold-hearted.&quot; &quot;Everybody thinks you are
too young.&quot; &quot;The People Versus Sam Jones.&quot; &quot;The will of the
masses.&quot;

Case Manifestation

Example: Little boy screaming in rage when he makes a
mistake in drawing. Auditor observes little boy is upset.
Auditor: &quot;What are you upset about?&quot; Little Boy: (howling)
&quot;My drawing is no good!&quot; Auditor: &quot;Who said your drawing is
no good?&quot; Little Boy: (crying) &quot;The teachers at school
(plural).&quot; Auditor: &quot;What teacher (singular)?&quot; Little Boy:
(sobbing) &quot;Not the teachers, the other children (plural)!&quot;
Auditor: &quot;Which one of the other children?&quot; Little Boy:
(suddenly quiet) &quot;Sammy.&quot; Auditor: &quot;How do you feel now?&quot;
Little Boy: (cheerfully) &quot;Can I have some ice cream?&quot;

The Formula

1. Ask what the Pc is upset about.

2. Ask who thought so.

3. Repeat the generality the Pc used and

4. Ask for the singular.

5. Keep 3 and 4 going until the Pc is happy.

As it's a near Q and A it should be awfully easy. They name
prunes, you say what prune is prunes.

Result

It's quite magical done barehanded or on a meter.

Errors

You can miss in English sometimes on YOU. The Pc says YOU
are mean. We have no plural or singular signal in the word
YOU. Therefore a statement that &quot;YOU are ARC Breaking me&quot;
or &quot;YOU ARE MEAN&quot; may not mean, as an egocentric auditor
may take it, the auditor but YOU may be being used as THE
WHOLE WORLD. The above formula holds 1 to 5. Just find out
&quot;Which person is meant by the word you?&quot;

Our old &quot;Look at me, who am I?&quot; was not too wrong.

So next time your Pc says, &quot;The Instructors are mean,&quot;
don't be goofy enough to indicate the charge with &quot;OK, you
are ARC Broken because the Instructors are mean.&quot; And then
be amazed when the ARC Break continues. You didn't find out
&quot;What Instructor is Instructors?&quot; If you ask a bit further
you'll find it probably wasn't &quot;the Instructors&quot; but
somebody else. And that somebody will be a unit, not a group.

A less workable but interesting approach is &quot;Who uses the
word 'everybody' frequently?&quot; It's of interest only because
&quot;everybody&quot; makes a dispersal which the Pc can't see
through. It will take quite a while sometimes for a Pc to
spot such a person! How many people have died heartbroken
because &quot;they&quot; were mean to him. And it was just one
vicious being who had been blown up to &quot;they&quot;.

The Not There is also a generality because it can be
anywhere. But it is a special case.

When something becomes unlocatable it can cause an ARC Break.

The cure for this one is to find out what's gone.

If you see somebody with a cold, ask &quot;Who's gone?&quot; and
you'll be amazed at the recovery if you pursue the matter.

One concludes it's less the loss than not knowing where
something has gotten to, making a one into a generality.

The common response to sudden loss is to feel everything is
gone or going.

This is the state of anxiety explained.

The beaten and downtrodden respond well on this (when
brought up through normal levels to the Level of Remedies).

A very sneaky question is &quot;Who (or what) was everything to you?&quot;

But use it sparingly. The Pc will go whole track like a
flash if overworked.

Remarkably (at this late date to find it!) that's why he
rather fancies his pictures! At least he has a picture of it!

Dreams follow a sudden loss. It's an effort to orient
oneself and get something back.

Level VI ARC Breaks

Of course, there's nothing wrong really with a thetan but
his reactive bank. He can recover from the rest. And his
reactive bank is full of generalities which explains the
hard ARC Breaks of Level VI. But don't tamper with Level VI
if the Pc belongs at II. You can get enough locks off any
day from normal life to cure the ARC Breaks you'll
encounter getting up to VI.

Main thing to know is: AN ARC BREAK OCCURS BECAUSE OF A GENERALITY

OR A NOT THERE.

Fortunately it doesn't always occur. Only sometimes. And
when it does: Find the singular form of the generality.

In Admin particularly you save more executives that way.
And in auditing you just don't have failed cases or blows
if you know it.

L. RON HUBBARD

LRH:wmc.aj.cden
Copyright  1965
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

66. HCOB   4 APR 65 ARC BREAKS AND MISSED WITHHOLDS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 4 APRIL AD15

Remimeo
Franchise

ARC BREAKS AND MISSED WITHHOLDS

The primary error one can make in ARC Break handling is to
handle the pc with ARC Break procedure when the pc really
has a missed withhold.

As some auditors dislike pulling withholds (because they
run into pcs who use it to carve the auditor up such as &quot;I
have a withhold that everybody thinks you are awful --&quot;) it
is easier to confront the idea that a pc has an ARC Break
than the idea that the pc has a withhold.

In case of doubt one meter checks on a withhold to see if
it is non-existent (&quot;Am I demanding a withhold you haven't
got?&quot;). If this is the case the TA will blow down. If it
isn't the case the needle and TA remain unchanged. If the
pc's nattery or ARC Breaky condition continues despite
finding by-passed charge, then of course it is obviously a
withhold.

ARC Break finding does work. When the pc doesn't change
despite skillful ARC Break handling, locating and
indicating, it was a withhold in the first place.

The hardest pc to handle is the missed withhold pc. They
ARC Break but you can't get the pc out of it. The answer
is, the pc had a withhold all the time that is at the
bottom of all these ARC Breaks.

Scientology auditing does not leave the pc in poor
condition unless one goofs on ARC Breaks.

ARC Breaks occur most frequently on people with missed
withholds. \-Therefore if a pc can't be patched up easily
or won't stay patched up on ARC Breaks, there must be basic
withholds on the case. One then works hard on withholds
with any and all the tools that we've got.

ARC Breaks don't cause blows. Missed withholds do. When you
won't hear what the pc is saying, then you have made him
have a withhold and it responds as a missed withhold.

In short, the bottom of ARC Breaks is a missed withhold.

But an anti-social act done and then withheld sets the pc
up to become &quot;an ARC Breaky pc&quot;. It isn't an accurate
remark really since one has a pc with withholds who on
being audited ARC Breaks easily. So the accurate statement
is &quot;the pc is a withholdy type pc that ARC Breaks a lot&quot;.
Now that type exists. And they sure have lots of subsequent
ARC Breaks and are regularly being patched up.

If you have a pc, then, who seems to have a lot of ARC
Breaks, the pc is a &quot;withholdy pc&quot; not an &quot;ARC Breaky pc&quot;.
Any auditor miss causes a pc blow-up. The auditor by
calling this pc an &quot;ARC Breaky pc&quot; is not using a
description which leads to a resolution of the case as
thousands of ARC Break assessments leave the case still
liable to ARC Break. If you call such a case that ARC
Breaks a lot a &quot;withholdy pc that ARC Breaks a lot&quot; then
you can solve the case. For all you have to do is work on
withholds.

The actual way to handle a &quot;withholdy pc that ARC Breaks a
lot&quot; after you've cooled off the last of his many ARC
Breaks is:

1. Get the pc to look at what's going on with his sessions.

2. Get the pc in comm.

3. Get the pc to look at what's really bugging him.

4. Get the pc's willingness to give withholds up on a gradient.

5. Bring the pc to an understanding of what he's doing.

6. Get the pc's purpose in being audited in plain view to
him or her.

Those are of course the names of the first six grades.
However, low down, these six things are all crushed
together and you could really pursue that cycle in one
session just to get the pc up a bit without even touching
the next grade up.

Whenever I see a sour-faced person who has been &quot;trained&quot;
or is being &quot;trained&quot; I know one thing-there goes a pc with
lots of withholds. I also know, there is a pc who ARC
Breaks a lot in session. And I also know his co-auditor is
weak and flabby as an auditor. And I also know his auditing
supervisor doesn't shove the student auditor into doing the
process correctly.

One sour-faced student, one glance and I know all the above
things, bang! So why can't somebody else notice it?

Auditing is a pleasure. But not when an auditor can't tell
a withhold from an ARC Break and doesn't know that
continual ARC Breaks are caused by missed withholds on the
bottom of the chain.

I never miss on this. Why should you?

The only case that will really &quot;bug you&quot; is the CONTINUOUS
OVERT case. Here's one that commits anti-social acts daily
during auditing. He's a nut. He'll never get better, case
always hangs up.

Unless you treat his continual overts as a solution to a
PTP. And find what PTP he's trying to solve with these
crazy overt acts.

You see, we can even solve that case.

BUT, don't go believing Scientology doesn't work when it
meets an unchanging or continually misemotional pc. Both of
these people are foul balls who are loaded with withholds.

We've cracked them for years and years now.

But not by playing patty-cake or &quot;slap my wrist&quot;.

Takes an auditor, not a lady finger.

&quot;Mister, you've been wasting my time for three sessions.
You have withholds. Give!&quot; &quot;Mister, you refuse just once
more to answer my question and you're for it. I've checked
this meter. It's not a withhold of nothing. You have
withholds. Give!&quot; &quot;Mister, that's it. I am asking the D of
P to ask the Tech Sec for a Comm Ev on you from HCO for no
report.&quot; If skill couldn't do it, demand may. If demand
couldn't do it, a Comm Ev sure will.

For it's a no report!

How can you make a man well when he's got a sewer full of
slimy acts.

Show me any person who is critical of us and I'll show you
crimes and intended crimes that would stand a magistrate's
hair on end.

Why not try it? Don't buy &quot;I once stole a paper clip from
the HASI&quot; as an overt or &quot;You're a lousy auditor&quot; as a
withhold. Hell, man, people who tell you those things just
stole your lunch or intend to empty the till.

Get clever, auditor. Thetans are basically good. Them that
Scientology doesn't change are good-but down underneath a
pile of crimes you couldn't get into a Confession Story
Magazine.

Okay. Please don't go on making this error. It grieves me.

L. RON HUBBARD

LRH:ml.rd
Copyright  1965
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

67. HCOB  19 JAN 66 DANGER CONDITIONS, TECHNICAL DATA FOR REVIEW AUDITORS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 19 JANUARY 1966

Review Auditors
Level III Students

DANGER CONDITIONS

TECHNICAL DATA FOR REVIEW AUDITORS

To cure a disagreement one can:

1. Locate disagreements on certain subjects by listing a
question such as &quot;On

.....what do you disagree with?&quot; and locating the item
with assessment and

blowing it by inspection (itsa).

2. Locate former similar subjects the person disagreed with.

3. Locate things on the subject the person has not
understood and get them clarified.

4. Locate earlier similar subjects the person has not
understood and get them clarified.

IMPORTANT-if a person's attitude does not change after
doing one of the above, do another or find another item
using same process (listed above) as before.

A whole case will fall apart this way.

Compulsive by-passing can be handled by:

1. Doing disagreements as above.

2. Doing misunderstoods as above.

3. Finding persons similar to the person being by-passed,
using standard listing and assessing as in all these.

4. Flattening a question &quot;Who shouldn't be ignored?&quot; (Don't
run &quot;Who has by-passed you?&quot; or &quot;Who should be ignored?&quot; as
these are out-of-ARC processes.)

Ordinary Comm processes also help of course and a good
Grade 0 release helps. Higher Release Grades help. And
Clearing, naturally takes care of the lot of course.

There is direct co-ordination between the state of a case
(state of meter also) and the ability to follow a command
line. The worse off the case (or meter) the less the person
can follow a comm line. A person with a very high or very
low TA and/or a stuck needle or an ARC Broke needle (floats
but never responds and lots of bad indicators) should not
only never be an executive but also will raise havoc in an org.

It is a standard review action in an org to handle such
cases sent to Review by reason of having been part of
Danger Condition assignments. In such cases, aside from
usual Review actions, the above should be done.

L. RON HUBBARD

LRH:ml.rd 
Copyright  1966
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

68. HCOB   1 AUG 68 THE LAWS OF LISTING AND NULLING


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 1 AUGUST 1968

Remimeo

CLASS III, SOLO VI &amp; VII, ACADEMY AND SHSBC
REQUIRED REVIEWED FOR SOLO AND VII

(Compiled from earlier HCOBs and TAPES of
the early 60's to give the exact stable data)

THE LAWS OF LISTING AND NULLING

(Star Rate. No attestations
allowed, clay and demos required)

The following laws are the ONLY important rules of listing
and nulling. If an auditor doesn't know these he will mess
up pcs thoroughly and awfully. An auditor who doesn't know
and can't apply these is not a Level III auditor.

LAWS

1. The definition of a complete list is a list which has
only one reading item on list.

2. A TA rising means the list is being overlisted (too long).

3. A list can be underlisted in which case nothing can be
found on nulling.

4. If after a session the TA is still high or goes up, a
wrong item has been found.

5. If pc says it is a wrong item it is a wrong item.

6. The question must be checked and must read as a question
before it is listed. An item listed from a non-reading
question will give you a &quot;Dead Horse&quot; (no item).

7. If the item is on the list and nothing read on nulling,
the item is suppressed or invalidated.

8. On a suppressed list, it must be nulled with suppressed.
&quot;On ....has anything been suppressed.&quot;

9. On an item that is suppressed or invalidated the read
will transfer exactly from the item to the button and when
the button is gotten in the item will again read.

10. An item from an overlisted list is often suppressed.

11. On occasion when you pass the item in nulling, all
subsequent items will read to a point where everything on
list will then read. In this case take the first which read
on first nulling.

12. An underlisted and overlisted list will ARC break the
pc and he may refuse to be audited until list is corrected,
and may become furious with auditor and will remain so till
it is corrected.

13. Listing and nulling or any auditing at all beyond an
ARC Br without handling the ARC Break first such as
correcting the list or otherwise locating it will put a pc
into a &quot;sad effect&quot;.

14. A pc whose attention is on something else won't list
easily. (List and null only with the rudiments in on the pc.)

15. An auditor whose TRs are out has difficulty in listing
and nulling and in finding items.

16. Listing and nulling errors in presence of Auditor's
Code violations can unstabilize a pc.

17. The lack of a specific listing question or an incorrect
non-standard listing question which doesn't really call for
item will give you more than one item reading on a list.

18. You cease listing and nulling actions when a floating
needle appears.

19. Always give a pc his item and circle it plainly on the list.

20. Listing and nulling are highly precise auditing actions
and if not done exactly by the laws may bring about a down
tone and slow case gain, but if done correctly exactly by
the laws and with good auditing in general will produce the
highest gains attainable.

NOTE: There are no variations or exceptions to the above.
(Does not alter 5A Power procedure.)

A failure to know and apply this bulletin will result in
the assignment of very low conditions as these laws, if not
known or followed, can halt case gain.

L. RON HUBBARD
Founder

LRH :jp js.cden
Copyright  1968
by L. Ron Hubbard
ALL RIGHTS RESERVED


**************

69. HCOB  23 SEP 68 VIOLATION OF THE LAWS OF LISTING AND NULLING


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 23 SEPTEMBER 1968

Class VIII

VIOLATION OF THE LAWS OF LISTING AND NULLING

Rudiments (ARC Bks, PTPs, M/W/Hs) are usually not necessary
in correcting a list as a wrong list usually is the ARC Bk
and PTP.

To correct a list ask the pc or pre-OT

(1) &quot;Is it an incomplete list?&quot; If it is, extend it and
find the item.

(2) &quot;Was it the first item on the list?&quot; If so, indicate
item to pc or pre-OT.

(3) &quot;Was it an unnecessary action?&quot; (dead horse). If so,
indicate it.

(4) &quot;Had you not answered the listing question?&quot; If so,
re-clear question and if it reads list it.

The 4 basic reasons for a wrong list are here

(1) It was the first item.

(2) It is not a complete list.

(3) The question didn't read (which causes a dead horse).

(4) The pc didn't answer the question.

L. RON HUBBARD
Founder

LRH: jp
Copyright  1968
By L. Ron Hubbard
ALL RIGHTS RESERVED

**************

70. HCOB  15 OCT 73 NULLING AND F/Ning PREPARED LISTS


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 15 OCTOBER 1973

Remimeo

C/S Series 87

NULLING AND F/Ning PREPARED LISTS

A prepared list is one which is issued in an HCOB and is
used to correct cases. There are many of these. Notable
amongst them is C/S 53 and its corrections.

It is customary for the auditor to be required to F/N such
a list. This means on calling it that the whole list item
by item is to F/N.

Now and then you get the extreme oddity of a list selected
to exactly remedy the case not reading but not F/Ning.

Of course this might happen if the list did not apply to
the case (such as an OT prepared list being used on a Grade
IV, heaven forbid). In the case of lists to correct
listing, and in particular the C/S 53 series, it is nearly
impossible for this situation to occur.

A C/S will very often see that the auditor has assessed the
list on the pc, has gotten no reads, and the list did not F/N.

A &quot;reasonable&quot; C/S (heaven forbid) lets this go by.

Yet he has before him first-class evidence that the auditor

1. Has out-TRs in general,

2. Has no impingement whatever with TR-1,

3. Is placing his meter in the wrong position in the
auditing session so that he cannot see it, the pc and his
worksheet,

4. That the auditor's eyesight is bad.

One or more of these conditions certainly exist.

To do nothing about it is to ask for catastrophe after
catastrophe with pcs and to have one's confidence in one's
own C/Sing deteriorate badly.

An amazing number of auditors cannot make a prepared list
read for one of the above reasons.

Putting in suppress, invalidation or misunderstood words on
the list will either get a read or the list will F/N.

The moral of this is that prepared lists that do not read
F/N. When prepared lists that do not read do not F/N or
when the auditor cannot get a prepared list to F/N, serious
auditing errors are present which will defeat a C/S.

In the interest of obtaining results and being merciful on
pcs, the wise C/S never lets this situation go by without
finding what it is all about.

L. RON HUBBARD

LRH:rhc.nt.rd 
Copyright  1973 Founder
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

71. HCOB  13 SEP 67 REMEDY B


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 13 SEPTEMBER 1967

Applicable Levels
Internes
Remimeo


REMEDY B


Remedy B in The Book of Case Remedies MUST NOT BE RUN TO
LIMIT THE PC TO THIS LIFE.

The way to do this remedy is BY LISTING. It is a process of
Level III.

One asks for subjects or practices similar to Scientology.
He LISTS the answers. He makes a complete list, not too
short, not too long, and the item on it. Usually the
correct subject or practice gives a Blowdown.

The pc sometimes cognites at this point and good indicators
come in strongly.

If this does not spectacularly occur, one asks for the
misunderstoods (not the misunderstood words) the pc might
have on this subject. This probably cleans it all up IF YOU
GOT THE RIGHT ITEM ON THE LIST.

Remedy B has been run lately in a manner to limit it to
this life. That is an error. The pc never has done anything
in this life that aberrated him. The subject on which
Scientology is hanging up is almost always in a past life.
Hence it is reached only by generalized listing.

You don't ask, in Remedy B, for misunderstood WORDS in the
found subject as these would be in Hottentot, Arabic,
lingua spacia or some outlandish tongue the pc has no
memory of.

As a comment, why can't people just understand a process
and do it without goofing it.

Remedy B has been rendered wholly ineffective by the
misinterpretation it has received.

Remedy B is a vital process and if run and run right as
above it cures the slow Academy student.

So let's do it do it do it and without goofs, huh?

L. RON HUBBARD
Founder

LRH:jp.cden
Copyright  1967
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************

72. HCOB   9 NOV 67 REVIEW AUDITORS, BOOK OF CASE REMEDIES


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 9 NOVEMBER 1967

Remimeo

REVIEW AUDITORS

BOOK OF CASE REMEDIES

REVISION OF REMEDY A, REMEDY B, AND S AND Ds

(Note: To be reprinted for insertion in every
copy of The Book of Case Remedies. )

This bulletin is to be inserted in and changes The Book of
Case Remedies PROCEDURES for Remedy A, Remedy B and S and
Ds (Search for and Discovery of Suppressives).

Recent analyses made of Qualifications Divisions
Departments of Review and of the flow of students and pcs
through the Saint Hill org show:

1. The KEY processes so far as orgs are concerned are
Remedy A, Remedy B and S&amp;Ds.

2. Auditors need direct mechanical technology to do these
three processes effectively.

REMEDY A

Remedy A locates the MISUNDERSTOODS a person has in
Scientology. Originally it read &quot;Misunderstood words&quot;.
Words of course will emerge in the general run of
misunderstoods.

REMEDY A is done only by LISTING. It must not be done
verbally alone. It is a Level III process.

The listing question is &quot;In the subjects of Dianetics or
Scientology who or what has been misunderstood?&quot;

The item is found on the list and given to the student.
That is all. There is no other step.

The rules of listing all apply.

If the student won't have the item it is not correct and
the list must be straightened up with the general auditing
rules that govern listing.

REMEDY B

The form of this process is changed. It is done by three
lists. These three may only be done by formal LISTING and
the general tech of listing as governed by Level III tech.

The lists make the form of an I


 ------------&gt; PT Subject List
    \/
    ||
 Into Past List
    ||
    \/
 ------------&gt; Misunderstood List


LIST 1B

This is done to locate what in the Scientology PT is giving
trouble. It is done as a list and the item is found.

The listing question is

&quot;In your studies of Dianetics and Scientology who or what
are you having trouble with? &quot; The item is found and given
to the student.

This step is governed by all the tech of listing.

LIST 2B

The item found on List 1B is now listed in order to find
the past track subject similar to what is giving trouble in
present time.

The listing question is

&quot;In your past, who or what was similar to ............(item
found in List 1B)?&quot; It is highly illegal to limit the
question to this lifetime.

All the rules of listing apply.

The item is found and given to the student.

LIST 3B

The third list of the process is now done.

The listing question is

&quot;Who or what was misunderstood in ..........(the item found
on list 2B)?&quot; The listing is covered by the general tech of
listing as found in Level III.

The item is found and given to the student.

This completes the Remedy B.

If a floating needle occurs any time during the process
with good indicators thoroughly visible in the student the
process is concluded at that point.

The process is used on anyone having trouble studying
Dianetics or Scientology. The trouble, as it doesn't clear
up with Remedy A, is coming from some prior subject.

More than one of these can be done if all steps are done
for each one.


S &amp; D

Search and Discovery of Suppression is called an &quot;S and D&quot;.
It locates the suppressives on the case.

I have several times undercut (gotten processes that reach
deeper) on S &amp; Ds.

The earliest process asked merely who might have been
suppressive to the pc. This is still valid but I have found
2 flaws in it.

1. The auditor does not do a listing type S &amp; D at all but
just chattily brushes it off.

2. The list from this question contains an actual
suppressive that is passed right over.

Therefore I undercut the question and obtained much better
results because the new question reached deeper.

The new question was &quot;Who or what might have suppressed you?&quot;

Then I recalled an even deeper question. This was &quot;What
purpose has been suppressed?&quot; This was given to Qual Div SH
some time ago. It would have 2 lists. The first is for the
purpose as above and the second would be &quot;Who or what
suppressed ......(purpose found)?&quot; For some reason,
probably because no one did 2 lists, this undercut was
neglected.

Therefore I researched further and developed what we will
now use as an S &amp; D.

It is one of these killer processes. It is VERY strong. So
it isn't to be carelessly done.

If you get a wrong item on an S &amp; D YOU CAN MAKE THE PC
ILL. So one has to do an S &amp; D right and follow all the
rules of listing as given in Level III tech.

Also I find now that when a list item found is a generality
(multiple subject, not specific such as &quot;dogs&quot; or &quot;the
public&quot;) the list is simply not complete. One does not have
to settle for a generality and then list the generality. He
will find that the pc will eventually list the specific
non-general item anyway. Of course one can also do a
represent list of a general item found if that seems best.

The real question for an S &amp; D was established only when I
found a purpose all Suppressives have in common and is a
very fundamental effort in suppressives. This effort by
suppressives, when found, then permitted me to form the
question.

The key S &amp; D question is:

&quot;Who or what has attempted to unmock you?&quot;

Unmocking (an effort to reduce or make disappear) is the
primary effort of suppressives.

Therefore the listing question on test delivers up items
totally overlooked by the earlier types of S &amp; D.

The question needs to be cleared carefully for
non-Scientology. If it has to be rephrased, watch out as
the meaning may vanish. &quot;Tried to make nothing of you&quot;
might substitute but at this writing only unmock has been
tested and a question for others than educated
Scientologists will be developed and issued and made part
of the enclosure for the book.



This S &amp; D question must be done by LISTING only and with
great care to follow Level III Listing tech as it, being
powerful, will backfire on the pc if done carelessly and a
wrong item is found.

The item is found by listing and given to the pc, which is
the end of the process. If a generality results it may be
represented. But listing continued will give the same
result of a single item. A general item must not be given
to the pc as the final result.

This process will now be standard review S &amp; D.

L. RON HUBBARD
Founder

LRH:jp.cden
Copyright  1967
by L. Ron Hubbard
ALL RIGHTS RESERVED


**************

73. HCOB   3 JUL 71 AUDITING BY LISTS REVISED


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 3 JULY 1971

Remimeo
Franchise
All Auditors
Level III Checksheets

Replaces HCO Bs 22 May 65 and 23 Apr 64,
and cancels HCO B 27 July 65 all on the
same subject.


SCIENTOLOGY III

AUDITING BY LISTS REVISED


(Note: We now F/N everything. We do NOT tell the pc what
the meter is doing. This changes &quot;Auditing By Lists&quot; in both
respects. We do not say to the pc, &quot;That's clean&quot; or &quot;That
reads&quot;.)


AUDITING BY LISTS

(Reference: HCO B 14 Mar 71, &quot;F/N Everything&quot;)

Use any authorized, published LIST. (Green Form for general
review, L1C for ARC Brks, L4B for listed items list errors.)

METHOD 3

Use meter at a sensitivity so meter needle is loose but it
is easy to keep needle at &quot;Set&quot;. If sensitivity is too high
the needle will be in constant motion as one tries to set
the TA. If too low, the instant read will not be visible. 5
is usual for upper grade cases. 16 is usual for lower grade
or Dianetic cases.

Have your meter in a position (line of sight) so you can
see the list and the needle or you can see the needle and
the pc. The meter position is important.

Hold the mimeoed list close beside the meter. Have your
worksheet more to the right.

Keep record on your worksheet. Mark the pc's name and date
on it. Mark what list it is on the W/S with Time. It
remains in the folder stapled to the W/S.

Read the question on the list, note if it reads. Do NOT
read it while looking at the pc, do NOT read it to yourself
and then say it while looking at the pc. These are the L10
actions and are called Method 6, not Method 3. It is more
important to see the pc's cans than his face as can fiddle
can fake or upset reads.

TR 1 must be good so the pc clearly hears it.

You are looking for an INSTANT READ that occurs at the end
of the exact last syllable of the question.

If it does not read, mark the list X. If the list is being
done through an F/N and the F/N just continues, mark the
Question F/N.

If the question reads, do not say &quot;That reads&quot;. Mark the
read at once (tick, SF, F, LF, LFBD, R/S), transfer the
number of the Q to the W/S and look expectantly at the pc.
You can repeat the Q by just saying it again if pc doesn't
begin to talk. He has probably already begun to answer as
the Q was live in his bank as noted by the meter.

Take down the pc's remarks in shortened form on the W/S.
Note any TA changes on the W/S.

If the pc's answer results in an F/N (Cog VGIs sometimes
follow, GIs always accompany a real F/N), mark it rapidly
on the W/S and say, &quot;Thank you. I would like to indicate
your needle is floating.&quot;

Do NOT wait endlessly for the pc to say more. If you do he
will go into doubt and find more, also do NOT chop what he
is saying. Both are TR errors that are very bad.

If there is no F/N, at the first pause that looks like the
pc thinks he has said it, ask for an Earlier
Similar_____whatever the question concerned. Do NOT change
the Q. Do NOT fail to repeat what the Question is. &quot;Was
there an Earlier Similar Restimulation of 'rejected
affinity'?&quot; This is the &quot;E/S&quot; part of it. You do not leave
such a Question merely &quot;clean&quot;.

It does not matter now if you look at the pc when you say
it or not. But you can look at the pc when you say it.

The pc will answer. If he comes to a &quot;looks like he thinks
he said it&quot; and no F/N, you ask the same Q as above.

You ask this Q &quot;Was there an earlier similar______&quot; until
you finally get an F/N and GIs.

You indicate the F/N.

That is the last of that particular question.

You mark &quot;F/N&quot; on the list and call the next question on
the list. You call this and other questions without looking
at the pc.

Those that do not read, you X as out.

The next question that reads, you mark it on the list,
transfer the question number to the W/S.

Take the pc's answer.

Follow the above E/S procedure as needed until you get an
F/N and GIs for the question.

Ack. Indicate and return to the mimeoed list.

You keep this up until you have done the whole list in this
fashion.

If you got no read on the list Question but the pc
volunteers some answer to an unreading question, do NOT
take it up. Just ack and carry on with your mimeoed list.

BELIEVE YOUR METER. Do not take up things that don't read.
Don't get &quot;hunches&quot;.

Don't let the pc run his own case by answering non-reading
items and then the auditor taking them up. Also don't let a
pc &quot;fiddle the cans&quot; to get a false read or to obscure a
real one. (Very rare but these two actions have happened.)

BIG WIN

If half way down a prepared list (the last part not yet
done) the pc on some question gets a wide F/N, big Cog,
VGIs, the auditor is justified in calling the list complete
and going to the next C/S action or ending the session.

There are two reasons for this-one, the F/N will usually
just persist and can't be read through and further action
will tend to invalidate the win.

The auditor can also carry on to the end of the prepared
list if he thinks there may be something else on it.

GF AND METHOD 3

When a GF is taken up Method 3 (item by item, one at a time
and F/Ned) it can occur that the TA will go suddenly high.
The pc feels he is being repaired, that the clearing up of
the first item on the GF handled it and protests. It is the
protest that sends the TA up.

This is not true of any other list.

Thus a GF is best done by Method 5 (once through for reads,
then the reads handled).

L1C and L4B, L7 and other such lists are best done by Method 3.

The above steps and actions are exactly how you do Auditing
by List today. Any earlier data contrary to this is
cancelled. Only 2 points change-we F/N everything that
reads by E/S or a process to handle (L3B requires
processes, not E/S to get an FIN) and we never tell the pc
that it read or didn't read, thus putting his attention on
the meter.

We still indicate F/Ns to the pc as a form of completion.

L1C and Method 3 are NOT used on high or very low TAs to
get them down or up.

The purpose of these lists is to clean up by-passed charge.

________

An auditor also indicates when he has finished with the list.

An auditor should dummy drill this action both on a doll
and bullbait.

________

The action is very successful when precisely done.

L. RON HUBBARD
Founder

LRH:nt.rd
Copyright  1971
by L. Ron Hubbard
ALL RIGHTS RESERVED

**************


