It can happen that a Dianetic list of somatics, pains, emotions and attitudes can act as a list under the meaning of the Laws of Listing and Nulling as per HCOB 1 August 68.

The most violent session ARC Brks occur because of list errors under the meaning of listing and nulling. Other session ARC Brks even under withholds are not as violent as those occurring because of listing errors.

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.

Therefore when a violent or even a “total-apathy-won’t-answer” session upset has occurred in Dianetics, one must suspect that the preclear is reacting under the laws of listing and nulling and that he conceives such an error to have been made.

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

The repair action is to assess the prepared list which corrects listing errors. This is L4BRA – HCOB 15 Dec 68 amended to 18 March 71.

It is used “On Dianetics lists” as the start of each of its questions when employed for this purpose.

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.

When a pc has not done well on Dianetics and when no other reason can be found the C/S should suspect some listing error and order an L4BRA to be done “On Dianetic lists “ at the start of each question.

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

Each read obtained on the list is carried earlier similar to F/N as per HCOB 14 Mar 71 “F/N Everything” or, preferably the list is found in the folder and properly handled in accordance with what read on L4BRA.

Dianetic lists can be carried to an item that blows down and F/Ns.

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

This does not mean the item found is now wholly clean. Even though it F/Ned it will in most cases need to be run on secondaries and/or engrams (R3RA Quad) to erasure and full Dianetic end phenomena. (Ref: New Era Dianetics Series 1 through 18.)

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

A C/S must be alert to the fact that:

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.

(a) Extreme upsets and deep apathies are almost always list errors.

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.

(b) That a Dianetic list can be conceived to be a formal list and can behave that way.

Use fresh C/Ses.

(c) L4BRA is the correction list used in such cases.

(d) Laws of Listing and Nulling HCOB 1 August 1968 can sometimes apply to Dianetic lists.

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.

Very few Dianetic lists behave this way but when they do they must be handled as above.

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: