Русская версия

Search document title:
Content search 2 (exact):
ENGLISH DOCS FOR THIS DATE- Checking Questions on Grades Processes - B800623 | Сравнить
- Checking Questions on Grades Processes - B800623R82 | Сравнить
- Checking Questions on Grades Processes - B800623RA83 | Сравнить

RUSSIAN DOCS FOR THIS DATE- Проверка Вопросов на Процессах Ступеней - Б800623 | Сравнить
- Проверка Вопросов на Процессах Ступени - Б800623R82 | Сравнить

CONTENTS CHECKING QUESTIONS ON GRADES PROCESSES Cохранить документ себе Скачать
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 JUNE 1980
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 JUNE 1980RA
RE-REVISED 25 OCTOBER 1983
RemimeoRemimeo
All AuditorsAll Auditors
C/SesC/Ses
Academy LevelsAcademy Levels
TechTech/Qual
Qual

CHECKING QUESTIONS ON GRADES PROCESSES

(Cancels BTB 22 Oct 1970
Iss I, reissued 1 Aug 74
as BTB, READING QUESTIONS.)

Refs:

CHECKING QUESTIONS ON GRADES PROCESSES

  • HCOB 12 June 70 C/S Series 2 PROGRAMING OF CASES

Ref:

  • HCO PL 17 June 70RB Rev. 25.10.83 KSW Series 5R TECHNICAL DEGRADES
    • HCOB 12 Jun 70 C/S Series 2; PROGRAMMING OF CASES
  • HCOB 19 Apr. 72 KSW Series 8 C/S Series 77 “QUICKIE” DEFINED
  • HCO PL 17 Jun 70R URGENT AND IMPORTANT; TECHNICAL DEGRADES
  • HCOB 3 Dec. 78 UNREADING FLOWS
  • HCOB 19 Apr 72 C/S Series 77; “QUICKIE” DEFINED
  • HCOB 27 May 70R Rev. 3.12.78 UNREADING QUESTIONS AND ITEMS
  • HCOB 27 May 70R Rev. 3.12.78 UNREADING QUESTIONS AND ITEMS
  • HCOB 8 June 61 E-METER WATCHING
  • HCOB 3 Dec 78 UNREADING FLOWS
  • HCOB 7 May 69 IV THE FIVE GAEs
  • HCOB 30 Apr 79 C/S Series 106; AUDITING THE DIANETIC CLEAR
  • HCOB 22 Apr. 80 ASSESSMENT DRILLS


  • When you are picking something to run on an individual that is handling his individual manifestations it must read well before you run it. Items, flows, listing questions (L&N) or other auditing questions directed toward the person’s individual case manifestations are always checked for read before running them. And if they don’t read they are not run. (Ref: HCOB 27 May 70R, Rev. 3.12.78 UNREADING QUESTIONS AND ITEMS and HCOB 3 Dec 78 UNREADING FLOWS.)

    (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.)

    To dispel any uncertainty or confusion on the part of any auditor or C/S in regard to how the above data relates to the handling of the routine questions or commands of the grades processes, the following is to be made broadly known and adhered to:

    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.

    RULE

    This rule applies to subjective grade processes. It does not apply to processes that are not run on a meter such as Objective Processes or assists (except for metered assist actions of a subjective nature).

    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.)

    Actually, a process that “doesn’t read” stems from one of three sources: (a) the process is not charged; (b) the process is invalidated or suppressed; or (c) ruds are out in session.

    The reason for this is that the grades processes are de­signed to handle those elements and areas of charge which are common to all thetans.

    Factually, pc interest also plays a part in this.

    The only exceptions to the above rule would be:

    I think quickying came from (1) auditors trying to push past the existing or persistent F/Ns or (2) auditors with TRs so poor that the pc was not in session. Nearly all grade processes and flows will read on pcs in that Grade Chart area unless the above two conditions are present.

    A. Where the checking of the question for a read is expressly designated as a part of that individual technique, or

    One also doesn’t make a big production of checking, as it distracts the pc. There is a system, one of many, one can use. One can say “The next process is (state wording of the auditing question)” and see if it reads. This does not take more than a glance. If no read but, more likely, if it isn’t charged, an F/N or smoothly null needle, one hardly pauses and one adds “but are you interested in it?” Pc will consider it, and if not charged and pc in session, it will F/N or F/N more widely.

    B. On listing (L&N) questions such as on the main Grade III and IV Listing Processes.

    If charged, the pc would ordinarily put his attention on it and you’d get a fall or just a stopped F/N followed by a fall on the interest part of the question.

    The Grade Chart was released as a result of thorough and painstaking research carried out over a number of years. The program it lays out is the basic program for any and every case, The fact that a routine grades process question may not read when first given to a pc does not mean there is no charge on the question. Nine times out of ten it means only that it will take a bit of time for the pc to get into the process and contact the charge that is there. It could mean that the ques­tion has not been properly cleared and thus is not fully under­stood by the pc. The initial action is, of course, to ensure that the pc does understand the question or command. But the auditor does not check a routine grades process command or ques­tion for read before running it, other than as noted in the exceptions listed above.

    It takes pretty smooth auditing to do this and not miss. So if in doubt, one can again check the question. But never hound or harass a pc about it. Inexpert checking questions for read can result in a harassed pc and drive him out of session, so this auditing action, like any other, requires smooth auditing.

    To summarize:

    L. RON HUBBARD
    Founder

    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?”.

    LRH:rw.iw.gm

    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 pre­viously 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!

    The Grade Chart is the basic program for any case.

    To omit whole segments of it because the data in this issue is not fully understood is to deny the pc the awarenesses and regained abilities that are vital to his progress up the Bridge and the attainment of OT.

    All the processes of a grade are run on the pc until the pc has honestly achieved the end phenomena for that grade.

    That is how we get a pc up the Bridge to OT.

    L. RON HUBBARD
    Founder
    LRH:dr