No matching fragments found in this document.
Date: 21 Aug 1999 09:52:53 -0000
Subject: FZ Bible NEW TECH VOL XII 04/17 (1980-4)
Newsgroups: alt.religion.scientology,alt.clearing.technology
Message-ID: <14905e75053b8ccee20b868a827837cf@anonymous.poster>
Sender: Secret Squirrel <squirrel@echelon.alias.net>
Comments: Please report problems with this automated remailing service to
<squirrel-admin@echelon.alias.net>. The message sender's identity
is unknown, unlogged, and not replyable.
From: Secret Squirrel <squirrel@echelon.alias.net>
Mail-To-News-Contact: postmaster@nym.alias.net
Organization: mail2news@nym.alias.net
Lines: 2273
Path: news2.lightlink.com!news.lightlink.com!skynet.be!news.belnet.be!news1.carrier1.net!cam-news-feed1.bbnplanet.com!washdc3-snh1.gtei.net!cpk-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.gtei.net!news.alt.net!anon.lcs.mit.edu!nym.alias.net!mail2news-x2!mail2news
Xref: news2.lightlink.com alt.religion.scientology:901017 alt.clearing.technology:97333
FREEZONE BIBLE ASSOCIATION TECH POST
NEW TECH VOL XII 04/17 (1980-4)
**************************************************
NEW TECH VOLUME XII 1980-84
(As issued in 1991 by CofS)
==================
[Because of its large size, the complete contents only appears
in part 0 and part 1.]
CONTENTS:
Part 4
018. HCOB 29 MAY 80RA r. 20 Apr 90 CO-AUDITS: HOW TO RUN THEM
019. HCOB 30 MAY 80RA SUPERVISING CO-AUDIT TRs
020. HCOB 31 MAY 80RA r. 21 Apr 90 STAFF CO-AUDITS
021. NOTE 1 JUN 80 RESEARCH & DISCOVERY SERIES
022. HCOB 19 JUN 80 THE AUDITOR'S CODE
023. HCOB 20 JUN 80 L1C WORD LIST
024. HCOB 22 JUN 80 INT RD CORRECTION LIST WORDS
025. HCOB 23 JUN 80RA r. 25 Oct 83 CHECKING QUESTIONS ON GRADES PROCESSES
026. HCOB 23 JUN 80RA r. 26 Jul 86 WORD CLEARING CORRECTION LIST WORDS
027. HCOB 28 JUN 80RA r. 18 Oct 86 STUDENT CORRECTION LIST WORDS
028. HCOB 30 JUN 80RA r. 26 May 88 STUDENT REHABILITATION LIST WORDS
**************************************************
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 freezoner's are "squirrels" who should be
stamped out as heritics. 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 Judiasm 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
**************************************************
==================
018. HCOB 29 MAY 80RA r. 20 Apr 90 CO-AUDITS: HOW TO RUN THEM
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 29 MAY 1980RA
REVISED 20 APRIL 1990
Remimeo
All Orgs
Tech/Qual
Co-audit Supervisor
Courses
Supervisors
C/Ses
Co-audit Series 2RA
CO-AUDITS: HOW TO RUN THEM
One of the simple secrets of a successful co-audit is
administration.
Without smooth workable lines and hatted terminals on those
lines who really know their business and run a snap and pop
operation no org or mission can expect to succeed with its
co-audits.
However, where lines and terminals are in and functioning
smoothly, rapidly, routinely, you'll have a high volume of
co-auditors, many released pcs routing on to their next
services, an active, uptone course room and new public
banging on the door demanding co-audit courses.
It's a very simple matter to run a highly successful
co-audit. The key to that success is standard administration.
Any co-audit course, whether it is a specific rundown
co-audit package, a professional co-audit on the Grades or
NED or other type of co-audit, follows the principles and
guidelines laid out in this issue.
CO-AUDIT REQUIREMENTS
Any fair-sized co-audit course, if one is to set it up to
succeed, will require at least:
A Co-audit Supervisor-to supervise co-auditing actions. The
Co-audit
Supervisor must be tech trained to a level which enables
him to handle the materials being co-audited.
Course Supervisors-for the theory and practical sections of
co-audits where some preparatory training is done.
In a small org or mission these posts might be covered by
one person, but it is not optimum.
Add to this: (a) a C/S to case supervise the co-auditing
sessions and (b) a Course Admin (who might be able to
service more than one co-audit), and one would have an
ideal scene, personnelwise, for a co-audit set up to
deliver in volume and expand.
CO-AUDIT THEORY
Refs:
HCO PL 2 Dec. 62 SUPERVISOR'S STABLE DATA
HCO PL 24 Oct. 68 SUPERVISOR KNOW-HOW RUNNING THE CLASS
HCOB 25 June 71R Word Clearing Series 3R Rev. 25.11.74 BARRIERS TO STUDY
Anyone dealing with the administration and supervision of a
co-audit course must realize first and foremost that it is
not a study course. It is not a study activity. It is a
doingness activity. Students are there to do the actions of
auditing, not to learn theory. This must be the
Supervisors' orientation toward the course.
The students enrolling on the course are going to be eager
beavers and the Course Supervisors must have the attitude
of contributing to the enthusiasm the students will bring
to the course. The students will be there to move further
along the Bridge and this is what the Supervisors must make
sure happens.
Auditing, auditing, auditing is what is stressed and that
is what is delivered.
On a professional co-audit, the co-auditors will already
have been trained in the theory and skills of the level
they are auditing.
On a rundown co-audit package, co-auditors will often have
no previous
technical training. New co-auditors do have to learn what
they will be applying but this has been cut down to the
bare bones essentials. They are given mainly the "How" and
only enough of the "Why" to make their co-audit actions
meaningful.
The student is not being trained here to think with his
materials. He is being trained to exactly apply the
auditing procedure rat-tat-tat. If the pc does "A," the
auditor is trained to respond with "B." And auditor and pc
alike soon learn that this produces results.
Also, for all their eagerness these students will not
necessarily have done a Student Hat so they will be
operating without the benefit of a command of study tech.
For these reasons, the Supervisors must be particularly
good at spotting and handling the manifestations of
misunderstood words and manifestations of skipped
gradients. The third barrier to study, lack of mass,
probably won't be as prevalent on a co-audit as on a
straight study course, but might possibly occur on any of
the co-audit's theory sections. Not being trained in study
tech, the students will not
necessarily be able to spot these things. The Supervisors
must be alert for them and handle them when they occur.
TWINNING AND COURSE ATTITUDE
Ref:
HCOB 21 Aug. 79 TWINNING
HCO PL 23 July 69 AUDITOR ASSIGNMENT POLICIES
HCOB 21 Aug. 79, TWINNING, is applied to the letter on
co-audits. Nowhere is this tech more applicable than on a
co-audit course.
Twinning also enhances the atmosphere the Supervisors must
establish on the course.
CO-AUDITORS ARE TWINNED ACCORDING TO COMPARABLE CASE
AND TRAINING LEVEL. People who intend to co-audit and
Co-audit Supervisors must be alerted to the fact that you
don't twin up mis-matched co-audit teams-e.g., a lower
level pc with a NOTs pc, etc. This is fully covered in the
above references.
Once twinned, co-auditors should not be musical chaired.
It is important that the Co-audit Supervisor twin students
correctly. Properly twinned co-auditors will fly along
while poorly twinned ones will generate problems, and where
there is a big difference in ability, create an
out-exchange situation in which the faster twin is always
coaching the slower one to get him to catch up.
A co-audit course is a team activity. It is a
jump-in-and-do-it activity and the Supervisors establish
this as the operating tone of the course from the first
day. The activity level of the course is very high.
The Co-audit Course Supervisors would exemplify this
attitude by being human dynamos in the course room and this
would rub off on the students.
The Co-audit Supervisor's activity level must be high
because he deals heavily in individual attention to each
student, co-auditor and pc. He must maintain a high level
of ARC with each student. He must always be approachable by
the students and stay in good comm with them.
The students will not be perfect students and this makes
individual attention for students a prime Supervisor duty.
THE COURSE ROOM/THE CO-AUDITING ROOM
The Course Supervisor(s) and the Co-audit Supervisor(s)
have different and distinct zones of operation on a
co-audit course.
Ideally, the course is divided into a study section, a
practical section and a co-audit section. These would exist
in separate rooms, each with its own Supervisor(s) in order
to provide the best possible study and auditing environments.
Where the above is not possible, the theory part of the
co-audit course would be done in one room with the Theory
Supervisor and the practical and coauditing part of the
course would be done in another room, with the Co-audit
Supervisor.
The theory and practical sections are not put together in
the same room.
The theory course room, practical course room and co-audit
course room would be as near as possible to one another in
the org. It is, after all, one course! In the co-audit
room, the auditing tables would be set up with the auditors
sitting with their backs toward the center of the room and
the pcs facing inwards toward the center.
In this way, the Co-audit Supervisor can monitor each
session from the center with a minimum of walking about.
NEW STUDENTS
When a new student enrolls he is greeted and welcomed by the
Course Supervisor (and the Co-audit Supervisor if available).
Right then and there the student gets indoctrinated with
the idea that this is a gung-ho activity, that the students
help each other out and take responsibility for one
another. He is also informed about twinning and given the
datum that the better the auditing he delivers the better
will be the auditing he receives. This is factually true
and has been proven over the years. He is informed that it
is to his advantage and best interests to become as
competent an auditor as possible.
BEGINNING MUSTER
The co-audit course begins on schedule with a roll call of
both the students on theory and the co-auditor teams (who
are mustered in the study room). Roll call is done this way
so that there is only one roll book and accurate 8-C can be
run.
Tight scheduling must be maintained in both theory and
co-audit room. Every minute counts if these students and
co-auditors are to get the most out of their scheduled periods.
Immediately after the initial muster the two teams split
up-students on theory sections to their seats in the study
area; co-auditors to their sessions in the co-audit room.
RUNNING THE COURSE
All points of HCO PL 16 Mar. 71R, WHAT IS A COURSE? must be in
on any co-audit course. HCOB/PL 30 Oct. 78R, COURSES-THEIR IDEAL
SCENE, must also be in.
A standard roll book, routine roll call each period,
student graphs, a Progress Board, are all used. The
materials that will be needed on the course must be readily
available. (This includes auditor admin materials.)
The course and the co-audit are both run with good stiff
control and ARC.
The Supervisor gets right onto targeting students for the
period after the beginning muster. He then works to ensure
every pair of students makes or surpasses their targets.
If there are a lot of checkouts for him to do, it is best
to have a sign-up sheet at the front of the room. This puts
order into the activity and makes it predictable for the
students. On a course of any size at all, a sign-up sheet
is a necessity to keep things from falling into chaos.
Heaven forbid that the Course Supervisor would ever be
caught at his desk during course hours! No! He would be out
moving about the course room, ensuring the students
studying their course packs were learning the data and that
the students drilling had their drills down cold. He'd be
watching for students manifesting MUs and jumping in to
handle when he spotted one.
He gives students studying their packs spot checks to
ensure they are getting what they are studying. If they
aren't, he gets the MU found. If he can't get it located
quickly, he sends the student to the course Word Clearer
or, lacking one or when extensive word clearing is needed,
to Qual for word clearing.
On practical checkouts the Supervisor cannot really afford
to turn it into a coaching session and get stuck with one
pair of students at the expense of everyone else in the
class. Either the student being checked out has the drill
down or he doesn't.
If he does, great; pass. If he doesn't, the Supervisor
issues the student a pink sheet with the errors noted and
what he has to do to correct it so the student will pass on
the next checkout.
Pink sheets are handled in the course/co-audit room, by the
student coauditor's twin or the Supervisor. Only if the
student became hopelessly bogged would he be sent to Cramming.
The Supervisor would give every student individual
attention and wouldn't get stuck with any one pair of
students for too long a period.
He would be moving from team to team, seeing how they were
doing, checking out their drilling, correcting outnesses
when he saw them, always encouraging them and establishing
the reality that they can audit successfully.
He would use every bit of supervisor tech at his disposal
to get students through their drilling and onto the
co-audit. And quickly. The student reads the material,
drills it and he does it. One, two, three.
HANDLING TRs AND OBJECTIVES CO-AUDIT STUDENTS
Many students on the TRs and Objectives Co-audit Course
will be fresh off the Purification Rundown, without having
done a Student Hat or any other Scientology course. But
putting someone through an Objectives co-audit does not
require any education to speak of; the Supervisor simply
demands that the student reads his course materials, drills
the exact actions and then does them on his twin.
For example, I have done this at as shallow a level of
getting two staff members and making them run Op Pro by Dup
on each other, 35 hours given and received.
They didn't have any coaching to amount to a hill of beans,
but they did it with excellent results.
A Supervisor would not allow a TRs and Objectives Co-audit
student to spend time clearing words within definitions of
words. The Course Supervisor would rapidly get the
misunderstood word handled, the student through the
materials and onto doing the TR or action.
There may also be circumstances where the co-auditor may
need to refer back to his materials during a session to get
the process commands straight. This does not mean the
session is bogged requiring Supervisor intervention. A
coauditor is free to look at the commands if he needs to
while running a process, and that he does so does not imply
that the session needs to be stopped so he can drill the
process further before continuing.
The Co-audit Supervisor must keep in mind that he is not
trying to get the student to do anything by study; he's
trying to get him to do something by actual action in the
auditing chair.
RUNNING THE CO-AUDIT
The Co-audit Supervisor's job is to ensure that auditing
occurs and that it is successful auditing and that the pcs
make the expected gains on their auditing.
Before the co-audit class starts, when the folders have
come out from the C/S, the Co-audit Sup checks each one,
notes what the pc needs and puts the folder in its proper
stack (to Co-auditor, D of P, Declare, Co-audit Sup
handling, Ethics, MO, Review, etc.). He then battle plans
his day to get all the actions done in the proper sequence.
For example, he would plan to do pc A's D of P interview,
get pc B to the MO, get pc C into session with his
co-auditor, make sure pc D's MAA interview gets done by the
MAA, etc. In this way he assures that the pcs make the
fastest progress possible. He doesn't want to spend time on
these administrative cycles once there are sessions going,
so he gets them planned out before course.
After roll call and muster at the start of class the
Co-audit Supervisor gets right down to 8-Cing co-audit
teams into session. He passes out the folders from the C/S
and handles any questions or uncertainties the auditor may
have about the C/S instructions. He does this by reference
to course materials and not by verbal tech. He then
arranges the co-audit teams in the auditing area and gets
the sessions going.
The Co-audit Sup must budget his time wisely so that maximum
co-audit production can occur. If one twin needed ruds to
start a session and another twin needed a D of P interview
but would not be going right into session after it, the Sup
would do the ruds first and get those twins into session.
Then he would do the D of P interview.
Once the sessions have started, he is there observing the
sessions.
He acts as a monitor for each co-audit session.
He ensures that if it's muzzled co-auditing that is to be
done, the co-auditor remains muzzled giving only command
and acknowledgment.
He is there to help out if a co-auditor gets into something
he can't handle. If a co-auditor gets into trouble, he
alerts the Co-audit Supervisor by putting his hand out
behind him. The Co-audit Supervisor comes over and, getting
in comm with both the auditor and pc, finds out what is
happening. This is done with good TRs and all points of the
Auditor's Code in. The Co-audit Supervisor would put in a
good R-factor to the pc about what was going on and include
the pc in any discussion. The pc may say he spotted why he
had done something and that he felt really good at that
point and that would be the bug right there- overrun. In a
metered session the Co-audit Supervisor might have to look
over the worksheets to find out where the session went amiss.
Once he finds the goof, he shows the auditor what to do to
remedy it per source references, and gives the pc another
R-factor about what the auditor will do.
The Co-audit Supervisor has to know his tech cold and be
able to figure out at a glance what is wrong with a session
and instruct the co-auditor (with the proper source
reference) what to do to put it right.
At no time does he criticize or belittle the auditor, or in
any way lower the auditor's altitude in the session. The
Co-audit Supervisor doesn't violate Auditor's Code clause
20 by explaining or justifying any auditor mistakes to the
pc. Nor does he invalidate the pc or evaluate for the pc
and tell him what is going on with his case.
The Supervisor steps in only to isolate the bug, get any
BPC found and indicated and get the auditor to resume the
session.
If the cause of the session difficulty isn't apparent, the
Co-audit Supervisor would R-factor both pc and auditor that
he is going to put the pc on the meter (if he isn't
already) and find what's bugging the session. (The Co-audit
Supervisor would keep copies of the appropriate correction
lists on his clipboard and readily available.) He makes it
clear that he is not taking over auditing the pc; he is
simply finding the session bug. He takes the auditor's
chair and, using the prepared correction list for the
co-audit materials, he assesses the list by the appropriate
method. If the co-auditor is trained to handle the read (or
reads), the Supervisor instructs the co-auditor on what to
do to handle it (according to the list instructions) and
gets the co-auditor back in the chair and running the session.
Should the Co-audit Supervisor find that what reads on the
list is something that the co-auditor is not trained to
handle but which the Supervisor is qualified to handle
(such as an out-rud, overrun, etc.), the Supervisor may
handle it then and there providing it would not keep him
away from supervising his other co-auditors for too long a
period of time. As soon as the pc's BPC is handled to F/N
and VGIs the Supervisor turns the session back over to the
co-auditor.
If the trouble is something which would require more
extensive handling, such as an Int Rundown or review
auditing of some sort or if the Co-audit Supervisor is not
qualified to handle the charge found on the prepared list,
he would indicate the charge found to the pc and R-factor
him that the folder must go back to the C/S for
instructions. He would then turn the session back over to
the auditor to end it.
Needless to say, the Co-audit Supervisor must guard against:
1. Verbal tech, and
2. Any kind of case evaluation or invalidation going on on
a co-audit course.
He must come down hard especially on any person who is trying
to belittle pcs or co-auditors or invalidate the case wins
or case problems or case oddities of any pc. Such offenders
must be gotten out of the space and sent straight to Ethics.
(Ref: HCO PL 1 July 65, ETHICS CHITS)
INTERRUPTING SESSIONS
The Supervisor must be able to quickly recognize any bad
indicator and must stay on the alert for them. If he
notices some-thing going wrong in a session he doesn't have
to wait until the auditor puts out his hand for help but
can gently step in and handle.
The Co-audit Supervisor must, however, give the auditor
sufficient opportunity to spot that something is wrong with
the session. If the Supervisor interrupts sessions all the
time and bypasses the auditor, the auditor may stop taking
responsibility for the pc and the session because "if
anything was wrong with the session the Supervisor would
jump in and take over." The auditor might decide he doesn't
have to concern himself with how his pc is doing because
"the Supervisor will do all of that." The goal in all of
this is to get a win for the co-audit team and get the pc
through his auditing.
RULE
The rule to follow in handling session difficulties is:
IF THE CO-AUDITOR CAN HANDLE IT, HE HANDLES IT.
The Co-audit Supervisor always maintains an encouraging
attitude, good TRs and the certainty that the auditor will
pull off the session. He never expects the auditor to do
anything above his training level, but he does expect him
to successfully audit what he has been trained to do.
The Co-audit Supervisor never steals the co-auditor's hat
but only borrows it for very short periods of time and even
then doesn't exclude the co-auditor from the proceedings.
He doesn't allow himself to become the auditor no matter
how much the pc may seem to demand it or how rattled the
auditor may appear at having made some goof. With ARC and
certainty he isolates the bug in the session, gets the
co-auditor to straighten it out or straightens it out
himself and gets the co-auditor to continue the session.
CAUTION
The Co-audit Supervisor must be sure not to become the pc's
auditor completely because then the pc is likely to
reactively create more trouble in order to get further
attention.
If at all possible, the co-auditor must handle the session
and bring his pc through it. Coming through a rough session
to a win is a tremendous morale booster and nothing will
more raise an auditor's confidence in the tech and his
ability to apply it.
AUDITORS DO NOT LEAVE THEIR PCS
The Co-audit Supervisor never assists an auditor who has
left the auditing chair or walked off from his pc to get
the Co-audit Supervisor to help. Should an auditor leave
his pc to seek assistance, the Co-audit Supervisor firmly,
but with ARC, tells the auditor to go back to his pc and
put his hand out behind him. The Supervisor then assists
that auditor as soon as he possibly can.
Permitting a co-auditor to leave his pc violates the
Auditor's Code clause 10, "I promise never to walk off from
a preclear in session," is bad form and adds unnecessary
randomity to the co-audit room. Co-auditors must be
R-factored about this procedure before they begin auditing.
SESSION ADMIN
The Co-audit Supervisor monitors the sessions until the
last one is finished. He gets the auditors to write up
their sessions correctly and legibly for their pcs' folders.
The Supervisor is responsible for the quality of the
co-auditors' admin and must see that the folder admin is
correctly done.
The Co-audit Supervisor also keeps a logbook in which each
co-auditor logs the number of hours he audits daily. In
this way both the co-auditors and the Co-audit Supervisor
have a ready record of the total number of hours co-audited
for the week.
Any co-auditors who finish their sessions early and have
their admin done and folders turned in before the end of
the class period can spend the remaining course time
helping out by drilling with other students or drill
themselves, etc.
When the last session is over for the course period and the
co-auditors have written up their sessions, the Co-audit
Supervisor ensures the Course Admin gets the folders over
to the C/S office. The Co-audit Sup should make it a point
to attend the end-of-class muster and should ensure that
his co-auditors are also there.
However, sessions that were still in progress at the end of
the course period would not be ended for these musters, nor
would the Co-audit Supervisor leave any sessions in
progress to attend the musters.
MUTUAL OUT-RUDS
The theory of mutual out-ruds is covered in HCOB 17 Feb.
74, C/S Series. 91, MUTUAL OUT-RUDS. Mutual out-ruds can
stack up on courses and the Supervisors must be sharp in
recognizing indicators in a pair of students with out-ruds
on the rest of the group, and get them handled.
A co-audit team withdrawn or out of comm with the rest of
the class could be a mutual ARC break or withholds. A pair
going around looking overly concerned or hunted likely have
a mutual problem. Two students joking or being snide
obviously have withholds from the group.
Now these things could also stem from something
misunderstood in their
training and the Supervisor must detect this and handle by
finding the MUs and straightening out the student's
drilling and procedure. Whatever the cause, the Supervisor
must not let mutual out-ruds go unhandled and the C/S must
order checks for mutual out-ruds when necessary to keep a
co-audit team's ruds in on each other and on the group.
Failing to do this can cost dearly in terms of lost gains
for pcs.
Mutual out-ethics must be spotted and handled as well.
(Ref: HCOB 13 Oct. 82, C/S Series 116, ETHICS AND THE C/S)
BLOWY STUDENTS
Students who are blowy or who have blown must be recovered
and handled.
They must first be checked for BPC in their sessions and
out-tech on their cases and then checked over for MUs and
overts and withholds as co-auditors.
Since they are engaged in both receiving and giving
auditing, both aspects must be thoroughly checked. When the
session BPC is found or the out-Int handled or the O/Ws
pulled such blowy feelings will cease.
The blown student's twin is responsible for recovering his
course partner per HCOB 21 Aug. 79, TWINNING.
REMEDIES
As mentioned before, students on the co-audit will be eager
beavers but may be unhatted on study tech and will need
help over any rough spots they may encounter.
The Supervisors have to know and use their available tools
to guide the student through such impasses.
On the study portion of the course, the Course Supervisor
has to be able to spot a student with an MU a mile off and
handle it rapidly and with ARC. If he cannot locate the MU
or bug easily he utilizes the course Word Clearer. If the
student is really plowed in, it is a job for Qual. Don't
let the bogged student stagnate on course and don't ever
buy any confused "it-can't-be-dones." We've had co-audits
for over 30 years in Dianetics and Scientology and the
co-audit courses have always been very, very successful.
The lack of mass phenomena won't be as likely to occur here
as on a theory course because of the amount of practical
prior to the auditing section but it must be handled and
remedied quickly if it does occur.
The most frequently observed manifestation on the drills
section will very likely be the skipped gradient. (Ref:
HCOB 25 June 71R, BARRIERS TO STUDY) If the student is
having trouble with a drill he's come up on too steep a
gradient. The remedy is to cut back to the action or drill
where he was doing well, where he understood it and was not
confused. Find out what he missed right at the tail end of
that action or drill, because that's where he thought he
had it down pat and went on and right there he skipped a
gradient. Clear up what he missed at that.point and bring
him forward again, on the right gradient, to where he was
having trouble. Now he will be able to do the drill because
he truly understands the earlier gradient.
The badly bogged student probably needs a trip to Qual for
handling. In such cases the bogged student's twin goes too.
For one half of a co-audit team to get so plowed under
means it is very likely that something is awry with the
other half of the team. Qual would check both students and
probably have to straighten both out.
The Co-audit Supervisor would mainly be remedying bogged
sessions. It may sometimes occur that the Co-audit
Supervisor notices something out with a session while
watching, before the auditor puts out his hand or is even
aware something is wrong. The Supervisor wouldn't let the
session fall completely to pieces even though the
co-auditor hadn't asked for help. Neither would he just
jump in without giving the co-auditor ample opportunity to
handle the session difficulties himself.
After determining what was wrong, the Supervisor would
place his hand gently on the auditor's shoulder and get in
comm with the pc and auditor. Without eval or inval he
would instruct the auditor with the appropriate source
reference on how to correct the situation.
For example, in a Dianetics co-audit the Supervisor notices
that the pc's TA has been going up and up while being run
on a somatic chain, but the auditor isn't checking for an
earlier incident. The Supervisor would place his hand on
the auditor's shoulder gently, R-factor the pc that he
wanted to interject something into the session and then
suggest to the auditor that he try checking for an earlier
incident or earlier beginning. Then he sees to it the
auditor does so and gets on with the session.
It is important to let the co-audit teams know what the
Co-audit Supervisor's purpose is. He is there to run the
class, oversee the sessions and ensure that the pcs achieve
the greatest gains possible from their auditing. He is not
there to run the session or audit the pc. The co-auditors
do the auditing.
RED TAG SESSIONS
In the event of a session that red tags at exams it must be
repaired within 24 hours per C/S Series 86RE, THE RED TAG LINE.
Occasionally a pc will red tag at exams after the session.
When this happens, the Supervisor does not take a
condemnatory attitude towards the auditor. And he certainly
does not let the auditor rabbit from further auditing even
if the pc must go to Qual for a review session.
Normally, the co-audit team will audit on a turnabout
basis. On Monday Joe audits Bill for the first part of the
class time and then Bill audits Joe for the second part of
the class period, etc. Or on Monday Joe audits Bill, on
Tuesday Bill audits Joe and so on. In the event of a
red-tagged session the pc would need to be handled until
repaired and the red tag removed. It is optimum for all
concerned that the co-auditor be instructed on how to
handle the goofed session and repair it himself if this is
feasible. However a review session in Qual may be needed.
That is up to the C/S who should keep in mind that this is
not an HGC operation and that the co-auditor handles his pc
except in dire circumstances.
Sending the pc to Review would only be done if the session
bug couldn't be spotted in the worksheets or by observation
or if a Scientology auditor was needed to fly the ruds or
do a Date/Locate, handle Int, etc.
If the co-auditor can handle it and it is within the scope
of the co-audit materials, he would take the pc right in
the next day and handle it. He may need to do a bit of
drilling on his procedure first but would still go back in
there and handle his pc. This keeps the members of the
co-audit team taking responsibility for each other. Of
course, the red tag session must be repaired in 24 hours no
matter who does it. This rule is invariable.
STATS
The Course Supervisor's stats are:
1. Student Points.
2 . Number of students moved through the theory and onto
the auditing portion of the course that week.
The Co-audit Supervisor has the stats of:
1. Co-audited WDAH.
2. Co-audit course completions.
The Co-audit student/auditor has the stats of:
1. Student Points.
2. Number of co-audited WDAHs.
(Note: The 24-hour rule for repair of any flubbed/red-tagged
session applies. The penalty for violation of the 24-hour rule
is loss of a day's stats for the division. [Ref: HCO PL 8 Sept.
70RA, EXAMINER'S 24-HOUR RULE])
I have given you the essentials for a successful co-audit.
For any co-audit, following the instructions in this issue
will give you a bustling, high morale co-audit course with
shiny completions rolling out the other side and further up
the Bridge.
Co-audits throw the gates to the Bridge wide, wide open.
They enable orgs to deliver far more auditing hours to more
public and staff than anyone ever dreamed possible. And
it's economical for the orgs and public, too.
Scientology is in an international boom, Supervisor, and I
am counting on you to do your part in keeping the boom going.
While we now have thousands making daily progress up the
Bridge, we have the line-up to handle millions. Millions of
Clears and OTs.
Do your job well and we'll have wins all around.
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================
019. HCOB 30 MAY 80RA SUPERVISING CO-AUDIT TRs
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 30 MAY 1980RA
REVISED 21 APRIL 1990
Co-audit Courses
Tech/Qual
Co-audit Series 3RA
SUPERVISING CO-AUDIT TRs
Ref:
LRH Technical Training Film number TR Fifteen,
"The Different TR Courses and Their Criticism"
Between Dept 17 TRs courses for brand-new people, which are
fairly permissive, and professional auditor TRs, which result
in the smooth, flawless comm cycle required of a professional
auditor, we have Co-audit TRs.
These are the TRs given to those who are not yet on the
professional training route but who are training to give
and receive auditing on a co-audit basis on rundowns and
other co-audits designed for the nonprofessional.
They are the same drills, TRs 0-4, that are done on the
Professional TR Course.
But on Co-audit TRs you are not trying to make a professional
auditor.
You give the co-auditor a chance to get his feet wet, to
get a taste of what's expected of him on TR drills and to
get some experience with them. You coach and supervise him
to some good wins, to where he gets the hang of it, and you
leave it at that.
The way to accomplish this is to start him on an easy
gradient and have him cycle through the TRs, getting a bit
stiffer each time he cycles through.
He would cycle through TRs 0-4 first, until he had achieved
some confidence with those TRs.
He would then go onto Upper Indoc TRs 6-9, cycling through
them and getting a bit stiffer each time through, until he
had achieved some confidence with TRs 6-9.
Thus, the steps in training a person on Co-audit TRs would
include, as a minimum:
1. Drilling TRs 0-4 (as listed in HCOB 16 Aug. 71R II,
TRAINING DRILLS REMODERNIZED) by cycling through these
on a gradient and stiffening the gradient each time through,
until the person has achieved confidence in his ability to
use them:
OT TR 0
TR 0
TR 0 BB
TR 1
TR 2
TR 2 1 / 2
TR 3
TR 4
2. Drilling Upper Indoc TRs (per HCOB 7 May 68R, UPPER
INDOC TRs), again cycling through these on an increasing
gradient until the person has achieved confidence in his
ability to use them:
TR 6
TR 7
TR 8
TR 9
If the student is having trouble and really flubbing on a
certain TR, he might want to spend a bit more time on that
one. But do not let him get stuck on trying to master one
TR. The fault will be in an earlier TR or in the theory
study of his course materials where something was not
grasped or learned fully enough.
You want him up to being able to apply his TRs passably in
a co-audit session with a terminal of comparable case level
and training to his own. That doesn't mean your coaching or
supervision is any less spot on. It doesn't mean the
co-auditor doesn't give it the best he's got or that he's
permitted to be sloppy or chop up pcs. It does mean that
you don't demand of a person on a nonprofessional co-audit
the same polish, the same expertise you're going to demand
of a student on an auditor training course who will need to
perfect his comm cycle to the point where he can handle any
case, any pc, any situation confidently and with ease.
Don't confuse these two levels of TRs.
Don't let your professional auditors-in-training get by
with anything less than perfect TRs. But with the person
who's there to bootstrap his way through, giving and
getting some auditing any way he can, realize you're not
out to make a professional auditor of him-yet.
Get him to the point where he can handle a session as a
co-auditor. When he's had some wins at that, when he's
discovered just what can be accomplished in auditing
sessions, he'll probably be reaching for professional
auditor training. And that's when you give him professional
auditor TRs, done the hard way.
Meantime, for beginning co-auditors, keep Co-audit TRs in
their own sphere.
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================
020. HCOB 31 MAY 80RA r. 21 Apr 90 STAFF CO-AUDITS
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 31 MAY 1980RA
REVISED 21 APRIL 1990
All Orgs
All Staff
and Execs
Qual Sec
SSO
Co-audits
Co-audit Series 4RA
STAFF CO-AUDITS
Refs:
HCO PL 20 July 70 CASES AND MORALE OF STAFF
HCO PL 14 Dec. 70 Personnel Series 14 Org Series 19 GROUP SANITY
HCO PL 17 June 63 STAFF CLEARING PROGRAM
HCO PL 21 Oct. 62 AUDITING SUPERVISOR AND AUDITING INSTRUCTORS, DUTIES OF
HCOB 7 Apr. 60 A NEW SUMMARY OF AUDITING
HCOB 21 Aug. 79 TWINNING
HCO PL 22 May 76 STAFF SECTION OFFICER HAT
HCO PL 30 Nov. 76R ONLY SSO CAN TIP Rev. 25.4.79
HCO PL 29 Oct. 79 SSO RESPONSIBILITY FOR STANDARD STAFF COURSES
HCO PL 23 July 69 AUDITOR ASSIGNMENT POLICIES
Tape: 7109C05 "A Talk on a Basic Qual"
Co-audit Series HCOBs
Org staffs are made up of individuals. The better the case
shape of each individual staff member, the more viable the org.
If an org is going to prosper, its staff must be getting
audited, making case gain and actively progressing on the
Grade Chart. Failure to use the tech on one's own staff is
one of the fastest ways to allow the tech to go out or slip
into disuse or become alter-ised.
Staff need a reality on the tech they deliver-not just
those technically trained who do the actual delivery but
those working in admin capacities as well.
And quite apart from the fact that inattention to staff
cases will result in a failing org and dwindling viability
and potential, is the fact that staff members should have
the benefit of the tech they are handling and making
available to others.
How does an org get all its staff audited? Every org should
have Staff Staff Auditors as provided on the org board. Not
all orgs do have them, but where they do, these auditors
serve a needed function and are valuable.
So how does an org get all its staff audited? The answer of
course is STAFF CO-AUDITS.
We have had co-audit tech since the early days and it's
high time we revitalized it and put it into active use as
one of an org's standard functions.
To create an immediate upsurge in staff morale, activity
level and enthusiasm all you have to do is establish a
going staff co-audit. It takes only some good planning and
a bit of determination. Among staff, the need and the want
and the interest are there. If you want to prove it, just
fan that interest a bit and watch what happens!
HOW TO ORGANIZE A STAFF CO-AUDIT
Qual is responsible for staff cases. A staff co-audit would
be organized and set up in Qual, in the Department of
Personnel Enhancement under the SSO.
The first actions of the Qual Sec and SSO would be to work
out the barebones essentials for a co-audit and get a
Supervisor selected.
An org of any size will require a single-hatted Co-audit
Supervisor and this had better be someone who knows how to
audit and can run good 8-C or he won't be able to handle
the entire scene or individual co-audit teams when they run
into trouble.
In a small org where there's no one available to be the
Co-audit Supervisor, the SSO holds the hat from above. And
if there's no SSO posted, it's the responsibility of the
Qual Sec to get a staff co-audit set up and running.
But regardless of who does the initial planning and setup,
there's got to be a trained Co-audit Supervisor in
attendance at all scheduled co-audit times who is actively
running the show. And he will need at least some part-time
help.
A staff co-audit doesn't eliminate the need for Staff Staff
Auditors. Staff Staff Auditors are very much a part of the
Qual org board, and even with a staff co-audit running they
would still need to handle individual cases and would also
be used as Review Auditors for the co-audit.
If the org has no Staff C/S, C/Ses will need to be set up.
These can be assigned from trained staff who volunteer or
are selected to help out on this basis after production hours.
Get some space allocated, arrange for any needed furniture,
chairs, tables, adequate paper, etc., and most important of
all-the needed tech materials. Don't let lack of equipment
be a bug. In one successful co-audit a couple of years ago
and in early co-audits as well, staff audited with a meter
on one knee and a clipboard on the other! Not ideal but
where it's necessary it can be done and can even add to the
esprit de corps. It's a matter of what it takes to get the
job done.
Set up a schedule that will accommodate the majority of
staff. Two scheduled co-audit periods may have to be
arranged so as not to disrupt regular production. This
would be done in liaison with other execs.
As soon as the general plan is established, hold a rousing
good staff muster and let the entire staff know what's
going to be done. The staff co-audit is for everyone- the
trained and the untrained.
The original maxim holds true: any two people can do it.
The untrained will simply need tighter guidance in order to
carry it off. Get some real enthusiasm generated and you'll
find you have no shortage of volunteers to help with the
initial setup. The way to get a staff co-audit rolling is
to make it an all-hands action.
The rest of the planning and execution takes shape from
there. It includes: 1. Review of all staff cases and staff
folders made ready for C/Sing. Get the staff cases sorted
out as to category, as covered in HCO PL 20 July 70, CASES
AND MORALE OF STAFF. Where staff cases have been neglected
you may need a corps of FESers to begin with to get all the
folders FESed so the C/S can operate with full data.
2. Get the folders programed and C/Sed.
3. Arrange that any staff who need medical treatment, PTS
handling or ethics handling are handled on a priority basis
so they can get onto the co-audit as soon as possible. This
gets done simultaneously with getting the co-audit into
operation.
4. While all this is going on, the Co-audit Supervisor or
the SSO, or both, get themselves trained up and boned up on
all the tech on co-audits and how to run them.
5. Set up the necessary admin lines and lines for folders
to and from the C/S.
6. Get the staff who can start immediately twinned up
according to comparable training and case level per HCO PL
23 July 69, AUDITOR ASSIGNMENT POLICIES, and HCOB 21 Aug. 79,
TWINNING. Note: lt's not ideal to twin up family members or
marital teams, if it can be arranged otherwise. There is a
greater possibility of mutual out-ruds between such teams,
as well as the possibility of overts or withholds from each
other, which could result in unnecessary difficulty on the
co-audit. Twin them up with other partners and it will very
likely go more smoothly. Additionally, don't break up any
successful existing co-audit teams when setting up the co-audit.
Keep these maintained.
7. START the staff co-audit and keep it rolling.
WHAT IS RUN ON A STAFF CO-AUDIT
All programing and C/Sing of cases for a staff co-audit is
done against the Grade Chart.
On a staff co-audit you have two main zones of
activity-co-auditing for the trained and the untrained.
In the first group you'll have staff with different levels
of training and in both groups you'll have different levels
of cases.
Where twinning is concerned, the two groups are handled
separately.
Those in the trained group are twinned with others in the
trained group, taking training and processing levels into
consideration. Those in the untrained group are twinned
with others in the untrained group, taking case levels and
study speed into consideration.
From there it's a matter of what needs to be run to get the
person on or up the Grade Chart.
While the co-auditing is all done in one room, it will save
wear and tear on the Co-audit Sup to have the trained staff
seated together in one section and the untrained staff
together in another section nearby. This way he can more
easily keep an eye on the new green auditors and pcs who
will require the most attention. But he does not neglect
one group for the other. (It is not mandatory for
professionally trained co-auditors to be closely supervised
in the classroom while they are in session. They normally
can be trusted to audit in a separate auditing room if the
pc prefers this to the classroom co-auditing setup.)
Ideally, all staff would do the following if they have not
already completed these steps:
1. The Purification Rundown (not an audited action).
2 . TRs and Objectives (as taught on the TRs and Objectives
Co-audit Course).
3. A Scientology Drug Rundown (or a NED Drug Rundown, if the person
has completed his Grades and is ready for NED.)
4. Method One Word Clearing (as taught on the Hubbard
Method One Word Clearing Co-audit Checksheet).
This is a matter for the C/S to determine according to
individual cases.
Those who are complete on the above opening steps for all
cases would then be programed for their next Grade Chart
action, whatever that might be.
TRAINED CO-AUDlTORS: Trained personnel are expected to
apply the skills of the highest level they were trained in
if that is what is required for the pc. Some of them may
need redrilling on certain actions or study of new
bulletins that have come out since they were trained.
When a team of trained staff co-auditors have audited each
other to release on a grade or grades up to the level of
any formal training they've had, they can move onto
auditing at the next higher level, either:
A. on a nonprofessional co-audit by taking it on a read-it,
drill-it, do-it basis, or
B. on a professional co-audit by getting fully trained on
that level before resuming their co-audit.
UNTRAINED CO-AUDITORS: The TRs and Objectives Co-audit Course
provides an excellent starting point for new, beginning
co-auditors.
Should you have an untrained staff member who has already
had Objectives as a pc he could still get trained to audit
Objectives on a read-it, drill-it, do-it basis, and deliver
them to his twin.
Meanwhile, the twin can get checked out on any actions his
co-auditor might need (Post Purpose Clearing, Word
Clearing, etc.) and deliver any such actions, in order to
keep his exchange in.
Untrained staff co-auditors will need some basic
definitions to begin with- auditor, preclear, session, etc.
Then teach them the comm cycle and get them through
Co-audit TRs. Do not make it a long runway. You want them
in there co-auditing and they can be polished up as they go.
Muzzled auditing is the keynote for the beginning
co-auditor. It is simple enough for a co-auditor to do and
it lends itself perfectly to the early Grade Chart
processes as well.
If the untrained co-auditor remains muzzled there's very
little trouble he can get into. But he will hit some
trouble spots somewhere along the line and he'll need to be
bailed out by the Co-audit Supervisor, set straight and
given a boost to keep going.
The attitude is always that he can do it.
Untrained staff co-audit teams who are kept at it can get
each other through TRs and Objectives, a Scientology Drug
Rundown, ARC Straightwire, Grades 0-IV processes and NED,
training and auditing on a read-it, drill-it, do-it basis
as they go.
They won't be fully classed auditors but the experience
will be invaluable, the gains can be tremendous and it
shouldn't take much to get them classified after that.
RESPONSIBILITY OF CO-AUDITORS:
The entirety of the Twinning HCOB (HCOB 21 Aug. 79) applies
to co-audit teams. That and the Auditor's Code make up the
co-auditor's bible. Co-auditors are responsible for getting
each other through.
They do twin checkouts, find and handle each other's
misunderstoods, drill their materials until they're
confident, and deliver the tech to each other. For the
untrained, it's a read-it, drill-it, do-it operation and it
makes auditors. A co-auditor is responsible for the quality
of the auditing he gives and receives. You'll find most
staff eager to meet the challenge.
HOW A STAFF CO-AUDIT IS RUN
All the tech on how to run a co-audit in HCOB 29 May 80RA,
Co-audit Series 2RA, and other co-audit HCOBs applies to a
staff co-audit.
Any Staff Co-audit Supervisor must know this tech well and
keep it fully applied.
Put a good auditor onto handling the staff co-audit because
he'll need to be able to handle all levels of cases, bail
any of them out at any time and run good 8-C on the entire
room.
He's got to be able to jump in and handle ruds if needed,
spot bad indicators, find and indicate bypassed charge,
assess lists, give D of P interviews, correct co-auditors
and keep all the sessions moving. He's alert and on the
move, with an eye on every session in progress.
For a co-audit of any size (and most staff co-audits will
be large) he'll need an assistant. The assistant can be
assigned to the post or arranged for on a volunteer basis,
but the Co-audit Supervisor should be given backup he can
rely on.
Running a large co-audit in a common room can be a noisy
business, and there will be distraction for pc and auditor
alike. But it can be done, preclears become used to it,
auditing does get delivered, and it makes a far better
auditor when one learns his trade under co-audit circumstances.
Don't expect it all to go smoothly, because it won't.
There's plenty of randomity on any co-audit but there's apt
to be more of it on a staff co-audit because of the
different case and training levels involved. The Co-audit
Supervisor holds it all together and keeps the co-auditors
auditing.
Staff co-audits are tightly scheduled and tightly
controlled. There's a roll book kept, with a roll call for
each scheduled period, graphs are kept and all points of
WHAT IS A COURSE? PL must be well in.
Correction is done by pink sheets which are handled in the
co-audit room.
Should that not always be workable, the person could be
sent to the Cramming Officer. But he must be handled
swiftly so co-auditing is not held up.
If a staff member simply is not making gains on the
co-audit, even with
debugging from the Co-audit Supervisor, he would be turned
over to a Staff Staff Auditor, an intern or a Review
Auditor for auditing and returned to the co-audit when he
can make it.
Red tags on a staff co-audit, as in any other auditing,
must be handled within 24 hours.
The Co-audit Supervisor rolls up his sleeves and makes sure
it all gets done.
And his job is made easier as it goes along by an
enthusiastic and winning staff.
___________
Let's pump some new life into org staffs everywhere with
staff co-audits that get people up the Grade Chart. You
have all the tech you need to do it. Everybody wins, and
the boost in staff morale, in staff spirit and staff
effectiveness will be quite astounding.
It's the way to make fully qualified staff members. And
you'll be making auditors at the same time!
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================
021. NOTE 1 JUN 80 RESEARCH & DISCOVERY SERIES
[Note on R&D series from the New Tech Vol.]
RESEARCH & DISCOVERY SERIES
VOLUMES
by L. Ron Hubbard
Volume 1 published June 1980
In the late 70s an ambitious and exciting project was
begun: the transcription and publication of all of Ron's
recorded technical lectures and demonstrations. In June of
1980 the project's first product was announced with the
release of Research and Discovery Series Volume 1.
Only the first of what will be approximately 100 such
volumes to be produced, this handsome and substantial
volume contains complete transcriptions of Ron's earliest
lectures on Dianetics technology and demonstrations of its
use, given in the days following the first publication of
Dianetics: The Modern Science of Mental Health.
The lectures themselves are supplemented with notes on
where Ron was and what he was doing at the time, to further
illuminate the track of research and development.
Of incalculable value and importance, this series of books
contains the only running record of Ron's years of research
into the mind and life-a complete chronology of his search
for truth and the development and refinement of the only
technology in this universe capable of freeing man.
==================
022. HCOB 19 JUN 80 THE AUDITOR'S CODE
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 19 JUNE 1980
(Also HCO PL 14 Oct. 68RA, Rev. 19.6.80.)
(Cancels HCO PL of 14 Oct. 68R)
Remimeo
Class VIIIs
All Auditors
THE AUDITOR'S CODE
The pledge of practitioners of pastoral counseling.
Required to be signed by the holders of or before the
issuance of certificates for the certificates to be valid.
____________
I hereby promise as an auditor to follow the Auditor's Code.
1. I promise not to evaluate for the preclear or tell him
what he should think about his case in session.
2. I promise not to invalidate the preclear's case or gains
in or out of session.
3. I promise to administer only standard tech to a preclear
in the standard way.
4. I promise to keep all auditing appointments once made.
5. I promise not to process a preclear who has not had
sufficient rest and who is physically tired.
6. I promise not to process a preclear who is improperly
fed or hungry.
7. I promise not to permit a frequent change of auditors.
8. I promise not to sympathize with a preclear but to-be effective.
9. I promise not to let the preclear end session on his own
determinism but to finish off those cycles I have begun.
10. I promise never to walk off from a preclear in session.
11. I promise never to get angry with a preclear in session.
12. I promise to run every major case action to a floating needle.
13. I promise never to run any one action beyond its
floating needle.
14. I promise to grant beingness to the preclear in session.
15. I promise not to mix the processes of Scientology with
other practices except when the preclear is physically ill
and only medical means will serve.
16. I promise to maintain communication with the preclear
and not to cut his comm or permit him to overrun in session.
17. I promise not to enter comments, expressions or
enturbulence into a session that distract a preclear from
his case.
18. I promise to continue to give the preclear the process
or auditing command when needed in the session.
19. I promise not to let a preclear run a wrongly
understood command.
20. I promise not to explain, justify or make excuses in
session for any auditor mistakes whether real or imagined.
21. I promise to estimate the current case state of a
preclear only by standard case supervision data and not to
diverge because of some imagined difference in the case.
22. I promise never to use the secrets of a preclear
divulged in session for punishment or personal gain.
23. I promise to never falsify worksheets of sessions.
24. I promise to see that any fee received for processing
is refunded following the policies of the Claims
Verification Board, if the preclear is dissatisfied and
demands it within three months after the processing, the
only condition being that he may not again be processed or
trained.
25. I promise not to advocate Dianetics or Scientology only
to cure illness or only to treat the insane, knowing well
they were intended for spiritual gain.
26. I promise to cooperate fully with the authorized
organizations of Dianetics and Scientology in safeguarding
the ethical use and practice of those subjects.
27. I promise to refuse to permit any being to be
physically injured, violently damaged, operated on or
killed in the name of "mental treatment."
28. I promise not to permit sexual liberties or violations
of patients.
29. I promise to refuse to admit to the ranks of
practitioners any being who is nsane.
___________________________
Auditor
___________________________
Date
_________________________ ___________________________
Witness Place
L. RON HUBBARD
Founder
==================
023. HCOB 20 JUN 80 L1C WORD LIST
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 20 JUNE 1980
Remimeo
C/Ses
Auditors
Tech/Qual
L1C WORD LIST
Refs:
HCO PL 4 Apr. 72R III ETHICS AND STUDY TECH Rev. 21.6.75
HCOB 8 July 74R I Word Clearing Series 53R Rev. 24.7.74 CLEAR TO F/N
HCOB 21 June 72 I Word Clearing Series 38 METHOD 5
HCOB 9 Aug. 78 II CLEARING COMMANDS
HCOB 17 July 79 I Word Clearing Series 64 THE MISUNDERSTOOD WORD DEFINED
These are the words from HCOB 19 Mar. 71, LIST-1C-L1C.
These words should be cleared on the pc before the LlC is
actually assessed, per HCOB 9 Aug. 78 II, CLEARING COMMANDS.
The auditor must have received high-crime checkouts from
Qual on the above references before clearing these words on
a pc. The auditor uses Method 5 Word Clearing when clearing
these words on the pc.
This word list need only be cleared once in the pc's
auditing if it was correctly cleared the first time.
The fact of having cleared this word list on the pc must be
noted in the appropriate place in the pc's folder. (Ref:
Auditor Admin Series 6R, THE YELLOW SHEET)
WORDS FROM THE L1C
A, acknowledged, action, actions, affinity, an, attention,
auditing.
Been, before.
Command, communication, confusing, continued, cut.
Data, decision, did, disappointed, done.
Earlier, emotion, engram, error, evaluated, exterior.
For.
Given, go, goal, grasped.
Has, have, haven't, help.
Ignored, in, incident, interrupted, invalidated.
Known.
Listing, long.
Made, meaning, missed, misunderstanding, misunderstood.
No, not.
Occurred, of, other, overrun.
Perception, prevented, problem.
Reality, reason, refusal, refused, rejected, rejection,
restimulated.
Said, shift, short, similar, situation, some, someone,
something, startled, sudden.
Than, the, there, too.
Understood, unnecessary, upset.
Was, what, withhold, willingness, word, wrong.
You.
L. RON HUBBARD
Founder
Assisted by
Mission Issues Revision
==================
024. HCOB 22 JUN 80 INT RD CORRECTION LIST WORDS
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 22 JUNE 1980
Remimeo
C/Ses
Auditors
Tech/Qual
INT RD CORRECTION LIST WORDS
Refs:
HCO PL 4 Apr. 72R III ETHICS AND STUDY TECH Rev. 21.6.75
HCOB 8 July 74R I Word Clearing Series 53R Rev. 24.7.74 CLEAR TO F/N
HCOB 21 June 72 I Word Clearing Series 38 METHOD 5
HCOB 9 Aug. 78 II CLEARING COMMANDS
HCOB 17 July 79 I Word Clearing Series 64 THE MISUNDERSTOOD WORD DEFINED
These are the words from HCOB 29 Oct. 71RA, Int RD Series 12, INT
RUNDOWN CORRECTION LIST REVISED.
The auditor must have received high-crime checkouts from
Qual on the above references before clearing these words on
a pc. The auditor uses Method 5 Word Clearing when clearing
these words on the pc.
These words need only be cleared once in the pc's auditing
if they were correctly cleared the first time.
The fact of having cleared these words on the pc must be noted
in the appropriate place in the pc's folder. (Ref: Auditor Admin
Series 6R, THE YELLOW SHEET)
WORDS FROM INT RD CORRECTION LIST
A, about, action, afraid, after, against, already, an, and,
another, anything, anywhere, ARC break, are, assessed,
assessment, audited, auditor.
Back, badly, be, because, been, begin, being, being in,
being stuck in, body, button, bypassed, bypassed charge.
Can't, cause, caused, chain, charge, clear, cleared,
concept, concerned, concerning, confused, continues,
correction.
Damage, Dianetic, Dianetics, did, didn't, different, do,
done, during.
Earlier, else, End of Endless Int Repair RD, engram,
engrams, errors, exterior.
Failed, feel, find, first, flat, flow, for.
Get, go, going, going in.
Had, handling, has, have.
If, in, incident, instead, Int, Int RD, interiorization,
into, is, it, item.
Jails, just.
Leaving, left, letting, list, long.
Misrun, misunderstood, move.
Neglected, no, not.
Of, okay, on, one, or, other, others, out, out-list, over,
overdone, overrepaired, overrun, overt.
Part, past, perfectly, place, post, practice, problem, push.
Read, recall, religion, repair, reviewed, run, rundown, running.
Scientology, secondary, several, should, some, something,
stuck, subject.
Than, that, the, there, things, thinking, this, time,
times, to, trying.
Understand, unflat, unnecessary.
Wanted, was, we, were, what, when, who, will, win, with,
withhold, word, wording, worried, would, wrong.
You, your, yourself.
L. RON HUBBARD
Founder
Assisted by
Mission Issues Revision
==================
025. HCOB 23 JUN 80RA r. 25 Oct 83 CHECKING QUESTIONS ON GRADES PROCESSES
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 JUNE 1980RA
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 AND ITEMS Rev. 3.12.78
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 cancelled
on 25 Feb. 82 and it remains cancelled. 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
==================
026. HCOB 23 JUN 80RA r. 26 Jul 86 WORD CLEARING CORRECTION LIST WORDS
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 JUNE 1980RA
Issue II
REVISED 26 JULY 1986
Remimeo
C/Ses
Auditors
Word Clearers
Tech/Qual
WORD CLEARING CORRECTION LIST WORDS
Refs:
HCO PL 4 Apr. 72R III ETHICS AND STUDY TECH Rev. 21.6.75
HCOB 8 July 74R I Word Clearing Series 53R Rev. 24.7.74 CLEAR TO F/N
HCOB 21 June 72 I Word Clearing Series 38 METHOD 5
HCOB 9 Aug. 78 II CLEARING COMMANDS
HCOB 17 July 79 I Word Clearing Series 64 THE MISUNDERSTOOD WORD DEFINED
These are the words from HCOB 27 Nov. 78RA, Rev. 17.10.85,
Word Clearing Series 35RH, WORD CLEARING CORRECTION LIST.
These words should be cleared on the pc before the list is
actually assessed on him, per HCOB 9 Aug. 78 II, CLEARING
COMMANDS.
The staff auditor or intern must have received high-crime
checkouts from Qual on the above references before clearing
these words on an org pc. (Ref: HCO PL 8 Mar. 66, KSW
Series 13, HIGH CRIME)
The auditor uses Method 5 Word Clearing when clearing these
words on the pc.
These words need only be cleared once in the pc's auditing
if they were correctly cleared the first time.
The fact of having cleared these words on the pc must be
noted in the appropriate place in the pc's folder. (Ref:
Auditor Admin Series 6RA, THE YELLOW SHEET)
WORDS FROM THE WORD CLEARING CORRECTION LIST
A, about, action, actual, already, an, any, apply.
Basic, been, being, but, by, bypassed, bypassed charge.
Cans, case, charge, clear, cleared, clearing, confused,
couldn't, courses.
Defined, definition, definitions, demo, dictionary, did,
didn't, difficult, distracted, do, done, during.
Earlier, else, enough, evaluation.
Fail, family, feel, find, first, F/N (noun and verb), F/Ns,
forgetting, fully.
Get, going, good.
Hands, has, have, hear, him, hopeless.
Improper, in, indicated, invalidated, invalidation, is, it.
Just.
Keep, kept, knew, knowingness.
List, look, look up.
Make, missed, misunderstood, misunderstoods.
Need, not, nothing.
Of, on, or, other, out-ruds, over, overrun, overwhelmed.
Past, place, protest, protesting, puzzled.
Read, reading, really, regard, in regard to, rid.
Said, school, Scientology, sentences, should, similar,
sized, some, something, specialized, still, studied, study,
subject, subjects.
Technical, tell, than, that, the, them, there, these,
tired, to, training, try.
Understand, understood, unreading, use, using.
Was, wasn't, were, what, when, which, why, win, with,
withhold, word, word cleared, Word Clearer, Word Clearing,
words, wrong.
You, your.
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================
027. HCOB 28 JUN 80RA r. 18 Oct 86 STUDENT CORRECTION LIST WORDS
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 28 JUNE 1980RA
REVISED 18 OCTOBER 1986
Remimeo
C/Ses
Auditors
Tech/Qual
STUDENT CORRECTION LIST WORDS
Refs:
HCO PL 4 Apr. 72R III ETHICS AND STUDY TECH Rev. 21.6.75
HCOB 8 July 74R I Word Clearing Series 53R Rev. 24.7.74 CLEAR TO F/N
HCOB 21 June 72 I Word Clearing Series 38 METHOD 5
HCOB 9 Aug. 78 II CLEARING COMMANDS
HCOB 17 July 79 I Word Clearing Series 64 THE MISUNDERSTOOD WORD DEFINED
These are the words from HCOB 27 Mar. 72RD, STUDENT CORRECTION
LIST.
These words should be cleared on the student (as the pc)
before the list is actually assessed on him, per HCOB 9
Aug. 78 II, CLEARING COMMANDS.
The staff auditor or intern must have received high-crime
checkouts from Qual on the above references before clearing
these words on an org pc. (Ref: HCO PL 8 Mar. 66, KSW
Series 13, HIGH CRIME)
The auditor uses Method 5 Word Clearing when clearing these
words on the pc.
This word list need only be cleared once in the student's
(pc's) auditing if it was correctly cleared the first time.
The fact of having cleared this word list on the pc must be
noted in the appropriate place in the student's pc folder.
(Ref: Auditor Admin Series 6RA, THE YELLOW SHEET)
WORDS FROM THE STUDENT CORRECTION LIST
A, abbreviations, able, about, acceptable, admin, afraid,
after, alcohol, all, already, an, and, another, any,
applicable, application, ARC break, ARC broken, are, as,
attest, available.
Bad, basic, be, been, behavior, being, breaking, but, by.
Can't, case, causing, change, checksheet, class, clay
demos, clear, clearing, cold, committed, completion,
complicated, concerning, confused, consideration,
correction, course, courses, cramming.
Data, decided, define, definitions, demo kit, demos,
determinism, Dianetics, dictionaries, dictionary, did,
didn't, diet, difficult, disagreements, disinterested,
distracted, distracting, distraction, do, doesn't, doing,
done, don't, drugs, duress.
Earlier, eat, else, enough, environment, errors, ever,
evil, eyesight.
Failed, falsely, falsify, fellow, find, finish, finishing,
first, follow, for, found, frequent, from, fully, fun.
Getting, given, going, gone, gradient, guide.
Had, hadn't, harm, has, hasn't, hat, have, haven't, hear,
help, him, hit, hot, how.
Ill, in, incomplete, interpreted, interruptions,
invalidated, invalidation, is, it.
Know.
Lack, language, learned, life, lighting, like, list,
listen, listening, looking up, lose.
Made, manual, many, mass, materials, mean, medicine,
memory, method, Method One, Method 3, missing,
misunderstood, misunderstoods, mixing, more.
Native, need, never, no, noisy, not.
Of, on, or, other, others, out-2D, over, overt, overts, own.
Pack, packs, part, participate, past, personal, physically,
poor, practical, practice, prerequisites, printed, problem,
PTS, purpose.
Rather, read, really, reason, refused, remember, restim,
room, rushed.
Said, same, Scientology, section, seeking, self, set,
should, shouldn't, similar, skipped, small, smoke, some,
somebody, someone, something, source, speak, stats, status,
student, student's, students, studied, studies, study,
studying, subject, Supervisor, Supervisors, supposed, system.
Tapes, targets, tech, terms, the, there, think, this,
threat, time, tired, to, told, too, trick, trouble,
troubled, twin, typographical.
Under, understanding, unreal, up, upset, use, using.
Ventilation, verbal.
Want, was, were, weren't, what, when, why, win, with,
withheld, withhold, withholds, without, won't, word, words,
work, would, wrong.
You, your, yourself, you've.
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================
028. HCOB 30 JUN 80RA r. 26 May 88 STUDENT REHABILITATION LIST WORDS
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 30 JUNE 1980RA
REVISED 26 MAY 1988
Remimeo
C/Ses
Auditors
Tech/Qual
STUDENT REHABILITATION LIST WORDS
Refs:
HCO PL 4 Apr. 72R III ETHICS AND STUDY TECH Rev. 21.6.75
HCOB 8 July 74R I Word Clearing Series 53R Rev. 24.7.74 CLEAR TO F/N
HCOB 21 June 72 I Word Clearing Series 38 METHOD 5
HCOB 9 Aug. 78 II CLEARING COMMANDS
HCOB 17 July 79 I Word Clearing Series 64 THE MISUNDERSTOOD WORD DEFINED
These are the words from HCOB 15 Nov. 74R, STUDENT REHABILITATION
LIST.
These words should be cleared on the student (as the pc)
before the list is actually assessed on him, per HCOB 9
Aug. 78 II, CLEARING COMMANDS.
The staff auditor or intern must have received high-crime
checkouts from Qual on the above references before clearing
these words on the student (pc). (Ref: HCO PL 8 Mar. 66,
KSW Series 13, HIGH CRIME)
The auditor uses Method 5 Word Clearing when clearing these
words on the student (pc).
These words need only be cleared once in the student's
(pc's) auditing if they were correctly cleared the first time.
The fact of having cleared these words on the pc must be
noted in the appropriate place in the student's pc folder.
(Ref: HCOB 30 Oct. 87, Auditor Admin Series 6RA, THE YELLOW SHEET)
WORDS FROM THE STUDENT REHABILITATION LIST
A, about, added, advice, after, alcohol, already, an, and,
apply, ARC, ARC breaks, at, attestation, audit, auditing,
available.
Bad, best, booted, by.
Came, certificates, checksheet, clear, clearing, coaching,
confused, couldn't, course, courses.
Dictionary, didn't, disagreements, dispute, do, downgraded,
drugs, duress.
Each, earlier, eat, else, enough, error, ethics,
evaluation, eyesight, exam, examination.
Failed, false, family, fees, find, flunked, for, forced,
from, fully.
Gave, get, getting, given, God, going.
Had, hadn't, have, having, HCOBs, help.
In, interference, interpreted, interruptions, invalidation.
Kept, knew, known.
Lied, list, live, lots.
Mad, made, master, materials, meter, method, Method One,
missed withhold, missing, misunderstood, misunderstoods, money.
Never, no, nobody, not.
Of, off, often, on, or, other, out, out-ethics, out-Int,
out-2D, over.
Passed, past, pay, people, personal, physical, place,
players, practical, prevented, problem, problems, PTS.
Quotas.
Reason, reasons, Registrars, restim, resulting, rules.
Scientology, service, set, similar, simply, sleep, some,
someone, something, stated, stopped, student, studied,
study, studying, subject, Supervisor.
Taking, tape, tape players, tapes, tech, terms, than, that,
the, there, things, this, to, told, too, trouble, TRs,
twin, 2D.
Under, understand, understood, unreal, use.
Verbal, violated.
Was, were, weren't, when, why, with, withhold, word, word
clearing, words, wrong.
You, your.
L. RON HUBBARD
Founder
Revision assisted by
LRH Technical Research
and Compilations
==================