8 NOVEMBER 1972RA Issue II Revised 4 June 1975 | 8 NOVEMBER 1972R Issue I Revised & Reissued 6 August 1974 as BTB Cancels HCO Bulletin of 8 November 1972 Issue I, Same Title (The only Revision is under References: the Revision date of HCO B 21 April 71 has been revised to read – “Revised 14 May 72, Revised 8 April 74”.) | |||
THE DIANETIC FLOW TABLE | ||||
The Dn Flow Table is a chronological list of Dn Items run, from earliest to latest, with the flows that have been run. | ||||
FOLDER ERROR SUMMARIES | Here is an example of the way to do it: | |||
Ref: | ||||
| DATE | ITEM | F-1 | F-2 | F-3 |
|---|---|---|---|---|
| ||||
| 2 Feb 62 | Guf Shoulder | Unflat | ||
| 3 Feb 62 | Gow in Foot | EP | ||
| 29 Sept 67 | Chow in Chump | EP | ||
| (NOTE: Data for this revision was taken from LRH's written reply to a letter from former Tech C/S ASHO.) | ||||
| Unflat Repaired to EP 2 Oct 70 (red) | Unflat Repaired to EP 2 Oct 70 (red) | |||
TWO METHODS OF FESing | ||||
| 30 Sept 69 | LX Anger | Unflat | ||
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. | ||||
| LX Peeved | Unflat | |||
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. | ||||
| 4 Oct 70 | Feeling Numb | EP | EP | EP |
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. | ||||
| 16 Dec 70 | Ext/Int R/D | Sec | EP | EP Unflat |
THE FLAW | ||||
| Eng | EP | EP EP | ||
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. | ||||
| 3 May 72 | Intention to fall off a log | EP | EP | EP |
Any flow that is later repaired is marked on the table in a different colour, with the date.
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.
The Flow Table is kept at the back of the folder for reference and use.
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.
References: HCO B 21 April 71RA “C/S Series 36RA, Dianetics”. (Revised 14 May 72, Revised 8 April 74)
This column is filled in by the FESer as he goes along, or by the Auditor as correction is done. For example a note:
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.
Any error noted in the correction of the case IS NOTED AS A NEW ERROR ON THE FES.
THE FES IS KEPT IN PT BY THE AUDITOR AS ERRORS ARE NOTED.
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.
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.
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.
An FES is NOT the same as an FS. The 2 must not be combined or confused.
Opinions have no part in FES.
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.