Integrity Processing has an important part to play in modern auditing. We have the datum that as a pc comes up in responsibility so does his recognition of overts. This factor can reriously hamper a pc’s progress. Integrity Processing is a case cleaning activity and it should be thoroughly and competently applied. It is not something to be done just for form’s sake. It is done to speed up the advance of the case. A person who has overts ready to be pulled just cannot make rapid progress as a pc, staff member, student, or in life until those overts are cleared. So don’t underestimate the value of Integrity Processing. Learn to do it. Learn to do it well and when you do it, go in and do an expert and thorough job.
Integrity Processing is a specialized type of auditing, and it takes a lot of skill and at times some courage to do it well. Auditors must not be kind nor yet unkind. This does not mean that you steer a lukewarm middle course between kindness and unkindness. Neither of these two impostors have anything to do with it. You just go in and audit, you go in to find — and that means dig for — overts. If you go in with pc’s needle clean and your questioning can get that needle to react, then you are winning.
The success of an Auditor can be measured by the extent to which he can get reactions on the needle and then cleaning those reactions getting more reactions and cleaning those and so on. The skilled Auditor gets to the root of the trouble and clears up a whole batch of overts at once by handling chains of overts to F/N.
Integrity Processing is done in Model Session. The beginning rudiments are put in and by the time you start the body of the session, in this case the Integrity Processing, the pc should have an F/N. The next thing is to tell the pc that you are going to help him to clean up, and really clean up, the questions on the Form that you are using. Remember it is the question you are going to clean — not the needle. You’ve already got a clean needle and you could probably keep it from reading on questions by bad TR 1, failure to dig, or just sheer bad auditing.
The next action is to announce the first question that you are going to handle, at the same time watching the meter for any read on first calling. It can be important to groove in the question. There are a variety of ways to do this, e.g. ask what the question means. What period or time the question covers. What activities would be included. Where the pc has been that might be something to do with the question. If any other people are likely to be involved. In other words, you are steering the pc’s attention to various parts of his bank and getting him to have a preliminary look. When this has been done using very good TR 1, you give him the question again. A small tick may now have developed into a real LF or BD. You take your pc’s answer and get the specifics. If he gives you a general answer you ask him for a specific time (or a specific example). Don’t accept motivators. If he gives you a motivator you say, “OK, but what did you do there?” and you want something before the motivator. Example: Pc: “I got mad at him because he kicked my foot.” Aud: “What had you done before he kicked your foot?” In this case the pc is giving an overt, “I got mad at him,” but in fact he is cunningly selling the motivator “He kicked me in the foot.” So the rule here is, “Go earlier than the motivator.” Similarly you don’t accept criticisms, unkind thoughts, explanations. You want what the pc has done and you want the Time, Place, Form and Event.
When you have succeeded in this you don’t leave it there. You ask for an earlier time he had done something like it and you keep going earlier. What you are after is the earliest time he stole, hit somebody, got angry with a pc or whatever is his “crime”. Get the earliest one and you will find that the others will blow off like thistledown.
Keep a sly eye on your meter and you can tell when you are in a hot area. Use it to help you to know where to dig, but don’t use it to steer the pc at this stage. This encourages laziness on the part of the pc. You want him in there foraging about and digging up his bank in the process.
Having once gotten a read on the question, the question is not further checked on the meter. One simply follows the chain back earlier similar (same chain). Use standard Integrity Processing procedure until an F/N is obtained with cognition and VGIs.
If you do this properly you will have a well satisfied pc. If he ARC breaks then you have missed something, so pull your missed withholds. A rising TA is a clue to something missed or a bypassed F/N. If pc isn’t happy — very happy — at the end of a question then you have missed something. Pcs will tell you a hundred and one things that are wrong with your auditing, the D of P’s instruction, the form of the question, etc., but they all add up to the same thing — something has been missed.
One word of warning. If you leave a question unflat, mark it on your Auditor’s Report and tell your pc it isn’t flat. It is very bad practice to end session on a question without first F/Ning that question.
[Above Bulletin is taken and altered from BTB 29 March 63 Summary Of Security Checking]