Documentation requirements for ISO 17025 NABL

Documentation requirements for ISO 17025 NABL
User Rating: 0 (0 votes)

Once the decision for ISO/IEC 17025 accreditation is made, the laboratory develops and implements documentation in preparation for the accreditation assessment. Typically implementation follows these steps:

  1. The project owner forms implementation teams for different areas. It is critical that all affected departments at all management levels are represented in the teams.
  2. The project owner with the help of QA searches for an accreditation body and selects the one that best fits the laboratory’s needs. There are several ways to find accreditation bodies. Probably the best way is to ask other accredited laboratories about their experiences.
  3. The teams develop documentation such as procedures under the supervision of the project owner.
  4. The project owner arranges for staff training.
  5. Quality assurance performs an internal audit and initiates corrective actions, if necessary.
  6. The selected accreditation company performs a pre-assessment.
  7. The project owner initiates corrective actions.
  8. The accreditation company performs an accreditation audit.

7. Documentation
ISO/IEC 17025 requires different types of documentation, as illustrated in the documentation pyramid in Figure 7.

A policy documents the laboratory’s intent to implement ISO/IEC 17025. The Quality Manual is the top tier of the document hierarchy. It describes the approaches to achieve quality data. It also includes policy statements describing the laboratory’s intention to conform to ISO/IEC 17025 requirements. For example, a policy statement could be: All personnel involved in calibration and testing should be competent for the assigned task.

A process or generic procedure describes how various quality requirements can be achieved. For example, it describes how the requirement ‘Personnel should be competent for the assigned task’ can be implemented.

Standard operating procedures (SOPs) or Working Procedures are step-by-step instructions for how to exactly perform a specific task, such as calibrating a specific instrument.

Records are generated on a day-by-day basis, such as analytical results from product tests or calibration records of a balance.

All documents should be properly controlled. For example, each change should be authorized and logged, and the updated document should get a new revision number or code.

Policies and Quality Manual
Policies including the quality policy statement should be documented in the Quality Manual. Senior management should write the quality policy statement, which should outline the laboratory’s commitment to quality. The quality manual describes the quality system and documents the laboratory’s goal and overall concept for how to conform to ISO/IEC 17025. It should also describe how the remainder of the quality system documentation is organized. It should be developed by working groups representing different departments.

Processes or standard procedures describe how various ISO/IEC 17025 requirements can be achieved. For example, it describes how the requirement ‘All personnel involved in calibration and testing should be competent for the assigned task’ can be implemented. Another example is the laboratory’s approach to calibrating and checking different types of equipment. For a better understanding, process flowcharts should be included in a process description.

Standard Operating Procedures (SOPs) and Work Instructions
Routine activities follow documented procedures. These are typically defined as standard operating procedures (SOPs) or work instructions. While quality manuals and processes describe tasks and approaches, procedures and work instructions give step-by-step instructions on performing tasks. Examples of SOPs are procedures for checking and calibration of equipment. All laboratory SOPs should use the same format, to make writing and reading easier. A good practice is to have an SOP for how to author, review, approve, distribute, and update SOPs. Preferably senior members of anticipated user groups should write SOPs. This helps ensure that SOPs have the right level of information and are used and followed.

Records to demonstrate conformity with ISO/IEC 17025 and as required by customers should be retained for a specific amount of time. Examples are original laboratory observations, test results, supporting documents such as chromatograms, and training certificates and equipment calibration protocols. Checklists, forms, templates, and examples help implement quality work effectively and consistently. Examples of these include checklists and worksheets for vendor assessment, handling nonconforming test results, and for internal audits. These items help document specific tasks consistently and effectively.

Document Control
Development and maintenance of documentation should be controlled through document control and management procedures that are part of the management system. Documents include both internal, such as SOPs, quality manuals, and training plans and external documents, such as regulations, standards, test methods, and instrument operating manuals.
The procedure for document control should ensure that:

  • Official documents are created or acquired, reviewed, and approved prior to use.
  • Documents are uniquely identified with document and revision number, date of revision, and issuing authority.
  • A quality list with all controlled documents is maintained by QA. The list includes document and revision number, title, date of issue, date of last review, and locations.
  • Internal documents include page numbers and total number of pages on each page. Users of the documents are adequately trained before the documents are released.
  • Current authorized versions of documents are readily available at the user’s

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>