The exactness required of Modern Processing Checks (Sec Checks), Problems Intensives and 3D assessments and runs have made new demands on rudiments and their processes.
As described in HCO B of Dec 14, 1961, the rudiments questions, beginning and end, are changed in the Model Session Script. The body of the session patter is unaltered.
Model Session is memorized, is used exactly, and is delivered with the TRs in. Model Session is a requisite of an effective session. All auditing and assessing are done in Model Session form and no other. Excellent accurate Model Sessioning is the hallmark of the good auditor.
Auditor sets up E-Meter and adjusts pc’s chair. Any agreement concerning length of time of session is made if there is to be any such agreement.
A session must have “R” or Reality. If the auditor feels ill or weary, or out of sorts or under other strain, the auditor should tell the pc, before session starts, the facts of the situation, giving the pc a chance to accept auditing under those conditions without feeling it is an overt. The time to put the pc’s attention on the auditor is before the session starts, not after it starts. The pc is always quick to scent an upset and if such an upset is evident in session a mystery is created for the pc that will throw rudiments out. Once the “R” factor is handled it is not again referred to in the session by the auditor. This should not be used to upset the pc or make the pc guilty of “the overt of receiving auditing”.
Auditor: “Is it all right with you if I begin this session now?” Pc: “Yes.”
Auditor: Acknowledges. “START OF SESSION.” (Tone 40) Auditor: “Has this session started for you?”
Note 1. If pc says “No,” Auditor: Acknowledges. “START OF SESSION.” (Tone 40) Then, “NOW has this session started for you?” If pc still says “No,” the auditor acknowledges and says, “We will cover it in the rudiments,” and continues the session.
Auditor: “What goals would you like to set for this session?” Pc: Sets goals or doesn’t. Auditor: Acknowledges. “Are there any goals you would like to set for life or livingness?” Pc: Sets goals or doesn’t. Auditor: Acknowledges. (Goals are usually written down by auditor. If list goes beyond ten or twelve auditor gently stops writing and acknowledges.)
Auditor: “Look around here and tell me if it’s all right to audit in this room.”
Note 2. If auditor gets a reaction that is not a body motion on the E-Meter, auditor says: “All right. Thank you. I am going to run some (TR 10 or pc’s havingness process).” And does so. Repeats rudiment question soon. If now nul on meter auditor goes on to 3 below. If not nul, runs more havingness. Etc. The rule is pc should be able to have or observe large objects before havingness is ended. (This is hard to apply on some havingness processes.)
Auditor: “Are you willing to talk to me about your difficulties?”
Note 3. If not, run a current process for this rudiment. Test again with rudiment question. This is not an E-Meter response rudiment but is done by observation of pc. This and 5 in end rudiments are the only rudiments so handled.
Auditor: “Are you withholding anything?”
Note 4. If meter gets instant reaction (only read meters by instant reaction in any case for anything), clear it by getting withholds off. Do not leave any withhold that registers on this rudiment question. If pc will not give withhold, vary the question. If pc still will not, run current rudiments withhold process. Leave this rudiment by asking the rudiment question again and leave it only if nul. An ARC break can also nul meter. If in doubt repeat rudiment 3, straighten up 3 and then repeat 4. A pc who is being vicious to auditor at this stage has one or more withholds.
Auditor: “Do you have a present time problem?”
Note 5. Only if PTP registers on the meter should the PTP be handled. Question can cause an ARC break in a pc anxious to get on and needle can register the ARC break rather than a PTP. In this case clear with two-way comm and repeat PTP rudiment question. If it is obviously a PTP and not an ARC break, do not ask if it is an ARC break. Handle PTP with current rudiment process. When handled, repeat rudiment question. Do not leave unless nul on needle.
Auditor: “Now I would like to run this process on you (name it). What would you say to that?” Pc: Answers.
Note 6. If pc is unwilling to run the process, two-way comm objections away or relieve earlier invalidations of process. Never run a process dictated by pc as this is self-auditing, throws pc out of auditor control and throws out all rudiments. Pcs quite routinely object to certain processes, even though they must be run.
Auditor: Acknowledges. Clears the command for pc only for the first time the command is used.
Note 7. If, during clearing of the command or failure of needle to react, it seems that the pc will not be able to handle or do the announced process profitably, auditor says: “According to what we have been talking about, it would seem better if I ran (name another process).”
Auditor: (Wishing to end process) “Where are you now on the time-track?” Pc: Answers. Auditor: Acknowledges. “If it is all right with you, I will continue this process until you are close to present time and then end this process.” Pc: Answers. Auditor: Acknowledges. Auditor continues the process, asking after each pc answer, “When?” until the pc is close to present time. Pc: Answers close to present time. Auditor: Acknowledges. “That was the last command. Is there anything you would care to say before I end this process?” Pc: Answers. Auditor: Acknowledges. “End of process.”
Auditor: “If it is all right with you I will give this command two more times and then end this process.”
Auditor: Acknowledges and gives the command two more times. Pc: Answers.
Auditor: Acknowledges. “Is there anything you would care to say before I end this process?” Pc: Answers.
Auditor: Acknowledges. “End of process.”
Note 8. The cyclical ending is only used on terminals that exist also in present time, and when pc is going into the past in his answers. It is not used after pc says he is in present time. Non-cyclical is used when the pc is running terminals which do not exist in present time or when the cyclic aspect can be neglected. 3D level runs and Processing Check answers are never given cyclical endings.
Auditor: Gives command.
Pc: “I don’t know. I can’t find any answer.”
Auditor: Acknowledges. “I will repeat the auditing command.” Repeats the command.
Note 9. If pc still cannot answer, two-way comm to discover why. Then get the command answered. Never leave an unanswered command.
Auditor: Gives command.
Pc: (Not having answered command yet.) “Say, that mass in front of my face just moved off.” Auditor: Acknowledges. Repeats command without announcing that it is a repeat.
Auditor: “Have you told me any half-truth, untruth, or said something only to impress me or tried to damage anyone, in this session?”
Note 10. If meter reacts, clear the reaction fully. In a difficulty, compartment the command, clear the reacting part. Do not leave until meter is nul on repeating this rudiment question.
Auditor: “Have you deliberately tried to influence the E-Meter?”
Note 11. If meter reacts, clear it thoroughly, getting, if necessary, the first time the pc tried it. Invalidations of meter will also be present if pc has tried to influence it. These must also be removed with, “Have you ever invalidated the E-Meter?” Also, “Have you ever tried to prevent an E-Meter from reading?” Clear these on needle. Clear rudiment question before leaving. (As in all such checking only vary the command if the pc answers “No” while meter reacts, otherwise ask same question.) Leave when exact rudiment question is nul.
Auditor: “Have you failed to answer any question or command I have given you in this session?”
Note 12. If meter reacts, find the question or command and get it answered. Leave rudiment with same question and only if nul.
Auditor: “Have you withheld anything from me?”
Note 13. If meter reacts, find and clear the withhold or withholds. Vary question only if pc refuses to give up withholds. If pc still refuses, run current rudiments process for this. Do not leave until meter clear on this exact rudiments question.
Auditor: “Are you willing to talk to me about your difficulties?”
Note 14. This is done by observation of pc, not by meter. If the answer is no, run current process for this rudiment. Leave it only when pc is willing to talk to auditor. If a process is run for this rudiment, repeat all end rudiments again.
Auditor: “Look around here and tell me if you can have anything.”
Note 15. If meter shows other than body movement, run TR 10 or pc’s havingness process. Retest the question before leaving this rudiment.
Auditor: “Have you made any part of your goals for this session?”
Note 16. Auditor may remind pc of session goals if pc can’t remember them.
Auditor: “Have you made any other gains in this session that you would care to mention?”
Auditor: “Is there anything you would care to say or ask before I end this session?”
Note 17. Auditor may show pc relative TA positions reached in session and tell pc what he cares to know about session.
Auditor: “Is it all right with you if I end this session now?”
Auditor: Acknowledges. “Here it is. End of Session !” (Tone 40) “Has the session ended for you?”
Note 18. If session has not ended for pc, get pc’s full attention and repeat “End of Session.” (Tone 40) If session still has not ended for pc two way comm briefly to find what pc has been doing. If this doesn’t ease it, say reassuringly, “You will be getting more auditing. End of session.” And leave it at that.
Auditor: (Optional) “Tell me I am no longer auditing you.”
Pc: “You are no longer auditing me.”
Note 19. The auditor has no further obligation to act as auditor when session is ended. However, this should not be used to evaluate for the pc concerning the session. But the auditor need not shun questions the pc puts to him or her directly concerning the auditor’s own reactions in session if these excite curiosity of preclear. This is ‘R’ factor.
Exact Rudiments processes for above will be given from time to time in future HCOBs. During early auditing short session a pc so as to handle fully end rudiments before session ends.
Short sessioning means that two or more sessions can be run in one auditing period.