The hardest thing perhaps for a beginning Class VI Auditor to accept is that he or she must get a proper identification of What The goal is.
Experience will eventually make a citizen out of the auditor on this subject. After wrapping a pc around a few telegraph poles with wrong goals and a bad goals plot the auditor, now in shock, realizes the terrible importance of proper Goals Identification,
But why wait?
There are two reads, both important. Each must be a good fall or RR, 2" or 3" long.
To be given any attention or Identification drill a goal must read. This can be a l” chug or a fall or RR. But it must read. If the goal has been suppressed or wronged, if it is charged, the “suppress” or “wrong” buttons will produce a l” to 3" read. (The goal charge transfers to “suppressed” or “invalidated”). Thus either by itself or suppress or invalidate, a goal must read or must have read to be given any identification drill.
Any goal that has read must now be identified. What is it? This read must be a long fall or RR - a sizable read - not a tick or a 1/4” flick. This is the IDENTIFICATION READ.
To be accepted or discarded, a goal must have (1) A goal read and (2) An Identification read.
It is (2) The Identification Read that auditors neglect, don’t believe in, become upset about. And yet lack of it is the only real way to wreak a pc. Of the two the Identification Read is the more important.
New pcs grow resistive. They don’t believe the Identification Read is important either. So they protest and sell and gum their meter up. “It’s my goal so why - etc., etc.” So the auditor, nervous about an ARC break, comes off Identification without finding out what the goal is, gives it to the pc AND THEN WONDERS WHY THE PC STARTS GOING TO PIECES. It is not kind, it is very cruel indeed for the auditor to skip Identification.
Another way an auditor gets around it is to take reads on what the pc says, not what the auditor asks.
BOTH GOAL READ AND IDENTIFICATION READS MUST BE TAKEN ONLY WHEN THE AUDITOR SAYS IT. The read must occur on the auditor’s call, not the pc’s. The read when the pc says it must repeat when the auditor says it or it isn’t true.
A new Class VI auditor runs out of questions in Identification. His knowledge of track is not up to really identifying the goal and so the new auditor comes to believe that Identification reads are impossible to get and so stops trying or blames the pc’s metering. It isn’t ever the pc’s metering. It’s lack of auditor knowledge and persistence.
The session tape of March 18, 1964 has a lot of Identification Drill on it. In each case the goal was made to read a nice long fall on what it was. The drill is not a pattern, or an assessment list.
Here are some questions for Identification:
The above are the basic questions. An auditor should be able to rip them off in a torrent and vary them.
Two long falls is enough to identify. And there is always a long fall available, believe it or not.
If it falls well on “correctly worded Actual GPM” that’s it. You go no further. But if it doesn’t, you must find out why it read.
ANY GOAL THAT HAS A READ WILL READ HUGELY ON WHAT IT IS IF YOU ASK THE RIGHT QUESTION.
To identify a goal puts the pc at ease and completes the cycle of action of the checkout.
It should take only two or three minutes.
It can get bizarre when standard questions fail. Then knowledge of the pc counts. Knowing the pc had had a life in Punjab, on the 18th March session tape, I asked if “To be untouchable” was “An Indian idea” and got the first long fall after all else had failed to identify.
The main reason some auditors will have trouble with Routine 6 will be their disbelief in the necessity to identify a goal well by getting a long read. These auditors will have ARC breaky pcs very soon, will be balked and will be in endless trouble.
The severest lesson R6 teaches, no matter what I say, is the necessity to identify goals.
You can suppress a goal and ARC break a pc, as you’ll find on the 18th March 1964 tape, by failing to give the pc a right goal. But that’s far far preferable to an apathetic shoveling out of anything that has a goal read. That way lies death.
The pc new to R6 gets impatient. He or she only needs to experience the horror of a few wrongly identified goals to become quiet as lambs during the identification step.
When Identifying, keep the pc posted. “That didn’t read.” “That ticked.” “That’s a long fall.” And then say to the pc what fell, “To Woof reads as a lock on an Implant GPM.”
If it’s a correctly worded Actual Goal get it in the bring about steps (and oppose if any) and get a fall on the number and then give it to the pc. “Is that your goal?” “That’s your goal.”
Failure to learn the knack of Identifying goals debars the R6 auditor from any success.
Failure to accurately Identify goals that get read sets the pc up for catastrophe. R6 moves smoothly only when goals found are properly identified by a big read.