The responsibility of a Solo Auditor who receives a Case Supervisor direction (C/S) of what to audit is NOT discharged of his responsibility as an Auditor.

THE SOLO AUDITOR HAS A SERIES OF RESPONSIBILITIES THAT ARE PART OF EVERY C/S HE GETS TO AUDIT.

When the Solo Auditor gets a C/S to do and he thinks it is not the correct thing to do, he has the right to return it to the C/S with the reason why and require another one he can agree to.

The Auditor does not have the right to start doing a C/S and change it during the session except as noted below.

A C/S that is a week or two old can be dynamite.

This is called a “Stale Dated C/S” meaning it is too old to be valid.

It should have been done sooner. The pc of last week when the C/S was written may have been well and happily employed but a week later may have headaches and reprimand from the body.

The Solo Auditor who sees his C/S is old and sees the pc has Bad Indicators is justified in demanding a fresh C/S giving his reasons why.

Use fresh C/Ses.

When the C/S he has is proving unworkable during the session, the Solo Auditor has a right to end the session and send the folder to the C/S.

Ending the session is totally up to the Auditor.

If the Auditor just doesn’t complete an action that was producing TA and could be completed it is of course a flunk. Such a case is just not running a basic incident the one more time through that would bring the TA down and give a proper end phenomena. This and similar actions would be an Auditor error.

The judgment here is whether or not the Auditor’s action is justified in ending the session.

Even though he may have made an error, the Auditor cannot be blamed for the ending off of the session as that is totally up to him. He can be given a flunk for the error.

Auditing a pc or pre-OT something else whose ruds are out is a MAJOR AUDITING ERROR.

Even if the C/S omits “Fly a Rud” or “Fly Ruds” this does not justify the Auditor from auditing the pc over out ruds.

The Solo Auditor can do one of two things: He can fly all ruds or he can return the folder and request ruds be flown.

If an Auditor cannot get a rud to F/N, cannot get any rud to F/N, he is to end the session and send the folder to the C/S.

This is an expected action.

It is understood the Auditor would use Suppress and False in trying to fly ruds.

When a pc has not had a session for some time, or when a pc gets sessions days apart RUDS MUST BE FLOWN. Otherwise the pc will get audited over out-ruds. This can develop mental mass.

Optimum session scheduling is a whole Advanced Course done in a block of sessions close together. This prevents the world from throwing the pc’s ruds out between sessions.

Giving sessions far apart barely keeps up with life. The auditing time is absorbed in patching life up.

Rapid gain gets above life’s annoyances and keeps the pc there.

When an item the Solo Auditor has been told to run doesn’t read on the meter, even when the Auditor puts in Suppress and Invalidate on it, the Auditor MUST NOT do anything with the item no matter what the C/S said.

It is expected he will see if it reads and use Suppress and Invalidate on it. And if it still doesn’t read he will be expected NOT to run it.

When the Auditor sees the TA is high on 2 cans (out of normal range) at session start yet the C/S says to “Fly a Rud” the AUDITOR MUST NOT TRY TO FLY A RUD.

Trying to bring a TA down with ARC brks or ruds is very hard on a pc as ARC Breaks aren’t the reason TAs go up.

Seeing a high TA at start the Solo Auditor does not start the session but sends the folder back to the C/S.

By carelessness the same process can be called for twice and done twice or even more.

A Folder Summary inside the front cover must exist and must be kept up.

Never neglect entering a session and what was run on the Folder Summary (FS).

Don’t copy worksheets from notes.

Keep all admin neat and in the original form.

Copying makes errors possible.

When the ruds go out during the session the Solo Auditor recognizes the following:

A Solo Auditor who isn’t sure what it is but runs into trouble with the pc is smart to end off the session quickly, writs down the full observation and get it to the C/S.

The Solo Auditor who is an old hand and knows what he is looking at as per above scale (and the C/S the C/S would give) handles it promptly.

The Solo Auditor has no business trying to do the C/S given when it collides with and isn’t designed to handle any of the above.

The vilest trick that can be played on his pc is for a Solo Auditor to falsify an auditing report.

It may be thought to be “good Public Relations” (good PR) for the auditor with the C/S.

Actually it buries an error and puts the pc at risk.

INTEGRITY is a hallmark of Dianetics and Scientology.

Just because psychiatrists were dishonest is no reason for Auditors to be. The results are there to be gotten.

False reports like false attests recoil and badly on both the Auditor and pc.

A Solo Auditor has a right to know what he did wrong in the session that went wrong.

Most often a sour session occurs only when the rules and data in this HCOB have been violated.

But an Auditor’s TRs can go out or his handling of the process is in error.

Not only does an Auditor have the right to be told what was wrong but he must be given the exact HCOB, date and title, that he violated.

Never take a verbal or written correction that is not in an HCOB or tape. Don’t be party to a “hidden data line” that doesn’t exist .

“You ruined the pc!” is not a valid statement. “You violated HCOB_________ page_____” is the charge.

No Auditor may be disciplined for asking “May I please have the tape or HCOB that was violated so I can read it or go to Cramming.”

If it isn’t on a tape, a book or an HCOB IT IS NOT TRUE and no Auditor has to accept any criticism that is not based on the actual source data.

“If it isn’t written it isn’t true” is the best defense and the best way to improve your

tech.

These are the rights of the Solo Auditor with relation to a C/S. They are all technical rights based on sound principles.

A Solo Auditor should know them and use them.

If a Solo Auditor stands on these rights and gets beaten down he should put all the facts before his nearest OTL or SO ship as something would be very wrong somewhere.

Solo Auditing is a happy business - when it is done right.