The errors in doing Routine 2-10 and Routine 2-12 are divided into two broad divisions:
This bulletin touches only briefly on the errors of (a) Auditing Errors. These consist of sloppy form, bad TRs, inability to read a meter, Auditor Code breaks, Q and A- ing, missing missed W/Hs, doing bad Mid Ruds or Tiger Drilling and using Auditing form to hold up results.
One remedies bad auditing (as different from bad 2-10 or 2-12) by following this prescription:
The poorer the auditor, the more a supervisor or instructor takes away from him the tools of auditing. In short, if an auditor makes bad auditing errors, one simplifies the auditing to prevent the errors. Don’t let him or her do 2-12. Make such an auditor use only 2-10. Then, as the auditor’s skill in basic auditing improves, the more he or she can be trusted with 2-12.
Do NOT let an auditor who can’t do any kind of a job of basic auditing do 2-12. Let such an auditor do only 2-10. And then as that auditor’s case improves on 2-10 or 2- 12, and as training drills are passed, let the auditor graduate up to 2-12.
Remember this: 2-12 works all by itself with no auditing niceties. And it can be prevented from working (but only to some degree) by bad auditing form or intention.
Strip off Model Session, Mid Ruds, Tiger Drilling, and two-way comm, demand it be run muzzled, muzzled, muzzled, use the meter only to find Rockslams, and modern Routine 2 works like a dream, a dream, a dream even for an auditor whose auditing skill is terrible.
Let a Q and A artist clean cleans on a meter, muck up the Mid Ruds, yap at the pc, and Routine 2 won’t work because it never gets done.
So the training stress and the use stress of Routine 2 is first on Routine 2, its rules and how it’s done, and when the auditor has case gains and wins, auditing form is then entered upon.
The backwards way is to insist on a good hard study of form before training on Routine 2. Always hammer Routine 2 home first and get it done, not fooled with by the Mixed-up Kid from Mid Rud Gulch. Your main trouble will come from not teaching Routine 2 hard just as itself before entering upon the niceties of auditing. You have to show the wild man it’s a house before you teach him to serve French Pastry a la Partie.
Of course nothing in this HCO Bulletin should be used to degrade the value of good auditing form.
Good metering, a smooth command of the TRs, a grip on the basics and a firm knowledge of fundamentals are vital in an auditor.
You can’t get all there is to get out of Routine 2-12 with rough auditing.
Auditing skill is not just something to acquire. It’s the only thing that gets real auditing done. And good auditors are scarce and I appreciate them. I’ve had my share of rough auditing and I know the diamonds and gold of a smooth, flawless auditor.
But Routine 2, at the time of this writing, and for always in some area of the world as we expand, will be handled with rough auditor skill. Therefore, for the purposes of this HCO Bulletin, we will consider the auditing skill to be rough and show what Routines 2- 10 and 2-12 can do in unpolished hands.
And never fear, when their cases are better and the training can be stepped up, they’ll become polished, never fear. And appreciate being so. It’s my brag I can get a pc out of anything with just auditing skill. That makes me pretty brave as an auditor. But this “Bring on your lions” attitude is born out of auditing skills, taught, not “native”. I use the same pattern and patter as you do if you audit text book. But I don’t clean cleans often or miss reads ever and I don’t Q and A. You can audit just as well as I can with practice and study. Why do I know this? Well, auditing is not my main forte, not even close to my appointments and goals.
We’re probably all Rockslammers somewhere on List One and this is Man pulling himself out of the mud indeed.
So don’t run down pure auditing skill. It’s more precious than anything in this universe.
But you can acquire it as you do Routine 2 and after.
Meanwhile don’t overrate the power of Routine 2 to work with rough auditing, so long as the Routine 2 is done right.
Routine Two (by which is meant 2-10 & 2-12) has its own rules and these must be learned first and learned well.
Routine 2 today is a powerful process. And if it can straighten up a pc so fast, it can also cave him in fast. However such cave-ins, while dramatic, are very easy to remedy even though they must be remedied with accuracy. (The remedies are all contained in this HCO Bulletin.)
Remember, in doing Routine 2, the primary pc upset is from badly done Routine 2, not badly done auditing. To repair a car don’t look for paint scratches when somebody has removed the engine. Auditing form is paint scratches. The removed engine is flubbed Routine 2.
Routine 2 must be taught hard, not just as a version of auditing but as itself. It is its own technical package and it doesn’t even infringe on the basics of auditing.
Routine 2 has several hills to climb. One of them is Auditor responsibility. This process has the peculiarity of handing all responsibility for case gain or worsening to the auditor.
You will hear people who haven’t a clue on Routine 2 crying about bad pcs, bad D of P-ing, bad Ron and blaming everyone but themselves. Investigate and you’ll find only an auditor flub on Routine 2.
All Routine 2 auditor flubs consist of:
There are no other Routine 2 auditor flubs.
In Routine 2 all gain or lack of gain is assignable directly and only to the auditor.
Frightening isn’t it?
But encouraging too. For it puts the auditor at cause, wholly and completely, over the pc’s case. You might have known that would happen with the first all case fast gain process.
Routine 2 is here to stay. You’ve been used to the changing face of processing.
That discouraged learning any process very well and setting up to get it done by one and all. Well, Routine 2 is here to stay. It isn’t going to change. You can invest a great amount of time and effort on learning it.
It’s here to stay because where it doesn’t get results, the auditor didn’t know it or didn’t do it, and we can always remedy that.
It only produces mediocre or worsening results when it either isn’t known or isn’t needed.
Further, it is quite easy to do.
And it produces fast, stable results, very startling to even raw meat. There is more miracle in 50 hours of well done Routine 2 than in the entire history of the church.
Further it has to be done on every case before a goal can easily or reliably be found, or even if found, before it can be run.
So there it is. Learn it.
The first and greatest error of Routine 2 is No-Auditing.
Yes, the auditor may be sitting there like a one-man band, busy as free beer at the boiler works and yet not be auditing Routine 2.
Example: Eat up two-thirds of every session with needless beginning, middle and end rudiments.
Example: Spend two hours Prepchecking the Mid Ruds and then find the reason the needle is dirty is an incomplete list.
Example: Spend three sessions full of general O/W trying to calm an ARC breaky pc when in actual fact the auditor has been opposing an Item off an incomplete list.
It’s not just Audit the pc in front of you. That’s vital enough. But Audit the pc in front of you with correct Routine 2.
Auditors have been known to spend hours, days, running old processes to get the pc “up to running 2-12” when five minutes of 2-12 would have had the pc sailing.
NO AUDITING means “While seeming to deliver auditing, actually get nothing done.” It’s the greatest crime in Routine 2 or Routine 3. NO AUDITING can be reduced to the finest art. Doing a wrong list, re-doing a dead horse, these aren’t no-auditing. Auditing may have been wasted or may be slow, but it’s still auditing. No, NO AUDITING means going through endless, useless motions, perhaps in top form, perhaps perfectly, none of which are calculated to advance the pc’s case one inch. Doing havingness every half page, endlessly Tiger Drilling, doing Mid Ruds just because it’s “good form”, all these and a thousand more add up to NO AUDITING. Absolute essentials, bare bone, and bounteous correct 2-12 are AUDITING.
Mid Ruds, Tiger Drilling are necessary to good auditing but using them an inch beyond necessity is NO AUDITING.
Almost the only way to completely bar the door on the pc is to lose his case folder or fail to put all lists and reports in it.
Every sheet of every list must have on it the pc’s name, date of the list and the question from which the list comes.
This is the biggest MUST in Routine 2: Preserve the records and make them identifiable and usable.
Failing to find and utilize an RS on List One is the most common (but not the most destructive to the pc’s health) error in Routine 2.
Example: Auditor has three dead horses. Abandons case. Another auditor assesses List One, Tiger Drills the RSs out, represents a tick. Gets another dead horse. Abandons case. Pc now known as a “tough pc”. A third auditor gets cunning, looks over the original assessment, sees “Auditor” RSed once long ago. It doesn’t now, having been Tiger Drilled to death. Opposes it. Gets a beautiful RSing List. Case starts to fly
This error has been done over, and over and over and is the source of all dead horses.
Rule: Oppose Every RS found on List One or IA or a “PT consists of” list. Oppose them even when they only RSed on Tiger Drill buttons. Take the RSing Item most intimate to the actual session as the first one to use. If in further doubt take the RSing Item closest to the session the pc is interested in.
List One, I A or “PT consists of” lists do not have to be RIs to be opposed. They are locks on RIs. They only need to briefly RS, or to have been seen to RS at some time, to be opposed. If they RSed at any time they must be opposed according to whether they are terms or oppterms.
I have seen a case fail to give more than dead horses until somebody recalled that on a Sec Check test a year before the case had RSed on “Scientology Orgs” (now not even a tick). When that was opposed, a dial-wide RS turned on for 55 consecutive pages of Items, a high record.
One remedy is to Tiger Drill “On List One_____”, but it isn’t infallible.
REPRESENTING AN RSing ITEM
One of the three most destructive actions to the pc is Representing an RSing Item. (The other two are opposing the wrong way and opposing an RSing Item taken from an incomplete list, both included below.)
Representing an RSing Item puts a terrible strain on the pc’s attention. The list may even RS, probably will. But the opposing Item, now hidden, wreaks havoc on the pc all the time its companion is being listed on a represent list. A real calm pc can turn into a screamer if an RSing Item is listed with a represent list, whether it has been opposed or not.
(Note: This is contrary to a 3GAXX action which could be done only because a detested person wasn’t a vital oppterm. It should not be done even in 3GAXX.)
Rule: Only do opposition lists on RSing Items. Never represent them.
Always oppose an RI and continue to oppose RIs until you get a satisfactory package. Never leave a BY-PASSED Item.
To do so is destructive to the preclear. This is not the greatest source of destructiveness and not every RI by-passed will ruin the preclear. But once out of three times the pc will be upset.
Example: “Scientology” RSes. A Reliable Item “A slavemaster” is found on the opposition list. It is not then itself opposed. Pc is upset by presence of a hidden Item that opposes “A slavemaster”. Pc stays upset until “A slavemaster” is opposed and its RI companion Item “A freedom Fighter” is found. “Slavery” shows up on the “Opp Scientology” List as the thing that actually fronted up to “Scientology” when the whole thing was packaged.
Rule: When a First List RSing Item is opposed and an RI is found, then Routine 2 steps are incomplete until the found RI is itself opposed.
It goes Represent — oppose — oppose or Oppose, Oppose.
It will be seen that First List RSing Items are usually locks into PT on actual RIs. It will also be seen that the Rockslams on the First List, the first opposing RI and the RI that opposes that all match. They have the same width and speed and pattern. They seldom all RS at the same time but in sequence of when first found.
Rule: All Items found must be completely packaged.
Rule: All RSs in a package must match in character and vanish when fully packaged.
Leaving a by-passed Item is also possible because of incomplete lists. (See below.)
If, after nulling, you have several Rockslamming Items remaining, your list is
always incomplete.
Bonus packages vanish as soon as spotted. They occur once in a while. They can be ignored in this rule:
Rule: If you find more than one RS in nulling a list that list is incomplete and must be completed.
Example: “Preclear (pn)” once RSed so it is opposed. The “Who or what would a preclear oppose” list is listed and a dozen RSs were seen on listing (OK so far). The list tested without reaction on the question. The auditor starts to null the list. Some of the Items that RSed while being listed, RS now on nulling. List is nulled down to 3 (!) RSing Items. Auditor chooses one. It RSes nicely. This is “A control device (sen)”. Auditor now lists “Who or what would oppose a control device?” List RSes well. However, masses tend to close in on pc. Havingness drops. Pc possibly ARC breaky. Auditor continues On listing. And on. And on. Finally gets to nulling. Very hard job. Pc cutting up. Auditor tries to pull missed withholds. After much blood auditor finds four RSing Items left on list, chooses “A wild man” and tries to package. Pc glum. Very little cognition. TWO Items have been By-passed. How? Auditing supervisor sees that several Items on the “Who or what would a pc oppose” list RSed on nulling. Assumes rightly list was incomplete. Directs it to be completed. Pc smiles brightly and with a suddenly clean needle lists 80 more Items (several of which RS on listing). Masses fall away from pc again. No ARC breaks. This time only one Item RSed on nulling. “A controller (sen).” (Only new list is nulled of course. You never re-null in 2-12.) RS has mysteriously (and correctly) vanished off every other RSing Item on that list. The list “Who or what would oppose a control device?” is wholly scrubbed, being wrong. The auditor now lists “Who or what would oppose a controller?” The pc happily lists 200 Items (many RSing). The needle goes clean. The auditor starts nulling. Finds he has two Items on the first three pages that RS. Has learned his lesson and, leaving off nulling for the moment, gets pc to add 50 Items. Auditor goes on nulling. Nulls down to one RSing Item, “An Insane Idiot”. The RS on “A Preclear”, “A Controller” and “An Insane Idiot” all matched when seen each in turn (but “a preclear” doesn’t RS any more). Pc cogniting like mad. Very happy. Masses all moved off and havingness up.
Rule: If in nulling more than one RS is seen on list, that list is incomplete and must be completed.
There are no exceptions to this rule. Bonus packages blow off on a completed list. Also, to clarify, keep in mind this rule:
Rule: If a list does not RS now and then or at least once when being listed, it will become a dead horse.
That some list Items RSed when the pc said them during listing is natural.
If, with Suppress clean, more than one of them RSes during nulling, that list is incomplete.
Also, in passing, don’t finish nulling a list before adding to it as a general practice. Add to it when the pc’s needle is dirty or when you see more than one RS on it during nulling. The pc ARC breaks if you keep completing the nulling of the existing list and then adding.
Pcs are not always right when telling you it’s a terminal (pn) or oppterm (sen). They even sometimes lie to try to save their face (to keep from looking bad in an auditor’s eyes or the world, or to seem even more villainous than they are).
The only real test of a right way oppose is whether or not the list lists easily with IMPROVED SKIN TONE in the pc and improved cheerfulness, and if it produces one RSing Item that packages later.
If you just can’t tell which way to oppose, oppose both ways and then decide on pc’s appearance which way was right and continue it.
Wrong way opposition is not usual. Usually the pc tells the truth and all is well. But when a list is listed wrong way to on opposition it’s long, horrible and deadly.
The pc goes faintly grey, green yellow or blackish, looks worse, and the list gets endless. A wrong way list will RS. So it’s only pc appearance that tells the story. Routine 2 is beneficial. Pcs that are listed with right way opposition look brighter, younger, with a more translucent skin tone. You won’t make a mistake if you can tell the difference between a young boy and an old man, it’s that distinct. (Remember, a pc will also look worse as above if you took an Item from an Incomplete list or committed any of the other R2 errors in this HCO Bulletin.)
The only reasons a list will not complete are:
In either case there is something wrong with the source of the list.
That a list in listing RSes is no guarantee of rightness of source. A wrong way to list will RS. Some lists taken from a wrong source cycle RS, DR, Clean needle, RS, DR, Clean needle.
Wrong sources are:
There are no other wrong sources and thus no other R2 way to get a list that won’t complete. But when you do get a list that won’t complete, be very careful to look over the above 5 reasons and pick out the right one. You may have to complete an earlier list first and scrub the one you’re on.
Incompleting lists are usually abandoned without further patch-up. How long is an Incomplete List? How long is a piece of string?
Don’t ever be afraid to have a long list, only be afraid of short ones. But when a list is running up toward thousands, something is wrong.
Endless Lists stem basically from wrong source as above or from the auditor’s failure to understand what indicates a complete list.
If, on close study of the case folder and pc, Routine 2 errors seem to be absent — the source is right and not something taken from another list itself incomplete, if the oppose is right way to, then look for the following:
The remedies are to get Decide in well and to make sure, without upsetting him, that the pc is answering the auditing question.
And if that is all OK, then it’s just a long list, so complete it.
Rule: A list is complete when it can be nulled and when it produces just one RI that RSes on Tiger Drilling and stays in.
A list can be nulled only when a needle is clean (except in 2-10).
The definition of a CLEAN NEEDLE is one which flows, producing no pattern or erratic motions of the smallest kind with the auditor sitting looking at it and doing nothing. A CLEAN NEEDLE is not just something that doesn’t react to a particular question. It’s a lovely slow flow, usually a rise, most beautifully expressed on a Mark V at 64 sensitivity.
A list has to be listed until this needle flow is observed (with no Mid Ruds put in). But ruds or no ruds, a CLEAN NEEDLE always appears when a list is complete.
A DIRTY NEEDLE is one that jerks, tips, dances, halts, is stuck or has any random action on it with the auditor sitting looking at it doing nothing.
There are the Auditing methods of converting a dirty needle to a clean needle, both as defined above. These are all the skills of auditing used with Big Mid Rud buttons.
Now entirely and distinctly separate from Auditing skills for cleaning a needle, there are the Routine 2 methods for converting a dirty needle to a clean needle.
Usually both Auditing and Routine 2 methods are used to clean a needle so that one can nul, the former briefly, the latter abundantly.
However, do not overlook the demonstrable fact that Routine 2 methods for cleaning a needle are very beneficial and lasting in results, whereas purely auditing methods (like Mid Ruds) have value only for the moment and, even though auditing methods are desirable in this operation, when the Routine 2 is in error, the clean needle is really impossible to achieve longer than seconds with auditing methods.
The obvious solution to cleaning a needle is to first have Routine 2 as perfect as possible (the errors outlined in this HCO Bulletin uncommitted or being rapidly corrected) and then use auditing methods.
Try it in reverse (auditing methods first and then using corrections of Routine 2) and you will not only fail to get a needle clean longer than seconds, you may also waste the better part of an intensive trying to do it.
So spend hours straightening up Routine 2 errors and doing it right and brief minutes with auditing methods when necessary.
And don’t revile a pc for having a dirty needle. It’s the auditor who dirties it up with incorrect or inaccurate Routine 2, not the pc.
Now a clean needle is vital in order to nul a list. Don’t ever try to nul a list with the needle dirty. If the Routine 2 is right, the needle will clean up with two minutes’ work of Big Mid Ruds. If Routine 2 errors (wrong list source, list incomplete, wrong way oppose, etc, as per this HCO Bulletin) exist and Routine 2 is being done wrong, then two hours’ worth of Big Mid Ruds will not clean a dirty needle.
Any of the Routine 2 errors taken up in this HCO Bulletin will create a dirty needle and keep it dirty and leave the auditor sweating over Mid Ruds and the pc going mad trying to answer the questions. Yes, the Mid Ruds are out. But why? Because one or more serious Routine 2 errors as described in this HCO Bulletin are present.
So see the light. If you sweat on Mid Ruds as an auditor, curse them as a pc or see a co-auditor dripping exasperation over Mid Ruds and the needle won’t stay clean, look
at the Routine 2, not the difficulty with Mid Ruds. Look for the errors here described. Check them off on the case, one by one, and don’t even be satisfied that it’s only “No- Auditing”. Check all the errors off, section by section. You’ll be startled.
So in general, difficult Mid Ruds and dirty needle indicate wrong Routine 2, not bad auditing. Somebody has flubbed the Routine 2 before the auditing was flubbed. Once the Routine 2 is in error, auditing becomes impossible.
This gives no excuse for bad metering, cleaning cleans, trying to look like an auditor but ignoring results. Auditing errors do exist. And can be serious, but a pc running on right Routine 2 would forgive the Pope for having a forked tail. You almost can’t muddy up a pc running on right Routine 2.
Here’s a trick. Don’t try to nul a list until you’ve seen a clean flowing needle for a lot of Items, maybe 50. Then get in fast Mid Ruds on the list and do it without cleaning any cleans. Then start nulling. If the needle dirties up after 30-40 Items, skip Mid Ruds, just show the pc the page and have him spot any big thoughts he had on it. Then immediately get back to nulling. If the needle is dirty still, resume listing until it’s clean. Just do those actions and (given error free Routine 2 as per this HCO Bulletin) you’ll have a smooth, smooth happy time of it in nulling.
Do anything you don’t have to do in auditing Routine 2 and you’re in trouble in the auditing department. Bang out almost total Routine 2 and you’re in clover. Give 1/10th of the session over to goals, Mid Ruds and other auditing actions and 9/10ths of the session to pure Routine 2 Actions and you’ll really win. And that l/10th includes any Mid Ruds on the list as well. Give half the session to auditing and half to Routine 2 and you’ll be in continuous trouble.
The righter the Routine 2, the less auditing you’ll have to do.
So how long is a list? Can you nul it with a needle that requires only a pc inspection of a page to keep it clean? Are all but one of the RSs that happened in auditing dead when you nulled? Are your pages long streams of X’s? Did you have to use suppress only once per page (fast check) to keep it clean?
Well, that’s a complete list. If it gave you an RI. Just one. So how long is a list?
But if all the above is true and a pc’s lists are still very long, another thing can be wrong.
That wrongness usually is the pc’s confronting ability being driven down by auditor unconfrontability. (But also can be caused by a wrong RI or other errors gone before it as covered in this HCO Bulletin.)
The auditor Qs and As, yap, yaps, nags the pc, blames, gets in endless Mid Ruds, cleans cleans, misses reads or does something else.
The length of an auditor’s pc’s lists is to some degree proportional to the Rough auditing or no-auditing done by the auditor. (And also by a failure to use Mid Ruds and TD in the right places when necessary.)
We have known since ‘55 that rough auditing reduces havingness. Here’s why: Rough auditing lowers the pc’s ability to confront in the session. The pc’s havingness is proportional to his ability to confront in the session. If a pc’s havingness by can squeeze test is lower at session end than at beginning on Routine 2, then there’s something wrong with the auditing or with the way Routine 2 is being applied (one of the above Routine 2 errors is being made).
The remedy for the bad auditing is to make the auditor only acknowledge anything and everything the pc says or put it on the list. Tear out all Rudiments, Tiger
Drills, two-way comm, and forbid any chance to comment or act on an Origin by the pc, and get only Routine 2 done.
The remedy for Routine 2 errors (and the errors themselves) are given above in this HCO Bulletin.
Routine 2 does not have an endless parade of DO-NOTS. They are basically just those above.
Simple, really.
And I’ve not seen one session on Routine 2 that was going really wrong, go wrong on auditing errors alone. Routine 2 sessions go wrong on bad Routine 2. The auditing form and meter errors start to pile up after Routine 2 has been balled up. One or more of the above Routine 2 errors has been done and overlooked.
The reason why Routine 2 errors are more deadly than purely auditing errors is that Routine 2 is handling the pc by batches of lifetimes. All the stress and gore- and agony of generations exist on the lists of any one package. An auditing error can be gross and get by unless it is sitting on a Routine 2 error. Then the tiniest auditing flub can produce a reaction like an earthquake. The charge is all coming from Routine 2 mishandling and is evident on the surface only by the auditing error.
Routine 2 case patch-up is elementary, done with a knowledge of the above errors. Just find out which one of the above sections is being violated. And get it done. The error will only be one of the above to cause case non-progress or worsening.
The sections are given in order of importance.
I will shortly work up a series of actual case history case repairs. So save the records and you save all.
Routine 2-10 and 2-12 are their own technology and must be learned as such.
Routine 2 errors are more shaking to a case than errors in form and meter (except where the auditor can’t even see a Rock Slam!) and where a case is not winning on Routine 2 auditing it is the Routine 2 that must be reviewed — and fast. The elements to be reviewed are all listed above by sections in order of importance. Of course many other smaller fantastic errors can be done and will be invented but they will be junior in value to those listed above and will be reported when found.
Routine 2 will be with us a long, long time and it is worth learning well. It takes the toughest case apart and is the only process that can start the actual clearing of 805’o or more of all cases.
I have done or reviewed thousands of hours of auditing in forming and organizing and testing Routine 2.
It is the most gratifying (and sometimes hair-raising) auditing I have ever done or viewed.
You can’t oversell Routine 2. You just can’t. For it is the first gateway to light, life and liberty for all Mankind at last.