FREEZONE BIBLE ASSOCIATION TECH POST CLASS IV - HUBBARD ADVANCED AUDITOR (HAA) CASE SUPERVISOR COURSE - PART 3/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 ************************************************** ===================== 008. BTB 30 Nov 1971R C/S Series 67 The Code of a C/S Reissued 17 July 1974 BOARD TECHNICAL BULLETIN 30 NOVEMBER 1971 R CORRECTED & REISSUED 16 DEC 71 (CORRECTION P.2,no.18) REVISED &.REISSUED 17 JULY 1974 AS BTB Remimeo All Auditors CANCELS All C/Ses HCO BULLETIN OP 50 NOVEMBER 1971 to Star- SAME TITLE rate on receipt* (The only revision is on P. 1, References Section. HCO PL 15 NOV 69 is now BPL 15 NOV 69.) C/S Series 67 THE CODE OF A C/S References: HC0B 15 NOV 69 C/Sing, How it Goes Non-Standard BPL 15 NOV 69 Rights & Duties HCOB I7 SEPT 68 Gross C/S Errors HCOB 22 SEPT 71 Three Golden Rules of a C/S (C/S Series No. 61) HCOB 19 JUNE 71 C/S Series 46 Declares This is the Code of a C/S as regards his Auditors and their PCs for whom he is C/Sing. 1. I promise to know my Dianetics ($) and Scientology ($) totally cold up to the Level at which I am C/Sing. 2. I promise never to look for some imagined error in Tech Data but always to look for and find the real error in the auditing programming or C/Sing. 3. I promise never to treat a case as "different". 4. I promise that if I cannot find the reason why a session has failed from the folder that I will suspect a False Auditing Report and get the PC asked about the session and get data as to why it failed. 5. I promise never to punish an Auditor for querying a C/S. 6. I promise to refrain from discussing or mentioning data from PC folders socially. BTB 30.11.71 R - 2 - Rev. 17.7.74 7. I promise to correct my Auditors' application of Tech positively without invalidation. 8. I promise that I will order the Auditor to Cramming or retraining for any flunked session. 9. I promise never to order an unnecessary repair. 10. I promise never to use repair processes to get case gain when the PC needs the next grade. 11. I promise never to give verbal C/S instructions but always to write them down. 12. I promise never to talk to the Auditor about the case. 15. I promise never to talk to a PC about his case. 14. I promise to send the PC to the Examiner or D of P, to get data, if unsure why the folder has been sent up for C/S. 15. I promise never to be reasonable as a C/S. 16. I promise to maintain sufficient Ethics presence to get my orders followed. 17. I promise never to issue involved repair orders. 18. I promise never to follow C/S advice from a PC but I will accept the PC's data. 19. I promise that I will ALWAYS read through the PC folder before C/Sing a case* 20. I promise I will always have the folders of cases in trouble case-wise, ethically or medically reviewed to find the Out Tech. 21. I promise never to put a PC on a grade to "solve his case". 22. I promise to always order a repair of a misaudited grade until the End Phenomena has been achieved. 23. I promise to advance the PC up the Grade Chart in the proper sequence. 24. I promise never to order a grade run that the PC is not set up for. 25. I promise never to indulge in the practice of "hopeful C/Sing". 26. I promise never to C/S a session I cannot read but BTB 30.11.71 R -3- Rev 17.7.74 will instead return it to the Auditor for clarification. 27. I promise to make every effort to find and point, out an actual goof and send the Auditor to Cramming. 28. I promise never to invalidate or harass an Auditor for a correct action or when no Technical goof has occurred. 29. I promise to recognize and acknowledge a Technically perfect session. 30. I promise to see that a PC or Pre-OT who knows he has made an EP is sent to Exams and C&A to attest. 31. I promise never to send a PC or Pre-OT who hasn't made it to declare and attest. 32. I promise to see that PCs and Pre-OTs who haven't made it are handled until they have made that specific Declare. 35. I promise to complete cycles of action on the PC and never start a new one while an old one is still incom- plete. 34. I promise to ensure that the Auditors for whom I am C/Sing continue to improve in skill and training level. 35. I promise to maintain a standard of the highest Professional conduct. Flag Dept 12 C/S Reissued as BTB by Flag Mission 1234 I/C: CPO Andrea Lewis 2nd: Molly Harlow Authorized by AVU for the BOARDS OF DIRECTORS of the CHURCHES OF SCIENTOLOGY BDCS:SW:AL:MH:RL:mh Copyright ($) 1971, 1974 by L. Ron Hubbard ALL RIGHTS RESERVED This is Reproduced and issued to you by The Publications Organization, U. S. ===================== 009. BPL 15 Nov 1969R Rights and Duties Reissued 26 June 1974 BOARD POLICY LETTER 15 NOVEMBER 1969 R Remimeo REVISED & REISSUED 26 JUNE 1974 AS BPL Class VIII Cksht CANCELS Qual Sec HCO POLICY LETTER OF 15 NOVEMBER 1969 Hat SAME TITLE Tech Sec Hat C/S Hat Auditor Ckshts RIGHTS AND DUTIES The following Rights and Duties are to be posted in the staff area of every Qual Division and Tech Div- ision, where they will he frequently seen by auditors and technical personnel. They are to be printed green on white in letters at least 1 inch high, each on a separate card (4 total) AN AUDITOR HAS THE DUTY: TO KNOW AND ABIDE BY THE AUDITOR'S CODE TO APPLY TECH EXACTLY AS PER HCOBS AND LRH TAPES TO BE THOROUGHLY FAMILIAR WITH THE FOLDER OF ANY PC HE AUDITS TO FOLLOW C/S INSTRUCTIONS EXACTLY IN SESSION TO REFUSE TO AUDIT AN INCORRECT C/S TO AUDIT ONLY THOSE MATERIALS ON WHICH HE HAS BEEN CHECKED OUT STARRATE TO BE FAMILIAR WITH AND APPLY ALL NEW TECHNICAL MATERIALS UP TO HIS CLASS LEVEL AN AUDITOR HAS THE RIGHT: NOT TO AUDIT A PRECLEAR HE HAS A DIRECT PERSONAL RELATIONSHIP WITH (IF HE DOES NOT WISH TO) TO REFUSE A C/S HE KNOWS TO BE INCORRECT T0 ASK TO BE REFERRED TO THE HCOB COVERING A C/S HE IS UNCERTAIN OF OR FEELS IS INCORRECT NOT TO BE PUNISHED FOR QUERYING A C/S WHETHER CORRECT OR NOT TO HAVE PCS, AUDITING ROOMS, AND MATERIALS MADE AVAILABLE TO HIM BY TECH SERVICES A CASE SUPERVISOR HAS THE DUTY: TO REFUSE TO DISCUSS A CASE WITH EITHER THE AUDITOR OR HE PC BPL 15.11.69 - 2 - Rev. 26.6.74 TO REFRAIN FROM DISCUSSING OR MENTIONING DATA FROM PC FOLDERS SOCIALLY TO CORRECT HIS AUDITORS' APPLICATION OF TECH POSITIVELY, WITHOUT INVALIDATION TO ORDER THE AUDITOR TO CRAMMING OR RETRAINING FOR ANY FLUNKED SESSION TO MAINTAIN A STANDARD OF PROFESSIONAL CONDUCT TO C/S ALL FOLDERS DELIVERED TO HIM DAILY A CASE SUPERVISOR HAS THE RIGHT; TO HAVE HIS OWN OFFICE TO HOLD NO OTHER POST NEVER TO RUSH HIS OWN C/S ACTIONS TO ACCEPT NO TECHNICAL ORDERS OR ADVICES OTHER THAN FROM LRH TO DEMAND A HIGH ADMINISTRATIVE STANDARD OF THOSE. WHO WORK ON HIS LII^ES TO DEMAND THAT PCS DO NOT DISCUSS THEIR OWN CASES OR OTHERWISE VIOLATE PC RULES TO ISSUE AND GET COMPLIANCE ON ANY ORDERS NEC- ESSARY TO THE PERFORMA.NCE OF HIS DUTY AND TECHNICAL RESULTS Lt. Nate Jessup, Chairman Ens. Janet Guilford, Sec. W/O Bob Guilford, Member Qual Board of Investigation. Revised & Reissued as BPL by Flag Mission 1234 I/C: CPO Andrea Lewis 2nd; Molly Harlow Authorized by AVU for the BOARDS OF DIRECTORS of the CHURCHES OF SCIENTOLOGY BDCS:SW:AL:MH:NJ:JG:BG:mh Copyright ($) 1969 1974 by L. Ron Hubbard. ALL RIGHTS RESERVED This is Reproduced end issued to you by The Publications Organization, U. S. ===================== 010. HCOB 22 Sept 1971 C/S Series 61 The Three Golden Rules HUBBABD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 22 SEPTEMBER 1971 C/S Series 61 THE THREE GOLDEN RULES OF THE.C/S HANDLING AUDITORS There are three firm rules in handling auditors which makes the difference between good auditors and poor auditors or even having auditors or no auditors at all. 1. NEVER FAIL T0 FIND AMD POINT OUT AN ACTUAL GOOF AND SEND THE AUDITOR TO CRAMMING. 2. NEVER INVALIDATE OR HARASS AN AUDITOR FOR A CORRECT ACTION OR WHEN NO TECHNICAL GOOF HAS OCCURRED. 3. ALWAYS RECOGNIZE AND ACKNOWLEDGE A TECHNICALLY PERFECT SESSION. By reversing these three things a C/S can wreck and blow every auditor in the place* By always doing these three things correctly the C/S winds up with splendid auditors. An auditor who knows he goofed and yet gets a well done ' doesn't think the C/S is a good fellow. He holds the C/S in contempt and his auditing worsens. An auditor who didn't goof and yet is told he did becomes bitter or hopeless and begins to hate the C/S. The test of a C/S in the auditors eyes is "Is he spot on?" meaning is the C/S accurate in giving the right program, the right C/S, spotting the goof and ordering cramming, and being well enough trained to see and commend a well done. You never get Bad Indicators in an auditor or student when you state the truth. You only get Bad Indicators when your statement is not true. "PR" (Public Relations cheery falsehoods) has nothing to do with getting good Indicators. Good indicators in auditors are made with TRUTH. "You goofed, go to Cramming, do TRs 101 to 104 until you cease to alter commands" HCOB 22.9.71 - 2 - "Well done by Exams. Practice Handwriting so I don't take so long reading your worksheets." "This F/N VGIs at session end and the Bad Exam Report do not agree. Is there any way this report was falsified? Is there any goof you didn't write down?" or "Very well done" on a very well done totally ON Tech, ON Admin and Correct Auditors C/S session. Auditors work well even for a bad tempered C/S when that C/S is always "Spot on" with program, C/S, Auditors grade or censure of auditor and TO CRAMMING* Auditors like a businesslike accurate C/S. A "good fellow" C/S who "lets it slide" and says nothing becomes a very bad fellow indeed in auditors eyes. A C/S who doesn't recognize and who invalidates good auditing is looked on as a suppressive even when its just ignorance. The Golden Rules of C/Sing are 1. Never fail to find and point out an actual goof and send the auditor to cramming. 2. Never invalidate or harass an auditor for a correct action or when no technical goof has occurred. 3. Always recognize and acknowledge a technically perfect session. Only those C/Ses who follow these Golden Rules are truly loved by their auditors. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 011. HCOB 20 June 1971 C/S Series 47 The Supreme Test of a C/S HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 20 JUNE 1971 C/S Series 47 THE SUPREME TEST OF A C/S (Reference HCO B August 19, 1967, The Supreme Test which must be read with this HCO B.) A C/S or auditor who knows his tech is able to hold the line on any given action in auditing or C/Sing and not mix up. One C/Ses Dianetics purely. Not Dn Cl VI Class VIII, Dn, Class VI. One C/Ses or audits a Rundown as itself, not as a botch of several actions run into it. So this brings to view that some can run the process or program for A to B. And some, worse luck, (a) Go from A to G to Q to A and wonder why they don't arrive at the B of result. (b) Some go from A to B all right but when at B go right on past it. Both, actually, are a type of non-confront. The A.G.Q.A can't confront and disperses off arriving at D. The A beyond B hasn't confronted B and so doesn't recognize B. The ability to confront the pc and the session and parts of the session permit one to accurately go from A to B. Proving this, perception reduces in ratio to overts. Accept that fact as its true. If you run 0/W on an auditor regarding the pc he is to audit, the auditor will give a perfect session to that pc. Why? He can confront because he can see. Programming is simply an A to B action. The road is all laid out. Auditing a process is a simple A to B Action. What if you had an auditor who half way through Level Zero with no completion found a picture, did Dianetics on it, didn't flatten the R3R because pc cogged it was like his mother and the auditor did 0/W on mother in the middle of the engram! HOOB 20.6.71 - 2 - The pc would be a mess! B was run away from. Same way with programming that isn't handled. What if you had an auditor who got an F/N Cog VGIs and continued the same process to TA 5.6? He got to B and kept right on going. Same way with programs. So really the Supreme Test of an auditor or C/S is to begin at the A and arrive at the B in any process or program. You should look into some folders where the C/S or auditor dispersed off B or where B was reached with no halt. The most recent examples I've seen have been taking processes out of one Rundown and using them in another Rundown all in an effort to achieve a maximum effect when the error that was present came from failure to complete 2 earlier programs. The correct action would have "been to complete the earliest program left incomplete and then complete the next incomplete program, not scramble parts of two new programs. A to B is a cycle of action. A clean one. It is beet to keep it so. The Supreme Test of an Auditor or a C/S is to make Auditing go right - by the book. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 012. HCO PL 21 Oct 1973R Case Supervisor Statistic HUBBARD COMUNICATIONS OFFICE Saint Hill Manor, East Grinstead Sussex HCO POLICY LETTLS OF 23 OCTOBER 1973R Remimeo UPDATFD 28 JANUARY 1975 TO INCLUDE SENIOR C/S CASE SUPERVISOR STATISTIC (Cancels HCG PL 1 Mar 72 of same name. Amends HCO PL 14 Oct 70 "Div 4 Org Bd Ideal Scene and Stats" Pg. 7 last section: "Tech C/S Stat". Cancels "Staff Case Supervisor STATISTIC" Pg. 3, HCO PL 20 July 70.) TECH (PUBLIC) CASE SUPERVISORS; IDEAL SCENE: EVERY Public Case resolved standardly per LRH HCOB and LRH tape and progressing, up the Grade Chart, flawlessly Audited by Auditors who are continually standardized, handled arid trained through C/Sing, Cramming, ethics, retread or retrain by the Case Supervisor and the C/S himself wall trained and in good and confident condition. STAT: Fully completed standard Auditing cycles accompanied by a rave success atory. DEFINITION: A standard Auditing cycle includes only those items which appear on the paid completions HCOB 30 Aug 71RA Issue II Revised 21 Oct 73 "Paid Completions - Second Revision". DEFINITION: A rave success story is one given voluntarily without coercion or threat at Success by the pc which expresses actual improvement and benefit due to Auditing received in complimentary terms which may include to Scientology, the Founder, the C/S and/or the Auditor, STAFF CASE SUPERVISOR: IDEAL SCENE: All staff injuries, upsets, PTSness, illness and drugs fully handled and F/Ning at Examiners and when awarded Grade Auditing rapidly completing major cycles of the Grade Chart with a rave success story. STAT: Fully and terminatedly handled cases who are in good physical and case condition and completed and off staff auditing lines less Staff remaining in poor condition or Incomplete. DEFINITION: Good Physical Condition: Not suffering from physical illness, not PTS, not currently physically damaged by accident. DEFINITION: Good Case Condition: Attained the level of case for which the org is classified and now in training during staff study time for Admin or Tech certification. DEFINITION: POOR Case Condition or Incomplete: A staff member who is in a state of chronic repair or who is who is not in good physical condition or good case condition as defined above. HCO PL 21.10.73R - 2 - Updated 28 Jan 75 DEFINITION: Staff: Means any staff member, crew member or executive or officer who is not directly paying for his or her Auditing but is obtaining it as staff. DEFINITION: An HGC or AO C/S who is C/Sing for staff or crew may only count the staff or crew under the above stat. Any Public pcs are counted as a dual or separate stat. SENIOR C/S: IDEAL SCENE: EVERY Public, Student Co-Audit and Staff Case resolved standardly per LRH HCOB and LRH tape and progressing up the Grade Chart, flawlessly C/Sed and audited by C/Ses and Auditors who are continually standardized, handled and trained through supervisions C/Sing, Cramming, Ethics, retread or retrain by the Senior C/S who is himself well trained and in good and confident condition. STAT: Total number of fully completed standard Auditing cycles accompanied by a rave success story on Public and Student Co-Audit PLUS total number of fully and terminatedly handled Staff cases who are in good physical and case condition and completed and off staff auditing lines less Staff remaining in poor condition or incomplete. SECOND STAT: Total F/N VGI percentage of all Public, Staff and Student Co-Auditing. ETHICS It is an Ethics offense to count or use public stats for staff or crew or to add staff or crew stats to public paid completions. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1973, 1975 by L. Ron Hubbard ALL RIGHTS RESERVED This is Reproduced and issued to you by The Publications Organization, U. S. ===================== 013. HCO PL 25 Sept 1974 Reduction of Refunds C/Ss and Overload HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO POLICY LETTER OF 25 SEPTEMBER 1974 All Execs All Tech and Qual Divs URGENT - IMPORTANT REDUCTION OF REFUNDS C/Ses AND OVERLOAD When a C/S is overloaded, he is a potential cause of OUT TECH. He may try to make up time by not reading worksheets of Auditors, by failing to do Folder Error Summaries, by not taking time to write Cramming Orders and neglecting other C/S duties. Recent evaluation has shown that OVERLOADED C/Ses CAN BE THE REASON FOR A HUGE REFUND RATIO IN THE ORG'S GI-CGI. Any non-tech person such as the Ethics Officer can tell at once when a C/S is either not working or overloaded. THE HANDWRITING IN THE WORKSHEETS CAN'T BE READ, WORDS ARE NOT CLARIFIED IN RED, NO FESes ARE SEEN IN FOLDERS AND NO CRAMMING ORDERS EXIST TO MAKE AUDITORS DO HANDWRITING DRILLS TO WRITE FAST AND WELL. Proper C/S posting was piloted by me on Flag years ago. The existing technical executives failed to export it to orgs. The irreducible minimum C/S postings are: SENIOR C/S who handles bugged cases and very upper level actions and keeps the other C/Ses functioning well. He is the highest classed C/S in the org. He is responsible for proper handling and results on all cases. (This is a hat I usually wore in an area.) EXPANDED DIANETIC C/S who does only Expanded Dianetics. GRADE C/S who C/Ses Grade pcs. DIANETIC C/S or C/Ses who handle all routine C/Sing of Dianetics including Drug Rundowns. There are several other C/S posts. In AOs additionally there are Solo C/Ses. In Saint Hills there are Power (Class VII) C/Ses. As an org expands it can have additional types of C/Ses. Some of these are: REVIEW C/S who reviews tech case failures, taking this load off the Senior C/S. STAFF CASES C/S who C/Ses for audited staff. HCO PL 25,9.74 - 2 - STUDENT AUDITING C/S who C/Ses student sessions, AO REVIEW C/S who C/Ses for fast reviews on Adv Cse students. CO-AUDIT C/S where a Co-Audit exists separate from HGC lines. WHAT IS OVERLOAD? When a C/S can't read every worksheet and study and program every case he has, due to time, he is overloaded. WASTED C/Ses To get a Class VI or even a Class IV to C/S lower action folders is a waste of C/Ses since it is easy to train Dianetic C/Ses. SUMMARY TRAIN AMD POST enough C/Ses and watch the GI go up and refunds go down. It is not enough just to get Auditors and more and more Auditors. DON'T OVERLOAD C/Ses. GET MORE OF THEM! L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1974 by L. Ron Hubbard ALL RIGHTS RESERVED this a Reproduced and issued to you by The publications Organization U.S. ===================== 014. HCOB 31 Aug 1974 C/S Series 93 New Grade Chart HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HC0 BULLETIN OF 31 AUSUST 1974 Tech Secs C/Ses Auditors URGENT Registrars C/S Series 93 NEW GRADE CHART The "NEW" thing to do ie the Grade Chart. Everything you are doing should contribute to getting the pc up the Bridge. THIS is the Bridge. There is a new Grade Chart being prepared which has some changes in it, based on recent discoveries. It is urgent that you know of these in advance* DRUG RUNDOWN The effects of an omitted or incomplete Drug RD are severe enough to deny a person any lasting case gain. This is covered in HCOB 31 May 74 Unhandled Drugs and Ethics. Some orgs have taken this HCOB so literally however, that they have taken pcs off Adv Cses Grades, refused to do Assists on ill pcs and some showed pcs the HCOB and invaled their gains. This was not the intention of the HCOB. The C/S Series remain valid. The Drug RD belongs on the Grade Chart after Life Repair. A Drug RD cannot be done over out ruds and a Life Repair may be necessary to get in a pc's ruds. Life Repair is not a prerequisite for the Drug RD, however, and if done is not to be dragged out intensive after intensive. In some cases a pc could not complete Life Repair without a Drug RD. Following the Drug RD is ARC S/W, then the rest of Dianetics to completion. EXPANDED DIANETICS Ex Dn by the way belongs after Grade IV Expanded. Some pcs R/S and have Evil Purposes to do others in. But no Grade 0 or Grade I or Grade II. What others? Martians? "Got to secretly do everybody in" probably applies to Apeville some long date ago and he's never come up to PT. The answer is to bring the pc up the Grade Chart to Expanded Grade IV then do his Ex Dn. HCOB 31.8.74 - 2 - The prerequisites for Ex Dn are covered on HCOB 23 April 74 Ex to Series 22 Expanded Dianetics Requisites. Add to that Expanded Grades up to IV and you have it. GRADE II Some, orgs specialize in Grade II, especially on org ataff. The pc is always getting Integrity Processing or his 0/Ws pulled on so and so. If you look on the Grade Chart you will find Withholds and Overts are Grade TWO. Below Grade TWO lies Grade I (Problems) and Grade Zero (Communications). And below that is Dianetics and at the bottom end of Dianetics is the Drug Handling. Now how do you expect a fellow who has unhandled drugs (or omitted drug items because of "no interest") to even know (no Grade 0) that other people are around or that (Grade I) he is caved in with problems he's never cognited on? And he's supposed to have enough responsibility to answer up on Grade II? With real overts and withholds? This does not mean you must never Sec Check. It does mean that Sec Checks are no substitute for auditing or guarantee of innocence. Grades are Grades and the Grade Chart sequence is correct. SOLO SET-UPS Set-ups for Solo are fully covered on HCOB 8 Jan 72R Revised 8 July 74 Solo C/S Series 11R. This will be included as part of Solo on the Grade Chart as it is a vital step. PCS won't make it on Solo if they aren't set up. FULL LIST Here's the full list of Grades showing where the various RDs now offered fit. GROUP PROCESSING - not mandatory or a prerequisite. LIFE REPAIR - As needed but not prerequisite for Drug RD. To get ruds in on Life. DRUG RD, means: TRs 0-4, 6-9 - mandatory for a Druggie currently on Drugs, FLAT. Full C/S-1 - where not done. To fully educate pc. Objectives - Full battery to full EPs per basic books and early HCOBs on them. HCOB 31.8.74 - 3 - Class VIII Drug Handling - List and rehab all drugs, 3 way Recalls, Secondaries and Engrams of Taking and Giving Drugs. AESPs on each reading Drug - Listed separately and handled with R3R, each drug to full F/N assessment of Drug List. "No Interest" Drug Items - All reading ones run where they exist. Prior Assessment - AESPs listed separately and run R3R, prior to first drug or alcohol taken. ARC S/W EXPANDED. DIANETICS, means: C/S 54 - Complete handling of PC Assessment Form begun with Drug RD. Health Form - Fully handled to full F/N Assessment. EXPANDED GRADE 0 - As issued. EXPANDED GRADE I - As issued. EXPANDED GRADE II - As issued, including Integrity Processing. EXPANDED GRADE III - As issued. EXPANDED GRADE IV - As issued. EX DN - Not mandatory except where pc is a low OCA, an R/Ser (2%), chronically ill or psycho. Means: Set-Ups - Per HCOB 23 April 74 Ex Dn Series 22. Introspection RD - Where pc ill, introverted or in a psychotic break. R3R all E. Purps. OCA Left Hand Side Handling - As issued. OCA Right Hand Side Handling - As issued, with PTS RD as necessary. POWER PROCESSING GRADES V & VA - Only prerequisites are Drug RD and Grade IV. SOLO GRADE VI, means: Solo Set-Ups - Done at SH or AO per Solo C/S Series 11R. Solo Auditor's Course. Solo Audit Grade VI materials. CLEARING COURSE OT I OT II OT III OT VII PROCESSES OT III EXPANDED OT IV OT V HCOB 31.8.74 - 4 - OT VI FULL OT VII VERIFICATION OT VIII - When issued. PROGRAMMING The C/S Series, especially the early HCOBs, numbers 1-13R, fully cover the use of the Grade Chart in programming. THE GRADE CHART IS THE BASIC PROGRAMME OF A PC. This datum has been neglected in some orgs, who have specialized in the new RDs developed since '71. With refinement of repair and corrective actions and the release of new RDs, some may have forgotten that repair is only done to get off the overwhelm so that you can put the pc back on the Grade Chart. SUMMARY I thought I'd better fill you in on these change's and how the new Grade Chart lines up. Make full use of this Chart with C/S Series programming tech in and you pcs will fly. Here's to lots of case gain and rave success stories. L. RON HUBBARD FOUNDER LRH:nt:rs Copyright (c) 1974 by L. Ron Hubbard ALL RIGHTS RESERVED