Ref:

Ref:

• HCOB 12 Jun 70 C/S Series 2; PROGRAMMING OF CASES

• HCOB 12 Jun 70 C/S Series 2; PROGRAMMING OF CASES

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.

I believe that the HCOB in question, HCOB 23 Jun 80 has created an Out Tech situation of pcs being run on unreading processes on Grades, leading to PC protest, out of session-ness and a tendency on some auditors' parts to cease to expect a process EP! Though the issue was purported to be a handling of quickying, it gave rise to quickying.

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:

A process or question or command can be suppressed or invalidated which would prevent a read and could cause a miss if these buttons were not gotten in.

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

A process that has been started but left unflat (not taken to EP) may no longer read on the process question but would read on unflat? or incomplete?

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.

These rules apply to subjective grade processes; they do not apply to processes that are not run on a meter such as objective processes or assists (except for metered assist actions).

The only exceptions to the above rule would be:

It is a Gross Auditing Error to run an unreading Grade process on a pc; it is also a Gross Auditing Error for an auditor to miss reads on processes or questions and so not run them. A C/S seeing too many processes or questions said to be unreading should suspect that the auditor's metering is out and get it checked in Cramming. If found to be out, order a retread or retrain of the E-Meter Drills and put the auditor through the drills given in HCOB 22 Apr 80, ASSESSMENT DRILLS.

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

Actually, a process that “doesn't read” stems from three sources: (a) The process is not charged; (b) The process is invalidated or suppressed or (c) Ruds are out in session.

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

Factually PC interest also plays a part in this.

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.

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.

To summarize:

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.

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

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.

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.

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.

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.