FREEZONE BIBLE ASSOCIATION TECH POST CLASS IV - HUBBARD ADVANCED AUDITOR (HAA) CASE SUPERVISOR COURSE - PART 7/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 ************************************************** ===================== 036. HCOB 6 Apr 1971 C/S Series 34 Non F/N Cases HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead Sussex Remimeo HCO BULLETIN OF 6 APRIL 1971 Class VIII All Auditors C/S Series 34 NON F/N CASES When cases do not bring an F/N VGIs to the Examiner, it is the signal to study the whole Case anew and find the bug or bugs that keep it from running and get-them handled. Recently I took over a whole series of these non F/N GI at Examiner cases and, very very carefully studied each one. IN EVERY EXAMINER NON F/N CASE I FOUND FLAGRANT OUT TECH IN (A) THE PROGRAMMING (B) THE C/Sing AND (C) THE AUDITING. All three outnesses existed. These cases were taken as all the Non F/N Exam reports on a line containing hundreds of folders and over 600 w.d. hours a week. So you can see that these errors had been missed by expert C/Ses and Auditors. The errors were missed because HOPE was being used instead of study. There was a hope that just routine C/Ses and auditing would work it out eventually. The factor of non F/N at Examiner was not given sufficient importance. The fact is that many who F/Ned at the examiner had small flaws in them yet still got by. The Exam Non F/N indicates FLAGRANT OUT TECH in the Programming and the C/Sing and the auditing. That's what it takes. If after a bug is found and corrected the case still may non F/N at the Examiner for a while. But after that while is passed the failure to give the Examiner an F/N means another bug and more study. One case I found had had a major grade done twice two years apart. This was pointed out and rehabbed. But after 2 or 5 sessions the TA remained high. A re-study now found Recall Flow 2 of the Exteriorization rundown had been run months ago to F/N and then continued for dozens of commands with the TA rising to 4.5. This was then repaired. The case then began to F/N at the Examiner. It now runs like an ordinary case, There is always a bug, not necessarily current, often very old in these Exam Non F/N Cases, There is sometimes two or three bugs, The answer is NOT go on C/Sing and hope. HCO B 6.4.71 - 2 - The answer IS, study and find the bug. Cases run on triples after a long list of singles is a type of bug. Cases exteriorizing and then getting no Ext RD is another bug. Cases given false reads or already run w/hs, cases who don't tell their cogs, cases who were on drugs but drugs were never run, cases that Rockslammed but no crime found, any of the GF 40 or GF reading items, cases with lists out, cases that are always sad or tired.......well these types of eases are the usual bugged cases. But even they sometimes F/N if only to roller coaster. The general rule of going back to where the case was running well and coming forward still holds. But an audit past Exteriorization can be before that and only eventually catch up, General repair is harmful when a big bug exists. Every case I examined had a big bug. Flagrant godawful overruns, messed up Exteriorlzation Rundown, three major programs begun, each incomplete, engram after engram botched and run to high TA then walked off from. The errors were real! They had been sitting there for some time unnoticed. Session after session mounting up into piles of Wasted auditing. Sick pcs are another indicator. Pc F/Ns at Exam, then reports sick. Look behind it you find some wild program, C/S and auditing error. So the answer is to STUDY THE CASE. Get a total FES done if one has never been done. current FES done or do it yourself. Then examine the programs and the FESes and Folder Summaries and suddenly you'll find it. Fortunately there aren't many things that can really foul a case up. 1. Overruns concealed within work sheets. Major grades twice. 2. Auditing past Exterior or flubbed Ext RDs. 3. Earlier unrun flows restimulated by later runs on those flows. 4. GF + 40 Items. 5. Never handled out lists. 6. Undetected drugs or drugs never handled by Dianetics. HC0 B 6.4.71 -3 - 7. False reads called (as in w/hs that "won't blow"). 8. Hidden standards. 9. Long Duration ARC Brks. 10. Impractical or inapplicable programs. 11. Major actions started never completed. 12. Overrepair. There can be combinations of these. So there aren't many. It's really knowing what is right so well that the wrong shows up like skywriting. Sometimes the errors are silly. A bogged Dianetic case had gotten tons of VI repair. The C/S, an VIII, had never realized Dianetic C/Sing is its own brand of C/Sing. He didn't shift gears to Dianetic C/Sing when C/Sing Dianetics sessions. The auditor way back had not known that when the pc originates "It's erased" and the TA remains high, his correct action is one more A B C D. This C/S had then tried Class VI remedies instead of telling the auditor "Flatten or rehab the last chain." When the chains left unflat were rehabbed all was suddenly well. Another case was interrupted for a year on a major action and when returned to auditing was begun on a long, long repair program. Inches of folder later the interrupted program was found and resumed and the case did great. All that "hopeful" repair was lost work. Ten minutes of case study would have saved twenty hours of useless repair. The stable datum is CASES MODERATELY WELL PROGRAMMED C/SED AND AUDITED RUN WELL. So cases that don't run well (unchanging Exam natter comment, Non F/N) have a BIG error in Programming C/Sing and Auditing. Look well and you will find it. And if that isn't it, there was another to be found as well. If you can't find the folder or data in it you should take every imaginable measure to acquire more data. D of P Interviews, 2wc sessions, telexes to his last org and telegrams to his auditors. But get data from somewhere somehow. Soon, when hours pick up and skill, all auditing will be sold by package not by hours. So learn economy of hours! An auditor or C/S who really knows his theory and has a good grasp of practical application knows the right way. From that he can easily see how things are wrong. HCO B 6.4.71 - 4 - An ounce of case study is worth ten pounds of wasted sessions. LRH:nt copyright ($) 1971 by L. Ron Hubbard L. RON HUBBARD ALL RIGHTS RESERVED FOUNDER ===================== 037. HCOB 26 May 1971 C/S Series 38 TRs Course and Auditing HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 26 MAY 1971 Remimeo Basic Cse Super Hat D of P Hat C/S Hats C/S Series 38 Tech Sec Qual Sec Dn Cse Ch/Sheet TRS COURSE AND AUDITING MIXING MAJOR ACTIONS With the use of TRs The Hard Way on basic courses, auditors and students, a rule must be laid down: A PERSON ON A TR COURSE OR IN PROGRESS ON A TR CYCLE MAY NOT ALSO BE AUDITED. And a second rule: HGC ADMIN AND THE D OF P MUST BE INFORMED OF ENROLLMENTS ON TR COURSES OR TRs CRAMMING AND MUST SO MARK A PCS FOLDER WITH DATE. And a third rule: IN AN ADVANCED ORG THE ADV CSE ADMIN MUST ALSO BE INFORMED OF STUDENTS ENROLLING ON A TR COURSE. And a fourth rule: A SIGN MUST BE PLACED IN QUAL AND IN A TR CLASSROOM "WHILE WORKING ON TRS AND UNTIL THEY ARE PASSED, DO NOT ACCEPT AUDITING." IN AN AO OR SH THIS READS : "WHILE WORKING ON TRS AND UNTIL THEY ARE PASSED. NOT ACCEPT AUDITING OR SOLO." The reason for these rules lie in the major C/S rules: DO NOT BEGIN NEW PROGRAMS TO END OLD. HCOB 26.5.71 -2- DO NOT START A NEW ACTION BEFORE COMPLETING THE EXISTING ONE. And the auditor rule: OBTAIN AN F/N BEFORE STARTING THE NEXT C/S ACTION. IF Unable to do so, NEVER BEGUN THE NEXT C/S ACTION BUT END SESSION AND RETURN THE FOLDER TO THE C/S. The surest way in the world to bog it one is to 1, Begin a new process without obtaining an F/N on the one just run; 2. Begin a major action without completing the old one; 3. Begin a major action without setting up a case with ruds and F/Ns. 4. Begin a new program without completing the old one. 5. Start several programs without finishing any. 6. Enter a new major action into a case already in progress on another incomplete major action. I have seen a case on as many as five major actions with none complete. And when I see this the first thing I take up is the first unflat incomplete program and get it finished, then the next, then the next. The case comes out all smooth. Example: Case is on but not complete on Dianetic auditing. Switched to grades. Incomplete on grades, gets a Prog Pgm. Incomplete on a Prog Pgm, shifted to Power, The only apparent execption is a repair. A case can be repaired if bogged PROVIDING THE ORIGINAL ACTION IS REHABBED IF O/R OR COMPLETED TO EP. A Progress Pgm may reach EP before the written up program is completed. Thus a Process Completion is defined as the END PHENOMENA of the process. A Program is complete when the End Phenomena of the Program is attained. Any course or program containing TRs 0-4, 6-9 or Admin TRs is a major Program in itself. It produces case gain - if run right - and has an End Phenomenon, HCO B 26.5.71 - 3 - Further, by actual experience when a person is on a real (not a patty cake & weak) TR Course and is also being audited at the same time, the C/S and Auditor if they don't know the person is also on TRs can be utterly baffled and worried as the case does not run right. "What did I do?" "What C/S was wrong?" "Look, his TA is high" "Now its low." "Last session he ______________ " And the C/S and auditor engage in efforts to handle the odd case behavior. But the person, unknown to them, was also on a real TR Course and his case was changing! INTERJECTED PGMS You can also run into this same oddity with a mystic who does "bathe the body in light" every night or a wife whose husband audits her between HGC sessions or a self- auditor. The principle is the same, The C/S and auditor are going down Wellbeing Street and hidden trucks keep dashing out of alleys and running into the pc. The reason auditing should be done in intensive packages, not 1 hour a week or a session a month lies in the fact that LIFE can run a new action in on a pc. It's a great way to waste auditing to let a pc have a session once a week. You can't even keep his ruds in if he lives in any confusions. So nothing is done for the case, all the auditing goes to handle the life interjections! A case runs on cycles of action. This is true in the auditing comm cycle. It is true in a process cycle. It is true in a program cycle. New things being crossed into old incomplete things make a sort of ARC Break situation like a cut comm cycle. One could do everything with a process or a program OR A COURSE that you find on an L1C. It would not be very wise. No case gain can be created by lack of a comm cycle in an auditor, lack of an action cycle in processes or messing up a program cycle. If you don't believe it, run an L1C on a pc with "Processes" and "Programs" and courses as a prefix. You'd be amazed. Further the fellow who doesn't reach the EP of a course is likely never to use that material or be faulty with the subject. Usual study courses like admin or tech give case gain. One can carry on with auditing parallel to them. But still expect a case to change a bit by study and baffle a C/S once in a while, HCOB 26.5.71 - 4 - But a real TR Course produces changes up and down and up that are not possible to also audit around. So they don't mix. VISUAL IDEA To get a visual idea of this: Optimum: Start Change End TR Course |---------------- | -----------------| Start Change End Pgm 1: |---------------- | -----------------| Start Change End Pgm 2: |---------------- | -----------------| Ghastly: TR Cse Start ? Change Start x, ' Cha ge Pgm 1 , -= ,== ........ ' . an Where's the End? Why, here, of course: Got it? LRH:nt:sb Copyright ($) 1 971 by L. Ron Hubbard L. RON HUBBARD ALL RIGHTS RESERVED ===================== 038. HCOB 9 June 1971 C/S Series 41 C/S Tips HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 9 JUNE 1971 ISSUE I Remimeo C/S Series 41 C/S TIPS LISTS Always C/S to correct lists first when lists are out or suspected be out. Don't do ARC Brks first in a case of out lists as an out list can make an ARC Break that can't be handled by ARC Brk but only an L4B. On a GF when lists show up or overlists you should handle that (first action in handling the GF) but also you must order an "L4B Method 5 and Handle." Method 5 is the once through for assessment. NO READ AUDITORS When auditors can get no reads on things you get their a) TRs checked to see if they can even be heard. b) Their metering checked for meter position on auditing table, can they see meter, pc and write without shifting eyes? And can they see pc's hands on the cans? And was the meter turned on and charged and can an auditor work the Tone Arm smoothly with his thumb. c) Does the auditor discount reads gotten on clearing commands? (They are the reads.) d) Can the auditor read out a list and see the meter reads as a coordinated action? CRAMMING Send auditors to cramming on all flubs, insist they GO to cramming, insist cramming calls them in and crams them and insist on a carbon copy of the fact that cramming has been done. All the hard work of C/Sing comes in when auditors are flubby. It takes weeks to make an auditor after he has had a course and. its only done by Cram - Cram - Cram. R FACTOR Never order an R Factor that takes pc into future or past as he then won't be in session. Example: C/Ses "R Factor We are setting you up for Dianetics." Promptly the pc is up ahead not in this session. HCOB 9.6,71 - 2- Issue I MIXING STARTS There are many ways to start a session. Don't mix them. It's "2 wc what do you have your attention on?" "Fly a rud if no F/N." "Fly all ruds." "2 wc the TA down." "Fly a rud or GF + 40 Method 5 and handle." It's not a mixture of frantic 'efforts to Set a TA down. If the auditor can't on what the C/S says THE AUDITOR ENDS 0FF. Interiorization is undone or out, there may be list errors, there may be overruns, but for sure it s a case for FOLDER STUDY, not for an auditor. C/Sing In the Chair. HIGH TA & ARC BREAKS Train your auditors NEVER TRY TO GET A TA DOWN FROM 3.5 OR ABOVE ON ARC BREAKS. Some auditors see a TA sink below 2.0 and then won't continue the 2 wc or process to get the TA back up. "The TA sank so I quit" is a common auditor note. Compare this: "The TA rose above 3.0 so I quit." See? Doesn't make sense. If a TA sinks below 2.0 - and the auditors TRs are good - the same action will usually bring it up to 2.0 and F/N. Come down hard on auditors who do this. Get their TRs checked make them continue. Pcs whose TAs are high in session or low in session get F/N at the Exams put the finger on the auditor. They are protesting or being overwhelmed. Always C/S "Examiner! Ask pc What auditor did in session." Then you know it's the auditor or the case. The pc will say the auditor was okay. So it's case. But usually when cases are puzzles there's weird things going on with TRs. Also the auditor may be noisy or laugh hard or is boisterous and being "interesting". HCOB 9.6.71 -3- Issue I The C/S is handling cases on the via of an auditor. If the auditor is perfect the C/S can handle the work out of the case. If the auditor is not perfect in TRs, metering, Code, reports and doing the C/S then the C/S is solving a factor unknown to him, not the pcs case. So, be a perfect C/S. Demand perfect auditing. Cases fly. HIGHER LEVELS A C/S who assesses a pc to higher levels to solve lower ones is really asking for a wreck. It's always the earlier actions that are out. Trying to cheat a case up to Grade 2 when he won't run on Grade 1 is like trying to run the whole grade chart to cure a cold. A pc can always be solved in or below where he is. "Oh, we'll put him up a grade and cure his high TA" is like "He can't pass kindergarten so we'll enroll him in college." C/S EXPERTISE A C/S has to know his auditing materials HCOBs and texts MUCH better than an auditor. If a C/S is not being successful, get a retread on VI and VIII materials. A C/S also must be confident HE could crack the case as an auditor. When a C/S is shaky on his materials then the world of auditing looks very unstable. The tech is very exact, very effective. If any errors existed in it they've been corrected. So the variables are the knowledge of the C/S, his discipline and demands of auditors and the actions of the auditor. If THESE are stable then the cases that come along are easy as can be. The successful C/S knows his materials. If he wants to be even more successful he keeps his study up. Then he is steady and calm for he is totally certain. RON HUBBARD FOUNDER LRH:sb Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 039. HCOB 9 June 1971 C/S Series 42 C/S Rules HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 9 JUNE 1971 ISSUE II C/S Series 42 C/S RULES COMPLETE CYCLES Don't leave cycles incomplete on a case. If a C/S starts a 37R and the auditor goofs, correct the auditor and then get the 37R completed. Don't disperse and do something new. If you have a program going and it's goofed, repair the auditor and the goofed pc and continue the program you began on the case. Repair (Progress) Programs are ended when the pc is flying nicely. When a repair hits that don't re-repair. On Advance Programs, take each step to its EP. Don't suddenly start something new. A sure way to solve a case is go back and find the earliest incomplete program, complete it and so on up to PT. Keep your "finger in the book" on a case. Don't lose your place. That's done by having the current pgm on the inside front cover, paper clipped on, and checked off with each step done. When it's done, put a new pgm on top of it. Insist that auditors keep up the inside front cover folder summary each session with their auditing time and admin time in the box. This FS is a 2 column set of boxes, date, what's run, F/N or bogged and time. By seeing Admin is in you can keep your place in the book or study back rapidly to find what's been done. DOUBLE ACTIONS The deadliest faults on cases are running the same action or grade twice. This drives TAs up through the roof. Example: Power done in '65. Done again in '69! Example: Grade IV done in '69, done in '70. You find the case isn't doing well or find the error. In doubles, rehab by date of the first time it was done. I've seem Interiorization done three times on one pc, Power twice and the same Dianetic Chains run over and over. And people wondered "Why is the TA high!" So when you order a major action always check to see if its ever been done before! Save you grief, And if a major action won't run, suspect it may have been done before. HCOB 9.6.71 - 2 - Issue II SET UPS Always set up a case fully for the next major action. Don't overrepair. But be sure the case is not sick, has had good exam forms and does well, Then C/S the next major action. BLAMING THE PC Never blame the pc. Many it is true are dog cases. But even dog cases can be handled. When you find auditors (or feel yourself) blaming the pc, get the overts and witholds run out. Once I got the most splendid sessions out of an HGC. I had the auditors overts and witholds checked on each auditor before he went into session. It Was just research, but my it worked! Those were the smoothest sessions! Pcs began to fly! Too many times one blames the pc only to find later that the auditor's TRs were ghastly and that a major action had been run twice. Such discoveries make a C/S out of a C/S. L. RON HUBBARD FOUNDER LRH:ab Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 040. HCOB 9 June 1971 C/S Series 43 C/S Rules - Trouble for the PC HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 9 JUNE 1971 ISSUE III C/S Series 43 C/S RULES TROUBLE FOR THE PC Never make trouble for the pc. When a pc is running well let It roll. The C/S can spot a possible error but the pc is Wide F/N VGIs at the Exam, let it go. Chew the auditor, send to Cramming. But don't throw the well runntng pc Into extensive repair - don't break into a wlnnlng program harshly. tt gives the pc a loss. The pc who Isn't running well is the one you repair. Don't keep a pc going on and on, running badly with no case study. Study the case folder, find the right why by going back to where the pc was running consistently well and then come forward for the error. It will be In the exact next session. If the pc wasn't ever audited before, you go into his life of course, with a GF + 40 Method 5 and handle and other Life repairs. OVER REPAIR Any Repair or Progress action has reached its End Phenomena when the pc Is running well again. This is peculiar to the Repair or Progress program. Wrong Example: Pc was on Grade III, fell on his head. C/S studied case, found out lists, wrote an extensive repair pgm and C/S. Half way through Repair the pc again was flying. C/S continued the repair. PC bogged. C/S C/Sed the pc to flying again. C/S continued the repair. Pc bogged, Right Example: Pc falls on his head on Grade III. C/S writes a Repair Pgm and C/S. Auditor finds the out list, corrects It. Pc flys. C/S puts pc at once back on Grade III to complete. AUDITOR INVAL An auditor can be Invalidated by a C/S by having a lot of questionable tech points thrown at him, The auditors data gets shaky. If no decision was ever made - Is not in HCOBs and tapes - Is not to hand and can't be referred to by HCOB and tape, then a C/S should not be making the point. Example: Auditor extends a list three more Items beyond an F/N, C/S chops him. There is no such rule. The pc maybe wouldn't accept the Item until he listed a few more. Result is a fire fight between C/S and Auditor, simply because It isn't a valid point. HCOBs and Tapes are the stable data that form the agreement between the auditor and the C/S. "If It isn't written (or spoken on tape) It isn't true". Don't wander off known tech points In C/Sing. Never shake an auditors data by advancing data not on HCOBs and Tapes. Always know your data, your HCOBs and Tapes and refer the auditor to them in Cramming. Cramming MUST have a library of all materials. A hidden data line can build up In C/S-Auditor lines (or course lines or Cramming lines) that CAN UNSTABILIZE ALL TECH AND DENY FURTHER RESULTS. The decay of tech in areas begins with hidden data lines that ARE NOT TRUE. So use and refer to HCOBs and Tapes and leave all other points alone. Your auditors will become confident and certain and Tech will Improve. It's enough Just to Insist on the usual. Then auditors and cases will fly. L. RON HUBBARD FOUNDER LRH:sb.mek Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 041. HCOB 19 June 1971 C/S Series 46 Declares HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 19 JUNE 1971 ISSUE II C/S Series 46 DECLARES It is the C/Ses responsibility that a pc or Pre OT is sent to Declare This is not an Admin point I'm making. It is a technical point. Every so often a pc is found hung up in not having declared and attested the state attained. A Declare Completes his cycle of action and is a vital part of the action. One never forces or feeds one to the pc. I recall one org where the entire tech and income structure crashed, the C/O and several personnel had to be removed because they were forcing "clear cogs" on their Dianetic pcs who hadn't had them (and then telling them they couldn't be audited further on Scientology) (Connie Broadbent, ASHO, March '70). So this goes 2 ways. THE PC OR PRE OT WHO KNOWS HE MADE IT MUST BE SENT TO EXAMS AND C&A to ATTEST. THE PC OR PRE OT WHO HASN'T MADE IT MUST NEVER BE SENT TO EXAMS TO DECLARE AND ATTEST. This gives us a third: PCs AND PRE OTs WHO HAVEN'T MADE IT MUST BE HANDLED UNTIL THEY HAVE MADE THAT SPECIFIC DECLARE EVEN THOUGH IT MEANS SIGNING UP FOR MORE AUDITING. TRUTH is the keynote, the essence, the point here. All the "PR" (slang for promotional talk) in the world, will not supplant truth. The pc KNOWS he made something. Therefore he must be sent to declare it whether its a standard grade or not! The pc who hasn't made it KNOWS he hasn't and so when forced to declare or ordered to attest tends to cave in. His concept of the validity of the org and honesty of Scientology depends on this, and really on this alone. HCOB 19.6.71 - 2 - Issue II The correct declare or not declare decision of the C/S is a vital C/S action. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 ALL RIGHTS RESERVED ===================== 042. HCOB 8 Aug 1971 C/S Series 55 The Ivory Tower HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 8 AUGUST 1971 C/S Series 55 THE IVORY TOWER It has been stated before that the Case Supervisor is most successful when he supervises in seclusion. This called the IVORY TOWER rule. It comes from the practical experience that in C/Sing thousands of cases the only few mistakes I made (and repaired) was when I listened to the opinion of the auditor or saw the pc. This can be quite fatal to a case's progress. The fantastic results I achieve as a C/S mainly stem from not permitting what I know of tech and cases to be clouded by "Human Emotion and Reaction" (a Scn Public Relations term) by others. Part of a C/Ses duty is to get the case through it despite auditor opinions and flubs or the opinions of others. A C/S has no political or personnel opinions. He can of course have hie own opinions of the pc's case. But he is the FRIEND of the pc even when being harsh. Often the C/S, unseen by the pc, is sometimes never suspected but quite often adored by those for whom he O/Ses. One often sees this in success stories, "Thank you, thank you to my great auditor (name) and the C/S (name) and Ron." Sometimes its only the auditor. But most pcs know the C/S is there. This awareness is also a great trust and it is a trust that is earned by great results and is never betrayed. To the majority of pcs, then, it is a trio - always in the same order - his auditor, his C/S and myself. He trusts us. And we do our best for him. We don't change our actions, then, if he is a dope addict, a wife beater, a criminal, a degraded being or an upstat (one who has high statistics) and a sterling person. When we are researching, C/Sing or auditing, we do our best for him. We have nothing to do with whether his seniors like him or for that matter whether we like him. It is our job. We hold it in trust. HC0 B 8.8.71 - 2 - In Our hands is his future, his sanity, his immortality. It depends on us whether he survives and lives a full life or whether he goes into limbo. If we do our duty, when we know and do our jobs, he achieves everything. When we don't, he is gone. No priest or fancied idol has ever been endowed with more fancied cause over the beingness of another than a C/S and his auditor. This isn't my opinion or my feeling about it. It's the way pcs look at it. Actually one can't really state the full actuality of it. The pc is justified in trusting us when we keep up to date on our tech, know our Job, take every care that a good job is done and do our duty. AUDITOR OPINION Some auditors develop overts and witholds on pc and color their auditing reports with critical remarks about a pc = more witholds. A C/S who pays much attention to these options is foolish. When they get too bad on too many pcs, get the auditors overts and witholds pulled as he'll begin to flub. The Worksheet and what the pc said or did is important. The opinions aren't. An auditor has a right to refuse to audit certain pcs as long as he audits others. That's as it should be. But a lot of "dog cases" are just unsolved cases that can be solved. Some are very difficult, true, but the difficulty is finding the bug. Some pcs are rather wild in conduct. But they solve too So an auditor's opinion is not a study of the case. Talking to an auditor about a case he is auditing is not of any technical value to a C/S. Again, a case does not know what is wrong with it or it would as-is and wouldn't be wrong. So talking to a case about his case is a waste of time for a C/S Some write huge notes to a C/S. The only value in all this is to analyze whether its a hidden standard or an ARC or a w/h or a PTS matter. TECHNICAL considerations are all that that enter into looking over such. EXECUTIVE opinion Is the world's worst source of data on a pc. No C/S should ever take what seniors say about a junior. It's all Human Emotion and Reaction. It's not tech. HCO B 8.8.71 - 3 - Family, husbands, wives, fathers, mothers, brothers and sisters, aunts and uncles are of little value to listen to about a case. The most they could give you would be a list of accidents or illness or time in a home, But beware, they may be worse off than the pc. No. The C/S is the pc's safest friend. The pc trusts the C/S and the auditor. Or he wouldn't sit still at all. Sometimes he only trusts me. And that's the time I have to trust you, And I do. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 043. HCOB 7 Sept 1971 C/S Series 58 Programming Cases Backwards HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 7 SEPTEMBER 1971 C/S Series 58 PROGRAMMING CASES BACKWARDS When you see a case that has struggled along through 200 hours of processing without much gain you sometimes see a C/S has only recently ordered, or has not ordered at all as yet, an Interiorization RD check and a Green Form No. 40 Expanded. That would be programming backwards. The tools of auditing are the Grade Chart Processes and the numerous correction lists. Like a gardener, a C/S has the choice of numerous tools to raise a flower. If you were to see a gardener digging holes with the lawn mower and cutting grass with a spade, you would say he needed to be checked out on the use of his tools, what each is for. Similarly, running Power on someone who needs Dianetics, doing a life repair on someone who is ready for R6EW, would be a misuse of tools. Similarly, going on auditing someone on Dianetics who desperately needs his ruds put in or an Interiorization Rundown is wasting auditing and messing up a preclear. Let me give you some examples I have seen recently: A. Case audited through many major actions since his Int RD. Auditor and C/S in despair. Pc not progressing. A C/S 53 disclosed the Int RD was faulty and its repair was also faulty. Int Rundown was handled. Case began to run. Months of auditing had been wasted. Needed had been a C/S 53 where out Int would have shown. B. After 200 or more hours of no change in his personality graph (Oxford Capacity Analysis) the pc came up with the withold that he was a homosexual and also that he did not know what "Scientology" meant. About 2 years of auditing had been wasted. Needed had been Word Clearing and rudiments. C. After scores of hours of no-win auditing and no graph change it was finally decided to run a GF 40X and found the person practiced witchcraft. D. After a year of auditing on major grades all wasted it was finally found that the person had had a leg injury he was trying to cure that required only a simple Dianetic assist. Today that would be a C/S 54. He had never had a Pc Assessment Form. HCO B 7.9.71 - 2 - E. After racing from POWER to OT III without doing any real auditing or having any change, it was found on a GF 40X that the whole world had been unreal and the person could not begin to face the idea of looking at pictures or the bank and had not been able to since her first drug experiences. Needed had been Objective Processes, CCHs, Op Pro by Dup etc which get a drug addict to look and be aware. All these are simple if flagrant errors in ordering the right program actions. In order to be able to say what should be done on the case, one has to have three things: 1. Data about the case. 2. A knowledge of what lists are available. 3. Auditors who can do the actions required., From a C/S point of view, all these things are under the C/S's control. DATA In the Class VIII materials the 7 Resistive Cases are described. The full lot of them are now found in GF 40X. There are numerous other lists for assessment. If a C/S really doesn't know his lists he can order them all, Method 5 and take his choice of symptoms. Also a C/S can have the pc simply asked questions. From this data a C/S knows why the case is not running well and can order the actions to remedy it. If nothing is wrong, complete the earliest incomplete grade on the grade chart. KNOWLEDGE A C/S who is well Word Cleared on his materials and has studied on the courses knows what things hang a case up more than what other things. This gives one the knowledge necessary to choose what lists. Case no case gain then its GF 40X. And to keep from auditing over an out Int RD there is C/S 53. And for chronic aches and pains there is C/S 54. HCOB 7.9.71 - 3 - And for "might be anything" there's a GF. What lists and actions that can be done are for is very easy to sort out. AUDITORS If a C/Ses auditors aren't flubless or expert one needs to get in a Cramming and needs to get hired and interned lots of new auditors. C/S Series 57, The C/S as a Training Officer, solves a lot of this. And a Tech Establishment Officer is vital to keep it solved. Then auditors, the number and quality of, are not on the C/S's plate as a continual problem. Scientologists want to audit. They will go on auditing as long as you make them audit well enough and C/S for them well enough to keep them winning on pcs. SUMMARY So the tools of the C/S are 1. Data from pcs. 2. Knowledge of list uses. 3. Knowledge of the Grade Chart. 4. Auditors. 5. The organization of delivery. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED =====================