Tips for Writing Effective Error Notifications

Write down as much relevant information about the error as you can find. Please include the following:

1) the name of the system you are searching

2) facility identification information (preferably the system identification number)

2) the data field in question

3) the section heading on the page for the data field in question

4) chemical name information, if applicable

5) reporting year, if applicable

Please be specific. There is no such thing as reporting too much detail. Here are examples of effective error notification language (pertinent information has been highlighted):

Example 1: Facility Identification

While looking at the results of a Facility Information Query, I selected the PCS National System Record, System ID = IN0040444. On the Facility Detail Report for this record, the Facility Name "NORTH WEBSTER MUNICIPAL STP NORTH" should be changed to 'NORTH WEBSTER WWTP" and the Postal Code, which is blank, should be 46555.

Example 2: Chemical Releases

While using the Toxic Releases Query Form, I noticed an error on the Envirofacts TRIS Report for ASHLAND SPECIALITY CHEMICALS CO., TRI ID = 94560SHLND6404E, under the heading, "Names and Amounts of Chemicals Released to the Environment by Year". The row for Hydrogen Fluoride releases to AIR FUG, for 1997, shows a value of 1610. Note that the real values should be 161. It appears that an extra 0 was added to this value.

Example 3: Permit Information

From the Hazardous Waste Data Query Form, the Process Information query results for ASHLAND CHEMICAL CO., HANDLER ID = CAD044046274, under the heading "List of Process Unit Information for Group "Tankstr1" contains an error. The Legal Status for process S02 (Tank Storage) shows 'INTERIM STATUS'. The Legal Status should be changed to "PERMITTED".

This amount of detail will allow EPA to begin research on this error. The System Action Officer will be able to go directly to the data field in question in the source system, verify the error and make corrections as necessary. These corrections should be reflected in Envirofacts during the next refresh schedule.


Click here to go back

Last modified on April 21, 2000