These are the most common goofs found made by auditors in case supervising over a hundred folders.

(1) Pc audited with no instructions from C/S.

A Case Supervisor cannot do a decent job of C/S when he is presented with lousy admin such as – no Auditor Report Forms, not handling Gr Form reads as they occur, not writing in F/Ns, not making a ring around the item found, not indicating where a list was extended. Also illegible writing, failure to go over a report when done and make obscure words plain in print is a No Report and gets liability.

(2) Audited on squirrel process.

When you run into a snag you can’t handle, don’t start inventing tech and doing something else other than the C/S instructions.

(3) False Auditor Report – flunk flunk.

End off the session and send it to the Case Supervisor.

(4) Audited past F/N.

It is, I am told, the wild fashion in Quals and HGCs around the world that if one hits a snag, the auditor rushes out and asks the D of P who gives him an unusual solution without even looking at a folder. If I catch or hear of anyone doing that, it’s the Deep 6*deep six: throw overboard (World Book Dictionary) .

(5) Auditing a pc while on medication.

The correct action and the only correct action is to end the session and get folder and session paper to a Case Supervisor, who

(6) Auditing a pc while ill.

(1) does not see the pc and

(7) Leaving pc with a problem.

(2) does not talk to the auditor.

(8) Auditing a pc on no sleep.

Case Super is folder only. Then there’s a chance of standard tech.

(9) Nulling an L1 to largest read.

(10) Not giving pc his item.

(11) Not tracing an ARC break, M/W/H or PTP down to basic when it doesn’t blow.

(12) Not handling reading GF items as they occur.

(13) Failure to use ruds on*Most probably a typing error and it should read: "Failure to use ruds or even GF when…" even GF when TA rises between session before starting major action of session.

(14) Not following C/S instructions.

(15) Taking frequent breaks.