(Reference:
Axiom 30: "The general rule of auditing is that anything which is unwanted and yet persists must be thoroughly viewed, at which time it will vanish. "
Excerpt from Axiom 38: "… Truth is the exact time, place, form and event… Thus we see that the discovery of Truth would bring about an As-is-ness by actual experiment. "
A thetan knows that if he could remember the exact place a thing had been generated, the exact time and the exact conditions, and the exact person who did it, he would then get a disappearance of the thing.
Dating is the action the auditor takes to help the pc spot the exact time something happened.
Locating is the action the auditor takes to help the pc spot the exact place something happened.
By dating and locating, getting the exact time and place a specific thing happened, the pc is able to blow the mass and energy connected with the occurrence which has hung him up at that point.
Date/Locate, as called for in the various prepared correction lists, is a very effective tool for the handling of certain items found to be out on such a list. These could be points of overrun, wins that have been bypassed or invalidated in some way, moments of loss, trauma, painful emotion, or any of various stuck points of this nature. It is also used in the correction of wrong dates or wrong locations given the pc in previous auditing.
In any of these cases the pc will be somewhat stuck at these points, or at the very least will have some attention units hung up at these points, and getting the exact "when" and "where" will unstick him.
That which is viewed in its own time, place, form and event can be as-ised.
A person can have a wrong date for an incident, or he might have a date totally occluded. He might have a confusion on two incidents, thinking one happened before the other when it is actually vice versa. He could have two incidents collapsed into one, time-wise. Or, more severely, he can be stuck in the time of an incident which acts as present time for him. In other words, that time is still in existence for him in PT. He is seeing things from that point in time.
By dating it exactly you blow the stuck viewpoint in time. You see it as a blowdown on the meter and the pc will feel the sudden dissipation of mass.
The question might then arise: If you have dated an incident to a "blow" what is there left to blow on the Locate step? The answer is that, in addition to a stuck viewpoint in time, a person can have a stuck viewpoint of location.
Since he had the wrong time, he could, as well, have the wrong location, or an occluded location, or a confusion between two or more locations. He could be quite stuck in a past location. That past location is still in existence for him. The point of view from that location is still there for him.
So you date and locate. Finding when it was and where it was blows both the time of the incident and the place of the incident. If he's still hung up in either of these he's out of present time and out of present location. Getting the precise date and location blows him out of these into present time.
Sometimes during dating the pc spots the correct past location simultaneously with getting the correct date, and it (the location) then blows at the same time. The auditor must know that this can occur and recognize when it does as he would not then rotely try to put the pc through the Locate steps.
While Date/Locate is a precise action, it is by no means a rote procedure. The auditor must know the theory of the action if he is to Date/Locate successfully. He must understand that he takes the pc's data and he works with the pc. Robotic application of the steps will not only not produce the desired result but can result in messing up a case badly.
Definition of Blow: The sudden dissipation of mass in the mind with an accompanying feeling of relief. (Technical Dictionary.)
This definition must be understood by both auditor and pc. It is cleared with the pc before beginning the Date/Locate steps. Have the pc demo it, using a demo kit, if necessary, so he has no confusion on it.
A blow is a definite manifestation. Vital data for the auditor is that the pc must say "Something blew" or "It disappeared" or "It's gone" or "It vanished," not simply "I feel lighter. "
During Dating/Locating the pc is on the meter but the auditor is consulting the pc and getting the pc's answers, while also keeping an eye on the meter. He does not resort to meter dating or meter locating unless the pc himself gives up on one or the other of these steps.
A pc can be made more dependent on the meter or can be made more independent of the meter, depending upon the way the meter is used by the auditor. If the pc's case is improving he becomes more independent of the meter. That is the direction you want to go.
"Rule: Use the meter to date and verify date correctness by all means but only after the pc has been unable to come up with the date. " (HCOB 4 Aug 63, All Routines, E-Meter Errors, Comm Cycle Error.)
The same rule would apply to using the meter on the Locate steps.
When dating anything you are using a system of measurement of time. There are various systems for measuring time and as time is basically a postulate or consideration there is no absolute system for measuring time. Time can be measured in terms of years ago. It can be measured by year, month and day (1918 AD, January 1st). These two systems are applicable to this planet, as the term "year" is the time it takes this planet to complete an orbit around the sun. In larger whole track dates different systems were used. The whole point is to use the system the pc is using, because the whole point of dating is to blow a past time that the pc is stuck in. And the pc will very often use the dating system of the time period he is stuck in. It doesn't matter what system of time measurement the pc uses. It is important that the auditor accepts and uses the system the pc is using and doesn't try to change it.
You're first going to ask the pc, "When was it?". He may tell you in terms of "years ago" or "weeks ago. " Or he may say "It was 1890" or "It was the 24th of August 1672. " Or he may use an earlier track system of dating. Either way, you take it, and if he has said "High noon on May 2nd, 1912" you don't then ask "How many years ago?" as he has just told you, and your question would be altering the dating system the pc is using.
You can use any system of time measurement in dating; the important thing is that you use the system the pc is using.
It is remarkable that a pc can date something that happened earlier than this planet in terms of years ago. He can by some sort of mental computer, but the auditor mustn't require that the pc convert a date to some other system.
And when the pc has it, the auditor doesn't then alter-is it in sequence. Found by years — months — weeks — days — hours — minutes — seconds and fractions of a second, one doesn't then call it back by day, year, month, as it tangles the pc. It is called back in the same order.
When calling back a date as an indication, always call it back in the same sequence that the date was found or given.
Implant dates usually only give small reads whereas actual dates read well. If you suspect that you are getting false dates out of an implant, you meter check "Implant date?" and you'll get a read on that question, and the false implant date will no longer read. The actual date will read well.
Meter check if it is:
a) a false date from an implant?
b) an actual date?
and the meter read will tell.
The purpose of dating is to get a blow of the past time the pc is stuck in.
Whether the pc gives the date, or whether the auditor has to meter date it, you must remember that all you are going for is a blow.
Sometimes you will get a blow as easily as the pc saying "It was a long time ago. " A blow is accompanied by a BD and F/N. So be alert when dating for a sudden LF or BD and F/N. And if the pc doesn't originate that it blew, ask him so you won't go on trying to date to blow, something that has already blown!
Very often a date has to be dated precisely down to the fraction of a second in order to get a blow.
If there is no blow on pc giving the date, or on auditor meter dating it, you then call the date back as an indication and it will blow. If it doesn't it is because there is an error in the date, or the auditor altered the date or its sequence in calling it back, or there already was a blow on dating that wasn't noticed and was overrun.
Usually a pc will need help from the auditor to start with and the auditor might need to do the whole dating drill on the meter establishing the order of magnitude and every part of the date on the meter. Then the pc's ability improves and the pc starts to become more able to find dates himself. The auditor must be alert for this and accept the pc's data and never challenge, meter check or invalidate the pc's data. Sometimes the pc will blurt the whole date out at once, and the auditor must be ready to write this down accurately and call it back accurately.
When locating something you are using direction and a system of measurement of distance. Just as time is basically a consideration, so is distance. And there are many systems of measuring distance, both on this planet and earlier on the track. Distance can be measured in miles, kilometers, light-years, to name a few. In one whole track space opera civilization, intergalactic distances were measured in terms of how long it took a particular spaceship, called a Hylan and intergalactic distances were measured by the number of "days of Hylan spaceflight. " You will probably find that the pc will tend to use the system of measurement of distance that was used at the time of the past location that he is stuck in. Just as a pc can use a sort of mental computer to convert whole track dates into "years ago," he can also mentally convert some distances into "miles. " But the auditor never expects him to do so, and never asks him to.
You can use any system of measurement of distance in locating, the important thing is that you use the system the pc is using.
And when you have the distance you must call it back accurately, and not alter-is it in sequence either.
When calling back a distance as an indication, always call it back accurately, and in the same sequence that it was given or found.
The purpose of locating is to get a blow of the past location the pc is stuck in.
As in dating the auditor may have to help the pc with the meter but usually the pc will be able to find and give the data, and the auditor never resorts to the meter if the pc can get it.
And you may get a blow on direction step alone or on the pc realizing it happened somewhere else, or "not here" or "Greece" or whatever. The auditor must be alert for the LF or BD and F/N and ask the pc if it blew, so as not to go on trying to get a blow of a location that has already blown!
Usually if you don't get a blow on finding the direction and distance, you will get a blow on calling the location back to the pc as an indication. If not there is an error in the direction or distance or the auditor altered it in calling it back.
In locating, the auditor is getting the past physical location. e.g. the auditor gets the direction, distance, what galaxy, star, planet, country, etc., pinpointing it down to the exact location in space where it happened.
But these items are not taken up rotely; one uses the questions that apply.
For example, if it occurred "next door" one would not ask "What planet?". Or if the pc has said it's "two years ago" when dating, in locating one doesn't then ask "What galaxy?" as, of course, it's this one. Or what star, either. If you start asking "What galaxy?" on an incident on Earth the pc is thrown backtrack.
And if it happened outside a town in the open you wouldn't ask what city, house, or street or room, either. You must use the questions that apply.
The pc is of course in the auditing room. One doesn't ask where he is. And it's never "Who else was there?" or "What else is there?" as these things put the pc down the track. One does not try to run engrams at the same time one is doing the Locate step. It is simply location. Where? What? How far? Location.
And in locating, if there is no instant blow when the location is fully spotted and it seems correct, the location is called back to the pc. It usually blows when it is called back to the pc after it is known.
There are two separate drills for dating and locating, and which is used depends upon pc ability to find and give the data. The first drill given is where the pc volunteers or gives the data. The second drill is where the auditor establishes all the data by metering. As with all processing, the pc's ability increases as you go along, and the auditor must be alert for this and change from meter dating and meter locating to accepting and taking the pc's data. It can also happen that a pc who was able to find and give the data may run into something particularly heavy and now need assistance from the auditor. The rule is:
Never resort to the meter if the pc can find and give the data, and never let a pc struggle if he can't find the data. And never, never use the meter to challenge, 'correct' or invalidate the pc's data.
Before dating and locating on a pc for the first time you must clear what you will be doing and the words and terms used, so that he understands these and knows what is expected of him.
1. Give the pc an R-Factor that you will be dating the past time of the incident (i.e. when it happened), until that blows.
2. Clear the word "blow" with the pc per the Tech Dictionary definitions No. 1 and No. 2.
3. Clear any misunderstoods the pc has on dates and dating or words used in measurement of time, or numbers (e.g. "billions," etc.).
4. Give the pc an R-Factor that you will be establishing the direction and distance in order to find the past location of the incident (i.e. where it happened), until that blows.
5. Clear the term "direction" and the concept of pointing. Clear the term "distance" and any misunderstoods the pc has on measurement of distance (e.g. miles, light-years, etc.).
6. Let the pc know you will be getting answers from him, not the meter, unless it is necessary to help him with the meter. And that if the pc should suddenly get the date or location he should tell you. Also let the pc know that you are dating and locating to get a blow and that when a blow occurs to tell you, as the purpose of this procedure is to get the mass to blow.
1. R-Factor: "We're going to date the past time when that (________) happened precisely, until the mass blows. "
2. Ask the pc when it happened. (If the pc doesn't know, go to meter dating, per Dating Drill No. 2.)
3. Write down the pc's answer.
4. If not already given, have the pc give the rest of the date right on down to the fraction of a second.
5. Call the date back to the pc accurately and in the same sequence in which it was given, and it will blow.
(Caution: The blow may occur earlier in the dating steps and the auditor must not go on past a blow. If you suspect a blow and pc hasn't volunteered this, ask him if it blew.)
1. R-Factor: "We're going to find the past location where (________) happened precisely, until the mass blows. "
2. Get the pc to point to where it happened. (Points with finger in the direction to the past location.)
3. Ask the pc the distance to that location. (This is the distance from where the pc is now to that past location.)
4. If not already given have the pc give the rest of the distance right on down to fractions, until you have a precise distance.
5. Call the distance back to the pc accurately and in the same sequence in which it was given, and it will blow.
NB. If the pc starts giving you the location in some other terms such as "On the corner of Times Square, New York," you would of course accept the pc's data, and not ask him to convert that into miles away, or anything else.
(Caution: The blow may occur earlier in the locating steps and the auditor must not go on past the blow. Sometimes the blow will occur on asking the pc to point. Sometimes the pc while dating will also get the location and blow it too. If you suspect a blow due to a BD and F/N and the pc hasn't volunteered this, ask him if it blew.)
If the pc didn't know when it happened (on step 2 of Dating Drill No. 1), you go to meter dating.
1. Establish what system of dating or time measurement this date is measured in. Such as "years ago," or by year (i.e. 1918 AD), or some entirely different system. Do not do this if you already know it is a this lifetime date, or a this planet date, as that would be robotic.
2. Establish the order of magnitude.
3. Meter date the date right on down precisely, even to fractions of a second, until you get a blow — F/N.
4. If no blow — F/N when the full date is found, call it back to the pc accurately and in the same order it was found and you should get a blow.
5. If you haven't got a blow, there is either an error in the date or some part of the date, or it is not precise enough, or it blew earlier and wasn't noticed.
Meter check:
and handle what reads, and you will get a blow — F/N.
It is rare that a pc can't get the direction and distance, or otherwise pinpoint the exact past location. Should you encounter this, do the same drill as given in Locating Drill No. 1, with the auditor establishing each step by metering.
1. Get pc to point to the location to get direction.
2. Establish what system of measurement of distance (i.e. miles, or light-years, or whatever).
3. Get the distance.
4. Get any remaining increments of distance on down to fractions or decimal points.
5. Call back the distance or location as an indication, and you should get a blow — F/N.
6. If no blow there has been an error and you should meter check:
and handle what comes up, and you will get a blow — F/N.
Caution: In Date/Locate, if it bogs and the auditor can't easily correct the error in dating or in locating, do not continue messing up the pc with wrong dates or wrong locations, as these can be very upsetting to a case. Indicate to the pc that there is an error in dating or locating and end off for C/S instructions.
A drill that can be used in locating when applicable is given below. This must not however be done rotely when it doesn't apply. If you knew the incident occurred in the recent past or this lifetime, you would not ask "What galaxy?" as the question wouldn't make sense, and would throw the pc backtrack.
Point (pc points with finger)
continuing with questions which will narrow it down to the precise location, to a blow — F/N.
Note: The above steps, particularly, cannot be rote. Listen to the pc and work with him, realistically, to get the location spotted exactly, but do not evaluate for him in any way.
If at some point on these steps the location turns out to be in the middle of the ocean or in a field, etc., the auditor uses available landmarks or reference points to get the location (i.e. , distance from the nearest point of land? or, distance from the big rock?) down to a blow — F/N.
If, while locating, the pc starts running the incident or gives too much "scene" the auditor has the pc point again, then continues from where he left off on the Locate steps.
In dating and locating there is a possible source of BPC, peculiar to dating and locating.
A correct date for one incident or mass can act as a wrong date for another incident or mass, as it is a wrong date for it.
A correct location for one incident or mass can act as a wrong location for other incidents or masses, as it is wrong for the others.
It is peculiar to dating and locating that a right date or a right location can cause BPC by also being a wrong date or wrong location for other incidents or masses. This does not always occur, but is noted here should an auditor or C/S encounter it.
Manifestations of this are:
a) pc getting upset inexplicably
b) getting a read on both "Correct date?" and "Wrong date?"
c) TA going up
d) increase of mass or pressure.
It will relieve on the indication that the date found is a wrong date for other incidents or masses, and on the indication that the location found is a wrong location for other incidents or masses.
A correct date, especially if taken down to seconds and fractions of a second, will blow.
A correct location, especially if taken down to minute increments of distance, will blow.
Date/Locate, when done correctly, quickly and smoothly, works well and is successful. The longer it takes the more it will restimulate all sorts of other things which have nothing to do with the course of action.
The Date/Locate steps must not be done robotically. One has to understand the mechanics of how it's done and why.
The essence of Date/Locate is to bring the pc to PT by erasing the date by spotting and the location by spotting, as the pc is out of PT fixed by both date and location.
If the theory is understood nobody would do it rotely.
This is a highly precise action to be done smoothly with good TRs. Its results are phenomenal.