Reading and Unreading Auditing Questions
|Reading and Unreading Auditing Questions|
|Topic||Reading and Unreading Auditing Questions|
|Author||Max Hauri, Ron's Org Grenchen|
|Type of Article||Category:Training|
At a certain moment I was no more willing to be reasonable with the inconsistency of the tech. I rejected to read one thing but to apply another. What LRH is teaching us on the Briefing Course is not the tech delivered in the eighties and later.
Around the end of the seventies but starting already beginning of the century the basics of the e-meter tech got altered and changed almost 180°, made it unnecessarily complicated especially for beginners, made it unworkable and was asking for unusual solutions.
The buttons became a solution to a problem.
The perverted viewpoint is that the METER GIVES THE AUDITOR THE PERMISSION TO AUDIT something. Without read on the meter nothing goes. The meter became predominant.
Probably it all got upside down by misunderstanding the HCOB 27 May 70 UNREADING QUESTION AND ITEMS and putting one sentence out of the context into the Tech Dict: "A "tick" or a "stop" is not a read. Reads are small falls or falls or long falls or long fall blowdown (of TA)." That became the unshakable stable data for all auditors especially in the church.
The correct viewpoint is that the METER TELLS THE AUDITOR WHEN AN ACTION IS COMPLETED AND SAFELY CAN BE ENDED without leaving the pc with BPC.
Rudiments, Prepcheck, Confessional, Grade Processes, Auditing by List (esp. L1C) became a sophisticated subject needing all kind of special references and tricks and how to apply buttons and deal with the meter. The key ingredient in auditing – Two Way Communication – got lost and it became a checking between the auditor and the meter.
The subject can roughly be divided into three parts which should not be mixed, they have to be considered as different subjects: a) rudiment type of things like ruds, prepcheck, confessionals etc. and b) reading items used in certain processes like Dianetics, Service Facs handling, other processes where you need reading items, and last c) "reading questions" being applied to simple grade processes.
a): Prepcheck, Confessionals[edit | edit source]
Let's go back to times of the SHSBC. You can find several references LRH clearly states that you do not check a Confessional question. You only start to check the question when the pc has no more answers to it. Now you use the meter.
HCO PL 15 Nov 70 CONFESSIONAL:
"Real criminals may have bad meters but crimes are often so unreal to them that they do not read (meters needle read only on things within the reality or borderline reality of a person). This permits unskilled Sec Checking or Confessional actions to pass right by the culprit."
HCOB 6 Jul 61 ROUTINE 1A; § Sec Check:
"If the pc owns up to a question, don't refer to the meter. Don't even look at the meter when asking a Sec question the first time. If the pc then says he hasn't done it, look at the needle and without looking at the pc ask again. Pc still says "No" or its equivalent and you get an instant read, pursue it with more questions. Never pass Sec Check question that is getting an Instant Read."
BTB 4 Jan 62 rev 6 Mar 77 CONFESSIONAL FUNDAMENTALS:
"So in confessionals the auditor on any particular question never looks at the E-Meter on that particular question, until the preclear has reached an impass on that question, and says that he really and truly can think of no further answers. This creates confidence that the Auditor and the preclear are really working together to overwhelm the reactive mind.
When the impasse is reached on any particular question, then the auditor asks the whole question looking all the time at the E-Meter. If the meter gives an instant read (any needle reaction, i.e. Fall, Rock Slam, Theta Bop or change of needle characteristic which occurs within half of a second or up to three-quarters of a second, in case the preclear has a delayed circuit on hearing) to the question or any word or phrase in the question, then the auditor uses the E-Meter to assist the preclear in pulling all further overts."
BTB 30 Aug 62 MISSED WITHHOLD HANDLING:
(Written by MSH) In this issue nothing is mentioned that the MWH question has to read, the auditor is expected to just pull the MWH when there are signs of MWH:
"If the preclear begins to boil off in a session, the Auditor should immediately pull the missed withhold or missed withholds. If he is in the middle of the Auditor rudiment and the preclear begins to boil off, he immediately pulls missed withholds and then returns to cleaning the Auditor rudiment. He does not wait until he has cleaned the Auditor rudiment or wait until he has completed the beginning rudiments to pull the missed withholds."
HCOB 3 Jul 62 REPETITIVE PREPCHECKING:
Without now looking at the Meter, the auditor asks the Form question repetitively until the preclear says that's all, there are no more answers.
The auditor then says, "I will check that on the meter" and does so, watching for the Instant Read (HCO Bulletin May 25, 1962).
If it reads, the auditor says, "That reads. What was it?" (and steers the pc's attention by calling each identical read that then occurs). "There… That… That…" until the pc spots it in his bank and gives the datum."
The first time mentioned that a confessional question must read is in the BTB 5 Dec 72RA rev 13 May 75 [I could not get any unrevised or first revised of that issue – if someone has them please scan it and send it to me] – but that is not LRH! Has he approved that? I don't know.
Fishy is also that exact that issue was taken and used as a basic for the HCOB 30 Nov 78 CONFESSIONAL PROCEDURE. For me hard to believe that LRH 1978 was using a BTB and making out of it a HCOB, especially as it is 180° degree opposite to earlier statements of him, see above.
a) Rudiments:[edit | edit source]
Take a careful look at the HCOB 11 Aug 78 RUD DEFINITIONS AND PATTERN – you cannot find anything written into the direction that the question "Do you have an ARCX?" must read. The "clever" ones say but you find it in HCOB 15 Aug 69, FLYING RUDS but that is actually a Class VIII reference and does not belong to Level 0. HCOB 11 Aug 78 is a good round-up of the ruds – so why is it not mentioned there?
You may say that "If a rudiment doesn't read and is not F/Ning, put in the Suppress button, using: "On the question 'Do you have an ARC break?' has anything been suppressed?" does indicate that the question has to read. But if you take the viewpoint that you check it only before you leave the question it makes much more sense.
Lets become practical, why to check the obvious? Pc is crying = ARCX. Nattery = MWH. etc. No need to put the meter higher in rank than C/S Series 1.
But let's see what Hubbard writes:
HCOB 3 Jul 65 MODEL SESSION REVISED:
(The following rudiments are used only in metered sessions.)
"Is there an ARC Break?" (On raw meat, "Are you upset by anything?")
"Is there any current problem that will interfere with auditing?"
"Should you have told me anything you didn't?"
"Has anything been suppressed?"
"Has anything been denied?"
"Has anything been rushed?"
To be clarified by: [Clarified by HCO B 19 AUGUST 1965, MODEL SESSION REVISED]
HCOB 19 Aug 65 MODEL SESSION REVISED:
"Pertaining to Level 0 training, whereas the student is to use a meter in order to familiarize himself with it and with using it in a session, he is not trained in the fine points of metering until Level II. Therefore during the training of Level 0 the Model Session as per HCOB 3 July 1965 is to be used, but the questions are actually unmetered (the student does not follow up needle reads), except for the fact that the student has a meter in front of him.
"Any auditor from Class II up would, of course, meter such questions in running Level 0 processes on a preclear.
"At Level 0 the student must know the parts of the meter and be able to recognize a floating needle and be able to record tone arm action."
HCOB 19 Mar 71 L1C:
"TAKE ALL READING ITEMS OR VOLUNTEERED ANSWERS Earlier Similar to F/N as they occur."
All this gives a fully different viewpoint.
b) Reading Items[edit | edit source]
HCOB 27 May 70 UNREADING QUESTION AND ITEMS:
That bulletin is just for "hard core". This is now real auditing not ruds:
"Never list a listing question that doesn't read.
Never prepcheck an item that doesn't read.
These rules hold good for all lists, all items, even Dianetics."
To put the statement "A "tick" or a "stop" is not a read. Reads are small falls or falls or long falls or long fall blowdown (of TA)." into the Tech Dict brought about a huge confusion and should never have done so. This statement applies for real items. But not when you have to clean a rud or confessional question!
This bulletin is written exactly for what you can read above: L&N questions, Prepcheck Items, Dianetics Items, or any items you need by the according bulletin a read.
To apply it to grade process questions is a pure arbitrary.
c): Checking Questions on Grade Processes[edit | edit source]
To check grade processes is one of the biggest squirrel actions ever in Scientology. Up to the date 25 February 1982 it was never done so! This is a fact.
There are for example the AUDITOR DRILL SERIES (BTBs) 9 Oct 71 which are giving the drill how to audit a process painstakingly! Every single details is given, almost ad absurdum. And it is not mentioned a single time that you check a grade process for read.
It just does not make senses to check them for read. Some say you are handling Locks with those processes – negative! That is another subject. Grades are to increase abilities, or to put them there.
There are certainly processes and commands you need a reading item – according to the reference (HCOB).
Those are the according references to it:
HCOB 22 Oct 70 READING QUESTIONS:
Refer: HCOB 26 Feb 1970 "Standard Tech & Invalidation" and HCOB 27 May 1970 "Unreading Questions and Items"
The routine questions of the Expanded Grade processes are not checked for read before running them. The exceptions are only as expressly designated where it is a part of that individual technique, or on listing questions such as the main Grade IV process.
1. When you're picking something to run on an individual that is handling his individual manifestations it must read well before you run it. Not all pcs have "a sharp pain in the left elbow" or are upset by false teeth or have a prepcheckable item called "reviews" or have an item for "Who or what has suppressed you?"
2. When you're running something that is common to all thetans – i.e. that all thetans have – then the charge is there, though it could take a little while to run the meter action into the process. Probably with Ruds well in most of the standard processes would read anyhow, if you happened to be looking at the meter; thus later you can check a previously run Grade process for read as an indication of whether or not it's flat.
To run 0-B you'd check the item for read before using it in the blank in the command … but you wouldn't check "communication", find no read, and then skip Grade Zero on the pc. All the processes of the level are run on each pc.
D/CS-4 for L. RON HUBBARD Founder
HCOB 23 Jun 80 CHECKING QUESTIONS ON GRADES PROCESSES:
The routine questions or commands of the grades processes, including the expanded grades processes, are not checked for read before running them. (This includes, of course, Objectives and Self Analysis list commands and questions.)
The reason for this is that the grades processes are designed to handle those elements and areas of charge which are common to all thetans.
1. When you are selecting something to run on the pc that is handling his individual case manifestations you always check it for read and it must read well before you run it. Not all pcs have "a sharp pain in the left elbow" or are upset by false teeth or have a prepcheck-able item called "reviews" or have an item for "Who or what has suppressed you?".
2. When you are running something that is common to all thetans – i.e., that all thetans have – then the charge is there, though it could take a little while to run the meter action into the process. Probably with the rudiments well in most of the standard processes would read anyhow, if you happened to be looking at the meter. Thus, later in the pc's auditing you can check a previously run grade process for read as an indication of whether or not it is flat.
An example of how all of this data applies on, say, Grade 0, would be:
To run the Process 0-B, you would check the item for read before using it in the blank in the command. But you wouldn't check "communication", find no read and then skip Grade Zero on the pc!
HCOB 23 Jun 80R CHECKING QUESTIONS ON GRADES PROCESSES:
Revised 25 Feb 1982
EACH GRADE PROCESS, THAT IS RUN ON A METER, MUST BE CHECKED FOR A READ BEFORE IT IS RUN AND IF NOT READING, IT IS NOT RUN AT THAT TIME.
HCOB 23 Jun 80RA CHECKING QUESTIONS ON GRADES PROCESSES:
Re-revised 25 Oct 1983
(The original version of HCOB 23 June 80 incorrectly stated that an auditor was not to check the processes of a grade for read before running them. That HCOB was then canceled on 25 Feb. 82 and it remains canceled. The person who had originally approved – and even taken part in writing – this incorrect and illegally issued HCOB later sought to cover these actions by "discovering the error," attributing it to someone else, and "calling it to my attention." With this re-revision, all earlier text written by others has simply been removed and further HCOB references have been added to the list above.)
EACH GRADE PROCESS THAT IS RUN ON A METER MUST BE CHECKED FOR A READ BEFORE IT IS RUN, AND IF NOT READING, IT IS NOT RUN AT THAT TIME.
You can now chose what bulletin is correct. We have two contra and two pro.
Note: All auditor being in business before 1980 confirmed clearly that grade processes have not been checked for read!
With the above we have a change of viewpoint: THE METER IS USED TO QUIT AN ACTION NOT TO GIVE THE PERMISSION TO START IT. The meter is used to see if you have got it all and you don't let the pc with BPC. "Today Tech" is that you don't ask anything unless the meter gives you the permission.