Guidance for Preparing Standard Operating Procedures (SOPs)

Data ML005
Rev. # 0.0
Date: 11/00
Page 14 of 16
methods used was specified by the QA Project Plan, note it here. If one or
more of the methods used deviated for that specified by the QA Project
Plan, note it here, and explain the deviation. If samples required repreparation
or re-analysis, note that here.
9.2.3 The purpose of the analysis, if known from the QA Project Plan, should be
summarized in a sentence or two. Action limits, such as permit limits, or
TCLP extract limits, should be stated, if known.
9.2.4 If analysts other than the preparer of the narrative participated in the
analysis in any way, their contribution should be documented.
9.3 Quality Control: All QC audits detailed in Sections 6.5 to 6.14 should be within
control limits, or if not, the outliers listed here. Significance of the outliers to the
usability of the data is discussed with reference to the acceptance criteria. If no
acceptance criteria are available for the batch, evaluate against the analysis SOP.
9.4 Technical Review: If any of the situations described in Section 7 affect the data
and result in a data flag, describe the condition here.
9.5 Electronic Data Inventory: The file names and paths for all electronic files used in
generating the final report is given. The paths given should direct the reviewer to
all data placed on the laboratory information management system (LIMS) per the
upload protocol (SOP xxxx).
10. References:
SOP xxxx, Protocol for Upload of Inorganic Data to the LIMS, Revision 5, October 2000.
SOP xxxx, Analysis of Metals using GFAA, Revision 1, September 1998.
SOP xxxx, Analysis of Metals using ICP, Revision 0, January 1999.
QA/G-6 E-14
March 2001