FREEZONE BIBLE ASSOCIATION TECH POST

LEVEL 0 COURSEPACK: Part 8 of 10

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

I am the Tech Lion.

Studying the Academy Levels gave me the ability to handle life.

I would like others to have the same knowledge that I now have.

Here is the Academy Level 0 Coursepack from 1988, in 10 parts.

There was an earlier FZBA post of the Level 0 coursepack from
1974, but due to extensive CofS revision, little remains the
same in both packs.

The full table of contents is in Part 1 only.

To see the proper formatting, use a fixed-pitch font such as
Courier to view this file.

Enjoy,

-The Tech Lion 

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

STATEMENT OF PURPOSE 

Our purpose is to promote religious freedom and the Scientology
Religion by spreading the Scientology Tech across the internet.

The Cof$ abusively suppresses the practice and use of
Scientology Tech by FreeZone Scientologists. It misuses the
copyright laws as part of its suppression of religious freedom.

They think that all freezoners are "squirrels" who should be
stamped out as heretics. By their standards, all Christians, 
Moslems, Mormons, and even non-Hassidic Jews would be considered
to be squirrels of the Jewish Religion.

The writings of LRH form our Old Testament just as the writings
of Judaism form the Old Testament of Christianity.

We might not be good and obedient Scientologists according
to the definitions of the Cof$ whom we are in protest against.

But even though the Christians are not good and obedient Jews,
the rules of religious freedom allow them to have their old 
testament regardless of any Jewish opinion. 

We ask for the same rights, namely to practice our religion
as we see fit and to have access to our holy scriptures
without fear of the Cof$ copyright terrorists.

We ask for others to help in our fight. Even if you do
not believe in Scientology or the Scientology Tech, we hope
that you do believe in religious freedom and will choose
to aid us for that reason.

Thank You,

The FZ Bible Association

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

PART 8 (this file)

49. HCOB 4 Dec. 1977R Checklist for Setting Up Sessions
and an E-Meter

50. HCOB 11 Aug. 1978 I Rudiments, Definitions and Patter

51. HCOB 6 June 1984 III Missed Withhold Handling

52. HCOB 11 Aug. 1978 II Model Session

53. HCOB 7 Mar. 1975 Ext and Ending Session

54. HCOB 10 Dec. 1964 Listen-Style Auditing

55. HCOB 11 Dec. 1964 Scientology 0 Processes

56. HCOB 26 Dec. 1964 Routine 0A (Expanded)

57. HCOB 23 June 1980RA Checking Questions on Grades
Processes

58. HCOB 3 Dec. 1978 Unreading Flows


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

49. HCOB 4 Dec. 1977R Checklist for Setting Up Sessions
and an E-Meter


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 4 DECEMBER 1977R
REVISED 19 AUGUST 1987

Remimeo
All Levels
All Auditors


CHECKLIST FOR SETTING UP
SESSIONS AND AN E-METER


In order to prevent constant interruptions of a session to get 
dictionaries, prepared lists, etc., etc., and in the vital 
interest of keeping the pc smoothly in-session -- interested in 
own case and willing to talk to the auditor-the following 
checklist has been made.

An auditor should drill this checklist until he has it down 
thoroughly, without reference to it.


A. PRE-APPOINTMENT:

1. Paid invoice slip of pc. ______

2. Pc folders --
2a. Current ______
2b. Old. ______

3. Pc folder study by auditor. ______

4. Folder Error Summary. ______

5. A C/S for the session. ______

6. Any cramming actions on the C/S. ______


B. CALL IN:

7. Enough time to do session. ______

8. Appointment (made by auditor or Technical Services). ______

9. Scheduling board (auditor, pc, room, time). ______


C. ROOM READINESS:

10. Clean up room. ______

11. Smells removed. ______

12. Room temperature handled. ______

13. Area and hall silence signs made. ______

14. Silence signs placed. ______

15. Knowing where the water closet is. ______

16. Right sized table, sturdy, doesn't squeak. ______

17. Side table. ______

18. Adequate light if room gets dark. ______

19. Flashlight in case power fails. ______

20. Quiet clock or watch. ______

21. Blanket for pc in case gets cold. ______

22. Fan or air conditioner in case pc gets too hot. ______


D. AUDITING MATERIEL:

23. Paper for worksheets and lists. ______

24. Ballpoints or pencils. ______

25. Kleenex. ______

26. Antiperspirant for sweaty palms. ______

27. Hand cream for dry palms. ______

28. Dictionaries including Tech and Admin Dictionaries
and a nondinky one in language. ______

29. Grammar.

30. Auditing materiel, Original Assessment Sheets,
prepared lists, including those that might be
called for on other prepared lists. ______

31. E-Meter. ______

32. Spare meter. ______

33. Preliminary meter check for charge and operational
condition. ______

34. Meter shield (to obscure meter from pc). ______

35. In Session sign for door. ______

36. Extra meter lead. ______

37. Different sized cans. ______

38. A plastic bag to cover one can for pcs who knock
cans together. ______

39. Finalize setting up room for session. ______


E. PC ENTRANCE TO AUDITING ROOM:

40. In Session sign on door. ______

41. Phone shut off. ______

42. Putting pc in chair. ______

43. Comfort of chair -- check with pc and handle. ______

44. Adjusting pc's chair. ______

45. Check pc clothes, shoes for tightness and handle. ______

46. Check with pc if room is all right and handle. ______


F. METER SET UP FOR SESSION:

47. Check test (for charge). ______

48. See that needle is not dancing by itself or
auditing itself. ______

49. Make sure 2.0 = 2.0 by trim. ______

50. Snap in leads. ______

51. Verify trim by calibration resistor onto alligator
clips. ______

52. Put needle on set. ______

53. Put pc on. ______

54. Adjust pc sensitivity for 1/3-dial drop by pc can
squeeze. ______

55. Go through False TA correction as needed including
change of cans, cream, antiperspirant as needed. ______

56. Have pc take a deep breath, hold it for just a
moment, then let it out through his mouth. See if
needle gives a latent fall (which it should). ______

57. Check for adequate sleep. ______

58. Check to be sure pc has eaten and is not hungry. ______

59. Ask for any reason not to begin session. ______


G. START THE SESSION.


L. RON HUBBARD Founder

Revision assisted by
LRH Technical Research
and Compilations

LRH:dr.ahg.ja.gm

_

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

50. HCOB 11 Aug. 1978 I Rudiments, Definitions and Patter


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 11 AUGUST 1978
Issue I

Remimeo
All Auditors


RUDIMENTS
DEFINITIONS AND PATTER

Ref:
HCOB 15 Aug. 69 FLYING RUDS

(NOTE: This bulletin in no way summarizes all the data
there is to be known about ARC breaks, PTPs and missed
withholds, or handling rudiments.

There is a wealth of technology and data on these subjects
contained throughout the Technical Volumes and in Scientology
books, which the student auditor will need as he progresses
up the levels.)


A rudiment is that which is used to get the pc in shape to be 
audited in that session.

For auditing to take place at all, the pc must be in-session which 
means:

1. Willing to talk to the auditor

2. Interested in own case.

That is all you want to accomplish with rudiments. You want to set 
up the case to run by getting the rudiments in, not use the 
rudiments to run the case.

ARC breaks, present time problems and withholds all keep a session 
from occurring. It is elementary auditing knowledge that auditing 
over the top of an ARC break can reduce a graph, hang the pc up in 
sessions or worsen his case, and that in the presence of PTPs, 
overts and missed withholds (a restimulated, undisclosed overt) no 
gains can occur. Thus, these are the rudiments we are most 
concerned with getting in at the beginning of a session so that 
auditing with gains can occur.


GETTING THE F/N

If you know bank structure, you know it is necessary to find an 
earlier item if something does not release.

If a rud doesn't F/N, then there is an earlier (or an earlier or 
an earlier) lock which is preventing it from F/Ning.

Thus, we have the procedure and the rule:

IF A RUD READS, YOU ALWAYS TAKE IT EARLIER-SIMILAR UNTIL IT F/Ns.

The question used is:

"Is there an earlier-similar (ARC break or problem or missed 
withhold)?"

If at the beginning of a session the rudiments are in (the needle 
is floating and the pc is VGIs), the auditor goes directly into 
the major actions of the session. If not, the auditor must fly a 
rud or ruds, as ordered by the C/S.


ARC BREAKS

ARC: A word from the initial letters of affinity, reality and
communication which together equate to understanding.

ARC BREAK: A sudden drop or cutting of one's affinity, reality or
communication with someone or something. Upsets with
people or things come about because of a lessening or
sundering of affinity, reality, communication or
understanding.

While the earlier-similar rule fully applies to ARC breaks, there 
is an additional action taken in handling ARC breaks that enables 
the pc to spot precisely what happened that resulted in the upset.

An ARC break is called that -- an "A-R-C break" -- instead of an 
upset because, if one discovers which of the three points of 
understanding have been cut, one can bring about a rapid recovery 
in the person's state of mind.

You never audit over the top of an ARC break, and you never audit 
an ARC break itself; they cannot be audited. But they can be 
assessed to locate which of the basic elements of ARC the charge 
is on.

Thus, to handle an ARC break you assess affinity, reality, 
communication and understanding to find which of these points the 
break occurred on.

Having determined that, you assess the item found (A or R or C or 
U) against the Expanded CDEI Scale (curious, desired, enforced, 
inhibited, no and refused). Refs: HCOB 13 Oct. 59, DEI EXPANDED 
SCALE, Scientology 0-8, The Book of Basics, and HCOB 18 Sept. 67, 
Corr. 4.4.74, SCALES.

With this assessment the actual bypassed charge can be located and 
indicated even more accurately, thus enabling the pc to blow it.

The assessment is done on every ARC break as you go earlier-
similar until the rudiment is in with F/N and VGIs.

The first rudiment question is:

1. "Do you have an ARC break?"

2. If there is an ARC break, get the data on it briefly.

3. Find out by assessment which point the ARC break occurred on:
"Was that a break in Affinity?
Reality?
Communication?
Understanding?"

You assess it once and get the read (or the largest read) on,
say, communication.

4. Check it with the pc: "Was that a break in (communication)?" If 
he says no, rehandle. If yes, let him tell you about it if he 
wishes. Then give it to him by indicating it, i.e., "I'd like to 
indicate that was a break in communication."

PROVIDED THE RIGHT ITEM HAS BEEN GOTTEN, the pc will brighten up, 
even if ever so slightly, on the very first assessment.

NOTE: On step 4 the pc may originate: "Yes, I guess it was 
communication but to me it's really more like a break in reality," 
for example. The wise auditor then acknowledges and indicates it 
was a break in "reality."

5. Taking the item found in step 4 above, assess it against the
CDEI Scale:

"Was it Curious about (communication)?
Desired (communication)?
Enforced (communication)?
Inhibited (communication)?
No (communication)?
Refused (communication)?"

6. As in steps 3 and 4 above, assess it once, get the item and
check it with the pc:

"Was it (desired) communication?"

If no, rehandle. If yes, indicate it.

7. If no F/N at this point, you follow it earlier with the
question

"Is there an earlier-similar ARC break?"

8. Get the earlier-similar ARC break, get in ARCU, CDEINR, 
indicate. If no F/N, repeat step 7, continuing to go earlier, 
always using ARCU, CDEINR until you get an F/N.

When you get the F/N and VGIs, you have it.


PRESENT TIME PROBLEM

PROBLEM: A conflict arising from two opposing intentions. It's
one thing versus another thing; an intention-counter-
intention that worries the preclear.

PRESENT TIME PROBLEM: A special problem that exists in the
physical universe now, on which the pc has his attention
fixed.

Any set of circumstances that so engages the attention
of the preclear that he feels he should be doing
something about it instead of being audited.

A violation of "in-sessionness" occurs when the pc's attention is 
fixed on some concern that is "right now" in the physical 
universe. The pc's attention is "over there," not on his case. If 
the auditor overlooks and doesn't handle the PTP, then the pc is 
never in-session, grows agitated, ARC breaks. And no gains are 
made because he is not in-session.

The second rudiment question is:

1. "Do you have a present time problem?"

2. If there is a PTP, have the pc tell you about it.

3. If no F/N, take it earlier with the question

"Is there an earlier-similar problem?"

4. Get the earlier problem, and if no F/N, follow it earlier-
similar, earlier-similar, earlier-similar to F/N.


MISSED WITHHOLDS

OVERT ACT: An intentionally committed harmful act committed in an
effort to solve a problem.

An act of omission or commission which does the least
good for the least number of dynamics or the most harm
to the greatest number of dynamics.

That thing which you do which you aren't willing to
have happen to you.

WITHHOLD: An undisclosed harmful (contrasurvival) act. Something
the pc did that he isn't talking about.

MISSED WITHHOLD: An undisclosed contrasurvival act which has been 
restimulated by another but not disclosed. This is a
withhold which another person nearly found out about,
leaving the person with the withhold in a state of
wondering whether his hidden deed is known or not.

The pc with a missed withhold will not be honestly "willing to 
talk to the auditor" and, therefore, not in-session until the 
missed withhold is pulled.

Missing a withhold or not getting all of it is the sole source of 
an ARC break. A missed withhold is observable by any of the 
following: pc not making progress, pc critical of, nattery or 
angry at the auditor, refusing to talk to the auditor, not 
desirous of being audited, boiling off, exhausted, foggy at 
session end, dropped havingness, telling others the auditor is no 
good, demanding redress of wrongs, critical of Scientology or 
organizations or people of Scientology, lack of auditing results, 
dissemination failures. (Ref: HCOB 3 May 62, ARC BREAKS, MISSED 
WITHHOLDS) The auditor must not overlook any manifestation of a 
missed withhold.

Thus, if the pc has a missed withhold you get it, get all of it 
using the system described below, and use the same system on each 
earlier-similar missed withhold until you get the F/N.

The third rudiment question is:

1. "Has a withhold been missed?"

2. If you get a missed withhold, find out

a. What was it?

b. When was it?

c. Is that all of the withhold?

d. WHO missed it?

e. What did (he/she) do to make you wonder whether or not
(he/she) knew?

f. Who else missed it? (Repeat [e] above).

Get another and another who missed it, using the Suppress
button as necessary, and repeating (e) above.

3. Clean it to F/N, or if no F/N, take it earlier-similar with the
question

"Is there an earlier-similar missed withhold?"

4. Handle each earlier-similar missed withhold you get per step 2
above, until you get an F/N.


SUPPRESS

If a rudiment doesn't read and is not F/Ning, put in the Suppress 
button, using

"On the question 'Do you have an ARC break?' has anything been 
suppressed?"

If it reads, take it and ask ARCU, CDEINR, earlier-similar, etc.

Use Suppress in the same way for nonreading PTP and missed 
withhold rudiments.


FALSE

If the pc protests, comments or seems bewildered, put in the False 
button. The question used is

"Has anyone said you had a ______ when you didn't have one?" Get
who, what, when and take it earlier, if necessary, to F/N.


END PHENOMENA

In ruds when you've got your F/N and that charge has moved off, 
indicate it. Don't push the pc on for some other "EP." When the pc 
F/Ns with VGIs, you've got it.


HIGH OR LOW TA

Never try to fly ruds on a high or low TA.

Seeing a high or low TA at session start, the Dianetic or 
Scientology auditor up to Class 11 does not start the session but 
sends the folder back to the C/S for a higher-classed auditor to 
handle. The C/S will order the required correction list to be done 
by an auditor Class III or above.

----------

Refs:
HCOB 15 Aug. 69 FLYING RUDS
HCOB 13 Oct. 59 DEI EXPANDED SCALE
HCOB 18 Sept. 67 SCALES
HCOB 7 Sept. 64 II PTPs, OVERTS AND ARC BREAKS
HCOB 12 Feb. 62 HOW TO CLEAR WITHHOLDS AND
MISSED WITHHOLDS
HCOB 31 Mar. 60 THE PRESENT TIME PROBLEM
HCOB 14 Mar. 71R F/N EVERYTHING
HCOB 23 Aug. 71 C/S Series I
AUDITOR'S RIGHTS
HCOB 21 Mar. 74 END PHENOMENA
HCOB 22 Feb. 62 WITHHOLDS, MISSED AND PARTIAL
HCOB 3 May 62 ARC BREAKS, MISSED WITHHOLDS

The above issues give further data on rudiments, ARC breaks, PTPs 
and missed withholds. Note, however, that this is not a complete 
list of references on the subject. There is much additional data 
to be found in the Technical Volumes.


L. RON HUBBARD
Founder

LRH:dr.gm

_

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

51. HCOB 6 June 1984 III Missed Withhold Handling


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 6 JUNE 1984
Issue III

Remimeo 
Auditors
C/Ses
Auditor-Training
Checksheets
HSSC Course
Tech/Qual
Sec Checkers


MISSED WITHHOLD HANDLING

Ref:
Tape: 6211C01 THE MISSED MISSED WITHHOLD

Modifies:
HCOB 30 Nov. 78 CONFESSIONAL PROCEDURE
HCOB 11 Aug. 78 I RUDIMENTS DEFINITIONS AND PATTER
HCOB 15 Aug. 69 FLYING RUDS


Part of the routine procedure that is expected of any auditor 
pulling a missed withhold, whether as a rudiment or in Sec 
Checking, is to get "who missed it" -- the people who missed the 
withhold-and what each of them did to make the pc wonder whether 
he or she knew. Sometimes, however, the rudiment keys out and 
F/Ns before the auditor has gotten to the "who missed it" step of 
the procedure.

Such an F/N is indicated, but you must then go forward and get 
who missed the withhold and what that person did to "miss" the 
withhold on the pc.

This handling can considerably widen the F/N and blow the missed 
withhold but good.


L. RON HUBBARD
Founder

LRH:rw.iw.gm

_

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

52. HCOB 11 Aug. 1978 II Model Session


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 11 AUGUST 1978
Issue II

Remimeo
All Auditors


MODEL SESSION

(Note: If a Dianetic or Level 0, I, II auditor is not trained in 
flying rudiments, he would have to get a Level III [or above] 
auditor to fly the pc's ruds before starting the major action of 
the session.)


1. Setting Up for the Session

Prior to the session, the auditor is to make sure the room and 
session are set up, to ensure a smooth session with no 
interruptions or distractions.

Use HCOB 4 Dec. 77, CHECKLIST FOR SETTING UP SESSIONS AND AN E-
METER, getting in every point of the checklist.

The pc is seated in the chair furthest from the door. From the 
time he is asked to pick up the cans, he remains on the meter 
until the end of the session.

When it is established there is no reason not to begin the 
session, the auditor starts the session.

2. Start of Session

The auditor says, "This is the session." (Tone 40)

If the needle is floating and the pc has VGIs, the auditor goes 
directly into the major action of the session. If not, the 
auditor must fly a rud.

3. Rudiments

Rudiments are handled per HCOB 11 Aug. 78 I, RUDIMENTS, 
DEFINITIONS AND PATTER.

(If the TA is high or low at session start, or if the auditor 
cannot get a rud to fly, he ends off and sends the pc folder to 
the C/S. A Class IV Auditor [or above] may do a Green Form or 
another type of correction list.)

When the pc has F/N, VGIs, the auditor goes into the major action 
of the session.

4. Major Action of the Session

a. R-factor to the pc. The auditor informs the pc what is
going to be done in the session with

"Now we are going to handle ________."

b. Clearing commands. The commands of the process are cleared
per HCOB 9 Aug. 78 II, CLEARING COMMANDS.

c. The process. The auditor runs the process or completes the
C/S instructions for the session to end phenomena.

In Dianetics, the end phenomena would be F/N, erasure of the 
chain, cognition, postulate (if not voiced in the cognition) and 
VGIs.

In Scientology processes, the end phenomena is F/N, cognition, 
VGIs. The Power Processes have their own EP

5. Havingness

When Havingness is indicated or included in the C/S instructions, 
the auditor runs approximately ten to twelve commands of the pc's 
Havingness Process to where the pc is bright, F/Ning and in PT. 
(Note: Havingness is never run to obscure or hide the fact of 
failure to F/N the main process or an auditing or Confessional 
question.)

(Ref. HCOB 7 Aug. 78, HAVINGNESS, FINDING AND RUNNING THE PC'S 
HAVINGNESS PROCESS)

6. End of Session

a. When the auditor is ready to end the session, he gives
the R-factor that he will be ending the session.

b. Then he asks

"Is there anything you would care to say or ask before I
end this session?"

Pc answers.

Auditor acknowledges and notes down the answer.

c. If the pc asks a question, answer it if you can or
acknowledge and say, "I will note that down for the C/S."

d. Auditor ends the session with "End of session." (Tone 40)

(Note: The phrase "That's it" is incorrect for the purpose of 
ending a session and is not used. The correct phrase is "End of 
session.")

----------

Immediately after the end of session, the auditor or a page takes 
the pc to the Pc Examiner.


L. RON HUBBARD
Founder

LRH:nc.gm

_

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

53. HCOB 7 Mar. 1975 Ext and Ending Session


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 7 MARCH 1975

Remimeo


EXT AND ENDING SESSION


When a pc exteriorizes on a good win in session or if the pc has 
a big win, usually followed by a persistent F/N, the usual action 
is to end session.

When ending session in these circumstances, the auditor must not 
do any other action but smoothly end session.

This includes asking Say or Ask, running Havingness or anything 
other than smoothly ending session.


L. RON HUBBARD
Founder

LRH:nt.gm

_

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

54. HCOB 10 Dec. 1964 Listen-Style Auditing


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 10 DECEMBER 1964

Remimeo
Franchise
Sthil Students
Sthil Co-audit


SCIENTOLOGY 0

LISTEN-STYLE AUDITING


There are two ways to run listen-style auditing -- (1) As a 
number of teams directly under an Auditing Supervisor, and (2) As 
an individual auditor. Correct training procedure at Level 0 is 
to have the auditor do co-audit style until confident and then 
train him to do the same thing individually.

LISTEN-STYLE CO-AUDIT

The co-audit version is merely to get the student to do auditing 
without having to assume too much responsibility.

In this version it is really the Instructor who is doing the 
auditing. He starts the sessions and tells the auditors to give 
the commands and acknowledge the answers. If this relationship is 
understood, it makes the supervision of a Level 0 group of teams 
much easier.

The procedure for running a listen-style co-audit is as follows:

1. Instructor gets the auditors to seat their pcs in their chairs 
and then sit down.

2. He writes up on a board the exact wording of the process to be 
used.

3. He asks students if the room is all right for them to be 
audited in.

4. He tells them what is going to be run in the session (R-
factor) and cleans up any questions on the part of pcs 
(obviously, stress is on getting them able to talk to anyone).

5. He tells auditors and pcs that all the auditor is permitted to 
do is to give the command and acknowledge the answers. If pc says 
anything that cannot be handled with an acknowledgment, the 
auditor will put out his hand behind him and wait for an 
Instructor.

6. He tells the auditors to keep their Auditor's Reports.

7. Instructor then says "Start of session." And tells the 
auditors to give the command. No goals or rudiments are set or 
done.

Notes: Students should be taught that before they give an 
acknowledgment they should understand pc's answer. They are 
permitted, therefore, to ask pc to amplify an answer or to 
explain a word so that they (the auditors) understand the answer.

If a student puts out his hand, the Instructor goes to session 
and without ending it handles what needs handling and then lets 
session go on. The Instructor is careful not to become the pc's 
auditor completely as transference will set in and pcs will 
invent trouble to get more attention. Instructor should have a 
meter handy so that in the case of an ARC break he can quickly do 
an assessment. In doing the ARC break assessment, he is of course 
careful not to audit the pc, only to locate and indicate the 
bypassed charge.

At end of period, Instructor says, "Commence ending your 
sessions." He waits a bit and then says, "Tell your auditor any 
gains you've made in the session. Auditors write them down." 
Waits again and then says, "All right, I'm going to end the 
session now. End of session." Instructor then gives whatever 
instruction is necessary either to end the period or to get the 
room ready for the next period or gives a break, etc.

LISTEN STYLE, INDIVIDUAL

This is done exactly the same as the co-audit version but in this 
case, of course, the auditor handles the session. It goes like 
this:

1. The auditor seats the pc in his or her chair and then sits 
down across from the pc, knees a few inches from the pc's. A 
table is used, or just two chairs, the Auditor's Report being 
kept on a clipboard. There is, of course, no meter.

2. The auditor takes the exact auditing command to be used from 
his textbook, bulletin or notes.

3. He asks the pc if it is all right to audit the pc in the room 
and, if not, makes things right by adjusting the room or location 
of auditing.

4. He tells the pc the purpose of such sessions (reality factor). 
"I want to get you used to talking to another." "I want to 
improve your reach," etc. It's the auditor's goal at this level, 
not the pc's. Pcs don't get a chance to have goals in listen 
style as they would set goals they can't attain at this level and 
wouldn't have enough reality on auditing anyway to be sensible 
about it. So, only an R-factor is used-no goals. The auditor also 
tells the pc exactly how long the session will be.

5. The auditor tells the pc that all he is going to do is to 
listen and try to understand the pc, and that all he wants the pc 
to do is talk on the selected subject the auditor will give him 
and that if he veers off, the auditor will call it to his 
attention.

6. The auditor then quickly starts his Auditor's Report.

7. The auditor says, "Start of session."

8. The auditor gives the command from his text, bulletin or 
notes. The command must have something to do with telling people 
things or communicating, and may also specify a subject to talk 
about.

9. Further commands are given only when the pc loses track of the 
subject and wants to know what it was (see routines for Level 0 
for exact handling of commands).

10. When the pc says something and obviously expects a response, 
the auditor signifies he has heard, using any normal means.

11. When the pc says something the auditor doesn't grasp, the 
auditor asks the pc to repeat It or amplify it so that the 
auditor does hear it in the fullest sense of the word. (See "The 
Prompters" below. Only four are allowed.)

12. When the pc stops talking, the auditor must adjudicate 
whether the pc is simply no longer interested in the subject or 
has become unwilling to talk about some bit of it. If the auditor 
believes the pc has stopped because of embarrassment or some 
similar reason, the auditor has the prompters, the only things he 
is allowed to use.

Prompter (a) "Have you found something you think would make me 
think less of you?"

Prompter (b) "Is there something you thought of that you think I 
wouldn't understand?"

Prompter (c) "Have you said something you felt I didn't 
understand? If so, tell me again."

Prompter (d) "Have you found something you haven't understood? If 
so, tell me about it."

(The student must know these prompters by heart.) He uses as many 
as needed, in the sequence given, to start the pc talking again.

The auditor must not start a new subject or process just because 
the pc can't bring himself to go on talking. The whole essence of 
Level 0 is to get the pc up to being willing to talk about 
anything to anyone. Thus, any coaxing is also allowed. Threats 
are forbidden. (a), (b), (c) or (d) usually handle. These are the 
commonest reasons people cease talking. Mere forgetting is 
handled just by reminding the pc of the subject.

13. New processes (or new subjects in a routine which are in 
essence new processes) are started only when the pc has 
brightened up and become quite able by reason of getting 
comfortable about the last one. Realizing that the whole target 
of Level 0 is to get people willing to talk about anything to 
others, a regained ability on a subject governs when to start a 
new process. If the auditor can answer to himself this question 
in the affirmative, then he can go to a new process, "Is this pc 
able to talk freely to or about (subject of last process)?" If 
so, it's all right to select a new question from the same routine 
or a new routine (more rarely) and ask it now. But it is never 
all right to prevent a pc from talking by butting in with a new 
question. One never asks amplifying questions at Level 0. 
Commentary-type questions are also out. The auditor listens to 
the question's answers and only interrupts when he truly hasn't 
heard or didn't grasp some point. No over and over repetitive use 
of commands is made, of course, as that's Level One. The commands 
are given rarely, same commands, but only to get the pc going 
again. Staccato repetitive commands and brief pc answers are not 
for Level 0.

14. Toward the end of the auditing period, the auditor warns, 
"The session time is about over. We'll have to be ending 
shortly."

15. When the pc has given an extra comment or two, the auditor 
says, "We're closing the session now. Time is up. Have you made 
any gains in this session?"

16. The pc's answers are quickly noted.

17. The auditor says, "End of session."

----------

Note: Pcs, of course, often keep on talking and make it hard to 
end a session. End it anyway. If this seems to shock the pc, 
point out the time the session ended as originally set and say 
also, "You'll be getting more auditing and we'll take that up in 
the next session." You'll always have trouble ending a session if 
you fall to put in its time in the R-factor (reality factor) in 
(4) above. As the auditor notes the time in his report (see [4] 
above) he must say, "This session will go until _____ (hours and 
minutes) precisely." Thus, he has an out for ending it. An 
auditor must never run beyond that time set and must, of course, 
audit until it is reached. This, by the way, does not just hold 
good for Level 0. It is very good practice for all levels in 
regular sessions. The only exception is the assist where one is 
auditing toward a definite gain. In general auditing one seeks to 
obtain general gains, not sudden momentary spurts.

----------

The auditor, whether in co-audit or individual session at this 
and the next level, will soon become impressed with this fact: 
The more he himself says during the session, the less gain the pc 
gets. Therefore, aside from the above, the auditor does very 
little in the session and is paid handsomely for it in pc gains.


L. RON HUBBARD
Founder

LRH:jw.cden.gm

_

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

55. HCOB 11 Dec. 1964 Scientology 0 Processes


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 11 DECEMBER 1964

Remimeo
Franchise
Sthil Students
Sthil Co-audit

SCIENTOLOGY 0

PROCESSES


The whole case gain to be expected from a pc at Level 0 is an 
increase of ability to talk to others.

At Level 0 we do not expect or lead people to expect any sudden 
miracle of physical or mental recovery. Rather, we emphasize that 
we are getting their feet on the ladder and as they progress up 
through levels they will achieve all they ever hoped for and 
more.

Jumping to higher levels leaves the lower-level disabilities 
untouched, and while trying to audit somebody at, say, Level III, 
we will find ourselves struggling with things that should have 
been handled at Level 0.

Further, this target is the one that beginning pcs make the most 
gains on in my experience. I recall one near miracle on a girl 
who couldn't bring herself to talk to her parents, and all I did 
was get her to tell me what she'd say to them if she could talk 
to them.

Recalling is too steep for a starting pc. They can't recall well 
really until about Level IV when they can be cleaned up on their 
ARC breaks with life.

Here we have the whole design of Level 0:

"Recover the pc's ability to talk to others freely."

If you realize that a pc can't be in-session unless he is willing 
to talk to his auditor, you will also realize that he can't be in 
life until he is able to communicate freely with others.

Thus, any process that does not forward this end is not for Level 
0, no matter how frantic the case may be to become Clear 
yesterday.

The more hysterical a pc is about getting advanced processes or a 
case gain, the less strenuous the process administered must be. 
The psychiatrist erred on this one point and it wiped him out as 
a social benefactor. The more desperate the case, the more 
desperate were his measures. He was just echoing his patients. It 
is very important for an auditor to realize this one datum for it 
is the second guiding rule of Level 0. It is a very senior datum. 
One must not become desperate and use desperate measures just 
because the pc is desperate or the family or society is desperate 
about the pc. The worse off the pc, the lighter the approach to 
that pc must be.

Psychotics (real, gibbering ones) are below auditing treatment in 
sessions. The measure used for them should be just rest and 
isolation from their former environments. And the first process 
used should be just getting the person to realize you are safe 
and safe to talk to.

So, although a few cases are psychotic, this still holds good. 
The auditor must get the pc to realize he is safe -- won't 
punish, scold, reprimand or betray confidences -- and that the 
auditor will listen.

It doesn't give the auditor a withhold to not speak of another's 
withholds. One can only withhold what one oneself has done. What 
the pc did or said isn't even subject for a session on the 
auditor, for withholding it had no aberrative value.

Even when we're Class VI, we still start all our pcs at the pc's 
level, which is, for a beginning pc, Level 0.

So what we are trying to do with our pcs at Level 0 is the 
following:

1. Recover the pc's ability to talk to others freely;

2. Teach the pc by example the auditor is safe to talk to and 
won't scold, reprimand, punish or betray, and

3. Refuse to engage in desperate measures just because the pc is 
desperate; and therefore get a real, lasting gain for the pc.

ROUTINES

A routine is a standard process, designed for the best steady 
gain of the pc at that level. The remedy is different. It is an 
auditing process which is designed to handle a nonroutine 
situation. The only real remedy at Level 0 is patching up having 
failed to hear or understand the pc. The rest is all done by 
routine. The case remedies are at Level II, and while we all 
realize that every Level 0 case needs a lot of Level II remedies, 
we also know that no remedy will work well until the pc is able 
to talk to others. When you run into trouble at Level 0, there 
are only three reasons possible:

1. The pc was not run in a direction or on a process to improve 
his or her ability to communicate to others;

2. The auditor failed to understand the pc's statements, either 
words or meanings, or

3. The auditor engaged in desperate measures, changed processes 
or scolded or did something to lower the pc's feeling of security 
in the session.

That's all. As you go on up through the levels, you will find 
many other ways a pc can get upset. But at Level 0, the pc is not 
close enough to reality on his own case to even be touched by 
these at first. The pc is a long way off when he first starts 
getting audited. He can only approach his own case by degrees. So 
a pc, no matter how wildly he or she dramatizes at Level 0, is 
really only capable of a reality of the smallest kind about sell. 
And such a pc must be able to talk before anything else can 
happen. Pcs can he ruined by someone who doesn't grasp that 
simple fact. Psychiatrists, failing to grasp it, murdered several 
million people -- so it's no light matter. It's an important one.

A pc at Level 0 usually can't even conceive of an overt (a 
harmful act) done by himself. When they can, they go religiously 
guilty and seek to atone or some such thing. Become a monk. Or 
commit suicide.

The reason 33 1/3 percent of all psychoanalytic patients are said 
to have committed suicide in their first three months of 
treatment is not that they "came too late" but that a lot of wild 
data was thrown at them to get at their "source of guilt" and 
they went head-on into the reactive bank, sought to demonstrate 
their "guilt" by making others guilty and killing themselves.

You don't want anything out of the pc but an increased ability to 
talk relaxedly to others without fear, embarrassment, suspicion 
or guilt. So all processes at Level 0 are arranged accordingly.

WORDINGS

To give all possible wordings of routines that will accomplish 
the above is completely beyond need.

Once you have the idea of it straight, you can invent them by the 
dozens.

One doesn't even have to think of a particular pc. All Level 0 
processes are good only when they apply to all pcs.

ROUTINE 0-0 (ZERO-ZERO)

The starting routine is the most basic of all auditing routines. 
It is simply

"What are you willing to talk to me about?"

Pc answers.

"What would you like to tell me about that?"

At Level II, the first question alone becomes a remedy. Here the 
two questions make a routine -- and a very effective one it is!

ROUTINE 0A

This is how the auditor puts together Routine 0A:

1. Make a list of people or things one can't generally talk to 
easily. That includes parents, policemen, governments and God. 
But it's a far longer list. The auditor must do this. It must 
never be published as a "canned" list.

2. Using any one of the listed items: "If you could talk to 
______ (listed item), what would you say?"

All right, that's all there is to finding the commands for 
Routine 0A.

One doesn't get the pc to do the list. The list isn't done in 
session. The auditor does it himself on his own time. And each 
auditor must do his own list for his pcs and add to it from time 
to time as he thinks of new ones.

The pc isn't necessarily given any choice of items. The auditor 
picks one he thinks may fit. That's easy to do after one session. 
The pc keeps complaining about parents. Okay. Run 0A on parents.

And flatten it!

By flatten is meant to use that one subject until the pc is 
darned sure he or she could now talk to the item chosen. If the 
pc still wants to abuse the item, it isn't flat. If the pc still 
wants to do something about the item, it is not flat. When the pc 
is cheerful about the item or no longer fascinated with it, it's 
flat.

Remember, there's no need to find out what the pc can't talk to. 
In fact, most cases, you're better off just to take an item of 
your own for 0A and use it. May seem strange, but you'll have a 
smoother time of it with the pc. Further, you'll not restimulate 
(churn up) the pc's bank so hard.

ROUTINE 0B

The second routine consists of things to talk about.

One puts the routine together this way:

1. The auditor makes a list (not from the pc but himself) of 
everything he can think of that is banned for any reason from 
conversation or is not generally considered acceptable for social 
communication. This includes nonsocial subjects like sexual 
experiences, water closet details, embarrassing experiences, 
thefts one has done, etc. Things nobody would calmly discuss in 
mixed company.

2. An item from the list is included in the auditing command, 
"What would you be willing to tell me about ______?" Add the item 
you choose.

3. When they have "run down" (as in clocks), ask them, "Who else 
could you say those things to?"

4. Rechoose a subject on the list.

5. Repeat (2) and (3).

6. Continue to repeat (4) and (5).

Above all, don't be critical of the pc. And very calmly hear and 
seek to understand what the pc said. (You never, by the way, seek 
to find out why the pc reacted or responded in some way. A real 
blunder at Level 0 is "Why did you feel that way?" Or "Why do you 
think you can't say that?" You're not after causes of things at 
Level 0. You will find out why at Level VI!) At Level 0, just 
keep them talking while you listen. And you use only the subject 
chosen to keep them talking.

ROUTINE 0C

Routine 0C is, of course, old R1C renamed. It is done without a 
meter and it has any subject under the sun included in its 
command. It is elsewhere covered.

In all the above routines, it is vital not to alter the commands 
given above.

And it is vital to audit with the Auditor's Code in full force.

----------

There are many more possible routines. But to be a Level 0 
routine it must have as its goal only freeing up the ability of 
the pc to talk freely to others.

This is not a level to be regarded with a brush-off. It takes a 
lot of skill to restore a pc's ability to communicate freely.

When an auditor has that skill, he will succeed at all higher 
levels.

When a pc has that skill regained, his world will look to him to 
be a far, far better place.

So it is very important to get over this first hurdle. And very 
important not to dodge it and try to climb the hill anyway. It 
will become an awfully steep hill.


L. RON HUBBARD
Founder

LRH:jw.cden.gm

_

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

56. HCOB 26 Dec. 1964 Routine 0A (Expanded)


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 26 DECEMBER 1964

Remimeo
Franchise
Sthil Students
Sthil Co-audit


SCIENTOL0GY ZERO

ROUTINE 0A (EXPANDED)

(Corrections to HCOB 11 Dec. 64,
PROCESSES, and to HCOB 10 Dec. 64,
LISTEN-STYLE AUDITING)


An additional command increases the usefulness of this routine. 
It is therefore rewritten as follows:

The auditor makes a list of things people generally can't talk to 
easily. That includes parents, policemen, governments and God. 
But it's a far longer list. The auditor must compile this list 
himself or herself out of session. It may be added to by the 
auditor from time to time. It must never be published as a 
"canned list." Scientology Instructors and Scientology personnel 
should not be listed on it as it leads to upset in sessions.

STEP 1. The auditor chooses one of the subjects off the list and 
uses it in Steps 2 and 3 below until the pc is comfortable about 
it. Subjects from the list can be chosen in sequence or at 
random. A chosen subject is not left until the pc is comfortable 
about it. By this is meant, the pc would not feel disturbed 
talking to the subject chosen.

The auditor does not ask the pc which subject or if it is all
right to choose that subject as the pc at the moment of selection
is not likely to feel comfortable about any of the listed
subjects and so will just reject. No, the auditor just chooses
one and starts on it.

STEP 2. The auditor asks, "If you could talk to ________ (chosen 
subject), what would you talk about?" Pc answers one or more 
things at greater or shorter length.

STEP 3. When the pc seems satisfied the question has been 
answered, the auditor then says, "All right, if you were talking 
to ________ (chosen subject in [1]) about that, what would you 
say, exactly?" The pc is expected to speak as though talking to 
the subject chosen in (1).

STEP 4. The auditor notes whether pc is comfortable about the 
subject chosen in Step 1, yet without asking pc. This is done by 
noting the voice tone or text of what the pc would say. If it is 
shy, diffident, or if it is belligerent or annoyed, the same 
subject is retained for a new go with Steps 2 and 3. If the pc 
seems bright and cheerful, a new subject is chosen from the list 
for a working over with Steps 2 and 3. If the subject in (1) is 
retained, the auditor again does Steps 2 and 3 above over and 
over until the pc is cheerful. A subject chosen in (1) is not 
left until the pc really can respond cheerfully. When this is 
accomplished, a new subject is chosen as Step I and the process 
is continued with Steps 2 and 3 using the new subject.

The whole of Routine 0A is flat when the pc feels far more 
comfortable about talking to specific items and isn't shying off 
from items on the list. It is flat, therefore, when an ability is 
regained on specific items on the list and the list items aren't 
producing big new changes in the pc's communication ability.

LISTEN-STYLE CO-AUDIT

It is expected that by the time an auditor is permitted to do the 
Zero routines, individual listen style will have been entered 
upon.

Until the class seems able to run individual sessions, old R1C 
can be used by the Auditing Supervisor on a group basis using 
listen-style co-audit until the group has the idea of sessions.

Routines work best on individual listen style. The pc is always 
wondering, in listen-style co-audit, if the Auditing Supervisor 
is listening to him personally. The auditor is not the receipt 
point of the pc's comm in many instances.

Old R1C is the best training mechanism to get auditors to run 
sessions. In this process the Auditing Supervisor just chooses 
something for all the pcs to talk to the auditors about, like a 
dynamic or a common social problem.


L. RON HUBBARD
Founder

LRH.jw.rd.gm

_

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

57. HCOB 23 June 1980RA Checking Questions on Grades
Processes


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 23 JUNE 1980RA
RE-REVISED 25 OCTOBER 1983

Remimeo
All Auditors
C/Ses
Academy Levels
Tech/Qual


CHECKING QUESTIONS ON GRADES PROCESSES


Refs:
HCOB 12 June 70 C/S Series 2
PROGRAMING OF CASES
HCO PL 17 June 70RB KSW Series 5R
Rev. 25.10.83 TECHNICAL DEGRADES
HCOB 19 Apr. 72 KSW Series 8
C/S Series 77
"QUICKIE" DEFINED
HCOB 3 Dec. 78 UNREADING FLOWS
HCOB 27 May 70R UNREADING QUESTIONS
Rev. 3.12.78 AND ITEMS
HCOB 8 June 61 E-METER WATCHING
HCOB 7 May 69 IV THE FIVE GAEs
HCOB 22 Apr. 80 ASSESSMENT DRILLS


(The original version of HCOB 23 June 80 incorrectly stated that 
an auditor was not to check the processes of a grade for read 
before running them. That HCOB was then canceled on 25 Feb. 82 
and it remains canceled. The person who had originally approved
-- and even taken part in writing -- this incorrect and illegally 
issued HCOB later sought to cover these actions by "discovering 
the error," attributing it to someone else, and "calling it to my 
attention." With this re-revision, all earlier text written by 
others has simply been removed and further HCOB references have 
been added to the list above.)

EACH GRADE PROCESS THAT IS RUN ON A METER MUST BE CHECKED FOR A 
READ BEFORE IT IS RUN, AND IF NOT READING, IT IS NOT RUN AT THAT 
TIME.

This rule applies to subjective grade processes. It does not 
apply to processes that are not run on a meter such as Objective 
Processes or assists (except for metered assist actions of a 
subjective nature).

Actually, a process that "doesn't read" stems from one of three 
sources: (a) the process is not charged; (b) the process is 
invalidated or suppressed; or (c) ruds are out in session.

Factually, pc interest also plays a part in this.

I think quickying came from (1) auditors trying to push past the 
existing or persistent F/Ns or (2) auditors with TRs so poor that 
the pc was not in session. Nearly all grade processes and flows 
will read on pcs in that Grade Chart area unless the above two 
conditions are present.

One also doesn't make a big production of checking, as it 
distracts the pc. There is a system, one of many, one can use. 
One can say "The next process is (state wording of the auditing 
question)" and see if it reads. This does not take more than a 
glance. If no read but, more likely, if it isn't charged, an F/N 
or smoothly null needle, one hardly pauses and one adds "but are 
you interested in it?" Pc will consider it, and if not charged 
and pc in session, it will F/N or F/N more widely.

If charged, the pc would ordinarily put his attention on it and 
you'd get a fall or just a stopped F/N followed by a fall on the 
interest part of the question.

It takes pretty smooth auditing to do this and not miss. So if in 
doubt, one can again check the question. But never hound or 
harass a pc about it. Inexpert checking questions for read can 
result in a harassed pc and drive him out of session, so this 
auditing action, like any other, requires smooth auditing.


L. RON HUBBARD
Founder

LRH:rw.iw.gm

_

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

58. HCOB 3 Dec. 1978 Unreading Flows


HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

HCO BULLETIN OF 3 DECEMBER 1978

All Auditors
All C/Ses
NED Checksheet


UNREADING FLOWS

Refs:
HCOB 5 Aug. 78 INSTANT READS
HCOB 25 May 62 E-METER INSTANT READS
HCOB 28 Feb. 71 C/S Series 24
METERING READING ITEMS
HCOB 8 June 61 E-METER WATCHING
HCOB 27 May 70R UNREADING QUESTIONS
Rev. 3.12.78 AND ITEMS


EACH FLOW OF AN ITEM OR QUESTION IS CHECKED FOR A READ BEFORE 
RUNNING IT. UNREADING FLOWS ARE NOT RUN.

One of the governing laws of auditing is that you don't run 
unreading items. It doesn't matter what you are auditing. You 
don't run unreading items. And you don't run unreading flows. You 
don't run an unreading anything. Ever. For any reason.

Auditing is aimed at reactivity. You run what reacts on the meter 
because it reacts and is therefore part of the reactive mind. A 
read means there is charge present and available to run. Running 
reading items, flows and questions is the only way to make a pc 
better. This is our purpose in auditing. To run unreading flows, 
etc., requires the pc to run "analytical" answers or to "run" 
things that aren't there or to put something there to "run."

The most trouble you can get a pc into is running him on 
uncharged items or flows. For an auditor to sit in session 
watching a meter that didn't read, looking expectantly at the pc 
for an answer to an uncharged question, flow or item is a GAE and 
will wreck cases faster than anything you can do.

So you must check questions, flows or items before running 
anything. If it doesn't read, you just say "Thank you" and go on 
to the next one. You would, of course, use the buttons to ensure 
nothing was suppressed, invalidated or misunderstood before 
leaving an unreading item, flow or question.

This is probably one of the reasons that it has been observed 
that I can audit a pc for two and one-half hours and get the same 
result that another auditor might get in twenty-five hours. 
There's nothing mysterious about it. I never run a pc on things 
that aren't charged. And I don't miss reads.

I expect no less from you.


L. RON HUBBARD
Founder

LRH:jk.gm