I have brought the Model Session up to date, including “withholds” and changing “we” to “I” and “the” to “this” session throughout to reduce randomity. I have also added the proper processes to run at Rudiment level.

A Model Session is a Model Session because of its “patter”, not because of specific processes. This is a handy script of the “patter of a Model Session”. Use it. Don’t vary it. Know it by heart. It is the mark of a well trained auditor. By making all patter the same, later sessions run out earlier sessions.

This does not enjoin against two-way comm; but reduce auditor comments and chatter in sessions, if you want smooth results and no ARC breaks.

Auditor: “Is it all right with you if I begin this session now?”

Pc: “Yes.”

Auditor: Acknowledges. “Start of Session!” (Tone 40)

Note 1: If pc says “No”, Auditor two-way comms concerning objections, then asks again, “Is it all right with you if I begin this session now?”

Note 2: If pc is doubtful as to whether the session has started:

Auditor: “Has this session started for you?”

Pc: “No.”

Auditor: Acknowledges. “Start of Session!” (Tone 40) Then, “Now has the session started for you?”

If pc still says “No”, the Auditor 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.

Auditor: Acknowledges. “Are there any goals you would like to set for life or livingness?”

Pc: Answers. Auditor: Acknowledges.

Auditor: “Is it all right to audit in this room?”

Note 3: If not, use TR 10 (see Note 15) or pc’s Havingness process.

Auditor: “Is it all right if I audit you?”

Note 4: If not, clear objection, or use TR 5N (see Note 16) or “Who should I be to audit you?” or “Who am I?” depending on nature of difficulty. If TR 5N seems to worsen the ARC break, run O/W on Auditor (see Note 17).

Auditor: “Are you withholding anything?”

Note 5: If so, get withhold off or run Presession 37 (HCO B Dec 15, 1960).

Auditor: “Do you have any present time problem?”

Note 6: If so, clear problem, or use “What part of that problem have you been responsible for?”

Auditor: “Now I would like to run this process on you (name it). What would you say to that?”

Pc: Answers.

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

Pc: Answers.

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 7a: The cyclical ending is only used on terminals that exist also in present time, or 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.

Auditor: Gives command.

Pc: “I don’t know. I can’t find and answer.”

Auditor: Acknowledges. “I will repeat the auditing command.” Repeats the command.

Note 8: If pc still cannot answer, two-way comm to discover why.

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: “Do you have any present time problem now?”

Note 9: If so, run “What part of that problem have you been responsible for?”

Auditor: “Are you withholding anything?”

Note 10. Pulls withhold or runs Presession 37.

Auditor: “How do you feel about my auditing in this session?”

Note 11: Use only TR 5N or O/W on present auditor, “What have you (done to) (withheld from) me in this session?”

Auditor: “Look around here and see if you can have anything.”

Note 12: Run TR 10 or pc’s Havingness process.

Auditor: “Have you made any part of your goals for this session?”

Note 13: Auditor may remind pc of session goals if pc can’t remember them.

Auditor: “Is there anything you would care to say or ask before I end this session?”

Note 14: Auditor may show pc relative TA positions reached in session or tell pc what he cares to know about session.

Pc: Answers.

Auditor: Acknowledges. “Is it all right with you if I end this session now?” Pc: Answers.

Auditor: Acknowledges. “Here it is. End of Session!” (Tone 40) Auditor: (Optional) “Tell me I am no longer auditing you.”

Pc: “You are no longer auditing me.” Auditor: Acknowledges.

Note 15: Commands of TR 10: “Notice that (room object).”

Note 16: Commands of TR 5N: “What have I done to you?” “What have you done to me?” alternated. “In this session” may be added if auditor-pc have long known each other.

Note 17: Commands of O/W: “What have you done to me?” “What have you withheld from me?” or in general form if pc berates auditors, “What have you done to an auditor?” “What have you withheld from an auditor?” or if the pc has been psychoanalyzed heavily, “What have you done to a practitioner?” “What have you withheld from a practitioner?”

Note 18: Present Time Problem for the purpose of rudiments must be what is called “a problem of short duration”. A problem of long duration (such as a goal or psychosomatic difficulty) is not handled as in rudiments but in proper session and will emerge in the normal course of assessing S.O.P. Goals.

Note 19: If any rudiment difficulty can be blown with a very small amount of two-way comm, no process is run.

Note 20: Only the meter reaction shows if the environment, ARC break, withhold or PTP is still in existence. In all questions of whether something is blown or not or if a terminal is flat or if the process is flat, take what the meter says if it is different from what the pc says. The meter knows even if the pc says something else.

Note 21: After running a process on a rudiment because a meter reaction showed it should be run, always ask the rudiment question again before bridging to end the process. If it still reacts, audit the process further. Do not abandon a rudiment until the meter gives no reaction to the question.

Note 22: Always get an answer to every auditing command.

Note 23: Never expect two answers for one question even in doing an assessment.

Note 24: It is not obligatory for the pc to actually set goals. He must always be asked. He cannot be forced to do so. Ordinarily when he does not care to set goals for this part of the rudiments, he is suffering from an ARC break.

Note 25: Follow the Auditor’s Code.