In doing a Former Release rehabilitation, if you find the point of key-out of the moment the pc was formerly released, and then the moment of key-in afterwards and then get the pc to Itsa these alternate points, one after the other, with a bit of guiding when you see a fall (telling the pc [who is thinking] the needle fell by saying, “What’s that?”), and then if you get off any unacknowledgment by the auditor in the rehabilitation session, and if you handle all such moments in the pc’s auditing history, recent or distant, you will get the TA down and momentary floats of the needle.

Then if you end it with the pc happy and all well in the release rehabilitation session, the pc will feel terrific and you will probably have regained the floating needle.

Remember it isn’t a repetitive alternate question, “What was keyed out then?” “What was keyed in then?” but a use of these and any such wording one after the other as Itsa invitations, until you get the TA off it and the TA down (and not up again on session comm cycle goofs).

By hitting the key-out, then the key-in in that former session where the pc went release, he or she really gets the charge off it and you’ve regained it.

I daresay you could take a stuck TA at 5 on an old-time pc and by locating the moments when he or she felt good in sessions and handling each one in turn until you get the pc happy he or she has “got it”, you would eventually get the TA to clear read and a momentary or continuously floating needle.

It’s gentle.

The only goof you can really make, aside from comm cycle and code breaks, is not to quit when the needle floats in your rehabilitation session.

The rule of all processing is never run a process further than it produces a Floating Needle with the TA between 2 and 3.

This applies to former release rehabilitating session as well. When that needle floats again, if it does, you have to gently “That’s it” and desist and send to Declare? To go on is to overaudit.

Good hunting.