Recall Processes have always worked well. But it has been hard to get the most fundamental processes that would reach the lowest cases.
Here are some Recall Processes that work way down South of the Auks:
“Recall a Communication”
These are very good, especially on bad off cases. They all work.
When the lowest seems flat one can go to one above. Probably there is an E-Meter tellingness that denotes flatness. I’m working on this and will have the gen soon.
The earliest experiments of this were on “Recall a Mystery” as a method of raising IQ and the pc was spouting poetry he’d “forgotten”.
There are many possible versions of these simplicities as one can run them on terminals and significances. Also, remember that these things (Recall Processes) take the pc out of PT and put him back in. You stop one with the PC back in PT. The Comm bridge to be used on this process is: “When you next get an answer close to present time we will end this process if it is all right with you.” Then don’t go on for an hour or two, catch it with 8 or 10 commands by seeing the pc is doing a short cycle at the time and has started back up.
“Recall Exhaustion” is a simple, very effective version of a work process. “Recall Creating” is a good way, apparently, to mop up Step 6 flubs.
Therefore you can use these processes in the HGC or you can, when it is okayed, use them in training. These are individual processes and not co-audit. As a note on co-audit, the process, the only basic affinity process, “What would you like to confront,” could cut your co-audit attendance losses. It is now allowed, having been carefully tested. Man, do they get interested in cases and hence into session. This is a fine individual process for pcs that “have no reality on pictures”.