It occasionally comes to my attention that auditors entering Classes V and VI do not believe a meter can be made to read big.

They settle for ticks, tiny falls, etc., of the sort that can be found usually in getting mid ruds in. In all auditing up to Class V the usual meter needle read is around an eighth to a quarter of an inch long at sensitivity 16.

The Mark V is designed to give good serviceable reads for the lower classes of auditing and is quite wonderful at it.

You can get the shivers seeing how close you can caving in the pc’s whole case by poor administration.

But the moment you enter the wide vistas of Class V, the whole character of meter needle behaviour changes, you go from tiny read to big read.

If the pc gives you any goal, for all our sakes, please record it in that session’s auditors report or in his papers if he is not in session.

In Classes V and VI tiny reads are used only for mid ruds as they were in lower levels. But in all work in goals, case analysis, plotting, finding items, checking things out, etc., reads are enormous.

And if the pc thinks of a goal it must be written down and handed over to the auditor to be recorded, with the date noted.

A new horizon of metering dawns and an auditor coming up through the lower levels, entering Class V and VI work, just doesn’t believe it. Most of his early mistakes in checking out goals or finding the wrongnesses are entirely based on this. He thinks a tiny read is enough and he uses it. Whereas he really must never use a small read for this work.

Any goal that is offered must become a matter of record so that it can be located bydate.

If a goal is a real GPM, it will read with great, intermittent, inconsistent slashes. If an analysis of a situation is brought to the right answer, the meter needle falls hugely.

Don’t lose the pc’s goals.

The trouble is that the auditor just doesn’t press on looking for the right answer and settles for ticks — because he can’t think up the right combination. The right combination “No GPM” or “Lock on an implant” will send the needle racing.

Attach them to reports and worksheets that are dated.

All mistakes on goals or situations in Classes V and VI can be traced to a failure to appreciate that metering is different at these levels.

Out of thousands of goals offered you may just glide over the key goal If you have recorded it by date, it can be recovered. If you haven’t, then I don’t know what you’ll do.

The sensitivity at Class VI has to be kept around 4. You only use sensitivity 8 or 16 to get in since mid ruds. On all R6 work you shut the meter down. You can’t keep the needle at set if you use a sensitivity higher than 4.

Here’s a Class V or VI student fiasco, based on using Class III expected meter behavior on high-level work:

If a pc develps a bad somatic, the chances are a goal has been invalidated or lost and invalidated.

Auditor finds goal on list that ticks (1/8"). Asks if it’s the correctly worded goal. Gets a tick (1/16"). Runs it on the pc. Pc collapses.

The only way you can get a somatic in R6 is actually to invalidate a GPM (skip it, miss it, fail to pick it up). The invalidation of the GPM causes the somatic.

Here’s the real way it should have been: Auditor finds goal on list that only ticks. Gets in Suppress and Invalidate on the list. Re-nulls. Finds another goal. Gets in Suppress on it. Gets a third of a dial instant slash (all goals and items must instant read). Checks it out until he gets a 3" prior slash on actual GPM. Gets a 2" slightly latent or prior slash on “correctly worded.” Gives it to the pc and pc thrives.

All human suffering basically stems from invalidated GPMs (and they are, of course, all skipped or missed and nobody has picked them up before we came along).

It’s not asking the right question (what it really is) that gives you ticks.

Thus, when a pc’s case is going badly and the pc has a nagging somatic, the cause is an invalidated GPM. A GPM, therefore, has been skipped, missed or been refused.

In fact a tick with a sharp edge at Class V or VI really means “wrong question asked!”

This is a sweeping fundamental: Somatics (meaning mostly pain in this case) are caused by Skipped, Refused or Missed GPMs. The exception is the sick stomach. This is always caused by a wrong goal. Somatics, meaning pain or lots of sensation, are caused by skipped, missed or refused GPMs. Sick stomachs (not cold stomach) are caused by wrong goals. Cold stomachs are caused by mis-placed (wrongly plotted) GPMs. A cold body is caused by Implant GPMs or a wildly mis-plotted Actual GPM that may also be an Implant GPM.

Big reads are the only reads you buy at Class V and VI. Learn the right questions to ask about the character or nature of what you’re examining and you get the big falls, RRs, etc.

Thus we see that a skipped, missed or refused GPM is the only one that causes pain or sensation. And we can see that skipping, missing or refusing a GPM all add up toinvalidating it.

So it’s a lack of knowledge of track analysis that makes the auditor fall back on small reads.

A wrong goal won’t ruin a case. Neither will the inclusion of an implant goal in the plot ruin a case. They only make the pc uncomfortable and will eventuall be found and thrown out.

And he’ll fail.

But the missed or refused goal once gone into the discard may have been vital to the case and, now being heavily invalidated, may never come up again.

The second stage of desperation enters at Class V and VI when the student, hammered by the Instructors, still can’t get big reads (through lack of knowledge of the track and what things can be).

So the GPM invalidated by being missed or refused is the dangerous one.

The student then abandons all he knew about body motion causing needle reaction. The quickly exhaled breath, the shuffled feet, the can fling about, the stretch, the can bang, all cause big surges. So the auditor encourages the pc to shout goals and items or fling himself about so the meter will react big.

If the pc’s records are in order and legible, if the auditor has recorded all goals mentioned by the pc, the missed or refused GPM can be located.

This, of course, will spin the pc, getting no charge off, running wrong goals and RIs.

How? This is an actual case:

By the time the student auditor is trained not to take body motion, shout or breath reads, his track analysis has also improved and he starts to ask the right questions and gets his big reads with the pc quiet as a lamb.

The pc’s goals plot just wouldn’t assemble. The pc was in considerable pain. “A goal has been invalidated” gave a third of a dial surge. The invalidation was dated on the meter. The session reort for that date was looked up.

I never touch a TA during the pc’s body movement. This loses TA, of course, since a pc is most likely to move when an RI starts to discharge. I never buy a goal unless I’ve seen it instant read, bang on the last letter. I never ask the character of anything to instant read, i.e. “Is this an implant GPM,” because it may go on anticipate or arrive latent.

And there recorded was a goal the pc had offered, the auditor had refused (since it wouldn’t read). This goal was checked out and was found to be one of a series of four GPMs that monitored the goals plot.

And do I get TA on the pc! In goals finding and plotting you don’t expect much TA. Yet in six consecutive sessions I built TA a few divisions more per session, from 70 TA down divisions to 103 TA down divisions in 2½-hour sessions, and all by never buying a tick, only big RRs or falls. Gradual build of TA shows all is well.

It had never again occured to the pc. It was so invalidated it seemed completely unreal to the pc. It was so unreal that every goal mentioned in that session had to be nulled as a goals list to find it. Only one goal gave the big invalidated surge first noticed. And only after a prepcheck (5 minutes) did it read.

So Classes V and VI are not only big read classes, but they are big TA classes as well.

As it had already been invalidated by life, it didn’t read when the auditor called it in that session and the auditor had not gotten in supress or invalidate on it.

As you are handling the basic sources of charge on a case in Classes V and VI, you expect big meter behaviour and you get it.

There was the whole case stalled.

Only ignorance of the track keeps the auditor in the small read, small TA departments.

If the auditor had not recorded it in that session report where it had a date on it, it would have been completely lost. In that session the pc had merely mentioned it as a possible goal, the auditor had said “that didn’t read”. A month later the pc started getting pains. Within four months the pc became very hard to audit.

If you keep on trying to get what it really is until you have it, you will always see a big read on what it is.

Tjhe lessons here are that one can date an invalidation or supression; and that an auditor must record every goal mentioned by a pc and make it part of the records coupled with a date.

You wouldn’t expect to handle high voltage wires with tiny sparks. You would expect huge arcs to crackle. Similarly with the materials of Classes V and VI.

That was a close call.

If you don’t believe a meter will read big at Classes V and VI, then you haven’t learned yet to find the right things and ask the right questions.

So if your pc is running with pain, a goal has beem missed or refused. It will read that “a goal has been invalidated”. The invalidation read can be dated and if recording has been done, the goal can be recovered.

And if you settle for ticks or have to make the pc yell items to get big reads you’ll soon have a very messed up case on your hands.

These are probably some of the most important Case Repair facts of R6.

So it’s a different meter behaviour at the higher classes. Expect it, look for it and make it R E A D!