Monday, 15 August 2011

change certification dates – a good idea?

Personally, to change a certification date, a precertification date or a post certification date is not best practice.  In fact, to a certification body (CB) and or the friendly auditor, it hints at the priority your company is placing on either the certification  process or the quality management system itself.  Do it too often and the desired business relationship could be soured.

Most organisations change these dates for a number of reasons, the least being sound business judgment or external business factors (other than survival), and if it is the latter, then perhaps certification, could well be the expense that breaks the camel’s back.

Your quality management system should be able to operate no matter what the current business status is, assuming the organisation can continue to operate without key personnel for an hour, a day, a week?  Second in commands, explicit instructions, pre-prepared records, audit trails, etc can all be put in place in order to meet an agreed deadline or event.  Sure there will be times when calendars don’t sync, but once they do, commit and prepare.  Don’t make it so low on your priorities that is the first date you think of changing when reviewing your time.

Remember, some CBs have quite heavy and intricate penalties for changing dates.  Most CBs use subcontracted auditors who book such events 2, 3, 6, 12 months in advance, to chop and change them within a week, 2 weeks or more will cause lack of income that cannot be reorganised with shorter lead times.  Then they may not be so accommodating with forward planning future audits or charge you more for fully flexible airfares just in case and so on.

The whole point being.  Commit to your quality management system, commit to your certification.  Give both priority and if you are only doing either for certification sake, be prepared to pay for this strategy and the baggage that comes with it.

previous blogs;
http://johnmasonstuff.blogspot.com
http://john-mason-stuff.blogspot.com/

0 comments:

Post a Comment