Don't leave cycles incomplete on a case.

Never make trouble for the pc.

If a C/S starts a 37R and the auditor goofs, correct the auditor and then get the 37R completed. Don't disperse and do something new.

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.

If you have a program going and it's goofed, repair the auditor and the goofed pc and continue the program you began on the case.

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.

Repair (Progress) Programs are ended when the pc is flying nicely. When a repair hits that, don't re-repair.

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.

On Advance Programs, take each step to its EP. Don't suddenly start something new.

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 sure way to solve a case is go back and find the earliest incomplete program, complete it and so on up to PT.

Keep your "finger in the book" on a case. Don't lose your place. That's done by having the current program on the inside front cover, paper clipped on, and checked off with each step done. When it's done, put a new program on top of it.

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

Insist that auditors keep up the inside front cover folder summary each session with their auditing time and admin time in the box. This FS is a 2 column set of boxes, date, what's run, F/N or bogged and time.

This is peculiar to the Repair or Progress program.

By seeing Admin is in you can keep your place in the book or study back rapidly to find what's been done.

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.

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.

The deadliest faults on cases are running the same action or grade twice. This drives TAs up through the roof.

Example: Power done in '65. Done again in '69!

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

Example: Grade IV done in '69, done in '70.

The auditor's data gets shaky.

You find the case isn't doing well or find the error. In doubles, rehab by date of the first time it was done.

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.

I've seen Interiorization done three times on one pc, Power twice and the same Dianetic Chains run over and over. And people wondered "Why is the TA high"!

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.

So when you order a major action always check to see if it's ever been done before! Save you grief. And if a major action won't run, suspect it may have been done before.

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. "

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

Always set up a case fully for the next major action.

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

Don't overrepair. But be sure the case is not sick, has had good exam forms and does well.

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

Then C/S the next major action.

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.

Never blame the pc. Many it is true are dog cases.

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

But even dog cases can be handled.

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.

When you find auditors (or feel yourself) blaming the pc, get the overts and withholds run out.

It's enough just to insist on the usual.

Once I got the most splendid sessions out of an HGC. I had the auditor's overts and withholds checked on each auditor before he went into session. It was just research, but my it worked! Those were the smoothest sessions! Pcs began to fly!

Then auditors and cases will fly.

Too many times one blames the pc only to find later that the auditor's TRs were ghastly and that a major action had been run twice. Such discoveries make a C/S out of a C/S.