Note: This issue is by no means a complete summary of the subject of havingness. There is a vast amount of material on havingness and the remedy of havingness in early publications and other HCOBs to be found in the Technical Volumes — data the student will acquire as he continues to train up the levels and on the SHSBC.
This issue is to give the beginning auditor a working knowledge of the subject of havingness.
“HAVINGNESS: 1) that which permits the experience of mass and pressure. 2) the feeling that one owns or possesses. 3) can be simply defined as ARC with the environment… 6) the ability to duplicate that which one perceives, or to be willing to create a duplication of it… 8) havingness is the concept of being able to reach or not being prevented from reaching… 4) that activity which is run when needed and when it will not violently deflect the pc’s attention.” (From the Technical Dictionary.)
The above are all valid, but the final definition of havingness can be simply stated as:
Havingness is the concept of being able to reach. No Havingness is the concept of not being able to reach.
Inherent in the ability to reach is the willingness and ability to duplicate. That which makes communication work in processes is the duplication part of the communication formula (Axiom 28 Amended).
The position of a being on the Tone Scale is determined by his ability to reach (and thus his willingness and ability to duplicate, to communicate and experience). The lower the tone of the being the less willing he is to reach, communicate with and experience his present time environment, and the less willing he is to reach and duplicate events of the past or permit them to happen again.
This is remedied by Objective Havingness Processes. These are processes that deal with observing and touching objects in the auditing room or in the environment. They are “look around” or physical contact processes, used to remedy a low or “no havingness” condition.
Thus we find the pc’s Havingness Process early on in auditing and use it to gain or remedy havingness before or after processes or at session end.
The preclear’s Havingness Process is tested for on the meter in an exact way. You test it on the needle with can squeezes from the pc.
Use HCOB 6 October 1960R, Revised 8 May 74, “Thirty-Six New Presessions.”
1. Set the sensitivity for 1/3 of a dial drop when the pc squeezes the cans. (See E-Meter Drill 5, The Book of E-Meter Drills.)
2. Run 5 to 8 commands of the first Havingness Process on the above bulletin, with the pc on the meter.
3. Then have the pc squeeze the cans, noting the size of the needle read now. If this second can squeeze shows the needle looser (wider swing) than the first can squeeze did, you’ve got it. The Havingness Process you’ve tested is the Having-ness Process for the preclear and may be used to remedy his havingness as necessary.
4. If the process tightens the needle during the test, don’t use it. Don’t bridge off. Just get off the process now and test the next process, or the next, continuing until you find a Havingness Process that does loosen the needle and gives a wider swing. One will be found among the list of Havingness Processes on HCOB 6 Oct 60R.
5. The correct Havingness Process selected is then run 10 to 12 commands at a time, usually just before ending off a session.
A pc’s Havingness Process can change as the pc changes with auditing. If at some point in the auditing the Havingness Process which has been being used fails to get the desired result, simply re-test for a new Havingness Process, find one that works and use it.
Even the right Havingness Process, if run too much at one time (more than 10 or 20 commands) will start running the bank. It doesn’t harm the preclear but that isn’t its use, as there are other processes that run the bank better.
The purpose of a Havingness Process is to get the preclear stabilized in his environment.