CLASS VIII CONFIDENTIAL COURSE PACK PART 10/16 CLASS VIII COURSE PACK CONTENTS: Part 10 104. HCOB 1 OCT 63 HOW TO GET TONE ARM ACTION 105. HCOB 21 JAN 64 METER LEVEL WARNING - HOW TO KILL A PC IN LEVEL 5 106. HCOB 24 MAY 62 Q AND A 107. HCOB 7 APR 64 ALL LEVELS - Q AND A 108. HCOB 24 AUG 64 SESSION MUST-NOTS 109. HCOPL27 MAY 65 PROCESSING 110. HCOPL 1 JUL 65 COMM CYCLE ADDITIVES 111. HCOB 3 AUG 65 AUDITING GOOFS - BLOWDOWN INTERRUPTION 112. HCOB 21 SEP 65 OUT TECH 113. HCOB 12 FEB 66 THE "DANGEROUS AUDITOR" 114. HCOB 11 FEB 66 FREE NEEDLES, HOW TO GET THEM ON A PC 115. HCOB 26 AUG 68 REHAB & CORRECTION 116. HCOB 11 AUG 78 MODEL SESSION 117. HCOB 9 AUG 78 CLEARING COMMANDS 118. HCOB 24 JUL 64 TA COUNTERS, USE OF 119. HCOB 2 JAN 67 DATING - FORBIDDEN WORDS ************************************************** CLASS VIII CONFIDENTIAL COURSE PACK PART 10/16 ************************************************** 104. HCOB 1 OCT 63 HOW TO GET TONE ARM ACTION HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 1 OCTOBER 1963 Franchise CenOCon SCIENTOLOGY ALL HOW TO GET TONE ARM ACTION The most vital necessity of auditing at any level of Scientology is to get Tone Arm Action Not to worry the pc about it but just to get TA action. Not to find something that will get future TA. But just to get TA NOW. Many auditors are still measuring their successes by things found or accomplished in the session. Though this is important too (mainly at Level IV), it is secondary to Tone Arm Action. l. Get good Tone Arm Action. 2. Get things done in the session to increase Tone Arm Action. NEW DATA ON THE E-METER The most elementary error in trying to get Tone Arm action is, of course, found under the fundamentals of auditing-reading an E-Meter. This point is so easily skipped over and seems so obvious that auditors routinely miss it. Until they understand this one point, an auditor will continue to get minimal TA and be content with 15 Divisions down per session-which in my book isn't TA but a meter stuck most of the session. There is something to know about meter reading and getting TA. Until this is known nothing else can be known. TONE ARM ASSESSMENT The Tone Arm provides assessment actions. Like the needle reacts on list items, so does the Tone Arm react on things that will give TA. You don't usually needle assess in doing Levels I, II and III. You Tone Arm Assess. The Rule is: THAT WHICH MOVES THE TONE ARM DOWN WILL GIVE TONE ARM ACTION. Conversely, another rule: THAT WHICH MOVES ONLY THE NEEDLE SELDOM GIVES GOOD TA. So for Levels I, II and III (and not LEVEL IV) you can actually paste a paper over the needle dial, leaving only the bottom of the needle shaft visible so the TA can be set by it and do all assessments needed with the Tone Arm. If the TA moves on a subject then that subject will produce TA if the pc is permitted to talk about it (Itsa it). Almost all auditors, when the Itsa Line first came out, tried only to find FUTURE TA ACTION and never took any PRESENT TA ACTION. The result was continuous listing of problems and needle nulling in an endless search to find something that "would produce TA action". They looked frantically all around to find some subject that would produce TA action and never looked at the Tone Arm of their meter or tried to find what was moving it NOW. This seems almost a foolish thing to stress-that what is producing TA will produce TA. But it is the first lesson to learn. And it takes a lot of learning. Auditors also went frantic trying to understand what an ITSA LINE was. They thought it was a Comm Line. Or part of the CCHs or almost anything but what it is. It is too simple. There are two things of great importance in an auditing cycle. One is the Whatsit, the other is the Itsa. Confuse them and you get no TA. If the auditor puts in the Itsa and the preclear the Whatsit, the result is no TA. The auditor puts in the Whatsit and the pc the Itsa, always. It is so easy to reverse the role in auditing that most auditors do it at first. The preclear is very willing to talk about his difficulties, problems and confusions. The auditor is so willing to Itsa (discover) what is troubling the preclear that an auditor, green in this, will then work, work, work to try to Itsa something "that will give the pc TA", that he causes the pc to "Whatsit Whatsit Whatsit that's wrong with me". Listing is not really good Itsa-ing; it's Whatsit-ing as the pc is in the mood "Is it this? Is it that?" even when "solutions" are being listed for assessment. The result is poor TA. TA comes from the pc saying, "It IS" not "Is it?" Examples of Whatsit and Itsa: Auditor: "What's here?" (Whatsit) Pc: "An auditor, a preclear, a meter." (Itsa) Itsa really isn't even a Comm Line. It's what travels on a Comm Line from the pc to the auditor, if that which travels is saying with certainty "It IS". I can sit down with a pc and meter, put in about three minutes "assessing" by Tone Arm Action and using only R1C get 35 Divisions of TA in 2% hours with no more work than writing down TA reads and my auditor's report. Why? Because the pc is not being stopped from Itsa-ing and because I don't lead the pc into Whatsit-ing. And also because I don't think auditing is complicated. Tone Arm Action has to have been prevented if it didn't occur. Example: An auditor, noting a Whatsit moved the TA, every time, promptly changed the Whatsit to a different Whatsit. Actually happened. Yet in being asked what he was doing in session said: "I ask the pc for a problem he has had and every time he comes up with one I ask for solutions to it." He didn't add that he frantically changed the Whatsit each time the TA started to move. Result-9 Divisions of TA in 21/2 hours, pc laden with by-passed charge. If he had only done what he said he had he would have had TA. If it didn't occur, Tone Arm Action has to have been prevented! It doesn't just "not occur". In confirmation of auditors being too anxious to get in the Itsa Line themselves and not let the pc is the fad of using the meter as a Ouija Board. The auditor asks it questions continually and never asks the pc. Up the spout go Divisions of TA. "Is this Item a terminal?" the auditor asks the meter. Why not ask the pc? If you ask the pc, you get an Itsa, "No, I think it's an oppterm because ....." and the TA moves. Now to give you some idea of how crazy simple it is to get in an Itsa Line on the pc, try this: Start the session and just sit back and look at the pc. Don't say anything. Just sit there looking at the pc. The pc will of course start talking. And if you just nod now and then and keep your auditor's report going unobtrusively so as not to cut the Itsa, you'll have a talking pc and most of the time good TA. At the end of 21/2 hours, end the session. Add up the TA you've gotten and you will usually find that it was far more than in previous sessions. TA action, if absent, had to be prevented! It doesn't just fail to occur. But this is not just a stunt. It is a vital and valuable rule in getting TA. RULE: A SILENT AUDITOR INVITES ITSA. This is not all good, however. In doing R4 work or R3R or R4N the silent auditor lets the pc Itsa all over the whole track and causes Over-Restimulation which locks up the TA. But in lower levels of auditing, inviting an Itsa with silence is an ordinary action. In Scientology Levels I, II and III the auditor is usually silent much longer, proportionally, in the session, than he or she is talking-about 100 of silence to 1 of talking. As soon as you get into Level IV auditing however, on the pc's actual GPMs, the auditor has to be crisp and busy to get TA and a silent, idle auditor can mess up the pc and get very little TA. This is all under "controlling the pc's attention". Each level of auditing controls the pc's attention a little more than the last and the leap from Level III to IV is huge. Level I hardly controls at all. The rule above about the silent auditor is employed to the full. Level II takes the pc's life and livingness goals (or session goals) for the pc to Itsa and lets the pc roll, the auditor intruding only to keep the pc giving solutions, attempts, dones, decisions about his life and livingness or session goals rather than difficulties, problems and natter about them. Level III adds the rapid search (by TA assessment) for the service facsimile (maybe 20 minutes out of 2l/2 hours) and then guides the preclear into it with R3SC processes. The rule here is that if the thing found that moved the TA wouldn't make others wrong but would make the pc wrong, then it is an oppterm lock and one Prepchecks it. (The two top RIs of the pc's PT GPM is the service facsimile. One is a terminal, the pc's, and the other is an oppterm. They each have thousands of lock RIs. Any pair of lock RIs counts as a service facsimile, giving TA.) A good slow Prepcheck but still a Prepcheck. Whether running Right-Wrong-Dominate-Survive, (R3SC) or Prepchecking (the only 2 processes used) one lets the pc really answer before acking. One question may get 50 answers! Which is One Whatsit from the auditor gets 50 Itsas from the pc. Level IV auditing finds the auditor smoothly letting the pc Itsa RIs and lists but the auditor going at it like a small steam engine finding RIs, RIs, RIs, Goals, RIs, RIs, RIs. For the total TA in an R4 session only is proportional to the number of RIs found without goofs, wrong goals or other errors which rob TA action. So the higher the level the more control of the pc's attention. But in the lower levels, as you go back down, the processes used require less and less control, less auditor action to get TA. The Level is designed to give TA at that level of control. And if the auditor actions get busier than called for in the lower levels the TA is cut down per session. OVER-RESTIMULATION As will be found in another HCO Bulletin and in the lectures of summer and autumn of 1963, the thing that seizes a TA up is Over-Restimulation. THE RULE IS: THE LESS ACTIVE THE TA THE MORE OVER-RESTIMULATION IS PRESENT. (THOUGH RESTIMULATION CAN ALSO BE ABSENT.) Therefore an auditor auditing a pc whose TA action is low (below 20 TA Divisions down for a 2l/2 hour session) must be careful not to over-restimulate the pc (or to gently restimulate the pc). This is true of all levels. At Level IV this becomes: don't find that next goal, bleed the GPM you're working of all possible charge. And at Level III this becomes: don't find too many new Service Facs before you've bled the TA out of what you already have. And at Level II this becomes: don't fool about with a new illness until the pc feels the Lumbosis you started on is handled utterly. And at Level I this becomes: "Let the pc do the talking". Over-Restimulation is the auditor's most serious problem. Under-Restimulation is just an auditor not putting the pc's attention on anything. The sources of Restimulation are: 1. Life and Livingness Environment. This is the workaday world of the pc. The auditor handles this with Itsa or "Since Big Mid Ruds' and even by regulating or changing some of the pc's life by just telling the pc to not do this or that during an intensive or even making the pc change residence for a while if that's a source. This is subdivided into Past and Present. 2. The Session and its Environment. This is handled by Itsa-ing the subject of session environments and other ways. This is subdivided into Past and Present. 3. The Subject Matter of Scientology. This is done by assessing (by TA motion) the old Scientology List One and then Itsa-ing or Prepchecking what's found. 4. The Auditor. This is handled by What would you be willing to tell me, Who would you be willing to talk to. And other such things for the pc to Itsa. This is subdivided into Past and Present. 5. This Lifetime. This is handled by slow assessments and lots of Itsa on what's found whenever it is found to be moving the TA during slow assessment. (You don't null a list or claw through ten hours of listing and nulling to find something to Itsa at Levels I to III. You see what moves the TA and bleed it of Itsa right now. ) 6. Pc's Case. In Levels I to III this is only indirectly attacked as above. And in addition to the actions above, you can handle each one of these or what's found with a slow Prepcheck. LIST FOR ASSESSMENT Assess for TA motion the following list: The surroundings in which you live. The surroundings you used to live in. Our surroundings here. Past surroundings for auditing or treatment. Things connected with Scientology (Scientology List One). Myself as your auditor. Past auditors or practitioners. Your personal history in this lifetime. Goals you have set for yourself. Your case. At Level II one gets the pc to simply set Life and Livingness goals and goals for the session, or takes up these on old report forms and gets the decisions, actions, considerations, etc., on them as the Itsa, cleaning each one fairly well of TA. One usually takes the goal the pc seems most interested in (or has gone into apathy about) as it will be found to produce the most TA. Whatever you assess by Tone Arm, once you have it, get the TA out of it before you drop it. And don't cut the Itsa. MEASURE OF AUDITORS The skill of an auditor is directly measured by the amount of TA he or she can get. Pcs are not more difficult one than another. Any pc can be made to produce TA. But some auditors cut TA more than others. Also, in passing, an auditor can't falsify TA. It's written all over the pc after a session. Lots of TA = Bright pc. Small TA = Dull pc. And Body Motion doesn't count. Extreme Body Motion on some pcs can produce a division of TA! Some pcs try to squirm their way to clear! A good way to cure a TA conscious body-moving pc is to say, "I can't record TA caused while you're moving." As you may suspect, the pc's case doesn't do a great deal until run on R4 processes. But destimulation of the case can produce some astonishing changes in beingness. Key-out is the principal function of Levels I to III. But charge off a case is charge off. Unless destimulated a case can't get a rocket read or present the auditor with a valid goal. Levels I to III produce a Book One clear. Level R4 produces an O.T. But case conditioning (clearing) is necessary before R4 can be run. And an auditor who can't handle Levels I to III surely won't be able to handle the one-man band processes at Level IV. So get good on Levels I to III before you even study IV. THE FIRST THING TO LEARN By slow assessment is meant letting the pc Itsa while assessing. This consists of rapid auditor action, very crisp, to get something that moves the TA and then immediate shift into letting the pc Itsa during which be quiet! The slowness is overall action. It takes hours and hours to do an old preclear assessment form this way but the TA flies. The actual auditing in Level III looks like this-auditor going like mad over a list or form with an eye cocked on the TA. The first movement of the TA (not caused by body motion) the auditor goes a tiny bit further if that and then sits back and just looks at the pc. The pc comes out of it, sees the auditor waiting and starts talking. The auditor unobtrusively records the TA, sometimes nods. TA action dies down in a couple minutes or an hour. As soon as the TA looks like it hasn't got much more action in it the auditor sits up, lets the pc finish what he or she was saying and then gets busy busy again. But no action taken by the auditor cuts into the TA action. In Levels I to III no assessment list is continued beyond seeing a TA move until that TA motion is handled. In doing a Scientology List One assessment one goes down the list until the TA moves (not because of body motion). Then, because a TA is not very pinpointed, the auditor covers the one or two above where he first saw TA and, watching the pc for interest and the TA, circles around that area until he is sure he has what made the TA move and then bleeds that for TA. by Itsa or Prepcheck. Yes, you say, but doesn't the auditor do TRs on the pc? One question-one answer ratio? NO! Let the pc finish what the pc was saying. And let the pc be satisfied the pc has said it without a lot of chatter about it. TA NOT MOVING SIGNALS AUDITOR TO ACT. TA MOVING SIGNALS AUDITOR NOT TO ACT. Only the auditor can kill the TA motion. So when the TA starts to move, stop acting and start listening. When the TA stops moving or seems about to, stop listening and start acting again. Only act when the TA is relatively motionless. And then act just enough to start it again. Now if you can learn just this, as given here, to act when there's no TA and not act when there is TA, you can make your own start on getting good TA on your preclear. With this you buy leisure to look over what's happening. With half a hundred rules and your own confusion to worry about also, you'll never get a beginning. So, to begin to get TA on your pc, first learn the trick of silent invitation. Just start the session and sit there expectantly. You'll get some TA. When you've mastered this (and what a fight it is not to act, act, act and talk ten times as hard as the pc) then move to the next step. Cover the primary sources of over-restimulation listed above by asking for solutions to them. Learn to spot TA action when it occurs and note what the pc was saying just then. Co-ordinate these two facts-pc talking about something and TA moving. That's Assessment Levels I to III. Just that. You see the TA move and relate it to what the pc is saying just that moment. Now you know that if the pc talks about "Bugs" he gets TA action. Note that down on your report. BUT don't otherwise call it to pc's attention as pc is already getting TA on another subject. This pc also gets TA on Bugs. Store up 5 or ten of these odd bits, without doing anything to the pc but letting him talk about things. Now a few sessions later, the pc will have told all concerning the prime source of over-restimulation I hope you were covering with him or her by only getting the pc started when he or she ran down. But you will now have a list of several other things that get TA. THE HOTTEST TA PRODUCER ON THIS LIST WILL GET A PC'S GOAL AS IT IS HIS SERVICE FAC. You can now get TA on this pc at will. All you have to do is get an Itsa going on one of these things. ANY TA is the sole target of Levels I to III. It doesn't matter a continental what generates it. Only Level IV (R4 processes) are vital on what you get TA on (for if you're not accurate you will get no TA at Level IV). From Levels I to III the pc's happiness or recovery depends only on that waving TA Arm. How much does it wave? That's how much the case advances. Only at Level IV do you care what it waves on. You're as good an auditor in Levels I to III as you can get TA on the pc and that's all. And in Level IV you'll get only as much TA as you're dead on with the right goals and RIs in the right places and those you don't want lying there inert and undisturbed. Your enemy is Over-Restimulation of the pc. As soon as the pc goes into more charge than he or she can Itsa easily the TA slows down! And as soon as the pc drowns in the over-restimulation the TA stops clank! Now your problem is correcting the case. And that's harder than just getting TA in the first place. Yes, you say, but how do you start "getting in an Itsa Line?" "What is an Itsa?" All right-small child comes in room. You say, "What's troubling you?" The child says, "I'm worried about Mummy and I can't get Daddy to talk to me and ..." NO TA. This child is not saying anything is it. This child is saying, "Confusion, chaos, worry." No TA. The child is speaking in Oppterms. Small child comes in room. You say, "What's in this room?" Child says, "You and couch and rug ...." That's Itsa. That's TA. Only in R4 where you're dead on the pc's GPMs and the pc is allowed to say it is or isn't can you get TA good action out of listing and nulling. And even then a failure to let the pc say it is it can cut the TA down enormously. Auditor says, "You've been getting TA movement whenever you mention houses. In this lifetime what solutions have you had about houses?" And there's the next two sessions all laid out with plenty of TA and nothing to do but record it and nod now and then. THE THEORY OF TONE ARM ACTION TA motion is caused by the energy contained in confusions blowing off the case. The confusion is held in place by aberrated stable data. The aberrated (non-factual) stable datum is there to hold back a confusion but in actual fact the confusion gathered there only because of an aberrated consideration or postulate in the first place. So when you get the pc to as-is these aberrated stable data, the confusion blows off and you get TA. So long as the aberrated stable datum is in place the confusion (and its energy) won't flow. Ask for confusions (worries, problems, difficulties) and you just over-restimulate the pc because his attention is on the mass of energy, not the aberrated stable datum holding it in place. Ask for the aberrated stable datum (considerations, postulates, even attempts or actions or any button) and the pc as-ises it, the confusion starts flowing off as energy (not as confusion), and you get TA. Just restimulate old confusions without touching the actual stable data holding them back and the pc gets the mass but no release of it and so no TA. The pc has to say, "It's a " (some consideration or postulate) to release the pent-up energy held back by it. Thus an auditor's worst fault that prevents TA is permitting the dwelling on confusions without getting the pc to give up with certainty the considerations and postulates that hold the confusions in place. And that's "Itsa". It's letting the pc say what's there that was put there to hold back a confusion or problem. If the pc is unwilling to talk to the auditor, that's What to Itsa-"decisions you've made about auditors" for one example. If the pc can't seem to be audited in that environment, get old environments Itsa'ed. If the pc has lots of PTPs at session start, get the pc's solutions to similar problems in the past. Or just Prepcheck, slow, the zone of upset or interest of the pc. And you'll get TA. Lots of it. Unless you stop it. There's no reason at all why a truly expert auditor can't get plenty of TA Divisions Down per 2 1 / 2 hour session running any old thing that crops up on a pc. But a truly expert auditor isn't trying to Itsa the pc. He's trying to get the pc to Itsa. And that's the difference. Honest, it's simpler than you think. L. RON HUBBARD LRH :gw.cden Copyright © 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 105. HCOB 21 JAN 64 METER LEVEL WARNING - HOW TO KILL A PC IN LEVEL 5 HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 21 JANUARY 1964 Central Orgs Franchise METER LEVEL WARNING HOW TO KILL A PC IN LEVEL 5 Breath and Body Motion (All levels) Body Motion, sudden expulsions of breath, emphatic gestures, shouts and foot squirmings and anger can make the TA move down and can cause surges that can be mistaken for reads, even rocket reads. Not knowing this can falsify an assessment or leave the bank undischarged. In all assessing or meter running make sure it was the Bank the meter read, not Breath or Body Motion. * * * * * * * * * * How to Kill a Pc in Level 5 (taken from LRH instruction to students on Saint Hill Special Briefing Course) What's all the shouting on Items in "R3N"? Items won't read unless pc quietly random lists. I think you've forgotten in written random listing as how to make RRs appear on the Implant RIs. Get a random list of a few the pc thinks of. Then the Implant RI will read easily with no shout. This datum gets lost every few months. Keep it around. Pc's sudden expulsion of breath can cause an RR too. Maybe you're getting no charge off. L. RON HUBBARD LRH:vm.bh Copyright © 1964 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 106. HCOB 24 MAY 62 Q AND A HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 24 MAY 1962 Franchise Q AND A A great deal has been said about "Q and A-ing" but few auditors know exactly what it is and all auditors have done it without exception up to now. I have just completed some work that analyses this and some drills which educate an auditor out of it. With a better understanding of it, we can eradicate it. Q and A means ASKING A QUESTION ABOUT A PC'S ANSWER. A SESSION IN WHICH THE AUDITOR Qs and As IS A SESSION FULL OF ARC BREAKS. A SESSION WITHOUT Q and A IS A SMOOTH SESSION. It is vital for all auditors to understand and use this material. The gain for the pc is reduced enormously by Q and A and clearing is not just stopped. It is prevented. The term "Q and A" means that the exact answer to a question is the question, a factual principle. However, it came to mean that the auditor did what the pc did. An auditor who is "Q and A-ing" is giving session control over to the pc. The pc does something, so the auditor also does something in agreement with the pc. The auditor following only the pc's lead is giving no auditing and the pc is left on "self audit". As nearly all auditors do this, no auditing is the rule of the day. Therefore I studied and observed and finally developed a precision analysis of it, for lack of which auditors, although they understood Q and A, nevertheless "Q'd and A'd". THE Qs AND As There are 3 Qs and As. They are: 1. Double questioning. 2. Changing because the pc changes. 3. Following the pc's instructions. The Double Question This occurs on Rudiment Type questions and is wrong. This is the chief auditor fault and must be cured. The auditor asks a question. The pc answers. The auditor asks a question about the answer. This is not just wrong. It is the primary source of ARC Breaks and out rudiments. It is quite a discovery to get this revealed so simply to an auditor as I know that if it is understood, auditors will do it right. The commonest example occurs in social concourse. We ask Joe, "How are you?" Joe says, "I've been ill." We say, "What with?" This may go in society but not in an auditing session. To follow this pattern is fatal and can wipe out all gains. Here is a wrong example: Auditor: "How are you?" PC: "Awful." Auditor: "What's wrong?" In auditing you just must never, never, never do this. All auditors have been doing it. And it's awful in its effect on the pc. Here is a right example: Auditor: "How are you?" PC: "Awful." Auditor: "Thank you." Honest, as strange as this may seem and as much of a strain on your social machinery as you'll find it, there is no other way to handle it. And here is how the whole drill must go. Auditor: "Do you have a present time problem?" PC: "Yes" (or anything the pc says). Auditor: "Thank you, I will check that on the meter. (Looks at meter.) Do you have a present time problem? It's clean." or ".........It still reacts. Do you have a present time problem? That ......That." PC: "I had a fight with my wife last night." Auditor: "Thank you. I will check that on the meter. Do you have a present time problem? That's clean." The way auditors have been handling this is this way, very wrong. Auditor: "Do you have a present time problem?" PC: "I had a fight with my wife last night." Auditor: "What about?" Flunk! Flunk! Flunk! The rule is NEVER ASK A QUESTION ABOUT AN ANSWER IN CLEANING ANY RUDIMENT. If the pc gives you an answer, acknowledge it and check it on the meter. Don't ever ask a question about the answer the pc gave, no matter what the answer was. Bluntly you cannot clean rudiments easily so long as you ask a question about a pc's answer. You cannot expect the pc to feel acknowledged and therefore you invite ARC Breaks. Further, you slow a session down and can wipe out all gain. You can even make the pc worse. If you want gains in a session never Q and A on rudiments type questions or Form type sec check questions. Take what the pc said. Ack it. Check it on the meter. If clean, go on. If still reacting, ask another question of a rudiments type. Apply this rule severely. Never deviate from it. Many new TR drills are based on this. But you can do it now. Handle all beginning, middle and end rudiments exactly in this way. You'll be amazed how rapidly the pc gains if you do and how easily the rudiments go in and stay in. In Prepchecking you can get deeper into a pc's bank by using his answer to get him to amplify. But never while using a Rudiment or sec check type question. Changing because the Pc changes This is a less common auditor fault but it exists even so. Changing a process because the pc is changing is a breach of the Auditor's Code. It is a flagrant Q and A. Getting change on the pc often invites the auditor to change the process. Some auditors change the process every time the pc changes. This is very cruel. It leaves the pc hung in every process run. It is the mark of the frantic, obsessive alteris auditor. The auditor's impatience is such that he or she cannot wait to flatten anything but must go on. The rule of auditing by the tone arm was the method of preventing this. SO LONG AS YOU HAVE TONE ARM MOTION, CONTINUE THE PROCESS. CHANGE THE PROCESS ONLY WHEN YOU HAVE RUN OUT ALL TONE ARM MOTION. Rudiments repair processes are not processes in the full sense of the word. But even here the rule applies if to a limited extent. The rule applies this far: If a pc gets too much tone arm motion in the rudiments, and especially if he or she gets little tone arm motion in the session, you must run Prepchecking on the rudiments questions and do CCHs on the pc. Ordinarily, if you run a rudiments process in getting the rudiments in, you ignore the Tone Arm Motion. Otherwise you'll never get to the body of the session and will have Q'd and A'd with the pc after all. For you will have let the pc "throw" the session by having out rudiments and will have let the pc avoid the body of the session. So, ignore TA action in handling rudiments unless you are Prepchecking, using each rudiment in turn in the body of the session. When a rudiment is used as a rudiment, ignore TA action. When a rudiment is used in the session body for Prepchecking, pay some attention to TA action to be sure something is happening. Don't hang a pc up in a thousand unflat processes. Flatten a process before you change. Following the Pc's Instructions There are "auditors" who look to the pc for all their directions on how to handle their cases. As aberration is composited of unknowns this results in the pc's case never being touched. If the pc only is saying what to do, then only the known areas of the pc's case will get audited. A pc can be asked for data on what's been done by other auditors and for data in general on his reactions to processes. To this degree one uses the pc's data when it is also checked on the meter and from other sources. I myself have had it bad in this. Auditors have now and then demanded of me as a pc instructions and directions as to how to do certain steps in auditing. Of course, snapping attention to the auditor is bad enough. But asking a pc what to do, or following the pc's directions as to what to do is to discard in its entirety session control. And the pc will get worse in that session. Don't consider the pc a boob to be ignored, either. It's the pc's session. But be competent enough at your craft to know what to do. And don't hate the pc so much that you take his or her directions as to what to do next. It's fatal to any session. SUMMARY "Q and A" is slanguage. But the whole of auditing results depends upon auditing right and not "Q and A-ing". Of all the data above only the first section contains a new discovery. It is an important discovery. The other two sections are old but must be discovered sooner or later by any auditor who wants results. If you Q and A your pc will not achieve gains from auditing. If you really hate the pc, by all means Q and A, and get the full recoil of it. A session without ARC Breaks is a marvellous thing to give and to receive. Today we don't have to use ARC Break processes if we handle our rudiments well and never Q and A. L. RON HUBBARD LRH:jw.rd Copyright © 1962 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 107. HCOB 7 APR 64 ALL LEVELS - Q AND A HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 7 APRIL 1964 CenOCon ALL LEVELS Q AND A A great number of auditors Q and A. This is because they have not understood what it is. Nearly all their auditing failures stem not from using wrong processes but from Q and A. Accordingly I have looked the matter over and re-defined Q and A. The origin of the term comes from "changing when the pc changes". The basic answer to a question is, obviously, a question if one follows the duplication of the Comm formula completely. See Philadelphia Congress 1953 tapes where this was covered very fully. A later definition was "Questioning the pc's Answer". Another effort to overcome it and explain Q & A was the Anti-Q and A drill. But none of these reached home. The new definition is this: Q AND A IS A FAILURE TO COMPLETE A CYCLE OF ACTION ON A PRECLEAR. A CYCLE OF ACTION IS REDEFINED AS START-CONTINUE-COMPLETE. Thus an auditing comm cycle is a cycle of action. It starts with the auditor asking a question the preclear can understand, getting the preclear to answer it and acknowledging that answer. A process cycle is selecting a process to be run on the preclear, running the Tone Arm action into it (if necessary) and running the Tone Arm action out of it. A programme cycle is selecting an action to be performed, performing that action and completing it. Thus you can see that an auditor who interrupts or changes an auditing comm cycle before it is complete is "Q and A-ing". This could be done by violating or preventing or not doing any part of the auditing cycle, i.e., ask the pc a question, get an answer to a different idea, ask the different idea, thus abandoning the original question. An auditor who starts a process, just gets it going, gets a new idea because of pc cognition, takes up the cognition and abandons the original process is Q and A-ing. A programme such as "Prepcheck this pc's family" is begun, and for any reason left incomplete to go chasing some new idea to Prepcheck, is a Q and A. Unfinished cycles of action are all that louse up cases. Since Time is a continuum, a failure to carry out a cycle of action (a continuum) hangs the pc up at that exact point. If you don't believe it, prepcheck "Incomplete actions" on a pc! What Incomplete action has been suppressed? etc, cleaning the meter for real on every button. And you'd have a clear-or a pc that would behave that way on a meter. Understand this and you'll be about ninety times as effective as an auditor. "Don't Q and A!" means "Don't leave cycles of action incomplete on a pc." The gains you hope to achieve on a pc are lost when you Q and A. L. RON HUBBARD LRH:dr.rd.cden Copyright ©1964 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 108. HCOB 24 AUG 64 SESSION MUST-NOTS HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 24 AUGUST 1964 Sthil Students Franchise SCIENTOLOGY I TO VI SESSION MUST-NOTS Not that you would do such a thing-you undoubtedly already know better. But just as a matter of record, the following session must-nots should be taught in letters of fire to any new auditor. I NEVER tell a pc what his present time problem is. The pc's PTP is exactly and only what the pc thinks or says it is. To tell a pc what his PTP is and then audit what the auditor said it was will inevitably ARC Break the pc. This of course is under the heading of Evaluation in the Auditor's Code and is one way of evaluating, a very serious way too. II NEVER set a goal for a pc. Don't set a session goal, a life or livingness goal or any other kind of a goal. Auditors get tangled up on this because everybody has the same R6 goals and when you call out the next goal from the list it appears you are giving the pc a goal. But an R6 educated pc knows that and it isn't evaluation. Other goals are highly variable. The pc's life and livingness goals and session goals are especially variable pc to pc and even within one session on the same pc. To tell a pc what goals to set for a session or for life is to upset the pc. If you don't believe it, trace some pc's upsets with their parents and you will find these usually trace back to the parents' setting life and livingness goals for the child or youth. The pc's session and life and livingness goals are the pc's and for an auditor to deny, refute, criticize or try to change them gives ARC Breaks; and for an auditor to dream up a brand new one for the pc is especially evaluative. III NEVER tell a pc what's wrong with him physically or assume that you know. What's wrong with the pc is whatever the pc says or thinks is wrong physically. This applies of course only to processing, for if you weren't auditing the person, and if the person had a sore foot and you found a splinter in it and told him so, it would be all right. But even in this case the person would have had to tell you he had a sore foot. The main reason society has such a distaste for medical doctors is the MDs' continuous "diagnosis" of things the person has not complained of. The violence of surgery, the destruction of lives by medical treatment rather educates people not to mention certain things. Instinctively the patient knows that the treatment may leave him or her in much worse condition and so sometimes hides things. For the medical doctor to cry "Aha" and tell the person he or she has some undefinable ill is to drive many into deep apathy and accounts for the high frequency of operational shock wherein the person just doesn't recover. So NEVER tell a pc what is physically wrong with him. If you suspect something is physically wrong that some known physical treatment might cure send the pc for a physical check-up just to be safe. In the field of healing by mental or spiritual means, the pc is sick because he or she has had a series of considerations about being sick. Deformity or illness, according to the tenets of mental healing, traces back to mentally created or re-created masses, engrams or ideas which can be either de-stimulated or erased completely. Destimulation results in a temporary recovery for an indefinite period (which is nonetheless a recovery). Erasure results in permanent recovery. (De-stimulation is the most certain, feasible and most rewarding action below Level VI; erasure below Level VI is too prone to error in unskilled hands as experience has taught us.) The reality of the auditor is often violated by a pc's statement of what ails him. The pc is stone blind-but the pc says he has "foot trouble". Obviously, from the auditor's viewpoint, it is blindness that troubles this pc. BUT IF THE AUDITOR TRIED TO AUDIT THE AILMENT THE PC HAS NOT OFFERED, AN ARC BREAK WILL OCCUR. The pc is ailing from what the pc is ailing from, not from what the auditor selects. For it is the statement of the pc that is the first available lock on a chain of incidents and to refuse it is to cut the pc's communication and to refuse the lock. After that you won't be able to help this pc and that's that. PERMITTED AUDITOR STATEMENTS There are, however, two areas where the auditor must make a statement to the pc and assume the initiative. These are in the OVERT-MOTIVATOR SEQUENCE and in the ARC BREAK. A. When the pc is critical of the auditor, the organization or any of many things in life, this is always a symptom of overts priorly committed by the pc. The pc is looking for motivators. These criticisms are simply justifications and nothing more. This is a sweeping fully embracive statement-and a true one. There are no criticisms in the absence of overts committed earlier by the pc. It is quite permissible for the auditor to start looking for the overt, providing the auditor finds it and gets it stated by the pc and therefore relieved. But even here the auditor only states there is an overt. The auditor NEVER says what the overt is for that's evaluation. You will be amazed at what the pc considered was the overt. It is almost never what we would think it should be. But also, an auditor whose pc is critical of him or her in session who does not say, "It sounds like you have an overt there. Let's find it," is being neglectful of his job. The real test of a professional auditor, the test that separates the unskilled from the skilled is: CAN YOU GET AN OVERT OFF THE PC'S CASE WITHOUT ARC BREAKING THE PC AND YET GET IT OFF. The nice balance between demanding the pc get off an overt and getting it off and demanding the pc get off an overt and failing to get it off but ARC Breaking the pc is the border line between the unskilled and the professional. If you demand it and don't do it you'll ARC Break the pc thoroughly. If you fail to demand it for fear of an ARC Break you'll have a lowered graph on the pc. The pro demands the overt be gotten off only when necessary and plows on until it's gotten off and the pc brightens up like a lighthouse. The amateur soul-searches himself and struggles and fails in numerous ways-by demanding the wrong overt, by accepting a critical comment as an overt, by not asking at all for fear of an ARC Break, by believing the pc's criticism is deserved-all sorts of ways. And the amateur lowers the pc's graph. Demanding an overt is not confined to just running O/W or some similar process. It's a backbone auditing tool that is used when it has to be used. And not used when it doesn't have to be. The auditor must have understood the whole of the overt-motivator theory to use this intelligently. B. Indicating by-passed charge is a necessary auditor action which at first glance may seem evaluative. However, the by-passed charge is never what the pc says it was if the pc is still ARC Broken. By-Passed Charge is, however, found by the meter and the pc has actually got it or it wouldn't register. So the pc has really volunteered it in a round-about way-first by acting like he or she has by-passed charge and then by bank reaction on the meter. Always indicate to the pc the by-passed charge you find on the meter. Never tell a pc what the by-passed charge is if you don't know. A Class VI auditor knows all goals but the goals are wrong and often sloppily just tells people at random they have "a wrong goal" knowing this to be probable. But it's very risky. If you find it on the meter, telling the pc what the by-passed charge is is not evaluation. Telling the pc "what it is" without having found it is evaluation of the worst sort. L. RON HUBBARD LRH :jw.cden Copyright © 1964 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 109. HCOPL27 MAY 65 PROCESSING HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO POLICY LETTER OF 27 MAY 1965 Remimeo Qual & Tech Divs Sthil Cl VII Course Students Sthil Staff HCO Div Ethics Hats ALL HATS PROCESSING Since 1950 we have had an iron bound rule that we didn't leave pcs in trouble just to end a session. For fifteen years we have always continued a session that found the pc in trouble and I myself have audited a pc for nine additional hours, all night long in fact, just to get the pc through. Newer auditors, not trained in the stern school of running engrams, must learn this all over again. It doesn't matter whether the auditor has had a policy on this or not-one would think that common decency would be enough as to leave a pc in the middle of a secondary or an engram and just coolly end the session is pretty cruel. Some do it because they are startled or afraid and "Rabbit" (run away by ending the session). Auditors who end a process or change it when it has turned on a heavy somatic are likewise ignorant. WHAT TURNS IT ON WILL TURN IT OFF. This is the oldest rule in auditing. Of course people get into secondaries and engrams, go through misemotion and session because things are running out. To end off a process or a session because of the clock is to ignore the real purpose of auditing. The oldest rules we have are (a) GET THE PC THROUGH IT. (b) WHAT TURNS IT ON WILL TURN IT OFF. (c) THE WAY OUT IS THE WAY THROUGH. These now are expressed as POLICY. A falsified auditor's report is also subject to a Court of Ethics. Any auditor violating this policy letter is liable to an immediate Court of Ethics convened within 24 hours of the offence or as soon as is urgently possible. Auditing at all levels works well when it is done by the book. The purpose of Ethics is to open the way for and get in Tech. Then we can do our job. THERE IS NO MODERN PROCESS THAT WILL NOT WORK WHEN EXACTLY APPLIED. Therefore in the eyes of Ethics all auditing failures are Ethics failures-PTS, Suppressive Persons as pcs, or non-compliance with tech for auditors. And the first offence an auditor can commit is ceasing to audit when he is most needed by his pc. Hence it is the first most important consideration of Ethics to prevent such occurrences. Then we'll make happy pcs, Releases and Clears. L RON HUBBARD LRH:nt:rd Copyright © 1965 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 110. HCOPL 1 JUL 65 COMM CYCLE ADDITIVES HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO POLICY LETTER OF 1 JULY 1965 Issue II Remimeo Tech Hats Qual Hats HCO Division Tech Div Qual Div COMM CYCLE ADDITIVES There are no additives permitted on the Auditing Comm Cycle. Example: Getting the pc to state the problem after the pc has said what the problem is. Example: Asking a pc if that is the answer. Example: Telling pc "it didn't react" on the meter. Example: Querying the answer. This is the WORST kind of auditing. Processes run best MUZZLED. By muzzled is meant using ONLY TR 0, 1, 2, 3 and 4 by the text. A pc's results will go to HELL on an additive comm cycle. There are a hundred thousand tricks that could be added to the Auditing Comm Cycle. EVERY ONE of them is a GOOF. The ONLY time you ever ask for a repeat is when you couldn't hear it. Since 1950, I've known that all auditors talk too much in a session. The maximum talk is the standard model session and the TR 0 to 4 Auditing Comm Cycle ONLY. It is a serious matter to get a pc to "clarify his answer". It is in fact an Ethics matter and if done habitually is a Suppressive Act, for it will wipe out all gains. There are mannerism additives also. Example: Waiting for the pc to look at you before you give the next command. (Pcs who won't look at you are ARC Broken. You don't then twist this to mean the pc has to look at you before you give the next command.) Example: A lifted eyebrow at an answer. Example: A questioning sort of ack. The Whole Message is GOOD AUDITING OCCURS WHEN THE COMM CYCLE ALONE IS USED AND IS MUZZLED. Additives on the Auditing Comm Cycle are ANY ACTION, STATEMENT, QUESTION OR EXPRESSION GIVEN IN ADDITION TO TRs 0-4. They are Gross Auditing Errors. And should be regarded as such. Auditors who add to the Auditing Comm Cycle never make Releases. So, that's Suppressive. Don't do it! L. RON HUBBARD LRH:ml.cden Copyright © 1965 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 111. HCOB 3 AUG 65 AUDITING GOOFS - BLOWDOWN INTERRUPTION HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 3 AUGUST 1965 Remimeo All Students All Staff AUDITING GOOFS BLOWDOWN INTERRUPTION It is a serious goof for the auditor to speak or move during a blowdown of the Tone Arm. When a Tone Arm has to be moved rapidly down, the needle appears to float to some but it is just falling. To see if a needle is floating the TA must have stopped moving down. A Blowdown is a period of relief and cognition to a pc while it is occurring and for a moment after it stops. Therefore it is a serious goof for an auditor to speak or move during the blowdown or for a moment afterwards. This was noted years ago and is given in early materials on goals. AN AUDITOR MUST NOT SPEAK OR MOVE DURING A BLOWDOWN. When the auditor has to move the TA from right to left to keep the needle on the dial and the movement is .I divisions or more then a blowdown is occurring. The needle of course is falling to the right. That is a period of charge blowing off the bank. It is accompanied by realizations for the pc. Sometimes the pc does not voice them aloud. They nevertheless happen. If the auditor speaks or moves beyond adjusting the TA quietly with his thumb the pc may suppress the cognitions and stop the blowdown. To see if a needle floats the TA must be halted for the moment between 2 and 3 on a calibrated meter. A floating needle cannot be observed during a blowdown. For an auditor to sit up suddenly and look surprised or pleased, or for an auditor to say the next command or "That's It" during a blowdown, can jolly well wreck a pc's case. So it's a real goof to do so. To get auditing results one must audit with a good comm cycle, accept the pc's answers, handle the pc's originations, be unobtrusive with his auditing actions, not hold the pc up while he writes, not develop tricks like waiting for the pc to look at him before giving the next command, not prematurely ack and so start compulsive Itsa, and be very quiet during and just after a blowdown. L. RON HUBBARD LRH:ml.cden Copyright ©1965 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 112. HCOB 21 SEP 65 OUT TECH HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 21 SEPTEMBER 1965 Tech Sec Qual Sec Dir Rev Ds of P HGC Ds of T Course Supervisor All Students OUT TECH (Additional Data on HCO Bulletin of 13 September 1965) ALL THIS DATA COVERED AND EXPLAINED IN THE SAINT HILL SPECIAL BRIEFING COURSE TAPE OF 21 SEPTEMBER 1965 Note the 5 GAEs are also covered in Tape Lecture of 10 July 1963 See also HCO Pol Ltr 21 September 1965, Issue II, "Auditor Estimation Test" The five Gross Auditing Errors (GAEs) are: 1. Can't handle and read an E-Meter. 2. Doesn't know and can't apply Technical data. 3. Can't get and keep a pc in session. 4. Can't complete an auditing cycle. 5. Can't complete a repetitive auditing cycle. (Including repeating a command long enough to flatten a process.) These are the only errors one looks for in straightening up the auditing of an Auditor. The six things that can be wrong with a pc are: 1. Pc is Suppressive. 2. Pc is ALWAYS a Potential Trouble Source if he Roller Coasters and only finding the RIGHT suppressive will clean it up. No other action will. There are no other reasons for a Roller Coaster (loss of gain obtained in auditing). 3. One must never audit an ARC Broken pc for a minute even but must locate and indicate the by-passed charge at once. To do otherwise will injure the pc's case. 4. A present time problem of long duration prevents good gain and sends the pc into the back track. 5. The only reasons a pc is critical are a withhold or a misunderstood word and there is NO reason other than those. And in trying to locate a withhold it is not a motivator done to the pc but something the pc has done. 6. Continuing overts hidden from view are the cause of no case gain (see number 1, Suppressive). IN TECH In getting in Tech one need only locate in the auditor (or self as an auditor) which of the 5 GAEs are being committed and, in the pc, which of the above six is out. There are no reasons exterior to the 11 given. To get Tech In, requires getting the 5 in for auditors and the six in for pcs and after that, watching the 5 for auditors and 6 for pcs, running standard processes. If you look for other reasons, this is itself a gross goof. There are no others. L. RON HUBBARD LRH: ml. cden Copyright © 1965 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 113. HCOB 12 FEB 66 THE "DANGEROUS AUDITOR" HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 12 FEBRUARY 1966 Remimeo Staff Auditors' Hats Tech Hats Qual Hats THE "DANGEROUS AUDITOR" We long have had a term for an auditor who consistently did things that were upsetting to a pc's case. We call this a "dangerous auditor". There are certain exact specific actions or omissions that make such an auditor dangerous. These are: 1. Breaks the Auditor's Code or ignores it as "only applying in certain cases". 2. Audits past floating needles or directs additional auditing on that process when a floating needle has occurred. 3. Ceases to audit a process before the needle has gone free. 4. Starts a new grade of release without rehabilitation or making sure at least by record that an earlier grade has been rehabbed and was not overrun. 5. Does not locate the right SP on S & D but over or under lists or misses while assessing. 6. Goes on auditing the pc after an ARC Break without caring for the ARC Break (and believes it possible or usual to continue past one). 7. Consistently has hostile and derogatory opinions about his pcs. These are the really dangerous points that make an auditor who does them dangerous. (This list is composed by tracing back upset cases to the errors which made the upset.) An auditor who merely makes the five Gross Auditing Errors is just a bad auditor. (See HCO B 21 Sept 65 "Out Tech".) A dangerous auditor often seems to be quite accomplished, but does the above. On some pcs he seems to get away with it and so will argue the virtue of his approach or violations. But on the next pc he doesn't and has a mess on his hands. A "careful" auditor is not necessarily not dangerous. One doesn't audit carefully. One audits with a relaxed competence that follows the rules and avoids the errors listed above. There is no compromise for knowing one's business. Most auditors, when they are trained and no longer make the 5 Gross Auditing Errors, become very excellent auditors and do a fine job and I am proud of them. L. RON HUBBARD LRH:ml.cden Copyright © 1966 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 114. HCOB 11 FEB 66 FREE NEEDLES, HOW TO GET THEM ON A PC HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 11 FEBRUARY 1966 Remimeo All Students All Scn Staff Franchise FREE NEEDLES, HOW TO GET THEM ON A PC Free needles can be obscured only by overruns and auditor goofs in the rehab session and ARC Breaks in past auditing. When a TA goes up or is up it means an overrun in life or on a process or grade of release. The only place you can't get an overrun is at Grade VII. All grades below that are subject to overrun. Life subjects are subject to overrun before Scientology. The mechanism is this: one conceived a purpose. He or she succeeded in it, then kept on and overran it. In auditing one hits the purpose and the overrun of it and gets a free needle on it. That doesn't mean the person was a release then. It means that the spotting of the purpose and the overrun by auditing produces a free needle today. It may be necessary to find whole track overruns on some pcs in rehabilitation of grades. If a lot of levels have been run past free needle it may be necessary to take apart the mess like a bundle of yarn to get the first free needle. In such a case one rehabs any grade the pc has been run on that the pc can remember. One handles this briefly until the pc is happy but not necessarily to free needle. One then finds another overrun, does the same. One goes on and on looking for moments the pc felt good about processing at one or another time. If you keep this up, suddenly you will see a free needle on the pc! Establish what grade it is free on, then quickly get the needle free on the remaining overrun grades (but not grades pc was never run on). It may be necessary to take into account a whole track overrun of a purpose or even the purpose to get release, clear or OT. It is all very quick, deft auditing, very much on procedure using standard rehab tech-but no repetitive grind. -------------- You won't see a freeing up of a needle unless you set your sensitivity on a Mark V to a stiff needle for the pc. You can increase sensitivity or decrease it as the pc progresses but by setting the sensitivity so the needle is pretty still and stiff you will see easily a freeing up of the needle and then a free needle. Using sensitivity 128 will obscure every free needle as the needle is too loose already for the auditor to see any change. -------------- Pcs are most apt to go free needle after a big cog. So don't be so engrossed in looking at the pc during cognitions. Keep an eye on that needle. And if it goes free, don't ask anything else. Just gently give the pc a "That's it" and without a chop of comm, ease the pc off to "Declare?" in Qual. (Or if a field auditor, start the next grade. ) -------------- Gently, gently, smooth TRs get you free needles. A dirty needle is always caused by auditor chops, flubs, etc. You can always trace a dirty needle right back to a TR error by the auditor. If a needle goes dirty in a rehab session, get the List 1 out right now and quickly find why. It's always an auditor goof on the TRs or tech procedure. -------------- Rehabs are not a substitute for processes. If a grade hasn't been run, you can't rehab it of course. In rehab, never use a new process to cure an overrun. Rehab the process that was overrun, not new ruds. And see HCO Pol Ltr 10 Feb 1966 on this subject. --------------- You can get free needles on pcs. It just requires standard TRs, standard tech, standard rehab and wanting to get one and letting a pc have one. L. RON HUBBARD LRH:ml.rd Copyright © 1966 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 115. HCOB 26 AUG 68 REHAB & CORRECTION HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 26 AUGUST 1968 Remimeo Sea Org QUALS REHAB & CORRECTION You can correct a pc or Pre OT half to death. For instance the practice of rehabbing up to Grade II if it has been a week or two or more since the pc made Grade II in order to run III is a bit bonkers and serves as an Invalidation. You're going to get any upset anyway in the rudiments so why the rehab? At SH lower grades are rehabbed before Power only when the pc had the lower grades elsewhere as the grades aren't to be trusted and that's for Power only. And only when there's no good report available. Doing a Green Form "every day" on a pc or Pre OT may shove up Qual stats but it's actually an overrun of Green Forms. They go to F/N on the Green Form and to do another WITHOUT ANY REAL TROUBLE having occurred is asking for it. Sec Checks can be overrun and overdone. By-passing 2 or 3 Floating Needles on a Sec Check is bad business. Doing Disagreements Checks and S & Ds wholesale on pcs and Pre OTs eventually winds them up in a ball. Outnesses can usually be spotted by folder inspection by a good Case Supervisor. When Remedy Bs and S & Ds are done by auditors who haven't got the Laws of Listing recent HCOB down by heart and use it will generally mess up more pcs than they will help. Qual corrects. But it can get into over-correction and then invalidate the pc's or Pre OT's levels, fill his folder with bad lists, etc. If any organization, any Qual, at this writing had its folders fully gone over by a competent Case Supervisor who KNEW his Laws of Listing, knew his auditing, I guarantee that Org's stats would soar, not just Qual's. And having for once and all straightened out the folder then cease to correct things that would better be handled by the next Grade or Section. When over-correction has been present YOU STRAIGHTEN OUT THE BLUNDERS IN THE FOLDER not just maul the pc around some more. And when you have the folder straight you mark it up to that point as remedied and after that only handle the pc when there's something really gone wrong with him. At the present writing I am organizing the Class VIII Course to make Class VIII auditors. These are essentially Case Supervisors and crack standard tech people who can straighten out folders and pcs and Pre OTs. Looking over old Qual case folders I see they are desperately needed. But keep the fact in view, don't correct a pc who needs no correction. Don't rehab and Remedy him to death. Get him onto the next level or section and let him have his wins. L. RON HUBBARD LRH:jp.ei.cden Copyright © 1968 Founder by L. Ron Hubbard ALL RIGHTS RESERVED ************** 116. HCOB 11 AUG 78 MODEL SESSION HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 11 AUGUST 1978 Remimeo Issue II All Auditors (Cancels BTB 18 Nov 68R, MODEL SESSION) MODEL SESSION (Note: If a Dianetic or Level 0, I, II auditor is not trained in flying rudiments he would have to get a Level III (or above) auditor to fly the pc's ruds before starting the major action of the session.) 1 . Setting Up for the Session Prior to the session the auditor is to make sure the room and session are set up, to ensure a smooth session with no interruptions or distractions. Use HCOB 4 December 1977, "Checklist for Setting Up Sessions and An E-Meter," getting in every point of the checklist. The pc is seated in the chair furthest from the door. From the time he is asked to pick up the cans he remains on the meter until the end of the session. When it is established there is no reason not to begin the session the auditor starts the session. 2 . Start of Session The auditor says: "This is the session." (Tone 40.) If the needle is floating and the pc has VGIs, the auditor goes directly into the major action of the session. If not, the auditor must fly a rud. 3 . Rudiments Rudiments are handled per HCOB 11 August 1978, Issue I, "Rudiments, Definitions and Patter." (If the TA is high or low at session start, or if the auditor cannot get a rud to fly, he ends off and sends the pc folder to the C/S. A Class IV auditor (or above) may do a Green Form or another type of correction list.) When the pc has F/N, VGIs the auditor goes into the major action of the session. 4 . Major Action of the Session a) R-Factor to the pc. The auditor informs the pc what is going to be done in the session with: "Now we are going to handle ." b) Clearing commands. The commands of the process are cleared per HCOB 9 August 1978 Issue II, "Clearing Commands." c) The process. The auditor runs the process or completes the C/S instructions for the session to end phenomena. In Dianetics, the end phenomena would be: F/N, erasure of the chain, cognition, postulate (if not voiced in the cognition) and VGIs. In Scientology processes, the end phenomena is: F/N, cognition, VGIs. The Power Processes have their own EP. 5 . Havingness When Havingness is indicated or included in the C/S instructions, the auditor runs approximately 10 to 12 commands of the pc's Havingness Process to where the pc is bright, F/Ning and in PT. (Note: Havingness is never run to obscure or hide the fact of failure to F/N the main process or an auditing or Confessional question.) (Ref: HCOB 7 August 78, "Havingness, Finding & Running The Pc's Havingness Process. ") 6 . End of Session a) When the auditor is ready to end the session he gives the R-Factor that he will be ending the session. b) Then he asks: "Is there anything you would care to say or ask before I end this session?" Pc answers. Auditor acknowledges and notes down the answer. c) If the pc asks a question, answer it if you can or acknowledge and say, "I will note that down for the C/S." d) Auditor ends the session with: "End of session." (Tone 40.) (Note: The phrase "That's it" is incorrect for the purpose of ending a session and is not used. The correct phrase is "End of Session.") _________ Immediately after the end of session the auditor or a Page takes the pc to the pc Examiner. L. RON HUBBARD Founder LRH:nc Copyright © 1978 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 117. HCOB 9 AUG 78 CLEARING COMMANDS HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 9 AUGUST 1978 Issue II Remimeo (Cancels BTB 2 May 72R, Rev. 10.6.74, CLEARING COMMANDS.) CLEARING COMMANDS (Ref: HCOB 14 Nov 65, CLEARING COMMANDS HCOB 9 Nov 68, CLEARING COMMANDS, ALL LEVELS HCO PL 4 Apr 72R ETHICS AND STUDY TECH) Always when running a process newly or whenever the preclear is confused about the meaning of commands, clear each word of each command with the preclear. using the dictionary if necessary. This has long been standard procedure. You want a pc set up to run smoothly, knowing what is expected of him and understanding exactly the question being asked or the command being given. A misunderstood word or auditing command can waste hours of auditing time and keep a whole case from moving. Thus this preliminary step to running a process or procedure for the first time is VITAL. The rules of clearing commands are: 1. UNDER NO CIRCUMSTANCES IS THE AUDITOR TO EVALUATE FOR THE PC AND TELL HIM WHAT THE WORD OR COMMAND MEANS. 2. ALWAYS HAVE THE NECESSARY (AND GOOD) DICTIONARIES IN THE AUDITING ROOM WITH YOU. This would include the Tech Dictionary, the Admin Dictionary, a good English dictionary, and a good non-dinky dictionary in the pc's native language. For a foreign language case (where the pc's native language is not English) you will also need a dual dictionary for that language and English. (Example: English word "apple" is looked up in English/French dictionary and "pomme" is found. Now look in the French dictionary to define "pomme.") So for the foreign language case two dictionaries are needed: (1) English to foreign language (2) foreign language itself. 3. HAVE THE PC ON THE CANS THROUGHOUT THE CLEARING OF THE WORDS AND COMMANDS. 4. CLEAR THE COMMAND (OR QUESTION OR LIST ITEM) BACKWARDS BY FIRST CLEARING IN TURN EACH WORD IN THE COMMAND IN BACKWARDS SEQUENCE. (Example: To clear the command "Do fish swim?" clear "swim" first, then "fish," then "do.") This prevents the pc starting to run the process by himself while you are still clearing the words. 4A. NOTE: F/Ns OBTAINED ON CLEARING THE WORDS DOES NOT MEAN THE PROCESS HAS BEEN RUN. 5. NEXT, CLEAR THE COMMAND ITSELF. Auditor asks the pc, "What does this command mean to you?" If it is evident from the pc's answer that he has misunderstood a word as it is used in the context of the command: (a) Re-clear the obvious word (or words) using the dictionary. (b) Have him use each word in a sentence until he has it. (The worst fault is the pc using a new set of words in place of the actual word and answering the alter-ised word, not the word itself. See HCOB 10 Mar 65, WORDS, MISUNDERSTOOD GOOFS.) (c) Re-clear the command. (d) If necessary, repeat Steps a, b and c above to make sure he understands the command. 5A. NOTE: THAT A WORD READS WHEN CLEARING A COMMAND, AN ASSESSMENT QUESTION OR LISTING QUESTION DOES NOT MEAN THE COMMAND O R QUESTION ITSELF HAS READ NECESSARILY. MIS-UNDERSTOOD WORDS READ ON THE METER. 6. WHEN CLEARING THE COMMAND, WATCH THE METER AND NOTE ANY READ ON THE COMMAND. (Ref: HCOB 28 Feb 71, C/S Series 24, IMPORTANT METERING READING ITEMS.) 7. DON'T CLEAR THE COMMANDS OF ALL RUDS AND RUN THEM, OR OF ALL PROCESSES AND RUN THEM. YOU'LL MISS F/Ns. THE COMMANDS OF ONE PROCESS ARE CLEARED JUST BEFORE THAT PROCESS IS RUN. 8. ARC BREAKS AND LISTS SHOULD BE WORD CLEARED BEFORE A PC GETS INTO THEM AND SHOULD BE TAGGED IN THE PC'S FOLDER ON A YELLOW SHEET AS CLEARED. (Ref: BTB 5 Nov 72R II, Rev. 24.7.74, Auditor Admin Series 6R, THE YELLOW SHEET.) As it is difficult to clear all the words of a correction list on a pc over heavy bypassed charge, it is standard to clear the words of an L1C and ruds very early in auditing and to clear an L4BRA before commencing listing processes or an L3RE before running R3RA. Then, when the need for these correction lists arises one does not need to clear all the words as it has already been done. Thus, such correction lists can be used without delay. It is also standard to clear the words of the Word Clearing Correction List early in auditing and before other correction lists are cleared. This way, if the pc bogs on subsequent Word Clearing, you have your Word Clearing Correction List ready to use. 9. IF, HOWEVER, YOUR PC IS SITTING IN THE MIDDLE OF AN ARC BREAK (OR OTHER HEAVY CHARGE) AND THE WORDS OF THE L1C (OR OTHER CORRECTION LIST) HAVE NOT BEEN CLEARED YET, DON'T CLEAR FIRST. GO AHEAD AND ASSESS THE LIST TO HANDLE THE CHARGE. OTHERWISE IT'S AUDITING OVER AN ARC BREAK. In this case you just verify by asking afterwards if he had any misunderstoods on the list. All the words of the L1C (or other correction list) would then be cleared thoroughly at the first opportunity-per your C/S's instructions. 10. DO NOT RE-CLEAR ALL THE WORDS OF ASSESSMENT LISTS EACH TIME THE LIST IS USED ON THE SAME PC. Do it once, fully and properly the first time and note clearly in the folder, on the yellow sheet for future reference, which of the standard assessment lists have been cleared. 11. THESE RULES APPLY TO ALL PROCESSES, LISTING QUESTIONS AND ASSESSMENTS . 12. THE WORDS OF THE PLATENS OF ADVANCED COURSE MATERIALS ARE NOT SO CLEARED. ____________ Any violation of full and correct clearing of commands or assessment questions, whether done in a formal session or not, is an ethics offense per HCO PL 4 Apr 72R (Rev. 21.6.75) ETHICS AND STUDY TECH, Section 4, which states: "ANY AUDITOR FAILING TO CLEAR EACH AND EVERY WORD OF EVERY COMMAND OR LIST USED MAY BE SUMMONED BEFORE A COURT OF ETHICS. "The charge is OUT TECH." L. RON HUBBARD Founder LRH:dr Copyright © 1978 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 118. HCOB 24 JUL 64 TA COUNTERS, USE OF HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 24 JULY AD14 Remimeo Sthil Students Franchise SCIENTOLOGY III & IV TA COUNTERS, USE OF With the advent of the TONE ARM COUNTER new problems arise in Auditing and Auditing supervision. Without an adequate written record of time and "TA" (by which is meant the total number of divisions down a tone arm has moved accurately in a unit of time such as 20 minutes or a 21/2 hr session) one does not know whether or not a process was flattened. A process is considered "flat" when it produces no more than .25 div of TA in 20 minutes. The auditor can't recheck the last 20 minutes because he has no time noted and no Tone Arm notations. Therefore he or she audits by guess and leaves process cycles of action on the case either unflat or overflattened. This alone is enough to upset pcs. Further, when two processes have been run in a session and only a counter was used, an auditing supervisor has no idea at all of whether one was flattened before the other was begun. Also "TA" for a session can be a gross error by reason of poor handling of the Tone Arm. If an auditor fails to set the Tone Arm accurately each time the needle moves from "set" on the dial, less TA is shown for the session. If the auditor habitually overworks the Tone Arm, setting it further than it should have gone to bring the needle to "set", either up or down, then the TA Counter will show far more TA for the session than really happened. The way to handle this dilemma is to use the TA Counter only for a rough estimate of TA for a session (or process) and to continue to record Tone Arm action at Levels III and IV. (One is too busy at Levels V and VI and by that time should be able to rely on the counter as TA in such sessions is very large.) The Tone Arm is never touched during sneezing, body motion, etc, and no recording is made. But if the TA blew down because of it, the fact is noted in the worksheet column and the new reading entered. All meter auditing below Level V should be recorded by Time and Tone Arm position. To so record TA it is not necessary to use several pounds of Auditor's Report forms. One uses one Auditor's Report form to report on the session and similar sized rough work sheets to record Time, TA position and what is going on. These rough work sheets are divided into two or three vertical columns with a ball-point pen and each one of these is split in half vertically. In the first column enter time, in the second enter TA notes of where the Tone Arm is at that time. Take Tone Arm readings only with the needle at "set". If something noteworthy occurs write it across these two columns, using the spaces of Time and TA position for a brief note and below it going on with the Time and TA position notes. One writes down the TA position with the time it happened only when the Tone Arm needs to be moved to bring the needle back to "set". A needle that moves but comes back at once (within 1 or 2 seconds) to "set" is not recorded. Point One (.1) division changes are not recorded as too minute. One fills up these three double columns, turns over the sheet and does the same on the back. Printed Auditor's Reports are never used as work sheets. They give the details of the beginning of the session, condition of pc, what's intended, the wording of the process, etc. Then one goes to work sheets and only returns to the Auditor's Report, which is half empty, to complete the session and end it off with pc goals and gains and all that. The TA Counter is then read and written on the report. This is all so written that one can see the whole session at a glance, including TA total, just by looking at the one side of the Auditor's Report form. On that one side the session begins, ends, and by seeing how the pc was at start and is at the end, and the TA Counter read, what was done and the success or failure of the session is grasped at a glance. In trying to analyze the session and help the pc more, one inspects the work sheets. When the session is completed, the work sheets are put in proper sequence (sequence quite visible because of the time notations), the Auditor's Report is put face up on top and the lot are all stapled together by the left-hand corner. If an ordinary stapler won't do it easily for a 2 1 / 2 hr session, far too many notations are being made, for no III or IV pc is that active. Faults of Tone Arm handling (over or under setting of it by the auditor) show up, process flattening can be traced, changes of process can be seen and the auditor or the auditing supervisor can find out what really happened. I myself wouldn't know how to guide the next session at Levels III and IV if I didn't have a record of TA of the last session to inspect, whether the session were mine or another's. Such delicate judgements as "was the TA just working into the process" or "was the processing dying down" or "was it being overflattened" just can't be answered by the auditor himself, much less an auditing supervisor if no Time-TA record exists. Also, don't take a Tone Arm reading "every 2 minutes" or "every minute". That's poor because such timed readings tell nothing. When the TA has to be moved more than .1 divisions to keep the needle at set, one notes Time and the new Tone Arm reading. That's the only answer to how often one reads and notes TA action. Changes of process are noted across both Time and Tone Arm columns but also at session ending noted on the Auditor's Report. One doesn't often change processes and only when the old one has (1 ) had time to get the TA worked into it (2) had the TA worked out of it and (3) the old one produces only .25 divisions of TA action in a consecutive 20 minutes of auditing. The Tone Arm Counter is a must or one spends ages adding up his session TA when he needs lunch or a break. But it jolly well never can supplant a work sheet. Automation can only go so far. Tone Arm Counters can't think. The Auditors I train can. L. RON HUBBARD LRH:nb.cden Copyright © 1964 by L. Ron Hubbard ALL RIGHTS RESERVED ************** 119. HCOB 2 JAN 67 DATING - FORBIDDEN WORDS HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 2 JANUARY 1967 Qual Personnel Tech Personnel Clearing Course Students SHSBC Students DATING - FORBIDDEN WORDS THE WORDS "MORE"-"LESS" OCCUR IN THE BANK AND THEIR USE IN DATING IS FORBIDDEN. In The Book of E-Meter Drills the patter for Track Dating, E-Meter Drill 25, containing the words "more"-"less", has to be changed to "GREATER THAN" - "LESSER THAN". E-Meter Drill 22, E-Meter Hidden Date, This Life, remains unchanged. Anyone who is using the words "earlier"-"later" in dating, words which are not to be found in any E-Meter Drill, is not only guilty of alter-ising Tech, but will grind his student or preclear into the Bank, since these words also occur in the Bank and are therefore forbidden. L. RON HUBBARD Founder LRH:jp.cden Copyright © 1967 by L. Ron Hubbard ALL RIGHTS RESERVED **************