"Standard" in standard tech auditing is a precise activity, done with good TRs, exact grade processes and exact actions.

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

A Green Form is done by handling every read, not by "uhuh" or nulling it, or doing it after the GF is all done.

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

Observe the Auditor's Code in every line and do the usual and solve the case.

(2) Audited on squirrel process.

Standard action in handling Green Form ARC Brks PTP and M/W/H (a) Itsa (b) If not cleared on Itsa get the basic on the chain. All GF and L and ruds follow this rule. A process is not used except ARC break ARCU CDEI.

(3) False Auditor Report – flunk flunk.

Always do a list like L1, L4 or GF, etc., by handling each read as it's found.

(4) Audited past F/N.

Random auditing on pcs and pre-OTs should not be done.

(5) Auditing a pc while on medication.

Knock off these arbitrary "Somebody else thinks he needs a_____. " This is evaluative and a break of the Auditor's Code. Pcs can be stopped by over-repairs they just need to get on with it.

(6) Auditing a pc while ill.

Do standard GF and remedy actions and let pc or pre-OT get on with the next cycle of section or grade.

(7) Leaving pc with a problem.

It's the grade processes and OT levels that improve cases. The process the pc should be on is always the next grade.

(8) Auditing a pc on no sleep.

If TA rises between sessions, get it down with ruds and if that doesn't get it down, a Green Form. This is a standing order. TAs that won't come down with routine rudiments come down with GF.

(9) Nulling an L1 to largest read.

True of all rehabbing actions is you don't rehab on a high TA at session start. Only when it is just then overrun. Then you rehab it back to F/N.

(10) Not giving pc his item.

In ruds, all you know when you see a read is that the meter read and the question you asked. The meter read is not uniformly what you asked and can be a protest or a repeating false read. Usually one goes right along auditing but when pc shows any sign of protest or bafflement on a rud read, you routinely trace it for an earlier false read, find and clean it.

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

If an R/S won't clean up on a pc, clean up "Have you ever been accused of things you haven't done" as a process as the R/S may be from invalidation. Can also clean up protest.

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

R/S on a child may be:

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

(A) Don't tell. Somebody told him not to.

(14) Not following C/S instructions.

(B) Crime.

(15) Taking frequent breaks.

(C) Accusation – said you did something you didn't do.

You set up a case with F/N before you undertake major new actions. Always set up a case to be run. End off an action at F/N.

It's not safe to begin a session without an ARC Br check when there's been a time between sessions.

With pcs in sad effect, you should always check ARC break of long duration.

You treble time in session every time you take any breaks. To economize in auditing time (session time) you should cut out breaks as they get the pc in trouble when he's out of the room, then you have to clean it up and so time is lost.

No TA on a Sec Check means pc tends to be out of valence. Anybody has a few.

TA goes high and low when a pc is going into and to PT from a heavy past life.

Never tell a pc he will have another session in session as it continues the session and doesn't end it. An old old old rule.

You never let pc off cans in standard tech.

A persistent item that doesn't blow is usually a wrong item. Other symptoms could proceed from a wrong item.

A Prepcheck in nearly every case turns on and uncovers old ARC breaks. In doing a Prepcheck be alert for BIs, and ask ARC Br question.