If a pc says something and the auditor fails to understand what the pc said or meant, the correct response is:

There are no additives permitted on the Auditing Comm Cycle.

"I did not (hear you) (understand what was said) (get that last). "

Example: Getting the pc to state the problem after the pc has said what the problem is.

To do anything else is not only bad form, it can amount to a heavy ARC Break.

Example: Asking a pc if that is the answer.

Example: Telling pc “it didn’t react” on the meter.

To say "You did not speak loud enough _____" or any other use of "you" is an invalidation.

Example: Querying the answer.

The pc is also thrown out of session by having responsibility hung on him or her.

This is the worst kind of auditing.

The Auditor is responsible for the session. Therefore the auditor has to assume responsibility for all comm breakdowns in it.

Processes run best muzzled. By muzzled is meant using only TR 0, 1, 2, 3 and 4 by the text. A pc’s results will go to hell on an additive comm cycle.

There are a hundred thousand tricks that could be added to the Auditing Comm Cycle. every one of them is a goof. The only time you ever ask for a repeat is when you couldn’t hear it.

Far more serious than Invalidation above, is the accidental evaluation which may occur when the auditor repeats what the pc said.

Since 1950, I’ve known that all auditors talk too much in a session. The maximum talk is the standard model session and the TR 0 to 4 Auditing Comm Cycle only.

Never repeat anything a pc says after him, no matter why.

It is a serious matter to get a pc to “clarify his answer”. It is in fact an Ethics matter and if done habitually is a Suppressive Act, for it will wipe out all gains.

Repeating not only does not show the pc you heard but makes him feel you're a circuit.

There are mannerism additives also.

The highest advance of 19th Century Psychology was a machine to drive people crazy. All it did was repeat after the person everything the person said.

Example: Waiting for the pc to look at you before you give the next command. (Pcs who won’t look at you are ARC Broken. You don’t then twist this to mean the pc has to look at you before you give the next command.)

Children also do this to annoy.

Example: A lifted eyebrow at an answer.

But that isn't the main reason you do not repeat what the pc said after the pc. If you say it wrong the pc is thrown into heavy protest. The pc must correct the wrongness and hangs up right there. It may take an hour to dig the pc out of it.

Example: A questioning sort of ack.

Further, don't gesture to find out. To say, pointing, "You mean this item, then," is not only an evaluation but a nearly hypnotic command, and the pc feels he must reject very strongly.

The Whole Message is good auditing occurs when the comm cycle alone is used and is muzzled.

Don't tell the pc what the pc said and don't gesture to find what the pc meant.

Additives on the Auditing Comm Cycle are any action, statement, question or expression given in addition to TRs 0-4.

Just get the pc to say it again or get the pc to point it out again. That's the correct action.

They are Gross Auditing Errors.

And should be regarded as such.

Also, do not shove things at a pc or throw things to a pc. Don't gesture toward a pc. It drives in anchor points and makes the pc reject the auditor.

Auditors who add to the Auditing Comm Cycle never make Releases.

So, that’s Suppressive.

The reason a person who Rock Slams on Scientology or auditors or the like can't audit well is that they are wary of a pc and feel they must repeat after the pc, correct the pc or gesture toward the pc.

Don’t do it!

But Rock Slammer or not, any new auditor may fall into these bad habits and they should be broken fast.

A very high percentage of ARC Breaks occur because of a failure to understand the pc.

Don't prove you didn't with gestures or erroneous repeats.

Just audit, please.