Sometimes interpreting ISO 9001 or API Q1/API Q2 requirements seems to force us to agree to things we won’t be able to do, or to sustain for more than a few months, let alone days. So how do we write our policies and procedures to explain our approach while avoiding being boxed in by our own words?
ADVERTISEMENT |
There are a handful of words or phrases you can use, as necessary, when you don’t want your procedures to be overly proscriptive. Call these “conditional” words or phrases (some might call it “hedging”). These words, when inserted into your procedures, may help you comply with the requirements of quality management system standards without backing yourself into a corner.
Leave maneuvering room in procedures or work instructions
Here are some useful words to include in your procedures or work instructions:
…
Comments
Using Conditional Words and Phrases
I must say I disagree with Ms. Boudreaux on the use of conditional words in process documentation. I have been in Quality for fourteen years, mostly as an ISO auditor. In my experience these are words and phrases that should be avoided. Whenever I see “as applicable”, “deemed appropriate” or “when required”, the next question I have is, “Where is it documented what is applicable/appropriate/required?” Unless those things are defined it is a very weak process. And typically, if you ask 10 different people to know this without it being defined, you will most likely get 10 different answers. Respectfully, Rhonda Case
A disagreement with the disagreement
Bingo
use at your own discretion
Five pages - Words !
The Bee Gees, Words, lyrics: " ... this world has lost its glory ... let's start a brand new story ... talk in everlasting words ... it's only words, and words are all I have".
Add new comment