How to Write an ISO or API Compliant Quality Manual

April 8, 2014

Numbering Schemes: Would a Document Register Help?

May 12, 2014

Procedure vs. Work Practice

by Miriam Boudreaux | May 5, 2014

A reader recently asked, “What is the difference between a procedure and a work practice? For example, when a job is completed it is sent to Invoicing.

If there are any issues, it is kicked back to order processing, fixed, and retired to Accounting for processing. Do I need a procedure or a work practice for this?

Through the Grapevine

First, let us make some distinctions. A work practice is simply a “practice,” an “activity,” or a “process” (a series of activities). A procedure, on the other hand, is usually a written document that depicts the necessary steps of a practice, an activity, or a process. A work practice, an activity, or a process may or may not have a written, documented procedure.

Now, back to the reader’s question. When trying to decide whether or not you need a procedure for a practice, keep these three questions in mind:

Have you had issues with people deviating from the work practice in the past?
Do you want people to do things in a specific way?
Do you want to hold people accountable?

If you answered “YES!” to any of these questions, then you need a procedure. Ask yourself, “Would I rather have a new employee learn something through the grapevine or through a written, documented procedure?”

This article was published by Quality Digest on 06/04/2014.

Comments are closed.