8 NOVEMBER 1972RA Issue II Revised 4 June 1975 | 8 NOVEMBER 1972RA Issue III Revised & Reissued 13 July 1974 as BTB Revised 20 November 1974 Cancels BTB OF 8 November 1972R Issue III, Same Title (Paragraphs 6, 7 & 8have been revised) |
INVOICE FORM AND ROUTING FORM | |
The Form of Board PL 3 Jan 72 (Revised) is stapled to the inside back cover of the pc’s current folder by HGC Admin. | |
FOLDER ERROR SUMMARIES | PC BEGINNING INTENSIVE |
Ref: | When a pc signs up and pays for auditing he arrives at the HGC Admin with a Routing Form and a Pink Invoice Copy. |
| The Invoice is used for pc scheduling, verification of payment before delivery of service, and preparation of the weekly income report. |
The Invoice does not go into the pc auditing folder and must not be lost as this could prevent scheduling, delivery of service, or result in auditing without payment. | |
The Invoice details are filled in on the Form (see attached) at the back of the folder. | |
(NOTE: Data for this revision was taken from LRH's written reply to a letter from former Tech C/S ASHO.) | The Invoice is placed in the basket of invoices for the weekly income breakdown sheet, and afterwards filed in a weekly envelope with the Tech copy of the weekly income breakdown sheet in Tech Services. |
TWO METHODS OF FESing | Advance payment invoices received are filed alphabetically in files in Tech Services. When the invoice indicating final payment of service is received, all related invoices for that person and service are pulled out of the alphabetical AP files and stapled to the final payment invoice, and the name and date of expected arrival posted up on a board in Tech Services. The invoices are filed alphabetically in a special file containing only paid up invoices, which are the Tech Div “hot” files for new students and pcs. |
There are two methods of FESing a case. The first is a full detailed FES where one goes back and picks up and notes down all past errors on the case so that a Progress and Advance Program can be done. | The Routing Form is paper-clipped to the front of the folder. |
Where the C/S is interested in handling the case more rapidly, the procedure is to go back to where the Pc was running well and come forward, looking for the goofs to repair. This would also apply in the case of a Pc who, already repaired, was goofed in further auditing. | The Auditor enters the Intensive Hours paid (i.e. 121/2 or 25) on his next Auditor’s Report Form and keeps a running total of hours used on the succeeding Auditor’s Report Forms. |
These are different FES methods-a Progress Program and Repair C/Sing. Neither one includes Admin errors or errors which do not affect the case. | PC RUNS OUT OF PAID HOURS |
THE FLAW | When the pc’s used total approaches close to the Intensive Hours paid, the Auditor puts a note on the front of the folder to HGC Admin to route the pc to buy more hours. |
Folder Error Summaries (FESes) which do not show clearly whether an error has been corrected later in the Pc's auditing, can lead the C/S into over-repair. Such a flaw lessens the usefulness of an FES. | HGC Admin routes the pc through lines to buy more hours. |
NEW FORMAT | These particulars are noted on the Invoice Form. (See attached form for example.) |
To handle the above flaw, the layout and contents of the FES have been revised. The following is the format of the FES which should be on legal or equivalent size pink or red paper according to availability. | FREE SERVICE = FREE FALL |
One can see at a glance that all the noted errors have been corrected. A blank space in the right-hand column would indicate that the error had not yet been fixed. | An auditor continuing to audit a person over and above the amount of hours signed and paid for, and who does not send that pc back to the registrar for sign-up and payment of additional hours in order to successfully complete the auditing PGM, is guilty of |
This column is filled in by the FESer as he goes along, or by the Auditor as correction is done. For example a note: | A. Covertly robbing his fellow staff members of their pay, and |
Chronic high TA would be marked off by the Auditor C/S 53RJ to F/N List. TA normal with the date, when that action had been completed. | B. In a condition of doubt to his org, and is so assigned. |
Any error noted in the correction of the case IS NOTED AS A NEW ERROR ON THE FES. | Similarly, an auditor continuing to audit a staff member over and above the amount of hours signed and invoiced for, and who does not send the pc back to the registrar and cashier for sign-up and debit invoicing of additional hours in order to successfully complete the auditing PGM, is guilty of A and B above. |
THE FES IS KEPT IN PT BY THE AUDITOR AS ERRORS ARE NOTED. | Invoices for staff services must carry the mention: |
The C/S will use the FES as a help in further programming of the Pc. | |
It is kept in the inside back cover of the Pc's folder. | and be accompanied by a signed promissory note for the full amount of the service. |
WHAT IS WANTED IN AN FES | An Auditor using the Invoice Form in conjunction with the running total of hours on his Auditor’s Report Form will comfortably know the position with regard to used up hours. |
An FES should contain those points of error in the auditing of a case which might cause the Pc future difficulty or may require handling. These would include rundowns left unflat or with missing steps; signs of unflat grades; absence of any of the parts of EP, noting what was being run; any chronic problem or difficulty; by-passed EP on any rundown; illness or ethics trouble after an auditing cycle. | References: |
The most important points which can bog a case are well covered in the C/S Series, with which an FESer should be familiar. In particular, anyone doing an FES must know very well C/S Series 1, 2, 15, 19, 29, 30, 34, 38, 59. He must be able to recognize and pick out any of the case errors described in the above issues. |
|
Anyone doing FES work must be thoroughly familiar with the GF40XRR. Anything on the case which falls under any of the headings on this list should also be clearly noted in the FES, Pc was a member of black magic society could be the thing which is stalling her case. | |
WHAT ISN'T WANTED | |
An FES is NOT the same as an FS. The 2 must not be combined or confused. | |
Opinions have no part in FES. | Training & Services Bureau Revised by CS – 5 Ens. Judy Ziff In co-ordination with Flag Mission 1234 I/C: CPO Andrea Lewis 2nd: Molly Harlow Commodore’s Staff Aides Approved by the Board of Issues for the BOARDS OF DIRECTORS of the CHURCHES OF SCIENTOLOGY |
Do not note admin errors in an FES. | |
Any error which is not part of the case or its auditing has no place on the FES. | |
It can be the subject of a chit or separate report. | |
Examples of this would be: Auditor did not fill in the Folder Summary or Pc not being audited on any program or No-one C/Sing the folder. | |
Statements which R/Sed, and Ev Purps given off by the Pc are not usually noted in an FES. THE FACT THAT HE DOES R/S, OR DOES GIVE OFF EV PURPS MUST BE NOTED ON THE LEFT-HAND EDGE OF THE PC'S TOPMOST PROGRAM. | |
R/S statements (which the Pc said that R/Sed when he said it) and Ev Purps are noted on the Pgm in red ink and may be noted on the FS. | |
Dianetic chains that did not go to EP, flows not run, are noted on a Full Flow Table, not on the FES. The fact that a series of items was run F1 only, or did not EP, is noted on the FES, to be marked off when corrected. | |
A C/S and his FES unit work closely together and the C/S would usually apprentice these people until they can very rapidly and accurately FES even a thick folder. | |
Flag Tech Comps I/C for W/O Ron Shafran, CS-4 Approved by Commodore's Staff Aides and the Board of Issues for the BOARDS OF DIRECTORS of the CHURCHES OF SCIENTOLOGY | |