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

Search document title:
Content search 2 (exact):
ENGLISH DOCS FOR THIS DATE- Routine 1a - B610706 | Сравнить

RUSSIAN DOCS FOR THIS DATE- Шаблон 1А - Б610706 | Сравнить

SCANS FOR THIS DATE- 610706 - HCO Bulletin - Routine 1A [B001-063]
- 610706 - HCO Bulletin - Routine 1A [B037-047]
- 610706 - HCO Bulletin - Routine 1A [B135-009]
CONTENTS ROUTINE 1A STEPS SEC CHECK RATIO BETWEEN PROBLEM AND SEC CHECK VALUE OF ROUTINE 1A Cохранить документ себе Скачать
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 6 JULY 1961
Franchise

ROUTINE 1A

Here is the first refinement of the Routines.

It sometimes happens that certain auditors cannot get results with CCHs and it also happens that certain pcs have heavy constant problems that prevent SOP Goals assessment, the problems being hidden standards by which all auditing progress is judged.

It also happens that Problems as a subject is the only reason why cases fail to advance (as in rudiments). Therefore problems are probably why some people clear easily and others don’t.

Considerations about the stable datum and the confusion also lead toward the auditing of problems as such. For a problem consists of two opposed stable data and therefore two confusions.

The definition of a problem is “Two or more postulates in opposition to each other”.

Probably all pcs should be run on Routine One. The Change Scale was aimed at handling alter-is in doing auditing commands. Auditing Problems, you will find, cures alter-isness in a case.

The full rundown on the basic Routine 1A was given to the Sthil Briefing Course Students on July 3, 1961, and the tape of this date should be studied for full data on Routine 1A. Routine 1A can however be used without serious consequences and with great benefit without all its data; at least it will get better results than poorly run CCHs and will get results anyway. Try it.

STEPS

Routine 1A only has two steps –

1. Problems

2. Security Check HCO WW Form 3 or HCO WW processing forms.

The original command was “Recall a problem”. This is the fundamental command. A somewhat better command, since it increases ability and does more than merely as-is track, and since it moves pc off the 1st dynamic, follows:

“What problem could you confront?”

“What problem don’t you have to confront?”

“What problem should another confront?”

“What problem wouldn’t another confront?”

“What problem would be confronted by others?”

“What problem wouldn’t others confront?”

Note: The third question may be “What problem could another confront?” also, whichever checks out on meter.

SEC CHECK

This is followed by a Security Check. The Security Check must be an HCO WW Form Sec Check and not a local version ever. A Sec Check is done with a full command of the new book E-Meter Essentials now being mailed from HCO WW. A Security Check is done (and so are goals) only by Instant Read and never by Latent Read. If the needle falls or reacts within a tenth of a second after the question is asked pursue it, for this is an Instant Read. If it doesn’t fall or react for a second or more and then reacts, do not pursue it or do anything about it. This is a Latent Read. Only use the E-Meter if the pc says “No” or disclaims having done it.

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. It’s hot. Always pass them if they only give a latent read. It’s cold or it’s something else. Only use the meter after a pc denies it. Increase sensitivity high, asking question again, before leaving any question which a pc disclaims.

RATIO BETWEEN PROBLEM AND SEC CHECK

Run Problems and Sec Checks one for one in terms of time. But never on the same morning or same afternoon or same evening. Never in the same session. Sec Check mornings, run Problems afternoons. Or vice versa. Or on alternate days. Don’t wait for Problems to flatten before you Sec Check. Problems are a long run. Two different auditors can work on one pc, one at one time of the day, the other auditor at another time of day. The pc may ARC Break if a Problems session is cut off to Sec Check. So Sec Checks are one session, Problems are another session. And spread them apart into different auditing periods.

VALUE OF ROUTINE 1A

Routine 1A should be run on every pc at one time or another when going to or having arrived near clear. It is best run first as it speeds the auditing later, removing PTPs and alter-is of commands… It does not go as far south as the CCHs but almost.

Routine 1A is extremely valuable on any case. It will give you many wins.

I believe at this time, though I have no broad data on it yet, that Routine 1A will speed up cases that are hanging fire or taking a long time to clear. Therefore use it.

L. RON HUBBARD LRH:jl.rd