FREEZONE BIBLE ASSOCIATION TECH POST

CLASS IV - HUBBARD ADVANCED AUDITOR (HAA)
CASE SUPERVISOR COURSE - PART 6/14

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

This is the Class IV Case Supervisor Course (HAA)
Course Pack as issued and delivered in the 1975 -
1976 time frame.

The contents will be posted separately as part 0 and
repeated in part 1 but will not be included in the
remaining parts to keep the size down.

NOTE: With the following exceptions, all documents
are reproduced exactly as issued.

All italicized or bold characters and underlines
have been omitted from this reproduction. Only 
minor spelling errors have been corrected.

If you have questions about the content of an
individual issue please refer to the Tech or
OEC Volumes (which were posted previously) for 
clarification. 

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

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 - Unit 21

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


=====================

028. HCOB 25 June 1970 C/S Series 11 


HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

Remimeo HCO BULLETIN OF 25 JUNE 1970 

C/S SERIES No. 11


The following HCOBs have been combined in this issue: 

HCOB 31 Aug '68 "It is a high Crime.........."
HCOB 1 Sept '68 "Points on Case Supervision"
HCOB 11 Sept '68 "Case Supervisor Data"
HCOB 17 Sept '68 "Gross Case Supervision Errors"
HCOB 17 Sept '68 "Out Admin - Liability"
HCOB 22 Sept '68 "Auditors Must Always........."
HCOB 8 Oct '68 "Case Supervisor - Folder Handling"
HCOB 15 Mar '70 "Double Folder Danger"
HCOC 29 Mar '70 Auditing and Ethics"
and reference to LRH ED 101 Int "Popular Names of Developments".


C/S DATA 

Case Supervisor Instructions are always written. A Case 
Supervisor always writes his C/S instructions on a separate sheet of 
paper for the pc folder. 

Repair Programs (now called Progress Programs) are on red sheets. 

Return Programs (now called Advance Programs) are on bright blue 
sheets. 

All C/Ses are written in duplicate (a carbon copy is made). 
The C/S keeps the carbon copy for reference in case the original ever 
gets lost. 


HIGH CRIME

It is a High Crime for a Case Supervisor not to WRITE in a 
preclear's folder what the case supervised instructions are and a 
High Crime for an auditor to accept verbal C/S instructions.

To commit this-crime causes:

1) Extreme difficulty when doing a folder error summary as there 
is no background of what was ordered and why. 

2) Gives the auditor, leave to do anything he likes as not in 
writing.

3) Is open to misduplication and can cause squirrel processes to 
be run and so mess up a preclear with Non-standard Tech. 

Any C/Supervisor found guilty of this from this date is to be 
removed as this could only be considered a deliberate attempt to mess 
up preclears.


HCOB 25.6.70 -2- 


POINTS ON CASE SUPERVISION 

1) Check your orders to find out if auditor did them. 

2) Check to see if commands correct and if pc's reaction was 
expected reaction for those commands. 

3) Check any list and find out if there was mislisting. 

4) Advise against a background of Standard Tech. 

5) Order any errors corrected or get the case on further up the 
grades. 

6) Beware of over correction. 

7) Beware of false, pessimistic or over-enthusiastic auditor 
reports. They are detected by whether the case responded 
to usual actions as they all do. 

8) Beware of talking to the auditor or the pc. 

9) Have implicit confidence in standard tech. If it is reported 
not working the auditor's report is false or the application 
terrible but not reported. 

10) Above all else hold a standard and NEVER listen to or use 
unusual solutions. 


DOUBLE FOLDER DANGER 

When a pre OT has a Solo and an Auditing folder, both, there is 
a great danger if the Case Supervisor does not look at BOTH before 
C/Sing. 

There has been an instance of a pre OT running strange C/Ses 
on himself. Another ran C/Ses out of other folders on himself. In 
both cases the consequences were hard to repair when finally found. 

In another case in the Solo Folder the pre OT had gone exterior 
with full perception. But the Non-Solo Auditing folder was being 
C/Sed. The TA shot up for 2 months without any C/S except myself 
calling for all folders. 

Pre OTs unfortunately run on a Solo folder and an audited folder. 
Unless both are to hand when C/Sing wild errors can be made by the C/S. 

There is also the case of a person having two audited folders, 
being C/Sed at the sane time. This is an Admin error. 

The firm rule is C/S ONLY WITH ALL FOLDERS TO HAND. 

The embarrassing situation where one can't get a folder from 
another org or field auditor or where the old folder is lost has to be 
made up for somehow. It mustn't halt auditing totally. 


HCOB 25.6.70 -3- 


CASE SUPERVISOR - FOLDER HANDLING 

Analyzing Folders

Go back in the folder to the session where the preclear was 
running well and come forward from it doing a folder error summary. 

Reviewing Folders 

In reviewing a folder, the first thing to do is to look at 
the C/S to see if it was done. 

Use the Summary Sheet to get the Auditor's attitude and pc 
mannerism changes. 

Use the Auditor's Report Form to get the time of processes. 

Read and take all your data from Worksheets and compare it to 
and see that C/S was complied with and ensure Standard Tech was 
applied. 

If you can't read the reports, send it back to have the 
auditor over-print illegible words. Never try to case supervise 
(C/S) an illegible worksheet as you'll only run into headaches. 

The After Session Examiner's Report gives you the first clue 
of how suspicious you should be in examining the folder and whether 
or not auditing reports contain falsities 

Standard Tech 

You're never led by anything from departing from Standard 
Tech. The only reason it doesn't work is that it hasn't been 
applied. 

The main question of a Case Supervisor is: 

WAS IT APPLIED? 

If you follow this exactly, you'll never miss. 

CASE SUPERVISOR DATA

A Case Supervisor should watch for Ethics record of pcs who 
have been C/Sed. 

If they fall on their head, get into low conditions, the 
folder should be reviewed. 

Most probably the auditor did not do what was ordered and, if 
folder looks okay, chances are the auditing report is false as 
something is wrong or pc would not be in trouble. 


HCOB 25.6.70 - 4 - 


AUDITING AND ETHICS 

Cases undergoing Ethics actions, Comm Evs, amends projects 
or low conditions should not be audited until the Ethics matter 
is cleared up and complete. It only louses up their cases to 
audit them when under such stress 

ADMIN 

Auditors must always put the pc's grade or OT level very
prominently On the Auditing Report. 

A Case Supervisor cannot properly C/S a case without having 
this data. 

To not do this is out admin.

OUT ADMIN LIABILITY 

Much has been said about the importance of admin in auditing 
but auditors just aren't getting it - so ....... it now becomes a 
LIABILITY to have out admin in pcs folders. 

Folders are to be submitted with the latest session on top. 
Auditor's report form is stapled to Work Sheets which are dated, 
numbered and in order, latest on top. Summary Report is then 
attached to the auditing report and W/Ss with a paperclip. This 
of course is as well as the usual admin such as legible writing, 
re-writing illegible words, marking reads and F/Ns, and all End 
Phenomena etc. 

The C/S instructions for that session go under that session, 
so you get C/S 4/6/68, Auditing Session 4/6/68, C/S 5/6/68, 
Auditing Session 5/6/68, C/S 7/6/68, etc., etc. 

As the whole purpose of Class VIII is to minimize the time
in auditing, by doing perfect Standard Tech, this cannot be done 
if it takes 15 minutes to put the folder in order, so it can then 
be case supervised, so it can then be audited. 

GROSS CASE SUPERVISION ERRORS

1. FAILING TO USE PROGRESS AND ADVANCE PROGRAMS WHEN NEEDED. 

2. Ordering unnecessary repairs. 

3. Trying to use repair processes to get case gain instead of 
getting the pc onto the next grade. 

4. Not writing down C/S instructions, but giving them to an 
auditor verbally. 

5. Talking to the auditor re the case. 

6. Talking to pc re his case. 


HCOB 25.6.70 - 5 - 


7. Failing to send pc to examiner if you're unsure why his 
folder has been sent up for C/S. 

8. Being reasonable. 

9. Not having enough Ethics presence to get his orders 
followed. 

10. Issuing involved repair orders. 

11. BIGGEST GROSS CASE SUPERVISION ERROR for C/S is not to read 
through the pc folder


L. Ron Hubbard
FOUNDER

LRH:sb 
Copyright ($) 1970
by L. Ron Hubbard
ALL RIGHTS RESERVED 

=====================

029. HCOB 25 June 1970 C/S Series 12 Glossary of C/S Terms


HUBBARD COMMUNICATION OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

Remimeo HCO BULLETIN OF 25 JUNE 1970 


C/S Series No. 12 


GLOSSARY OF C/S TERMS 

RECOVERY PROGRAM: The pack of 

LRH EDs 100 Int 10 May '70 Lower Grades Upgraded. 
102 Int 20 May '70 The Ideal Org 
103 Int 21 Nay '70 Fast Flow Grades Cancelled 
104 Int 2 Jun '70 Auditing Sales and Delivery Pgm No. 1 
106 Int 3 Jun '70 What was Wrong 
107 Int 3 Jun '70 Orders to Divisions for Immediate Compliance 
10 SH 6 Jun '70 SH Pcs 
108 Int 11 Jim '70 Auditing Mystery Solved 
101 Int 21 Jun '70 Popular Names of Developments 

comprising the program to recover full use and results of EXPANDED 
LOWER GRADES. 

PROGRESS PROGRAM

What is called a "Repair Program" on the first issue of the 
C/S Series HCOB just being issued is re-named a PROGRESS PROGRAM It 
has been found that case gain which has not been earlier achieved can 
be consolidated by a PROGRESS PROGRAM. It takes 25 hours, can be 
done by a Class I or above as long as it is C/Sed by an VIII who has 
starrated on the new C/S Series. This is quite a technical development 
in itself. It is the answer to a pc Who had "Quickie Grades" and 
didn't actually reach full abilities in earlier Scientology auditing. 
It is followed by an Advance Program which follows below 

ADVANCE PROGRAM: 

This is what was called a "Return Program" in the C/S Series. 
The name is being changed from "Return" to "Advanced" as more appropriate. 
It gets the pc really up to where he should be. It take 50 hours 
or more. 

EXPANDED LOWER GRADES:

Pcs won't like being told they "have to have their lower 
grades rerun". Actually that's not a factual statement anyway. The 
lower grades harmonic into the OT levels. They can be run again with 
full 1950-1960 to 1970 processes as given on the SH Courses all 
through the 1960s. These are now regrouped and sorted out and are 
called EXPANDED LOWER GRADES. Only this route will now be sold. 
There are no Dianetic or Scientology single - triple or "Quickie 
Lower Grades" any more. 


HCOB 25.6.70 -2- 
Issue II


DIANETIC CLEAR: 

There is such a state. It is not however attained by feeding 
people Scientology cognitions as was done in LA. 0nly about 2% go 
actually Clear on Dianetics. A Dianetic Clear or any other Dianetic 
pc now goes on up though the grades of Scientology and onto the 
proper Clearing Course. The Dianetic Clear of Book I was clear of 
soma tics. The Book I definition is correct. This is the End 
Phenomena of Dianetics as per the Class Chart and Book I. 2% no 
more make Dianetic Clear accidentally. They still need expanded 
lower grades to make Scientology Clear. Becoming a Dianetic Clear 
does not stop them from getting Power Processing. Modern Power is to its 
total End Phenomena. 

CLASSIFICATION CHART 

This chart "Classification and Gradation Chart" has been 
reissued many times. All issues are more or less valid. To save 
print, the processes run column appears in "Processes Taught" on the 
Auditor side of the Chart. All these processes and more are used 
in Expanded Lower Grades. The chart is Valid. 

QUICKIE GRADES:

Persons were too demanding to be done quickly. On many cases 
these grades as given were valid but a large number of cases needed 
Expanded Lower Grades. 20 minutes from Grade 0 to IV and 5 minutes 
Power was far more than many could stand up to. These need a PROGRESS 
and an ADVANCE PGM. This is true of persons at Va or R6EW or on 
CC or OT Levels. All those who haven't fully made it need a PROGRESS 
PGM and an ADVANCE PGM "to pick up all the latent gain they missed". 

DIANETIC PCs:

Dianetic pcs should be audited on Dianetics until no somatics, 
then go up through Expanded lower Grades to Power, R6EW, Clearing 
Course and 0T Levels. 

TRAINING: 

Any pc Who has trouble needs training and the amount of time 
required in Expanded Lower Grades and so on makes it cheaper to be 
trained. 

L. RON HUBBARD 
FOUNDER 

LRH:sb 
Copyright ($) 1970
L. RON HUBBARD 
ALL RIGHTS RESERVED 

===================== 

030. HCOB 21 Aug 1970 C/S Series 16 Session Grading 



HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

HCO BULLETIN OF 21 AUGUST 1970 

Remimeo 
C/S Checksheets 
All Level C/S Series No. 16 
Checksheets 
Dn Checksheet SESSION GRADING 
WELL DONE, 
DEFINITION OF


A "well done" to an auditor requires a precise meaning. It is not 
given by the C/S because an auditor is a friend or because he would be 
offended if he didn't get one.

"WELL DONE" GIVEN BY THE C/S FOR A SESSION MEANS THE PC HAD 
F/N VGIs AT THE EXAMINER IMMEDIATELY AFTER THE SESSION. 

This then pre-supposes that session lines include an Examiner even 
if it's a receptionist and it includes the use and understanding of Exam 
Reports. (See HCO PL 26 Jan '70 Issue III or any rewrite and Exam tech.) 

It pre-supposes the Examiner has a meter to hand and that the pc makes 
a statement. 

Thus, if there are no Exam reports there can't be a well done given, 
eh? True enough. A C/S who C/Ses without Exam reports done by a different 
person than the auditor is asking to fly blind and to get auditor "PR" 
(public relations or brag) and false auditing reports. 

No F/N at Exam no well done.

This is harsh as early on pcs often get no F/N at Examiner. BUT IN 
EVERY CASE THERE ARE CURRENT EARLIER TECH ERRORS ON THE CASE when the F/N doesn't get from the session to the examiner. It is also harsh because the 
failure to get the F/N to the examiner could be a C/S error! But (see 
HCOB 24 May '70 Auditor's Rights, C/S Series 1), the auditor should not have 
accepted the C/S. 

The C/S could be too heavy, or the case needed a repair first or the 
program ordered is not part of a proper program. 

HOURS SUCESSFULLY AUDITED INCLUDES ONLY "WELL DONE" OR "VERY 
WELL DONE" SESSIONS. 

VERY WELL DONE 

An auditor gets a "VERY WELL DONE" when the session by worksheet 
inspection, Exam Report inspection is: 

(1) F/N VGIs at Examiner.

(2) The auditing is totally flubless and by the book. 

(3) The whole C/S ordered was done without departure and to the expected result. 

NO MENTION 

A no mention or well done or very well done or anything simply means: 

(1) F/N did not get to Examiner. 


HCOB 21.8.1970 - 2 - 


(2) No major auditing errors exist in the session. 

FLUNK 

A FLUNK is given when: 

(1) The F/N did not get to examiner and didn't 
occur at session end. 

(2) Major errors or flubs occurred like no EP, 
multiple somatic, unflown ruds, etc. 

(3) The C/S was not followed or completed. 

(4) Auditor's Rights listed errors occurred. 

(5) No F/N and BIs at Examiner. 

The exact error must be noted on the worksheet and in the next C/S 
along with the Flunk. 

FLUNK AND RETRAIN

When an auditor does not improve but continues to get NO MENTIONS and 
FLUNKS, he requires retraining. 

Such retraining must include: 

(1) cleaning up all Misunderstoods of tech. 

(2) Cleaning up willingness to audit 

(3) Cleaning up overts on people and pcs. 

(4) Examination by inspection of TRS. 

(5) Starrating of materials missed or not grasped
as per session troubles. 

INVALIDATION

Invalidative remarks should not be made by a C/S. Experience has 
shown they do no good and also do harm. 

But there are 2 methods of invalidating all auditor's auditing: 

(1) Let him go on flubbing and getting no results. 

(2) Direct invalidation of his intentions or 
future or potential. 

In 1, nearly all auditors who stop auditing never really knew how to 
audit in the first place or have gross misunderstoods or have accumulated 
intentional or unintentional overts on pcs or who have been too harshly 
invalidated. When they don't really grasp the ease and simplicity of 
auditing they get into other troubles. 

A really well trained, smooth auditor never gets any real charge on 
his case on the subject of auditing. 

When you let an auditor flub, the whole object gets invalidated and be 
loses his value because he goes into doubt, This can be said with complete 
confidence today as the whole of Dianetics and Scientology is there and it 
works very very well indeed IF IT IS USED AND IF THE C/SING AND AUDITING IS 
CORRECT AND FLUBLESS. 


HCOB 21.8.1970 - 3 - 


AUDITOR HANDLING 

The C/S is really not just the Case Supervisor, he is also the 
auditor's handler. 

Like a boxer's trainer or a star's director, the C/S handles his guys. 
They are all a bit different, auditors. There are prima donnas and meek 
mousey ones and steady-on ones and all kinds. 

They get the credit for the sessions from the pcs most often. They 
really don't like not to be C/Sed. 

And they VALUE the well dones and the very well dones and they flinch 
at the flunks. And the honest ones know all about it before they turn it in. 
And some don't mention the flub but think you're a fool if you miss it. 

So it's important to have a constant in assigning what the auditor is 
given for the session. 

WELL DONE AUDITING HOURS are all that's valid for a stat. 

So a C/S must be very exact and correct in his determination of well 
very well done, no mention and (forlornly) a flunk. 

This should remove argument from the matter and bring certainty. 


L. RON HUBBARD 
FOUNDER 


LRH:rr 
Copyright ($) 1970
by L. Ron 
ALL RIGHTS RESERVED 

=====================

031. HCOB 26 Aug 1970 C/S Series 17 Incomplete Cases


HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

HCO BULLETIN OF 26 AUGUST 1970 

Remimeo 
C/S Book C/S Series No. 17 
Class VIII Checksheet 
Class VIII 


INCOMPLETE CASES 

OVERSHOOTING and UNDERSHOOTING are two very defeating errors in C/Sing. 

OVERSHOOTING would be defined as going beyond a completion or 
completing a completion. 

In such a circumstance the pc for instance reaches an F/N VGI point
in Review and then the C/S decides to handle the case in Review. 

Example: 2 or 3 sessions have been goofed. Review patches them all 
up to F/N VGIs all okay. Then a C/S C/Ses to Review the case to repair the 
errors. The case feels invalidated, caves in, needs further repair. 

I have seen more than one folder where this cycle has been done three 
times! In one of these an action had to be taken to patch up a goof so the 
pc could go back onto a grade. The goof was patched up to F/N VGIs. The 
correct action would have been to put the pc back on the incomplete grade. 
But no, a new Review cycle was laid out, audited, pc caved in. A new cycle 
to repair this was entered in upon. It was successful. The pc got F/N 
VGIs at Exam. The C/S ordered a new Review of the case, the case caved in, 
was then patched up and finally got an F/N VGIs. And was ordered to be 
reviewed ........... 

Studying what was wrong with the cases I found the above. I ordered 
an assessment of a list, got "unnecessary actions" and got the cases back 
onto the incompleted cycle of the grade and they did fine. 

This can be done with a grade. It was the fault of early Power. 

UNDERSHOOTING would be to leave a cycle incomplete and go off to 
something else. 

Example: Case sent to Review or given a Review session to repair goofs. 
One goof was handled but there were three to handle. Case returned to the 
grade before being set up. 

This can be so bad that the case never made any grade at all. 

The modern Repair (Progress) Pgm as outlined in this C/S series takes 
care of this. 

QUICKIE GRADES AND ACTIONS

Quickie grades left us with a totality of incomplete cases. 

You look over a folder and you see the pc at "OT IV". The folder is 
thick. He has had lots of auditing. He has aches and pains, problems, 
makes people wrong. 

Probably he could be audited for another thousand hours without 
coming right! Unless there was an orderly program to complete his case level 
by level on the Class and Grade Chart. 

It would take a Repair (Progress) Pgm and then an Advance Pgm that 
included each grade to completion.


HCOB 26.8.1970 - 2 - 


He would have to have his ruds put in, any flubs at once handled session 
to session, just to complete Dianetics. Finally, his chronic somatics gone, 
F/N on the Health form and that would complete his Dianetic s with 
his attestation. 

And so on right on up the Grades, each one done fully to the voluntary 
declare for that grade as per the Grade and Class Chart. 

In doing Dianetics, Grades etc. you still have to get in ruds and 
handle the case so it is set up for each major action and repair the flubs at 
once they occur. 

While completing an action you have to keep the case running, not audit 
over ARC Brks, PTPs, W/Hs and flubs. 

The best answer is NO FLUBS. But when they occur they must be repaired 
in 24 hours. 

When repaired (and not re-repaired and re-re-repaired with overshoots) 
you get the case back on the same cycle that was incomplete. 

COMPLETE CASES

A case is not complete unless the lowest incomplete Grade Chart action 
is complete and then each completed in turn on up. 

As you look over current folders who have had years of auditing, some 
of them you generally don't find completed actions and do find 
overshoots on Reviews. 

It is not the least bit hard to handle these cases. This C/S series 
shows you how. Auditing and Life Repairs (Progress), Advance Pgm completing 
fully each incomplete grade. 

The C/S is blessed who follows these two rules: 

RECOGNIZE A COMPLETION OF AN ACTION AND END IT OFF.

RECOGNIZE AN INCOMPLETE ACTION AND COMPLETE IT.

Don't overshoot, don't undershoot. 

Follow the rules. 


L. RON HUBBARD 
FOUNDER 


LRH:rr 
Copyright ($) 1970 
by L. Ron Hubbard 
ALL RIGHTS RESERVED 

=====================

032. HCOB 6 Oct 1970 C/S Series 19 Folder Error Summaries



HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

HCO BULLETIN OF 6 OCTOBER, 1970 

Remimeo 
C/S Hats C/S Series No. 19 
C/S Checksheet 
Class VIIIs 

FOLDER ERROR SUMMARIES


A folder error summary, (FES) is usually done by a student 
especially an interne well taught, learning his practical tech or by an 
auditor especially hired to do FESs.

It requires many hours to put a folder in sequence and then to 
list all errors in it. 

It should never be done by a working C/S who is responsible for 
an org's delivery flow. 

COST 

It is costly to do an FES and where possible the cost, duly 
consulting the pc should be borne by the pc as a special service. 

It can be directly paid for or simply deducted from auditing hours 
purchased. 

NECESSITY 

A good C/S looking over a folder usually goes back to the last time 
the pc was doing really well and notes actions necessary from that point. 

Programs of a lengthily audited case (fat folder) usually cover 
L1B, L3A, L4A lists and usually take up 2 way comm on earliest sessions 
and earliest auditing ever given (for auditors). Thus an FES is not 
vital in all cases. 

I like to have an FES done so I can compare areas covered by the 
pc in 2 way comm and be sure they come up in subsequent repair sessions. 

Also where I can see a lot of bad lists existed, I want to be able 
to assure they get handled.

Thus an FES is useful. 

On Flag an FES is carefully done so as to detect areas of out tech 
in the world. This is called "the Flub Catch System". 

Auditors and C/Ses so detected are sent to cramming in their areas 
to smooth out their knowledge of TRs, all to improve delivery of 
tech. 

Flub Catch makes an FES vital on Flag. 

Higher orgs have a similar interest in an FES.


HCOB 6.10.70 - 2 - 


HALTING DELIVERY 

To halt delivery because of a missing folder or to do a long time 
consuming FES is of course contrary to the need to deliver auditing and can 
result in a no-auditing situation worse than a blind repair. 

BLIND REPAIR 

When no FES is done, one is doing a Blind Repair. The Progress Pgm and 
Advance Pgm may have holes in them. 

However there are only five areas of danger: 

1: Flubbed lists. 

2. A bad series of evaluative sessions should be detected and directly 
handled. 

3. Flubbed Power. 

4. Extended of flubbed Interiorization. 

5. Missed grades. 

If a C/S doesn't know about these it may be that the case will not 
properly repair and ha also does not know what Advance Program to do. 

But as theses are specific areas they can be done on a Blind Repair by
making them into a list and getting them meter checked. 

Example: Pc has lost his folder. Has been audited for several years 
on and off. One can clear the idea of lists "Someone written down items you
say to a question" and see if it gets a read and if so do L4A Method Three 
"On Lists". One can ask if any auditor ever told the pc what to think and 
if that reads 2 way comm or prepcheck those sessions by that auditor. Power 
can be checked by rehab unless the person has gone Clear on the Clearing Course 
since at which time Power will not need repair. The commands of Interiorization
Rundown can be checked with 2 way comm or rehabbed. What wont rehab you run. 
Missed Grades can be checked, rehabbed or run including any expanded grades. 
The pc usually recognizes the process if it has been run. 

Thus one can wander through a Blind Repair without fouling up the case 
and add to it the inevitable actions common to all Progress Pgms. 

SUMMARY 

An FES has value. It is valuable to the pc to get done. It is a 
long and extensive action. It can be sold directly or removed from hours 
bought. It is of vast interest in training auditors and should be done by 
already trained internes or specially hired auditors. It is NOT done by a 
C/S and it is NOT used to halt all delivery of auditing and jam up the C/S lines. A lost or delayed folder is not a barrier to a very well trained C/S 
who has starrated a C/S course. An FES is very useful and tends to eradicate 
any mystery for a C/S. 


L. RON HUBBARD 
FOUNDER 


LRH:sb 
Copyright ($) 1970 
by L. Ron Hubbard 
ALL RIGHTS RESERVED 

=====================

033. HCOB 6 March 1971 Issue II C/S Series 27 Long C/Ses 



HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 

HCO BULLETIN OF 6 MARCH 1971 
Remimeo Issue II 


C/S Series 27 

LONG C/Ses

A long C/S is far more desirable than a short C/S in all 
but the most sickly and feeble cases. 

In doing a long C/S, the auditor can also end it off where
an F/N goes 3/4 to a dial wide and looks like it will persist. 
The pc has a win. 

A long C/S also permits an auditor to adjust his own 
length of session. 

If the C/S isn't complete on that day, one simply adds 
(1) "Fly a rud" and (2) "Continue C/S of (yesterday)." 

By having a whole progress program (repair) laid out on 
a red sheet and clipped with its green Advance Pgm (grade 
chart) inside the front cover, over the session summary, the 
guidance for the case is right there. This gets checked off 
as done. 

The C/S could consist of half the program or even (in 
shorter programs) all of it. 

Handling 

One speeds a line by taking repeated handlings out of it. 

Less sessions mean less handling. 

Thus the session is more economical if long. 

Getting the pc and folder rounded up 5 times when it 
means the same number of house to do it 2 times saves wear 
and tear. 

This is the benefit of very long C/Ses. 

DIANETIC C/Ses

Dianetic sessions often go 5 or even 8 hours. 

One tries to do all the flows of an item in one session 


HCOB 6 Mar 71 
Issue II - 2 - 


Length of Pgms 

When auditing the public, not staff, you long program. 

In a progress (repair) program you try to throw the 
whole bag of tricks at them. 

These are not only repairs, when you do a Progress 
Program. You throw in a lot of other bits like 2 way comms 
on BD items. 

You now have a Hi-Lo TA List to assess and an Expanded 
Green Form. 

Advance Programs 

All Advance (gradesheet) Programs start lower than the 
pc was if the pc got in trouble where he was. 

Often a grade is obviously out below where he is 
graded. 

Let us say he is a bogged "Grade IV." Well, he 
couldn't be a Grade IV. So the Advance Program (green 
paper) that you do picks him up at Grade 0 or even Dianetics. 

A bogged "OT I" the other day began to win when 

(a) given a long long Progress Program, and 

(b) shoved back to Grade III on the Advance Program 
and brought on up all the way including OT I before 
going on to OT II 

Thorough C/Ses 

Thus you can have long C/Ses only when You have long 
programs already done and pinned to the inside of the front 
cover, a pink one for Progress (non grade) and a green one 
for Advance (back up the grades). 

Don't try to save auditing time. Save instead 
repeated handlings. 

This does not go into "over-repair." A Progress Pgm 
contains all sorts of bits like 2 wc on "What do you feel 
you owe your family" (as the pc is always getting off about 
his family in Ruds). 

The advance of a case is the amount of charge you get 
off it. 


HCOB 6 Mar 71 - 3 - 
Issue II 


Long C/Ses ease your Admin lines greatly. 

They also give less chance of having ruds go out 
between sessions. 

Short sessioning has its uses - small children, sick 
people, psychoes. 

But long sessions save time in the long run and get 
the job done. 


L. RON HUBBARD 
FOUNDER 


LRH:mes 
Copyright ($) 1971 
by L. Ron Hubbard 
ALL RIGHTS RESERVED

=====================

034. HCOB 8 March 1971 C/S Series 29 Case actions, off lines



HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 


Remimeo HCO BULLETIN OF 8 MARCH 1971 


C/S Series 29 

CASE ACTIONS, OFF LINES 

A C/S can be plagued by off line case actions of 
which he is not informed. 

The existence of these can wreck his carefully laid 
out programs and make a case appear incomprehensible. 

Thus it Is up to a C/S to suspect and find these 
where a case isn't responding normally in auditing. 

1. LIFE KNOCKING RUDS OUT FASTER THAN THEY CAN BE AUDITED IN. 

Schedule sessions closer together and give very long 
sessions so life hasn't a chance to interfere. Can go as 
far as requiring person via the D of P to stay in a hotel 
away from the area of enturbulation or not associate until 
case is audited up high enough. 

Shows up most drastically in Interiorization Intensives 
where no ruds can be run unless the RD is complete. Thus 
Int has to be done in one session, with the 2 wc Int-Ext 
the next day. 

2. PC PHYSICALLY ILL BEFORE NEXT SESSION AND AUDITING OF 
A MAJOR ACTION BEING DONE ON A SICK PC WHO SHOULD HAVE 
ANOTHER C/S ENTIRELY. 

Happens when delayed or late new Exam reports don't 
get into folder before C/Sing it. Ginger up Exam routing. 

Happens when auditors are not alert to the pc's illness 
and audit anyway. Make auditors not audit and report at 
once sick pcs. 

Pcs hiding general illness may show up as no case 
gain. Answer is to get a full medical exam. 

3. SELF AUDITING

Detected by no lasting gain. Hi-Lo TA assessment 
will show it up. 

Two way Comm on when they began to self audit (usually 
auditor scarcity or some introverting shock). 


HCOB 8 Mar 71 - 2 - 


4. COFFEE SHOP AUDITING. 

Meterless fool around, often by students, stirring 
up cases. 

Forbid it in an area. 

5. TOUCH AND CONTACT ASSISTS INTERRUPTING A GENERAL 
COURSE OF AUDITING, OFTEN TO NO F/N. 

Make all such assists be done on a worksheet and make 
it mandatory to take the pc to an examiner afterwards. 

W/S and Exam Rpt then appear in folder. 

The C/S can then get in the other actions (Ruds, S & D, 
HCO B 24 July 69) on the injured pc. 

6. STUDY RUNDOWNS. 

An illegal and offbeat line can occur when auditing 
out misunderstoods in study or "Management Word Rundown" or 
such occurs in the middle of a general auditing program. 

Require that C/S okay is required. 

Get such done at the START of courses and BEFORE a 
major auditing cycle is begun. Enforce this hard as the 
other answer that will be taken will be to do it at the end 
of the cycle and wreck major auditing program results. 

7. ILLEGAL PATCH-UPS. 

Sometimes all through an intensive there is another 
auditor unknown to the C/S who 2 wcs the pc or audits the 
pc who is complaining to him or her. 

Shows up in the Hi-Lo TA Assessment. 

Forbid it. 

8. PEOPLE TALKING ABOUT THEIR CASES. 

Past life reality is often badly hurt by people who 
talk about being Napoleon, Caesar and God. This makes 
"past lives" an unreal subject by bad comparison. 

Restimulative material is sometimes used to "push 
someone's buttons." 

Bullbait that uses actual processes or implants should 
be stamped out hard. 


HCOB 8 Mar 71 - 3 - 


9. ADVANCE COURSE MATERIAL INSECURITY. 

I have seen several cases wrecked by careless storage 
of Ad Course materials where lower levels could get at them. 

One notable case was a suppressive who got hold of Ad 
Course materials and chanted them at his wife to drive her 
insane. She recovered eventually. He didn't. 

When a C/S gets a whiff of upper level materials on a 
lower level pc worksheet he should make an ethics matter of 
it and get it traced. 

10. ILLEGAL DRUG USE. 

A pc who suddenly relapses onto drugs or who has a 
long drug history can cause a case to look very very odd. 
The TA flies up. The case, running okay, suddenly ceases 
to run. 

Addicts can come off it if given TRs 0 to 9 and an 
HAS Course (modern). 

Drug chains are rehabbed and run out by Dianetics. 


L. RON HUBBARD 
FOUNDER 


LRH:mes 
Copyright ($) 1971 
by L. Ron Hubbard 
ALL RIGHTS RESERVED 

=====================

035. HCOB 31 March 1971 C/S Series 31 Programming and Misprogramming



HUBBARD COMMUNICATIONS OFFICE 
Saint Hill Manor, East Grinstead, Sussex 


HCO BULLETIN OF 31 MARCH 1971 
Remimeo 
C/S Series 31 


PROGRAMMING AND MISPROGRAMMING 

There are three important areas of technical application: 

1. Auditing Cases. 

2. Case Supervising Cases. 

3. Programming Cases 

Auditing generally should be gotten into an org on the 
routine basis of 

1. Get Auditing Volume UP. 

2. Get Auditing Quality UP. 

3. Get C/Sing Volume UP. 

4. Get C/Sing Quality UP. 

5. Get Programming Volume UP. 

6. Get Programming Quality UP. 

To do it in any other sequence is to organize before 
producing or to inhibit production. 

Auditing quality is raised by getting in Cramming and 
getting Cramming done. 

C/S Quality is raised by C/S study of cases and the Qual 
Sec Craming the C/S. 

Programming quality is raised by getting FESes done so 
that the action does not block production and Cramming or 
Programming and then studying the case to make the Programming 
more real and effective. 

MISPROGRAMMING 

1. Programming a case without data is risky. Dropping out 
the FES step, not getting white forms done, etc, short cutting 
on data in general can cost tremendous amounts of lost auditing. 

2. Doing a vague general hopeful programme of Repair (Progress) 
trusting something will come up is ineffective. With data on 
the person's life even on a pc never before audited, one can 
hit the key points even if only with 2 way comm on them. Cases 
that have been audited and are boggy are so for a reason. 
Programming without finding that reason can be very ineffective 
and result in few wins. 


HCOB 31 Mar 71 - 2 - 


3. Running a new major program into an incomplete major 
program can be as deadly as failing to flatten a process 
before starting another process only more so. 

4. Failing to end off a program when its End Phenomena 
is achieved is another gross error. 

5. Being too ignorant of the basic bank and the tech theory 
(as different than processes) is another barrier to programming. 

6. Not Programming at all. 

The above six are the principle gross errors in 
programming. 


L. RON HUBBARD 
FOUNDER 


LRH:mes 
Copyright ($) 1971 
by L. Ron Hubbard 
ALL RIGHTS RESERVED