Auditors Rights (HCOB 710823): Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
---- | ---- | ||
C/S Series 1 | '''C/S Series 1''' | ||
AUDITOR'S RIGHTS | '''AUDITOR'S RIGHTS''' | ||
AUDITOR RESPONSIBILITY FOR C/SES | '''AUDITOR RESPONSIBILITY FOR C/SES''' | ||
An auditor who receives a Case Supervisor direction (C/S) of what to audit on a pc is not discharged of his responsibility as an auditor. | An auditor who receives a Case Supervisor direction (C/S) of what to audit on a pc is not discharged of his responsibility as an auditor. | ||
The auditor has a series of responsibilities that are part of every C/S he gets to audit. | The auditor has a series of responsibilities that are part of every C/S he gets to audit. | ||
== Accepting the PC == | |||
No auditor is required to accept a specific pc just because the pc is assigned to him. | No auditor is required to accept a specific pc just because the pc is assigned to him. | ||
| Line 32: | Line 32: | ||
Thus an auditor has a right to reject or accept the pcs he is given. | Thus an auditor has a right to reject or accept the pcs he is given. | ||
== Accepting a C/S == | |||
When the auditor gets a C/S to do on a case and if he thinks it is not the correct thing to do he has the right to reject the C/S for that pc and require another one he can agree to. | When the auditor gets a C/S to do on a case and if he thinks it is not the correct thing to do he has the right to reject the C/S for that pc and require another one he can agree to. | ||
| Line 38: | Line 38: | ||
The auditor may NOT C/S in the auditing chair while auditing the pc. If he has NO Case Supervisor at all the auditor still audits from a C/S. He writes the C/S before session and adheres to it in session. To do something else and not follow the C/S is called ''C/Sing in the chair'' and is very poor form as it leads to Q and A. | The auditor may NOT C/S in the auditing chair while auditing the pc. If he has NO Case Supervisor at all the auditor still audits from a C/S. He writes the C/S before session and adheres to it in session. To do something else and not follow the C/S is called ''C/Sing in the chair'' and is very poor form as it leads to Q and A. | ||
== Stale Dated C/S == | |||
A C/S that is a week or two old or a Repair (Progress) Pgm that is a month or two old is dynamite. | A C/S that is a week or two old or a Repair (Progress) Pgm that is a month or two old is dynamite. | ||
| Line 49: | Line 49: | ||
Stale Dates only occur in poorly run backlogged Divisions anyway. The real remedy is reorganize and hire more and better auditors. | Stale Dates only occur in poorly run backlogged Divisions anyway. The real remedy is reorganize and hire more and better auditors. | ||
== Ending the Session == | |||
When the C/S he has is proving unworkable during the session, the auditor has a right to end the session and send the folder to the C/S. | When the C/S he has is proving unworkable during the session, the auditor has a right to end the session and send the folder to the C/S. | ||
| Line 57: | Line 57: | ||
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. | 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 Over Out Ruds == | |||
Auditing a pc on something else whose ruds are out is a Major Auditing Error. | Auditing a pc on something else whose ruds are out is a Major Auditing Error. | ||
| Line 64: | Line 64: | ||
The Dianetic Auditor is not excused from auditing over out ruds and in an HGC must be specially cautioned not to do so but return the folder for a new C/S. Better still he should learn to Fly ruds. | The Dianetic Auditor is not excused from auditing over out ruds and in an HGC must be specially cautioned not to do so but return the folder for a new C/S. Better still he should learn to Fly ruds. | ||
== Inability to Fly Ruds == | |||
If an auditor cannot get a rud to F/N, cannot get any rud to F/N, he is justified in starting a Green Form. | If an auditor cannot get a rud to F/N, cannot get any rud to F/N, he is justified in starting a Green Form. | ||
| Line 71: | Line 71: | ||
It is understood the auditor would use Suppress and False in trying to Fly ruds. | It is understood the auditor would use Suppress and False in trying to Fly ruds. | ||
== Sessions Far Apart == | |||
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. | 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. | ||
| Line 78: | Line 78: | ||
Rapid gain gets above life's annoyances and keeps the pc there. | Rapid gain gets above life's annoyances and keeps the pc there. | ||
== Unreading Items == | |||
When an item the 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. | When an item the 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. | ||
Revision as of 13:25, 28 December 2025
Document type: HCO Bulletin
Date: 23 August 1971
Author: L. Ron Hubbard
Place: Saint Hill Manor, East Grinstead, Sussex
C/S Series 1
AUDITOR'S RIGHTS
AUDITOR RESPONSIBILITY FOR C/SES
An auditor who receives a Case Supervisor direction (C/S) of what to audit on a pc is not discharged of his responsibility as an auditor. The auditor has a series of responsibilities that are part of every C/S he gets to audit.
Accepting the PC
No auditor is required to accept a specific pc just because the pc is assigned to him. If an auditor does not believe he can help that particular pc or if he dislikes auditing that particular pc the auditor has a right to refuse to audit that pc. The auditor must state why. The Case Supervisor, Director of Processing or Director of Review, nor any of their seniors, may not discipline the auditor for refusing to audit a particular pc. An auditor who refuses to audit his quota of hours or sessions is of course subject to action. Thus refusing to audit a particular pc, so long as one is not refusing to audit other pcs, is not actionable. "I do not wish to audit this pc because ______. I am willing to audit other pcs," is the legal auditor statement in the matter. Some pcs get a bad name with some auditors, some don't appreciate the auditing, some conflict with a particular auditor's own personality. There are such instances. It does not mean certain pcs cannot be helped by others. It is also true that an auditor who dislikes a pc may not do a good job so the rule also has a practical side to it. One auditor disliked young men and did a bad job on them. Another disliked old ladies and chopped them up in session. One pc had messed up several Scientologists and couldn't find anyone to audit him at all. We are not auditing people to make amends to the world. Thus an auditor has a right to reject or accept the pcs he is given.
Accepting a C/S
When the auditor gets a C/S to do on a case and if he thinks it is not the correct thing to do he has the right to reject the C/S for that pc 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. The auditor may NOT C/S in the auditing chair while auditing the pc. If he has NO Case Supervisor at all the auditor still audits from a C/S. He writes the C/S before session and adheres to it in session. To do something else and not follow the C/S is called C/Sing in the chair and is very poor form as it leads to Q and A.
Stale Dated C/S
A C/S that is a week or two old or a Repair (Progress) Pgm that is a month or two old is dynamite. This is called a "Stale Dated Pgm or 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 boss. It is dangerous to accept a Repair (Progress) Pgm if it is old. The 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. A program written in January may be completely out of date in June. Who knows what may have happened in between. Use fresh C/Ses and fresh Pgms. Stale Dates only occur in poorly run backlogged Divisions anyway. The real remedy is reorganize and hire more and better auditors.
Ending the Session
When the C/S he has is proving unworkable during the session, the 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 engram 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 judgement 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 Over Out Ruds
Auditing a pc on 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 auditing the pc over out ruds. The auditor can do one of two things: He can Fly all ruds or he can return the folder and request ruds be flown. The Dianetic Auditor is not excused from auditing over out ruds and in an HGC must be specially cautioned not to do so but return the folder for a new C/S. Better still he should learn to Fly ruds.
Inability to Fly Ruds
If an auditor cannot get a rud to F/N, cannot get any rud to F/N, he is justified in starting a Green Form. The auditor solution to no F/N on ruds is to do a GF whether the C/S said to or not. This is an expected action. It is understood the auditor would use Suppress and False in trying to Fly ruds.
Sessions Far Apart
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 series of sessions or a whole program 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.
Unreading Items
When an item the 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.
Original document header
HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex Remimeo All Auditors C/Ses SHSBC Acad Level IV Class VIIIs HGCs Class VIII Checksheet Class VI Checksheet Class III Checksheet C/S Course Checksheet HSST Internes HCO BULLETIN OF 23 AUGUST 1971 (HCO B 24 May 1970 Revised) (Revised to update and delete the O/R list and add Auditing Over Out Ruds. All changes are in this type style.)