Present Time Problem
The next rudiment to check is 'PTP', Present Time Problem.

Problem means: Two opposing intentions resulting in a conflict. Two opposing goals or any two things, one versus the other, resulting in a conflict that worries the pc.

A Present Time Problem (PTP) means: A special problem or situation upon which the pc has his attention fixed. It can be any set of circumstances the pc feels he should do something about rather than be audited.

Examples: The pc can not have his attention on his own case comfortably because his car is illegally parked; maybe he has a situation at work and he feels he has to do something about right now! His attention is fixed 'over there' and it violates being in-session.

In case of the parking situation it is better to let him handle it. Simply end off and let him repark the car so it is legal and come back and be sessionable.

In most situations his attention is fixed on something reactively. The right action is then to audit the rudiment.

The 'PTP' Question is:

1. DO YOU HAVE A PRESENT TIME PROBLEM?

2. If you have an instant read on the question or on pc's statement of one, you take it up.
You have the pc tell you about it - enough for you to see the situation.

3. If no F/N VGI's you go earlier similar:

"IS THERE AN EARLIER SIMILAR PROBLEM?

4. You have pc tell you about that problem. If no F/N you follow it earlier similar until you get F/N and VGI's.

A Missed Withhold   is a withhold being  restimulated by  somebody else -  here the man  coming by.

Missed Withhold
The third rudiment checked is 'M/W/H', Missed Withhold.

First some definitions:

Overt Act: 1) A harmful act committed intentionally to solve a problem.
2) An act of commission or omission which does the least good for the least number of dynamics, or the most harm to the greatest number of dynamics.
3) That action or thing you do or did which you aren't willing to have happen to yourself.

Withhold: An unrevealed harmful act. The pc did something 'bad' and now he keeps it secret. An overt act the pc did that he doesn't want to talk about. An embarrassing secret.

Missed Withhold: This is a 'nearly found out' or 'wonder if he knows'. It takes another person to miss a withhold. The pc has a withhold which another person nearly found out about. Now the pc wonders whether his withhold is known or not.

A pc with a missed withhold is not honestly 'willing to talk to the auditor' and thus not in-session. The M/W/H needs to be pulled before he can talk freely to the auditor.

It is important to be good at cleaning up missed withholds. Missed withholds is what is behind all ARC breaks. If the auditor doesn't pick up the M/W/H's or only gets part of a M/W/H the pc won't be in-session.

Pc critical:  Check for M/W/H's	Pc Exhausted: Check for M/W/H's

There are some clear symptoms of the pc having M/W/H's:

Pc is not making progress or lack of results. Pc is critical of auditor or auditing. Pc keeps making snide remarks about auditor or anybody else (meaning that person missed the withhold). Pc angry at the auditor or refusing to talk to him. Pc is trying to avoid getting audited. Pc telling others 'auditor is no good', being critical of ST, the course and the people involved with it. Pc demanding to be compensated for 'wrong actions' (demands free auditing, refund, etc.)
Also: pc feeling foggy or exhausted at session end. Pc's havingness going down.

You see it is important to handle these things first. So the auditor must keep an eye on pc's indicators and handle any signs of missed withholds.

The auditor uses the following system to get a missed withhold and get all of it.

(c) Is that all of the WH? (make sure to get all)
(d) Who missed it?
(Sometimes you can get an F/N on 'Who missed it'. You would indicate that F/N, but you would still ask the next question, 'what did he/she do'. This would usually cause the F/N to widen and blow the withhold completely.)

Make sure you get all the persons who missed it and repeat (e) on each. You can use 'suppress' button on (d) when needed:

3. Clean (2) to F/N VGI's. If no F/N you take it 'earlier similar':

You handle each Earlier Similar M/W/H with Step (2) until you get an F/N.

Suppress Button
If a rudiment question doesn't read but doesn't F/N either you can use the 'Suppress Button'.

Example: "Do you have an ARC break?" 'X' (= no read).
Ask: "On 'Do you have an ARC break' has anything been suppressed?" 'SF'
That is a valid read and you handle the ARC break rud per steps above.

Example: "Do you have a Present Time Problem?" 'X'

Ask: "On 'Do you have a Present Time Problem' has anything been suppressed?" 'F/N'.

You got an F/N on the question and the rudiment is 'in'.

Example: "Has a Withhold been Missed?" 'tick' (not a valid read, but a sign).

Ask: "On 'Has a Withhold been Missed' has anything been suppressed?" 'SF'
That is a valid read and you handle M/W/H per steps above to F/N VGI.

Example: You handled M/W/H's to F/N VGI's at the beginning of session. Pc keeps being critical of what you do. Pc is not in-session. Your first duty is to have the pc in-session so you check:
"Has a withhold been Missed" 'tick'
"On 'has a withhold been Missed' has anything been suppressed?" 'SF'
You now handle this M/W/H per steps above to F/N VGI's. You may even have to find additional ones to get the pc in-session fully.

False Button
You can also run into the situation where you get a false read. When asking 'Do you have a PTP' (SF) the pc thinks 'No' and that can be the read.

If your pc seems to protest, seems puzzled or surprised you will have to check the 'False' button:

"Has anyone said you had a Present Time Problem, when you didn't have one?"

You ask for or get : 'Who', 'What', 'When' and take that question E/S to F/N VGI's.
When you have F/N VGI's you are normally done with the ruds.

The End Phenomena on Ruds
The purpose of rudiments is only to get the pc in-session. You are not trying to bring about a major change. When you see the FN VGI's, that's it. You are not looking for a cognition or anything else.

During Session Out-Ruds
If the auditor sees any manifestations during the session of 'Out Ruds' he does not need a special C/S instruction to handle that.

The auditor's starting point is having the pc in-session. If the auditor perceives, the pc is not 'interested in his own case and willing to talk to the auditor', the auditor should suspect an out rudiment and can simply check for it. As described above each rudiment has its special manifestations or symptoms.

Usually the auditor will have a C/S instruction like:

1. Fly a Rud to FN
2. Do a major process.

The auditor will check each rudiment and take up the first reading one and take it to F/N VGI's.
Now the pc is assumed to be 'in-session' and he can begin to run the major process.

If the 'Ruds go out' during session, meaning distractive things make the pc go out of session, the auditor should notice and handle it right there and then by checking the rudiment he suspects out.

The major process can of course bring up Problems, ARC breaks or WH's and as long as pc is running the process and in-session you just continue.

For pc's that are new or haven't been audited for a while it is common to check all ruds.

You can have a C/S instruction like:

1. Fly each Rud to FN
2. Do a major process.

In this case the auditor will check each rudiment and take up the first reading one and take it to F/N VGI's.

Now he rechecks the remaining ones until he has a F/N on each of the rudiments questions.

High or Low TA at the Start
You don't fly rudiments on pc's with the TA above 3.5 (high) or below 2.0 (low).

The first thing to find out in this case is, if the pc has False TA. (See the False TA chapter and checklist).
You can check the hands for being too dry or wet and remedy it. Also check the size of cans.
If the TA is easily brought into range you can go ahead. If the TA stays high or low the rudiments are not the right thing to do. You need a new C/S instruction.

Pc's with chronic high or low TA (that isn't false) need to be audited on a correction list. As an auditor you simply write up your full observation and end off.

It is up to the C/S to look over pc's auditing folder and history and decide how to handle. It may require a higher classed auditor, typically a ST Level 3 auditor.

There is a correction list called C/S 53, High-low Ta handling that is most commonly used to handle this.

Floating Needles with VGI's are valid at any TA position. But since high or low TA (not false) still means mental mass on the case in restimulation it needs to be addressed with the right process or list.

This mass will be 'something else' that is on the pc's mind and not being addressed with the rudiments or major process. It needs to be addressed and handled.

The general rule of auditing is, handle what is already in restimulation. When this is done, use a process to restimulate a specific area of pc's case and handle that restimulation to EP.

Handling what is already in restimulation keeps the pc a little ahead of life and what is happing around him. The ruds are an important part of that.

Using a major process to restimulate a specific area and handle it is what makes up for permanent gains and increased ability, awareness and freedom.

Flying the rudiments first enables the auditor to advance the case as the pc is now in-session and benefiting from the major process.

Part of Auditor's Code is:

You do not leave that up to chance or assume he understands every word you speak. You should rather assume he doesn't.

Therefore: You clear the commands

Each time you take up a new process or if the pc seems confused about a command (you assumed already cleared) you need to ensure:

1) that pc understands each word in the command

2) that pc understands what the whole command means.

To do this you need to have different dictionaries with you.

You clear each word (using a dictionary if needed) with pc and then ask him what the command means.

You never tell a pc what the words or command means. To do that would violate Auditor's Code #1:

Using Dictionaries
You need a selection of good dictionaries in the auditing room. This you need to arrange that beforehand.

What you want are a dictionary that give full definitions - not just synonyms. You can find dictionaries that use simple terms to explain difficult words; those are the best. The two volumes 'World Book Dictionary' is a good example of that.

You also need a technical dictionary of auditing terms, 'Technical Dictionary of Scn'. There is also a word list in the back of this manual that can be used.

If you audit in another language than English you need a dictionary in that language, that actually explains the words - not just synonyms.

In case you audit a foreign language pc, but do the auditing in English, you need an English - foreign language dictionary, and a own language - own language dictionary.

Example: You audit a German pc in English. He needs to look up the word 'Horse'. You look it up in a English - German dictionary and find 'Pferd' for Horse.

Now you have your German pc look up 'Pferd' in a German - German dictionary.

You have the pc on the cans while clearing words. You, the auditor does the looking up and place the dictionary so he can read the definition.

You have him read the definition of 'Pferd' and clear it to F/N.

Have him use the English word 'Horse' in English sentences until he has an F/N.

You clear the words of the command backwards so he doesn't easily pick up the meaning of the whole command and start to think of answers.

Same Language PC
Here is how you clear commands on a same language (English) pc:

Example: You are clearing the command "Do horses run?"

You ask pc: "What does the word 'Run' mean?"

Pc tells you and has an F/N. (You indicate the FN)

Then you ask: "What does the word 'Horse' mean?"

Pc is not sure, so you look it up in an English - English dictionary.

You open the dictionary to 'Horse' and show him the definition. If more than one definition you need to show him which one applies in the command.

You have him read it and use examples until he has an F/N. Pc is on the cans all the time. (you indicate F/N's).

Then you ask: "What does the word 'Do' mean?"

Pc tells you and it F/N's (indicate FN).

Now you clear the command. You need to keep an eye on the Meter as an instant read on clearing commands is a valid read.

You ask: "What does 'Do horses run' mean to you?"

If pc has difficulties with it you re-clear the obvious word(s).

Have him use it in a sentence until he gets it.

You never replace words in a command to 'make it easy', because that would leave the misunderstood word in place.

Finally you can ask him without any misunderstoods in the way:

"What does 'Do horses run' mean to you?"

You notice any instant read on: 1) You stating the command, or 2) on pc telling you what it means.

If none, you check the command:

You say while looking at the needle:

"Do horses run?" X (no read)

On 'Do horses run' has anything been suppressed?" X (no read)

"On 'Do horses run' has anything been invalidated?" F (it reads)

You have put in the 'Suppress' and 'Invalidate' buttons and gotten a read.

You are not interested in what the 'Invalidation' is. You are only interested in 'Read' or 'No read'.

You would probably be able to get a read on 'Do horses run' if you checked again. But you simply realize that the read on the button tells you the item was charged and you have your item.

You say: "We are going to run this process"

"Do horses run?"
etc.

If you don't get a valid instant read on the actual command or buttons you go on to the next process.

Clearing Words and ARC Breaks
If you have an ARC broken or upset pc you don't clear the words first. You go ahead and handle the ARC break.

To clear the words would be 'auditing over an ARC break' which you don't do. You can ask for misunderstood words after the upset is handled and clear them up then. Better is to clear words for such lists early on in auditing.

Clearing Words in Advance
Usually you clear the words for one process and then clear the command and check and run it (if charged).

It is however a good idea to clear all the words for correction lists as a long list of words in advance, including lists for handling ARC breaks.

All these words only need to be cleared once and you should note in the folder summary when it is done.

The pc should have a Yellow sheet in the back of the pc folder that keeps track of lists cleared. The lists are usually needed when the pc is in trouble and you don't want to complicate it with having to clear a lot of words in those situations.

The following check list covers the things the auditor should prepare for beforehand and do up to the point he starts the session. To be fully prepared accounts for minimum interruptions and a more professional performance and appearance as an auditor.

1. Get pc's folder and any back folders needed.
2. Study the folder so you are familiar with the case.
3. Make sure you have a C/S for the session and you know what to do (do any study action needed).
4. Make sure you have a confirmed appointment and enough time to do the session.

The Room
5. Clean up the room
6. Make sure it's aired out and temperature is comfortable.
7. Make sure area is quiet and uninterrupted for the session and have a 'IN SESSION - DO NOT DISTURB' sign to hang on the door.
8. Make sure table and chairs are sturdy and comfortable.
9. Make sure the lighting is right.
10. You may need a quiet clock if one is not built into your Meter.
11. Have a blanket in the room (if pc cold).
12. Have fan or air conditioning in case it gets too warm.
13. For pc you need Kleenex napkins.
14. You need to have hand cream and anti-perspirant and different sized cans in case of false TA.
15. Make sure you have the needed dictionaries, including Scn Technical Dictionary and also a grammar book to clear up the small words.
16. Make sure you have all the lists and forms that could be needed - including the auditing commands for the session.

Meter Ready?
17. Ensure your Meter is in good repair and fully charged. You need a spare can lead.
18. You need to have a Meter shield (to obscure Meter from pc).
19. You may need a plastic bag to put over the pc's one hand in case pc knocks cans together.

The PC
When pc comes in:

20. Make sure the 'IN SESSION' sign is on the door.
21. Make sure any phone is shut off.
22. Have pc seated and check chair is comfortable or do adjustments.
23. Check with pc if room is OK or adjust so it is.

*Meter Check
24. Turn Meter on and check for fully charged.
25. Trim the Meter 2.0=2.0
26. Connect the cans and put them in front of pc.
27. Have pc pick up cans and adjust sensitivity to 1/3 dial drop on can squeeze (EM-5A).
28. Do any false TA adjustments needed (cream, anti-perspirant, tight shoes or clothes etc.)
29. Have pc take a deep breath and let it out - the metabolism test; it should give a latent Fall (EM-5B).
30. Check that pc has had enough sleep.
31. Check pc isn't hungry.
32. Check for alcohol or drugs if needed.
33. Ask pc: "Is there any reason not to start the session?"
34. if not, say: "This is the Session!".

Model session is the session form. An exact pattern or script is followed as it makes session predictable to the pc.
Also following an exact pattern and using the same words to open, continue and close a session and to begin and end processes with , causes a duplication of sessions which tends to run them out. In other words sticking to the same form causes better session control and less bad effects from unsuccessful sessions on the pc.

1. Check List
The auditor has already done the steps of the 'Check list for session' above.

He makes sure to seat the pc in the chair furthest away from the door.

He is asked to pick up the cans and stays on the cans until 'End of session'.

He has asked pc if there is any reason not to start the session and has done any final adjustments.

2. Starting Session
The auditor says with full intention (Tone 40):

"This is the session"
(he writes time and TA).
If the pc has F/N and VGI's he can go onto the major action. If not he fly the ruds:

3. Rudiments
The rudiments are done per earlier this chapter.

When auditor has a pc who is F/N VGI's on rudiments he can go on to the Major Action.

4. Major Action of Session
A. Auditor tells very briefly ('R-factor') what is going to happen:

B. The commands are cleared per earlier this chapter.

C. The auditor does the C/S instructions for the session and makes sure to end off with EP and complete a process if he can't do it all in one session.

5. Havingness
Sometimes the C/S instructions will include, "Run havingness as needed".

Havingness is a little type of process that gets pc back and oriented in present time after a session. It usually only takes 10-12 commands to do. EP of a Havingness process is F/N VGI's and pc in present time.

6. End of Session
When the auditor is about top end the session he says (R-factor):

"We are going to end session shortly"

and goes ahead and asks:

"Is there anything you want to say or ask before we end session?"

Auditor acks anything the pc has to say. If the pc has questions, the auditor says:

"I'll note that question down for the C/S"

When this is covered, the auditor ends the session by saying:

This is said with full intention (Tone 40) as to really mark a clear end.

If there is an Examiner available the auditor takes the pc to the Examiner.

Running Havingness
As mentioned in (5) above, the C/S instruction can include "Run Havingness". This is a little remedy.

The As-is of mental mass means the pc 'lost' some mass he was used to experience. The remedy is easy and can be done at any point between processes or - more commonly - at the end of a session. You actually don't need a C/S for it.

You should do such a check at the beginning of a new auditing activity. Then you will use the Havingness process found, until you suspect it is unworkable. If you suspect that, you test another process the same way.

The EP is simply: PC in present time with VGI's and F/N.

It's a very simple action. The same process as a remedy can be used many times.

Some More Theory
Havingness is apparently the willingness and ability to duplicate in all meanings of the word.

That which makes communication work in auditing is the duplication part of the communication formula (Axiom 28). The position of a pc on the tone scale is determined by his willingness and ability to duplicate. The lower the tone of the pc is, the less willing he is to permit a similar experience to happen again. It makes him less willing to duplicate and experience, and leaves him with an "experience scarcity"; it causes him to refuse further experience.

All this is remedied fully in Objective Havingness Processing, like the CCH's -- The CCH processes (Communication, Control, Havingness) which also contain the full theory of Havingness (ST level 1). As havingness can be defined as the willingness to duplicate, then anything which improves the pc's ability to duplicate improves his or her havingness.

"Point out something."
"Look around here and point out an effect you could prevent."
"What is the emotion of that (indicated object)?"
"Notice that (indicated object)." (No acknowledgment) "What aren't you putting into it?"
"Look around here and find something you could have." "Look around here and find something you could withhold."
Outside process: "What is the condition of that person?"
(Two small objects in auditor's hands.) Exposes them alternately to pc, with as little motion of arms and hands as possible. "Look at this (object) (no acknowledgment). What around here isn't this (object) duplicating?"
"Where is the (room object)?" (Pc points.)
"Look around here and find an object you are not in."
"Look around here and find something you can agree with."
"Point out something around here that is like something else."
"Where isn't that (indicated object)?"
"What is that (indicated object) not duplicating?"
"What scene could that (indicated object) be part of?"
"What bad activity is that (indicated object) not part of?"
"Look around here and find something you could have."
"Point out something in this room you could confront."
"Point out something in this room you would rather not confront. "
"What part of a beingness around here could you have?"
"Look around here and find something you could withhold."
"Notice that (room object). Get the idea of making it connect with you."
"What else is that (indicated object)?"
"Duplicate something."
"What is the condition of that (indicated object)?"
"What is the condition of that person?"
"Notice that body." "What aren't you putting into it?"
"Where would that wall have to be located so you wouldn't have to restrain it?"
"What around here would you permit to be duplicated?" or, "What is the safest thing in this room?"
"Who would that (indicated object) be a good example to?"
"What would you have to do to that (indicated object) in order to have it?"
Notice that (indicated room object). How could you get it to help you?"
"Notice that (room object). How could you fail to help it?"

© Clear Bird Publishing, 2003. All rights reserved. We allow downloading and electronic translations,  duplicate postings to the web, but not printed or commercial editions  without special agreement with the publisher. (About: Clear Bird)    (About: Jonathan Seagull)    Tell a Friend