For relatively new auditors and a smaller operation it pays for the C/S to personally check his auditors out in how to audit a process by checking them out on the theory and have them drill the process on a doll until the auditor and the C/S are both confident that the auditor can do it perfectly under trying circumstances. In a larger operation there will be a course room and a separate cramming section that does it for him. But starting out both the auditor and the C/S need a hands-on certainty about what exactly is being done and how. And this should be the C/S' basic attitude no matter how big the operation is. He has to be willing and able to step in at any point and demand that the basic skills of an auditor are the best they can be. It saves him from a lot of hardship to make this his top priority. The number of "mysterious cases" will reduce in direct ratio. It also saves the pc's and auditors for failed sessions.

Programs
The C/S always designs and works from a program. The basic program of any ST auditing is the Grade Chart. But each process on the Grade Chart is a Major Action and according to 'Auditors Rights' you do not start a Major Action unless the pc is F/N and VGI's. Therefore the pc will from time to time need a set-up program or repair to make him ready for Major Actions. On a daily basis the auditor will at least check the rudiments.

Also, if Grades and processes already done at a later time are found to be "out", meaning the pc is still hung up on them and did not get the expected benefit from them, repair is needed. The pc will first need a short repair (set-up), then he will need to complete these processes to their full End Phenomena. In the case of a Grade or Grades being out, previous processes run on that Grade will have to be checked and rehabbed or flattened if found unflat and additional items and processes may have to be run.

The C/S' work has a lot in common with good book-keeping. He has to carefully keep track of actions and their orderly succession and completion much as a book-keeper has to keep track of money and receipts. A good book-keeper will make sure money are spent wisely and correctly according to the company's or organization's rules and regulations, goals and purposes. When they are spent he will make sure that the goods bought are OK and put to good use. He will not accept the purchase of a machine that is never put to good use or just given a spin and then abandoned.

A C/S spends his processes    wisely and keeps track of the    return he gets - much like it was money.

In a similar way, you could say, the C/S designs the basic program for the pc. This is much like spending money to the book keeper. He will make sure each process is put to good use and the overall program is completed to the desired EP. The EP of a program may come about before all of the program is done, which is fine. The EP is what the C/S wanted, not just all the steps being done mechanically.

Sometimes the EP has not been brought about even though all the steps are done. In this case the C/S has to dive into his pocket to find additional steps for the auditor to do on the pc; he has to do an additional investment. He will watch it like a hawk to see that the auditor spends this investment right and gets the desired result on the pc. By completing programs in this fashion the pc's case will improve on a steady basis. It is an orderly campaign being conducted against the pc's Bank and case. Done this way the Bank does not stand a chance.

Session Instructions
The C/S grades the auditor's work. It can be from "Very Well Done" for a technically prefect session to "Flunk" for an awful auditor performance. The auditor with just a little bit of experience would suggest his own C/S instructions and ask the C/S to look them over and approve of them or write up new instructions for the auditor to go on. The auditor always works from written instructions.

Even an experienced field auditor working for himself would do that. If he had no C/S he would still C/S his own work and grade it. He would simply change hat after session and read through his own report, grade his work and write up a new instruction for the next session.

If an instruction is found to be unworkable, the auditor always have the options included in "Auditors Rights" he can apply. If he realizes it is still unworkable he should make sure to write down his full observation of the situation and end off. The reason for this is, that you do not want auditors to "C/S in the Chair", meaning coming up with new processes to do on the fly. This leads to incomplete cycles on pc's - Q and A. What you want is an orderly program executed in an orderly manner. This is how you keep getting results. This can seem a bit bureaucratic at times, but what works over time is proceeding from an orderly plan that is well thought out beforehand and then executed by the book. If it didn't produce the desired result you regroup and make a new plan before launching a new attack on the Bank.

When the auditor is done with the  session she writes it up so the C/S     can see exactly what was done and    how it went. Only written  communications about the  pc's case are allowed.

When the auditor is done with a session, he writes up his session, including Auditors Report Form, Folder Summary, etc., etc. per Auditors Admin chapter on ST-0. He then writes a suggested C/S for the next session and turns in his pc's folder to the C/S. Any communication about the pc between auditor and C/S is strictly done in writing. This ensures it all becomes part of the written record. You also want the C/S to keep a distance from the activity and any undue attempts to influence him by emotional talk. C/Sing has to be an objective thing based on the evidence and technical facts of the situation. The C/S simply looks over the folder, checks references, checks the pc's program and writes up or approves the next C/S for the auditor to do.

Ivory Tower Rule:   The C/S does not permit what he knows  of the tech and cases to be clouded by     "Human Emotion and Reaction" by others.    Part of a C/S's duty is to get the case  through it despite auditor opinions  and flubs or the opinions of others.

In looking over the session report the C/S will first check what instructions the auditor was supposed to do and make sure, that was what the auditor did. He will then check the overall outcome of the session. If there is a pc Examiner form it should show F/N and VGI's for the pc to be satisfactory. Also the session itself should end with an F/N, VGIs pc.

He would then check that each process run was run to its proper EP. Next he would read the details of the worksheets to make sure all was done according to the technical materials. He would make sure there were more good indicators than bad indicators, including good TA action and visible changes in the pc. Pc gains is what he and the auditor is working for in the final analysis. Good TA action means the pc is winning. Little or no TA action means it's not working right. The session is thus ultimately for the pc, but the C/S is doing "Quality Control" on the auditor's work. If he sees the auditor has misapplied the written materials in some way he will write a study order (on a Pink Sheet) or a cramming order for the auditor to do before he takes the same pc in session again.

Usually the C/S has an instructor    or other student drill the auditor. But     his basic attitude is "I'll see to it myself!".    He makes sure his auditors' basic skills  and knowledge of procedures are  drilled to perfection. Picture: Instructor  watching Assessment Drills.

Handling Auditors
The C/S has two main responsibilities,  1) he handles his auditors by on-the-job-training. 2) His ultimate responsibility is handling and solving the pc's cases. He is the person that programs the cases in the first place and ensures the programs are actually carried out and carried out correctly. He does not discuss the pc's case with the auditor except in writing through the pc's folder. If he drills his auditors himself they do not discuss pc's cases but can of course otherwise interact normally.

The C/S solves pc's cases by  moving pc's up the Grades when     things go fine. He studies the folder,    references etc. and uses all his  tools when pc's are not winning.

Solving Pc's Cases
As a pc's folder grows in size due to lots of good auditing there is more and more auditing history to keep track of. Thus for an extensively audited pc a folder study has to be done at different points. This Mini Hat is based on (1) Understanding the basic technology very well and (2) Folder Error Summaries (FES) as its stable data. An FES is a summary of auditing errors and pc difficulties. Knowing how things are supposed to run and knowing where it was less than perfect gives the scope of the C/S' work. When things are not running right the case has to be studied. You do a folder study. It is how you solve case difficulties. When an FES is done a Summary Form is usually filled out. Looking over such a Summary an experienced C/S will right away know how to get a pc back on track and winning on the Grades. We have expanded these Folder Error Summaries into Trouble Shooter Tools by listing references and handlings applicable to the many different situations they reveal. Thus folder study and the Trouble Shooter Lists are your ultimate weapons in solving difficult situations.

C/S Tools: C/S Dictionary Grade Chart    Trouble Shooter  Prepared Lists Auditor's Admin Cramming Tech. Materials