Refs:

• HCOB 6 Oct 70 C/S Series 19 FOLDER ERROR SUMMARIES
• HCOB 19 Mar 71 C/S Series 30 C/S-ing AUDITOR — C/Ses
• HCOB 6 Apr 71 C/S Series 34 NON F/N CASES
• HCOB 3 May 80 PC INDICATORS
• E-METER INSTRUCTION FILM NUMBER 10 — „PC INDICATORS“

A surprisingly large percentage of FESes done contain unnecessary data or omit vital data.

An FES (Folder Error Summary) is a summary of auditing errors in a folder and on a pc’s case not corrected at the time the summary is done which keep the case from running.

One does an FES when the case isn’t running right or has bogged and one wants to know the reason why, so the case can be put to rights again.

The usual action is to find where the case was last running well and come forward from there noting the bug or bugs which can then be repaired. It does not take days to do this FES or even hours if the bog is recent.

A full FES or an „FES to PT“ is not a long-winded account of everything in the pc’s entire folder. It should simply consist of a consecutive series of times when the case bogged after doing well, what the goof(s) was that caused the bog, whether the error(s) was corrected and the name of the auditor and C/S who goofed.

Some of the so-called „errors“ recently found listed in FESes would be laughable if it were not for the amount of wasted time and expense caused the auditor and C/S and the trouble made for the pc.

A folder picked at random contained an FES with the following consecutive entries:

• „(date) Note from Supervisor — Bogged on course.“
• „(date) Pc finally gets CS 53 completed to F/Ning — a nice thorough job.“
• „(date) Is on SRD. Routes on MO lines. Teeth hurting.“
• „(date) Origin — Cramps (gas).“
• „(date) Attests SRD.“
• „(date) 2D upset.“

And so it goes throughout the entire „FES.“

What does any of it have to do with a proper FES? Nothing!

The FESer couldn’t have had a clue about C/S Series 19, 30 or 34 which are the relevant issues and was just filling sheet after sheet of paper with useless data and wasting his own time and the time of anyone having to read it and stalling the pc’s progress.

Such FESes can have the liability of throwing the C/S totally off the track of what is really bugging the case. An unthinking C/S may buy an FES like the above and totally misprogram the case, resulting in more wrong targeted auditing and more trouble for the pc.

The things that bog a case are detailed in the C/S Series issues referenced above.

It does take study of the folder to find the bug. But it has to be a bug that is affecting the case, or else the case won’t resolve.

Don’t waste your and others’ time with improper FESes. They invariably arrive at no product through great expense.

Understand the target of an FES, get useful FESes done and watch tech quality in your area increase.