Inside Quality Insider

  •  

  •  

  •  

  •  

     

     

  • SUBSCRIBE

Miriam Boudreaux  |  07/27/2012

Miriam Boudreaux’s picture

Bio

Document Review: Do I Have To?

ISO 9001 requires that your procedures and work instructions are always accurate

Deciding how to control your documents can be difficult. ISO 9001, the quality management system (QMS) standard from the International Organization for Standardization (ISO), requires you maintain accurate and up-to-date procedures, but doesn’t give a lot of guidance on how to get there. Between the requirements and the implementation lie grey areas and confusion. Let’s take a look at the difference between what is required and what is a good idea in the world of document review.

When I say procedures, what does that include?

A procedure is a way of carrying out an activity; it explains who does what, where, and when; it’s a document that defines a process. ISO requires that your procedures, work instructions, etc. are always accurate and truly represent the steps to completing a process. How you ensure that accuracy is up to you.

A procedure could describe the process for obtaining customer feedback (e.g., using scheduled customer surveys, or calling customers and saying specific scripts). Review procedures to ensure workers have the most current, complete, and accurate information to do their job.

Do you have to review your procedures once a year?

As per ISO 9001, you do not have to review procedures once a year. How often you review procedures depends on the complexity of your business activities. Some people may decide to review their documents every two years and others every three years. In a company where processes are dynamic and procedures are constantly being revised, there may not even be a need for a formal review, since the procedures are probably being reviewed every time they are updated.

So, do I really need to review procedures periodically?

If your organization doesn’t update procedures very often or isn’t well-disciplined about updating procedures every time a process changes, then it may benefit from implementing a set review time.

I once audited an organization whose procedures were 3 years old. Basically it changed its processes and never went back to update its procedures. That was not good. A lot of the information wasn’t applicable anymore. It decided to implement a set review date every year. 

On the other hand, I audited a company with procedures that were 7 years old and still accurate because its business was not dynamic. In this case, even though everything was fine, the company decided to implement a review date of every three years; perhaps this would force it to consider better ways to do things, given that technology is always changing.

Periodically conduct employee surveys regarding the usability of procedures, and schedule times to monitor and review processes to measure the performance and effectiveness of the processes to identify opportunities for improvement.

What is the final word?

Hopefully you get the idea that there isn’t a right or wrong way to do document review. Remember that ensuring that your procedures, work instructions, and forms are true to what your company actually does is the ultimate goal; your organization must decide how to accomplish that goal.

Discuss

About The Author

Miriam Boudreaux’s picture

Miriam Boudreaux

Miriam Boudreaux is the president of Mireaux Management Solutions, a consulting and technology firm headquartered in Houston, Texas, providing ISO and API consulting, ISO and API training, internal auditing services, and implementation of the Web QMS hosted software platform. Miriam holds bachelor’s and master’s degrees in Industrial Engineering. She is an RABQSA certified QMS and ISMS auditor, ASQ Certified Quality Engineer (CQE), and a Certified Quality Manager (CQM). She has served as an examiner with the Texas Award for Performance Excellence and participates as a speaker at various conferences throughout the year.

Comments

Procedures

Hello Miriam,

Nice article, thank you.  I often use two meanings for "procedure".  One is the ISO 9000/quality system context in which procedures are level 2 documents, distinguished from level 3 work instructions.  Another meaning for me is "all written processes" or even "all processes whether written or not".  Of course some people like to debate this meaning.  In your article you seem to use procedures to mean "all written processes".  Do you agree with that usage?  If not, what term do you use when you want to say, "procedures and work instructions, but not forms"?

Jim Cook

Procedures vs Work Instructions

Thanks for your readership Jim! Ahh...the old pyramid of procedures, work instructions, etc. You are correct, I talk about procedures in general terms because in my view everything that provides a way to do something is a procedure. So a Work Instructions is in essence a step-by-step procedure to do something. I probably should have said Documents. I do think Work Instructions should also be reviewed along with forms and any other policy or procedures. Reviewing all these "documents" on some kind of frequency should help keep the system in check - should people not be diligent about updating documents when processes change. Hope this helps! Miriam

You can create content!

  • Classifieds
  • File Share
  • Forum Topic
  • Events
  • Links

Sign In to get started!