Risk Analysis - Voiding CPAR's (Corrective Preventive Action Request)

[bbelden]

I have been tasked with drafting a policy for determining when to not issue a Corrective action request and when to voids/cancel existing ones.

Any sugestions on or guidelines to follow?

bb,
Breeze through this thread and you may get some ideas. Particularly in respect to "commensurate with the risks encountered".

http://Elsmar.com/Forums/showthread....ure+and+goofed

[David Mullins]

Never, ever, ever discourage someone from initiating a documented action request - EVER.

4 case scenarios:
1. The only way to determine if a request, or the subsequent fixes are justified is to do an investigation and assessment. This is most easily accomplished if someone has recorded the event for you. The justification (or otherwise) can be money, risk, likelihood, impact, etc based.

2. Internal audits. NCRs can have a negative impact on the audit program (when raised from internal audits obviously), so I get the int auditors to write out an action request for each NCR and send the audit report and all attachments to me for review and publishing. After all, I have to register the action request/s too. I can then investigate and assess the identified nonconformance and validate it. If valid, I register the Action Request and record serial number/s on the audit report. If not valid, I talk it through with the auditor, and if we're both happy, I give it the flick. This is essentially the same as '1' above, however it avoids the potential animosity towards the audit program.

NB: The QM should be the normal arbitrator in determining the validity of Action requests

3. It, and anything remotely like it, will never happen again, ever - EVER.

4. Joe has just raised his fifteenth Action Request for the week, and his boss comes to you ranting about this bloody system. Together examine the requests and determine whether they have merit, or whether they are symptomatic of something else that is wrong. You may have to talk to Joe, without his boss, to get to the truth. Either way, the requests have help idenify a problem or trend.

[Mike S.]

Hi Aussie Bloke,

I can tell you're pretty passionate about this one! I don't mean to rile you more, but I gotta admit, I get really nervous whenever I see/hear someone say "never, ever, ever, ever" do _________ (fill in the blank). It seems to me there might be a few unusual circumstances where it might be better to handle a CAR without documentation. I think a few recent threads touched on examples but I don't have the time right now to find 'em.

It's just my opinion, but I think you should never, ever, ever, ever say "never, ever, ever, ever".

Mike S. said:

Hi Aussie Bloke,

I can tell you're pretty passionate about this one! I don't mean to rile you more, but I gotta admit, I get really nervous whenever I see/hear someone say "never, ever, ever, ever" do _________ (fill in the blank). It seems to me there might be a few unusual circumstances where it might be better to handle a CAR without documentation. I think a few recent threads touched on examples but I don't have the time right now to find 'em.

It's just my opinion, but I think you should never, ever, ever, ever say "never, ever, ever, ever".

Mike S.

That was my reaction, too, but I didn't want to get into a swingabout I just had an occasion when a Supervisor wanted me to issue a problem report because the HR person made a mistake on somebody's paycheck (shorted him two hours).
It was strictly personal and I told him to take a powder.
But, David did say that they review all that stuff before doing anything about it, so he would have tossed the guy out, too. Unless it was his paycheck!

How about this:

If it is bad issue a corrective action.

If it is not bad don't issue a corrective action!

MHO, Al...

[David Mullins]

Al,
Please define BAD.
You have reiterated bbelden's problem, not answered it!


Mike,
Sometimes I am passionate - this was not one of those times.
Dramatising my response - sure was.
I was hit by a car and went head first into a light post whilst cycling last weekend - that didn't rile me, so don't be nervous.
Have you ever had an action request cancelled? You'll never write another one unless out of spite or Homeritis.
Cripes, I gave 4 examples of when they weren't valid requests!
Mike, never, ever, ever rile me!


Energy,
Yes, I get the swings and roundabouts reference when you use them.
I had an ex-army colonel boss when I was working with the USAF, and he said there are 2 things you don't mess up on in terms of employees: their pay and their pay. In an organisation of 100, if you stuffed up one pay each week, you will have p!55ed off the entire workfore in under 2 years! (yes I know statistically, blah, blah....) HOWEVER, by documenting these instances, reviewing the trends, you could have used the management system to avoid upsetting the vast majority of the workforce, and fixed the root cause.
Never, ever, ever, stuff up an employee's pay!

bbelden said:

I have been tasked with drafting a policy for determining when to not issue a Corrective action request and when to voids/cancel existing ones.

Any sugestions on or guidelines to follow?

bb,

Drafting a policy will not work unless the policy states that issues will be handled on a case by case basis. Recently, we conducted a failed experiment in CA/PA with one of our business units. Everyone was encouraged to submit a problem detail report for anything that was wrong with the system. In a little over 2 months, we accumulated 138 reports. The root causes were never addressed. We have a thread about what is an acceptable response and employee arror was ruled out by the majority of the members. Our responses were, "Overlooked it", "missed it", "My mistake" and other admission of guilt. The decision was made to scrap the current method and develop a weekly "tick" list for any problems. We will then group problems by catagories and write CAR's for the top 2 or 3. You have to draw the line on frivilous complaints, unless you have the resources to throw at every problem. We'll get there, in due time. This "agreement" was made between Department Managers and there does not exist a written policy. You cannot create a policy that covers all things that can go wrong. Who's the judge? I would also be a little leery of showing a Customer or Auditor a policy that accepts nonconformances based on someone's idea of what is serious or not. JMHO