Never list a listing question that doesn’t read.

Never prepcheck an item that doesn’t read.

These rules hold good for all lists, all items, all flows, including Dianetics.

A “tick” or a “stop” is not a read. Reads are small falls or falls or long falls or long fall blowdown (of TA).

A preclear’s case can be gotten into serious trouble by listing a list that doesn’t read or prepchecking an item that doesn’t read or running an item or flow that doesn’t read.

On a list, this is the sort of thing that happens:

The list is “Who or what would fly kites?” The C/S has said to “List this to a BD F/ N item.” So the auditor does list it without checking the read at all. The list can go on 99 pages with the pc protesting, getting upset. This is called a “Dead horse list” because it gave no item. The reason it didn’t was that the list question itself didn’t read. One does an L4BRA on the pc to correct the situation and gets “unnecessary action.”

On a list that is getting no item you don’t extend. You correctly use L4BRA or any subsequent issue of it. If you extend a “dead horse list” you just make things worse. Use an L4BRA and it will set it right.

This weird thing can also happen. C/S says to list “Who or what would kill buffaloes?” The auditor does, gets a BD F/N item “A hunter.” The C/S also says to list as a second action “Who or what would feel tough?” The auditor fails to test the question for read and lists it. Had he tested it, the list would not have read. But the list comes up with an item, “A mean hunter.” It has stirred up charge from the first question and the item “A mean hunter” is a wrong item as it is a misworded variation of the first list’s item! Now we have an unnecessary action and a wrong item. We do an L4BRA and the pc is still upset as maybe only one or the other of the two errors read.

In a Dianetic “list” one is not doing a listing action. One is only trying to find a somatic or sensation, etc. that will run. The item must read well. Or it won’t produce achain to run. In actual fact the Dn list Q does usually read but one doesn’t bother to test it.

But an item or flow that doesn’t read will produce no chain, no basic and the pc will jump around the track trying but just jamming up his bank.

The moral of this story is:

ALWAYS TEST A LISTING QUESTION BEFORE LETTING THE PC LIST. ALWAYS MARK THE READ IT GAVE (SF, F, LF, LFBD) ON THE WORKSHEET .

ALWAYS TEST AN ITEM FOR READ BEFORE PREPCHECKING AND ALWAYS CHECK AN ITEM AND FLOW BEFORE RUNNING RECALLS OR ENGRAMS .

ALWAYS MARK THE READ AN ITEM GAVE (SF, F, LF, LFBD) ON THE WORKSHEET.

The whole subject of “charge” is based on this. “Charge” is the electrical impulse on the case that activates the meter.

“Charge” shows not only that an area has something in it. It also shows that the pc has possible reality on it.

A pc can have a broken leg, yet it might not read on a meter. It would be charged but below the pc’s reality. So it won’t read.

The Case Supervisor always counts on the AUDITOR to test questions and items

and flows for read before running them.

The auditor, when a question or item or flow doesn’t read, can and should always put in “Suppress” and “Invalidate.” “On this (question) (item) (flow), has anything been suppressed?” “On this (question) (item) (flow), has anything been invalidated?” If either one read, the question or item or flow will also read. The Case Supervisor also counts on the AUDITOR to use Suppress and Invalidate on a question or item or flow. If after this there is still no read on the question or item or flow, that’s it. Don’t use it, don’t list it. Go to the next action on the C/S or end off.