The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Policy - Have we ever defined the word "POLICY"? Definition sought


Randy
1st July 2004, 04:14 PM
Have we ever defined the word "POLICY"?

What is a policy?

What makes it a specific type of document, different from others?

Can your policy be the procedure you follow, our is this an "apple" & "orange" thing?

db
1st July 2004, 04:24 PM
I've found two separate things:

1) The policy required by either 14K or 9K. It is a generic statement that drives the organization in regards to either quality or environment.

2) Level one documents. These are generic statements that give direction in regards to a particular aspect (speaking non-environmentaly) of the organization's QMS or EMS. These policies are the ones where most organizations simply re-write the standard and put in "we will" in place of "the organization shall". They are not required. I've seen instances where organizations have replace these with process maps for 9K

My take anyway.

Tom W
1st July 2004, 04:26 PM
Have we ever defined the word "POLICY"?

What is a policy?

What makes it a specific type of document, different from others?

Can your policy be the procedure you follow, our is this an "apple" & "orange" thing?

As I sit at work and do little else but ponder your question; I came up with this.

A policy is more like a guideline to me. It is the establishment of general guidelines and establishes the intent.

A procedure explains how you will meet these guidelines or intents.

That is a QUICK thought about your question. But then again I am pretty bored right now so I hope that made sense. :D

Mike S.
1st July 2004, 04:28 PM
FWIW, ISO ISO 9000 Introduction and Support Package:
Guidance on the Terminology used in ISO 9001:2000 and
ISO 9004:2000
says:

- course of action or principle adopted or proposed by a government, party, individual, etc.- any course of action adopted as advantageous or expedient

Rob Nix
1st July 2004, 04:30 PM
Taking a giant leap, since I've looked nothing up yet, I would say that policy is to procedure as principle is to law. The overriding idea is your policy / principle, whereas the manner in which the idea is accomplished is the procedure / law.

The principle regarding intersections is to safely make it through without collision; the law may establish stop lights or signs.

I might have a "no smoking" policy, but my procedure explains what must be done to enable the policy to work.

I might have an "open door" policy, but there may be a memo distributed that explains how.

I hope someone can do better than that. :)

Edit: Like Tom's reply but I must have slow fingers; I ended up 5th in the queue.

Al Rosen
1st July 2004, 04:32 PM
Policy:

A plan or course of action, as of a government, political party, or business, intended to influence and determine decisions, actions, and other matters:

http://dictionary.reference.com/search?r=1&q=policy

SteelMaiden
1st July 2004, 04:46 PM
Well, I think that there are probably as many definitions used as there are systems, but I'll share mine. I hope that this does not stray into any of those areas that we have agreed not to discuss, but here goes:

The policies are kind of like the ten commandments.."Thou shalt not kill" is the policy. We all have probably entertained the thought of causing grave or mortal bodily harm to a co-worker at one time or another.

We know that killing someone is not right so we then set up our own procedure on how to keep our fantasy at bay. Mine is to look objectively at the situation and distance myself for a period of time until I can discuss it reasonably.

Then I have a set of work instructions to help remind me of how to do that. First,I take a deep breath. 2nd, I ask for some time to think the problem over. 3rd, I isolate myself from the problem by taking a walk, buying a soft drink, or working on some small and easy task to let my temper cool. 4th, I look at the problem through the other person's eyes and try to see if I can understand their point of view. 5th, I basically perform some sort of investigation, just like I would do for a corrective or preventive action, to see if one side or the other has more merit, and if there is a logical compromise that can be reached.

The policy, then, is a set of rules or requirements to be followed to acheive a given process. My procedures are guidelines of major methods to be used to meet the policies as defined by the company, and work instructions are specific steps needed to carry out the procedures.

Good question, Randy, this is always tough to define, especially when creating a new system, or training new people.

Wow, I must be slow, when I started this there were no replies!

Randy
1st July 2004, 05:12 PM
You guys must really be bored to respond this fast :applause:

I used to teach that a policy is a theory that is brought into reality by action.

Peter Fraser
2nd July 2004, 04:10 AM
Have we ever defined the word "POLICY"?

What is a policy?

What makes it a specific type of document, different from others?

Can your policy be the procedure you follow, our is this an "apple" & "orange" thing?

Randy

First of all, it doesn't have to be a document - although you may write it down. My view is that the policies which an organisation follows are the intentions and principles which provide a framework and guidance for what it wants to achieve and how it will operate. So when you define and manage your operating processes, you need to take the policies into account.

So "getting into new markets" / "treating staff well" / "protecting the environment" / "being the best not the cheapest" ... are all policies which shape what you do and how you do it. Some of these may be unspoken, some of them are built into the culture of the organisation, and some will have to be reinforced constantly because they may make life more difficult for the folk doing the work.

Jim Howe
2nd July 2004, 03:33 PM
If I go back far enough I can remember that the QA Manual of a major aerospace firm that I work for was written based on letters of "STANDARD PRACTICE". These letters of "standard practice" were a controlled document and spelled out to all employees how business was to be conducted. As stated they were then used as the basis of the QA Manual.

Sometime later it was determined that the QA Manual contained and awful lot of procedures which led to constant revisions of the manual.

The QA Engineers were tasked with rewriting the QA Manual and extracting the procedures as a seperate entity. The manual was thus rendered as a collection of policies (standard practices) with a seperate procedures manual.

Now a days of course we are all using the tiered system and us old timers say Thank God! :)
Jim Howe