Always C/S to correct lists first when lists are out or suspected to be out.

Never make trouble for the pc.

Don't do ARC Breaks first in a case of out lists as an out list can make an ARC Break that can't be handled by ARC Break but only an L4B.

When a pc is running well let it roll. The C/S can spot a possible error but the pc is Wide F/N VGIs at the Exam, let it go.

On a GF when lists show up or overlists you should handle that (first action in handling the GF) but also you must order an "L4B Method 5 and Handle. " Method 5 is the once through for assessment.

Chew the auditor, send to Cramming. But don't throw the well running pc into extensive repair – don't break into a winning program harshly. It gives the pc a loss.

The pc who isn't running well is the one you repair. Don't keep a pc going on and on, running badly with no case study. Study the case folder, find the right why by going back to where the pc was running consistently well and then come forward for the error. It will be in the exact next session.

When auditors can get no reads on things you get their

If the pc wasn't ever audited before, you go into his life of course, with a GF + 40 Method 5 and handle and other Life repairs.

a) TRs checked to see if they can even be heard.

b) Their metering checked for meter position on auditing table, can they see meter, pc and write without shifting eyes? And can they see pc's hands on the cans?

Any Repair or Progress action has reached its End Phenomena when the pc is running well again.

And was the meter turned on and charged and can an auditor work the Tone Arm smoothly with his thumb?

This is peculiar to the Repair or Progress program.

c) Does the auditor discount reads gotten on clearing commands? (They are the reads.)

Wrong Example: Pc was on Grade III, fell on his head. C/S studied case, found out lists, wrote an extensive Repair Program and C/S. Half way through repair the pc again was flying. C/S continued the repair. Pc bogged. C/S C/Sed the pc to flying again. C/S continued the repair. Pc bogged.

d) Can the auditor read out a list and see the meter reads as a coordinated action?

Right Example: Pc falls on his head on Grade III. C/S writes a Repair Program and C/S. Auditor finds the out list, corrects it. Pc flies. C/S puts pc at once back on Grade III to complete.

Send auditors to cramming on all flubs, insist they go to cramming, insist Cramming calls them in and crams them and insist on a carbon copy of the fact that cramming has been done. All the hard work of C/Sing comes in when auditors are flubby.

An auditor can be invalidated by a C/S by having a lot of questionable tech points thrown at him.

It takes weeks to make an auditor after he has had a course and it's only done by Cram-Cram – Cram.

The auditor's data gets shaky.

If no decision was ever made – is not in HCO Bs and tapes – is not to hand and can't be referred to by HCO B and tape, then a C/S should not be making the point.

Never order an R-Factor that takes pc into future or past as he then won't be in session. Example: C/Ses "R-Factor we are setting you up for Dianetics. " Promptly the pc is up ahead not in this session.

Example: Auditor extends a list three more items beyond an F/N. C/S chops him. There is no such rule. The pc maybe wouldn't accept the item until he listed a few more. Result is a firefight between C/S and auditor, simply because it isn't a valid point.

HCO Bs and Tapes are the stable data that form the agreement between the auditor and the C/S. "If it isn't written (or spoken on tape) it isn't true. "

There are many ways to start a session. Don't mix them.

Don't wander off known tech points in C/Sing.

• It's "2WC what do you have your attention on?"

Never shake an auditor's data by advancing data not on HCO Bs and Tapes.

Always know your data, your HCO Bs and Tapes and refer the auditor to them in Cramming.

Cramming must have a library of all materials.

A hidden data line can build up in C/S-Auditor lines (or course lines or Cramming lines) that can unstabilize all tech and deny further results.

The decay of tech in areas begins with hidden data lines that are not true.

It's not a mixture of frantic efforts to get a TA down.

So use and refer to HCO Bs and Tapes and leave all other points alone. Your auditors will become confident and certain and Tech will improve.

If the auditor can't on what the C/S says the auditor ends off.

It's enough just to insist on the usual.

Interiorization is undone or out, there may be list errors, there may be overruns, but for sure it's a case for folder study, not for an auditor C/Sing in the chair.

Then auditors and cases will fly.

Train your auditors never try to get a TA down from 3.5 or above on ARC Breaks.

Some auditors see a TA sink below 2.0 and then won't continue the 2WC or process to get the TA back up.

"The TA sank so I quit" is a common auditor note.

Compare this: "The TA rose above 3.0 so I quit. "

See? Doesn't make sense.

If a TA sinks below 2.0 – and the auditor's TRs are good – the same action will usually bring it up to 2.0 and F/N.

Come down hard on auditors who do this.

Get their TRs checked, make them continue.

Pcs whose TAs are high in session or low in session and get F/N at the Exams put the finger on the auditor. They are protesting or being overwhelmed.

Always C/S "Examiner! Ask pc what auditor did in session. "

Then you know it's the auditor or the case. The pc will say the auditor was okay. So it's case. But usually when cases are puzzles there's weird things going on with TRs.

Also the auditor may be noisy or laugh hard or is boisterous and being "interesting".

The C/S is handling cases on the via of an auditor.

If the auditor is perfect the C/S can handle the work out of the case. If the auditor is not perfect in TRs, metering, Code, reports and doing the C/S then the C/S is solving a factor unknown to him, not the pc's case.

So, be a perfect C/S. Demand perfect auditing. Cases fly.

A C/S who assesses a pc to higher levels to solve lower ones is really asking for a wreck.

It's always the earlier actions that are out.

Trying to cheat a case up to Grade 2 when he won't run on Grade I is like trying to run the whole grade chart to cure a cold.

A pc can always be solved in or below where he is.

"Oh, we'll put him up a grade and cure his high TA" is like "He can't pass kindergarten so we'll enroll him in college. "

A C/S has to know his auditing materials, HCO Bs and texts much better than an auditor.

If a C/S is not being successful, get a retread on VI and VIII materials.

A C/S also must be confident he could crack the case as an auditor.

When a C/S is shaky on his materials then the world of auditing looks very unstable.

The tech is very exact, very effective. If any errors existed in it they've been corrected.

So the variables are the knowledge of the C/S, his discipline and demands of auditors and the actions of the auditor.

If these are stable then the cases that come along are easy as can be.

The successful C/S knows his materials. If he wants to be even more successful he keeps his study up.

Then he is steady and calm for he is totally certain.