[continued from 04a] HCO B 23.8.71 - 7 - Soaring TA = 0/R or Protest = find which and handle. Such an 0/R is usually by rehab. Dope off = lack of sleep or BP F/N = check on sleep, or Rehab F/H. No interest = no interest in first place or out ruds = check for interest or put in ruds. List goes wrong = BPC = handle or do L4A or any L4 at once. Ruds won't fly = some other error = assess GF and handle. The auditor has no business trying to do the C/S given when it collides with and isn't designed to handle any of the above. If the previous session disclosed such an error and this session C/S was designed to handle and doesn't, the auditor should end off and the next C/S should be "2 way comm for data". CASE NOT HANDLED When the auditor or the Examiner collides with a pc who is asserting his case has not been handled, there should not be a new set of actions based on little data but the auditor should end off and the C/S should order a "2 way comm on what hasn't been been handled". The auditor should not at once take this up as part of any other C/S. In other words an auditor doesn't change the C/S to a 2 way comm on something not called for by C/S. MAJOR ACTIONS An auditor should never begin a major action on a case that is not "set up" for it. As this can occur during a session it is vital to understand the rule and follow it. Otherwise a case can be bogged right down and will be hard to salvage as now a new action to repair has been added to an unrepaired action. Now, if the auditor starts a major action on a case not "set up" we get 2 things to repair where we only had 1 as the major action won't work either. Repair = patching up past auditing or recent life errors. This is done by Prepared lists or completing the chain or correcting lists or even 2 way comm or prepchecks on auditors, sessions, etc. Rudiments = setting the case up for the session action, This includes ARC Brks, PTPs, W/Hs, GF or 0/R listing or any prepared list (such as L1B, etc.). HCO B 23.8.71 - 8 - Set UP = getting an F/N showing and VGIs before starting any major action- It means just that - an F/N and VGIs before starting any major act ion. Such may require a repair action and rudiments as well, Major Action = any - but any - action designed to change a case or general considerations or handle continual illness or improve ability. This means a Process or even a series of processes like 5 flows. It doesn't mean a grade. It is any process the case hasn't had. Grade = a series of processes culminating in an exact ability attained, examined and attested to by the pc. Program = any series of actions designed by a C/S to bring about definite results in a pc. A program usually includes several sessions. The vast bulk of auditing errors come about because C/Ses and auditors seek to use a Major Action to repair a case. It is a responsibility of an auditor to reject a C/S which seeks to use one or more major actions to repair a case that isn't running well. The auditor must understand this completely. He can be made to accept a wrong C/S for the pc and even more importantly can in his own session make the error and mess up the case. Example? Pc has not been running well (no real TA or had a grumpy Exam report). Auditor sees C/S has ordered a major action, not a repair by prepared lists, rude, etc. The auditor must reject the C/S as he will be made to fail in session by it. Example: Auditor gets a C/S, "(l) Fly a rud; (2) Assess LX1; (3) Run 5 way recall, 5 way secondaries, 5 way engrams on all //X items". The auditor can't get a rud to fly. Does the LX5. In other words he flunks by failing to SET UP the case. It could also go this way. Auditor can't get a rud to fly, does a GF, gets no F/N, He MUST NOT begin a major action but MUST end off right there. It is fatal to begin any new process on the case designed to change the case if the case is not F/N VGIs. The pc who starts processing for the first time and is surely not F/N VGIs must .be set up by repair actions! Simple rudiments, life ruds, 0/R list on life, even assessing prepared lists on life, these are repair actions. The pc will sooner or later begin to fly; Now at session start you put in a rud, get F/N VGIs and CAN start major actions. So the auditor has a responsibility not to be led up a garden path by a C/S which orders a major action on a pc who isn't repaired or by not being able in session to get an F/N VGIs by repair. HCO B 23.8.71 - 9 - The only exceptions are a touch assist or life ruds or the Dianetic assist all on a temporarily sick pc. But that's repair isn't it? PROGRAM VIOLATIONS When an auditor receives a C/S and sees that it violates the pc's program he should reject it. The pc, let us say, is supposed to finish his Dianetic Triples but is suddenly being given a Group Engrain Intensive. That violates the program and also the grade. If the pc is running badly, a repair should be ordered. If not, the program should be completed. Examples An effort is being made to get the pc to go backtrack. This is a program containing several major actions which probably consists of several sessions. Before this program is complete and before the pc has gone backtrack, the C/S orders "(l) Fly a rud, (2) 3 S&Ds". The auditor should recognize in 3 S&Ds a major action being run into the middle of a program and reject it. The correct action is of course the next backtrack process. GRADE VIOLATIONS A pc who is on a grade and hasn't attained it yet must not be given major actions not part of that grade. Example: Pc is on Grade I. C/S orders a list having to do with drinking. It is not a process on that Grade. It could be done after Grade I is attained and before Grade II is begun. The C/S is incorrect and should not be accepted. ABILIY ATTAINED Now and then before the full major action is complete or before all the grade processes are run, the pc will attain the ability of the grade or the end phenomena of the action. This is particularly true of valence shifters or Interiorization Rundowns and can happen in grades. The auditor should recognize it and with the F/N VGIs always present at such moments, end off. I know of one case who had a huge cog about Interiorization on Flow 1 Engrams and was pushed by both C/S and auditor to do Flows 2 and 3 who boiled so badly that it took a long while - weeks - to straighten the case out. The ability itself gets invalidated by pushing on. On the other hand this should never be taken as an excuse. HOC B 23.8.71 - 10 - "I think he cogged to himself so we ended off" It must be a real "What do you know!" sort of out-loud cog with a big F/N and VVGIs and directly on the subject to end off a major action or a program or a grade before its actions are all audited. REVIEWING REVIEWS An auditor who gets a C/S or an order to repair a case that is running well should reject doing the action. I have seen a, case ordered to repair who had Ext Full Perception Doing great. The repair bogged the case. The case then got running well again but a second C/S ordered a new repair which of course bogged it. Then major actions were done. The case was again repaired and rehabbed and became ok. Three times the auditor should have said NO. FALSE REPORTS The vilest trick that can be played on a pc is for an auditor to falsify an auditing report. It may be thought to be "good Pubic Relations" (good PR) for the. auditor with the C/S. Actually it buries an error and puts the pc at risk. INTEGRITY is a hallmark of Dianetics and Scientology. Just because psychiatrists were dishonest is no reason for auditors to be. The results are there to be gotten. False Reports like false attests recoil and badly on both the auditor and pc. OVERTS ON PCS When an auditor finds himself being nattery or critical of his pcs he should get his withholds on pcs pulled and overts on them off. An auditor who goes sad is auditing pcs over his own ARC Break. An auditor worried about his pc is working over a Problem. Getting one's ruds in on pcs or C/Ses or the org can bring new zest to life. AUDITORS DON'T HAVE CASES In the chair no auditor has a case. If breath shows on a mirror held to his face he can audit. HOO B 23.8.71 - 11 - faint afterwards if you must but see that the pc gets to the, examiner with his F/N. Then get yourself handled. "WHAT HE DID WRONG" An auditor has a right to know what he did wrong in the session that went wrong. Most often a sour session occurs only when the rules and data in this HCO B have been violated. But an auditor's TRs can go out or his listing and nulling is in error. After a session that went wrong somebody else (not the auditor) should ask the pc what the auditor did. This some- times spots a false auditing report. But it also sometimes is a false report by the pc. In any event, the auditor has a right to know. Then he can either correct his auditing or his know-how or he can advise the C/S the pc's report is untrue and better repair can be done on the pc. Savage action against an auditor is almost never called for. He was trying to help. Some people are hard to help. Not only does an auditor have the right to be told what was wrong but he must be given the exact HCO B, date and title, that he violated. Never take a verbal or written correction that is not in an HCO B or tape. Don't be party to a "hidden data line." that doesn't exist. "You ruined the pc!" is not a valid statement. "You violated HCO B ____ page __" is the charge. No auditor may be disciplined for asking "May I please have the tape or HC0 B that was violated so I can read it or go to cramming." If it isn't on a tape, a. book or an HCO B IT IS NOT TRUE and no auditor has to accept any criticism that is not based on the, actual source data. "If it isn't written it isn't true" is the best defense and the best way to improve your tech. These are the rights of the auditor with relation to a C/S. They are all technical rights based on sound principles. An auditor should know them and use them. HCO B 23.8.71 - 12 - If an auditor stands on these rights and gets beaten down he should put all the facts before his nearest OTL or SO ship as something would be very wrong somewhere. Auditing is a happy business - when it is done right. L. RON HUBBARD FOUNDER LRH:nt Copyright ($) 1971 by L. Ron Hubbard ALL RIGHTS RESERVED ===================== 020. HCOB 12 June 1970 C/S Series 2 Programming of Cases HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo HCO BULLETIN OF 12 JUNE 1970 C/S Series No. 2 (C/S Series No. 1 is Auditors Rights, HCO B 24 May 70, not so marked.) PROGRAMMING OF CASES Every action taken on a Case by a CASE SUPERVISOR (or an auditor doing his own C/S actions) should be part of a definite outlined PROGRAM for that case. PROGRAM Definition - A program is defined as the sequence of actions session by session to be undertaken on a case by the C/S in his directions to the auditor or auditors auditing the case. The master program for every case is given on the Classification and Gradation Chart issued from time to time. The earliest of these charts was 1965 followed by 1st December 1966 followed by 1st January 1968 followed by 1st December 1969. The reissues of the Chart are done to improve the communication of the data on the chart. The program factor has not much changed since its earliest issue. Tapes about this chart were made for the SHSBC at its first issue and of course remain valid. The processes called for on the Chart, are all part of the SHSBC or for upper levels part of the SH and AO Confidential materials. From time to time they are reissued but they remain standard and have been so since the first issue of the Chart. The Chart and its materials have now and again been neglected or disregarded and THE NEGLECT HAS RESULTED IN FIELD FLAP'S AND DOWN STATS. Omitting this gradient of processes not only stalls cases but results in a case manifesting out-grade phenomena. A pc must attain the full ability noted on the Chart before going up to the next level of the chart. Telling the pc he has made it is of course evaluation. The outnesses which have occurred surrounding this Chart are hard to believe. They consist of total abandonment of the Chart, degrading and losing all its lower grade processes, feeding a pc at Dianetic level data at Class VI and telling him, who has not made Dianetics yet, he is now Clear, cutting down all processes from the chart bottom up to IV to be able to do them in. 2 1/2 minutes, neglecting all levels up to OT V and then trying to put in a few lower grades and sending on to OT VI, having the pc after one trivial session attest all abilities at once and many other errors. HCO B 12.6.70. - 2 - This is crazy driving. If a bus were driven along a road this way it would soon by wrecked and back where it started but in an ash heap. Genius in C/Sing is normally required only when some former driver wrecked the thing instead of driving it right in the first place. To Case Supervise one has to accept the following facts: 1. Dianetics and Scientology work. 2. The subjects are serious subjects not experimental toys. 3. The basics and fundamentals are stated early in the period of development and have not changed. 4. The "newest and latest" is usually a recovery of basics and better statements of them. 5. The purpose of the subject has not altered and continues to be the attainment of ability and freedom for the individual. 6. That things which were true early in the subjects are sti21 true. 7. That the mind responds on a gradient of improvement not suddenly like a bomb explosion. 8. That the Classification and Gradation Chart and all its processes and steps IS the basic program of any case. 9. That all other programs are efforts to get the pc or Pre OT back on the basic program. 10. That there is no hidden data line and that the materials and procedures are refined mainly to facilitate use and communication of them. 11. That auditing is for the pc, not the org or the auditor. 12. That major processes are done to improve the case. 13. That repair is undertaken to eradicate errors made in auditing or the environment which impede the use of major processes. 14. That a case has to be programmed by the C/S to get it advancing as it should have been in the first place on the Classification and Gradation Chart. 15. That a C/S is not being called upon to develop a new Chart for the case but only to get the case back on the basic chart and get it done. 3 PROGRAMS There are then 3 types-of Programs: HCO B 12.6.70. - 3 - 1. THE program laid out in the Classification and Gradation Chart. (Called The Basic Program.) 2. Repair Programs to eradicate case mishandling by current life or auditing errors. (Called a Set-Up Program.) 3. Major actions to be undertaken to get the case back on the Class Chart from wherever he has erroneously gotten to on it. (Called a Return Program.) It has been a very common C/S action to disperse away from a program laid out. This has been happening ever since the first issue of the Class Chart and has been a principle source of trouble for C/Ses. This happens in several ways: 1. Not knowing the importance of the Class Chart. 2. Not knowing a basics, 3. Falling for SP propaganda that "we don't use that now", "this material is old", "it's only background data," etc. that deteriorates what one does know and could, use. 4. Failure of auditors to give good sessions and do the Usual required in a session. 5. Abandonment of the C/Ses. own Repair or Return program - usually because of false auditor reports or operating on insufficient data from the pc. The correct way to go about all this is to: A. Repair the case thoroughly with minor actions like GFs, prepared lists, ruds, two way comm. B. Acquire adequate data on the pc. C. Complete any C/S Return program begun. D. Get the pc back on the Class Chart without any processes of the grade skipped. E. Run the case on the Class Chart. F. Repair any departures or errors made in life or auditing. G. Get the pc back on the Class Chart. DISPERSAL Not following any program is a complete exercise in non-sequitur (mean one step does not follow the last but is different and unrelated). HCO B 12.6.70. - 4 - In giving a pc process after process that are not related to each other and follow no Repair Program or Return Program is non-sequitur in the extreme. If processes were remarks one would get a sequence of processes given the pc sounding like this. "The submarine just went by so we will order a hundred tons of bread. There wasn't any beer so birds are seldom seen. The dance was very fast so we fixed the carburator. He has very long hair so we decorated his father's tomb." "Give pc Scn Triples then do his Dianetics then fix up his hidden standard"! would be a series of crazy non-sequitur C/Ses. Nothing is connected to or proceeds from anything. That would be a dispersed program for sure. It actually happens horribly enough. Study a Class Chart and then look through some old folders. At once, the sequence of processes ordered sounds like "the submarine just went by so order a hundred tons of bread". Such C/Sing has no cause and effect in it, A person totally ignorant of basic cause and effect gets "Pc nattery, Run Dianetics". "PC'S case not advancing Do Grade O." The cause of the pc condition is not understood A nattery pc has withholds. A case not advancing has problems. That's real actual basic tech (see Auditors Rights HCO B for the table). This data is over 15 years old at this writing, ie part of proper Academy courses and the SBSBC and is even in Class VIII materials. The reasons for the pc's behavior or trouble are not mysterious reasons never revealed. They are all very well given in course materials. Here is an actual case, a folder I examined of a pc who is now in trouble and needing a, repair and return program. Pc was an accident prone (person who is apparently dedicated to having accidents). Very low aptitude score (about 50). Had been skipped over almost the entire Class Chart and given Power. To handle accident proneness was given CCHs. This cured it. Had exteriorized so was given Interiorization Rundown without a 2 way Comm session. Pc subsequently developed bad somatics. (Dianetics was never flattened or completed.) A quarter of an inch of Examiners reports wherein the pc was asking for help or medicine to get rid of somatics was then put one by one into the folder. Despite this the "C/S" saw "Va" on the pc's folder and ordered R6EW. More Examiners calls collected. HCO B 12.6.70. - 5 - The pc ran one item, making one mark on a worksheet and attested R6EW. More Examiners reports collected, pc reporting self ill. "C/S" seeing R6EW attested ordered pc to Clearing Course. Pc did one brief session attested Clear. More Examiners Reports into folder pc in pain and now in Ethics trouble. "C/S" ordered pc to OT I. Pc spent 35 minutes on OT I in terror of it, hastily attested, had 5 accidents in 3 days. Folder sent to me as a "baffling case". So the correct actions now have to be taken. 1. Repair pc with every list known to Man or Beast to get off BPC, collected in these overwhelming levels. 2. Repair pc in errors in current life. 3. Return Program the pc by running simple things, 2 way comm, to give pc some wins in actual case gain by maybe handling by 2 way comm minor this life or childhood upsets with family, maybe putting in ruds on some early subject that turns up. 4. Put pc back on the Class Chart TO COMPLETE THE INCOMPLETE GRADE (Dianetics) to its full end phenomena, as per Class Chart. 5. Bring the pc on up the Class Chart using all processes for each grade and honestly attesting each grade in turn. It's all a shame because the pc had a lose on status. She wanted to be Clear and OT, was actually on it and never walked up the stairs to get to it. PROGRAM NECESSITY One can see from all this the NECESSITY of working by program on a case. Even when one starts an honest program for the case one can get thrown off of it and begin to do something else. If the pc goes exterior, of course, one has to handle by Interioriz- ation Rundown before the case can be audited at all. But that's no reason to then skip all the grades! A pc can go exterior at any point. HCO B 12.6.70. - 6 - Thus it must be handled when it occurs. But that does not mean anything happened to one's program or the Class Chart. Exterior or Interior, a pc unflat in Dianetics (not attained the ability marked on the Class Chart) is unflat on Dianetics! And a pc who is unflat on Dianetics will have out lower grades. Jumping processes on the Class Chart set the pc up to fall on his head later. An "OT VI with problems" is really just an unflat Grade I. And until Grade I is flattened to permanent Ability Attained on the Class Chart, he remains an unflat Grade I. A C/S who gets wound up in this sort of skipped everything and made nothing of course has an awful mess on his hands. He can feel as lost as Hansel or Gretal. But waiting to get covered up by leaves is for the birds. If one finds the pc off the road, the thing to do is return the pc to the road at the point he didn't walk it AMD THERE ABE NO SHORTCUTS FOR THE MIND. The utter despair and insane barbarism psychiatry descended into was patient lost, psychiatrist lost, patient crazy, psychiatrist into insane sadism. So maybe the first lesson a C/S really has to learn is THERE IS A KNOWN ROAD OUT. There is no shortcut it has to be walked every inch of it. And therefore the greatest enemy of the C/S is the SP who says "that's all old" "we don't use that now" "that's just background data" and thereby obscures the actual road. And another enemy is the pc who screamingly demands to be put up to Clear at once so he won't have this awful headache ! STEADY ON Thus the measures a C/S takes to hold a steady course will profit him greatly in the end with good solid gains for the pc. As the pc should no longer be a total humanoid by Class IV the lower grade gains are the most important of all. A C/S who puts a Class Chart into every folder he handles is doing a wise thing. Even if it's big, clumsy, hard to handle, it is at least thorough. If on it he marks in red things the pc has gotten to falsely and if in green things the pc made from the bottom walking an honest road, he HCO B 12.6.70. - 7 - knows where he is at! Seeing the whole training cycle half of the chart continue blank means that much more ignorance and trouble for the pc in making his gains stably. If the C/S put his Repair Program on a Red sheet in the folder and dated it out session by session to be audited until it was DONE and all flubs made in doing it also marked in and repaired, the C/S wouldn't lose his place in the book. For a red sheet stands out in amongst other folder papers. A red sheet with a "folder error summary" on one side of it and the C/Ses Repair Pgm on the other keeps the pc's progress located. When that red sheet is done it should he signed by the C/S as DONE which retires all errors to that point. A bright blue sheet giving the C/S RETURN PGM properly dated also gives one a chance to not get steered off. A new Red Repair Pgm sheet fixing up errors occurring in doing the blue sheet can be pushed into the folder but the Blue sheet can be resumed again. The Blue Sheet completed should find the pc back on the Class Chart. A list of processes run tallied up by the auditor each session keeps the C/S from repeating a process and gives him the Dn items used singly to be done triple, While all this Admin may seem time consuming, lack of it mounts up into valuable AUDITOR TIME being thrown away. C/Sing is a road. It has milestones. When the pc didn't pass one honestly he got lost. There's no reason for pc, auditor and C/S to all get lost. The C/S has an exact road to hold to, return to and repairs to get done so the pc can get moving on the Return Pgm and the Class Chart which IS the road. It took too many trillions to find this road for it to be neglected. For if the C/S neglects it people won't arrive anywhere but lost as well. The right idea is the road. LRH:kjn Copyright ($) 1970 by L. Ron Hubbard ALL RIGHTS RESERVED L. RON HUBBARD FOUNDER