Home Book Store Toolstore Consulting Room Contact FAQs & Search About

FAQ Categories
Managing quality
Management systems
Manag't system standards
Identifying processes
Purpose and mission
Stakeholders
Policies
Key Performance Indicators
Critical success factors
Objectives
Measures
Targets
Process elements
Procedures
Maintaing quality systems
Measurement
System auditing
Customer complaints
Problem solving
Training

 

Procedures/FAQ 1 / FAQ 2 / FAQ 3 / FAQ 4 / FAQ 5 / FAQ 6 / FAQ 7

What does not need to be included in procedures?

 

 

There are several reasons for not documenting information.

  • If the course of action or sequence of steps cannot be predicted a procedure or plan cannot be written for unforeseen events.

  • If there is no effect on performance by allowing freedom of action or decision, there is no mandate to prescribe the methods to be employed.

  • If it cannot be foreseen that any person might need to take action or make a decision using information from a process, there is no mandate to require the results to be recorded. (However you need to look beyond your own organization for such reasons if demonstrating due diligence in a product liability suit requires access to evidence)

  • If the action or decision is intuitive or spontaneous, no manner of documentation will ensure a better performance.

  • If the action or decision needs to be habitual, documentation will be beneficial only in enabling the individual reach a level of competence.

For more information see ISO 9000 Quality systems Handbook
 
 
 

 

Active scripting needs to be enabled in IE to use the pull down menus
Last amended 26/08/2008
Home | Book store | Tool Store | Consulting Room | Contact

© Transition Support 2008