To write or not to write. That is the question. How many procedures should I write?

U

unitedc

#1
During our last audit it our auditor suggested/requested that we write more Procedures. Our procedures as of now are for the most part department only. My company does contract manufacturing in mostly PC Boards. He suggested we write procedures on things such as out SMT (surface mount) line. I recently wrote a Procedure on shipping.

To my question: Where do you say 'thats enough Procedures'? Should a company have a procedure for everything that has a start and end? I realize we don't need procedures for restroom visits. I think you will get my point so I'll stop there. Thanks all!
 
Elsmar Forum Sponsor
M

MDQSA

#2
Re: To write or not to write. That is the question.

Our auditor told us that if it's important enough to write down, then it's important enough to put into an actual procedure. He was specifically commenting on guidance documents that we have.
Another point is that if it's for something that needs to be replicated the same way every time, then documenting it is a best practice
 

Jim Wynne

Leader
Admin
#3
Re: To write or not to write. That is the question.

During our last audit it our auditor suggested/requested that we write more Procedures. Our procedures as of now are for the most part department only. My company does contract manufacturing in mostly PC Boards. He suggested we write procedures on things such as out SMT(surface mount) line. I recently wrote a Procedure on shipping.
To my question: Where do you say 'thats enough Procedures'? Should a company have a procedure for everything that has a start and end? I realize we don't need procedures for restroom visits. I think you will get my point so I'll stop there. Thanks all!
Other than the mandatory "big six" documented procedures, you should have as many as you feel you need, and no more than that. Remember that one of the prime purposes of process documentation is establishment of standard methods. In such cases your people may never have a need to read the documents--assuming they've been adequately trained--but when processes are designed, the design and methods should be documented, which obviates relying on tribal knowledge in the future.
 
#4
Re: To write or not to write. That is the question.

During our last audit it our auditor suggested/requested that we write more Procedures. Our procedures as of now are for the most part department only. My company does contract manufacturing in mostly PC Boards. He suggested we write procedures on things such as out SMT(surface mount) line. I recently wrote a Procedure on shipping.
To my question: Where do you say 'thats enough Procedures'? Should a company have a procedure for everything that has a start and end? I realize we don't need procedures for restroom visits. I think you will get my point so I'll stop there. Thanks all!
Can you give us any more information as to why the auditor was making such a suggestion?

Did they see, for example, a lack of process control or poor product/process performance which might be improved by writing a procedure? Did the auditor detect a lack of consistency in the description (by management and responsible personnel) of the process and its controls, which might also indicate a procedure would be helpful?

If none of these, then your auditor is waaaaaay off in making such comments. Their comfort around more procedures is counter to the revised ISO 9001 requirements (circa 2000) which reduced the reliance on mandatory documented procedures. The auditor has one foot in the past.

I'd suggest that you respectfully ask your CB for an alternate who is a little more 21st century in their understanding of contemporary quality systems and requirements (possibly auditing techniques too):notme:
 
S

somerqc

#5
Re: To write or not to write. That is the question.

Andy,

The auditor may not be in the past. It could simply be that it is a process that the company should have documented is not (i.e. is critical, lack of one has resulted in some near-miss customer issues, etc.).

By all means, I preach the "only document what is necessary to document". I also try to create "multi-purpose" forms as much as possible (thereby less forms, less document control, easier for people to complete).

Just an alternate look at the issue.

Another rule I have recently added - If you are going to write a procedure, make sure that tells someone how to do something! Don't just write a procedure for the sake of having words on a page!!:mad:
 
#6
Re: To write or not to write. That is the question.

This is where 4.2.1 d) comes into play. A procedure is the specified way to carry out a process. My take is that if the absence of a procedure would lead to a deviation, then you need a procedure. If the process is so complex (or the competence of personel is marginal), that the steps used to enact the process needs to be formalized, then formalize them. If folks can follow the process without something in writing, and there is no consequence for deviation, then avoid a documented procedure.
 
#7
Re: To write or not to write. That is the question.

Hello! Didn't I say that?

Did they see, for example, a lack of process control or poor product/process performance which might be improved by writing a procedure? Did the auditor detect a lack of consistency in the description (by management and responsible personnel) of the process and its controls, which might also indicate a procedure would be helpful?

I thought that encompassed the examples you've given, folks.......
 
J

JaneB

#9
Re: To write or not to write. That is the question.

Can you give us any more information as to why the auditor was making such a suggestion?

Did they see, for example, a lack of process control or poor product/process performance which might be improved by writing a procedure? Did the auditor detect a lack of consistency in the description (by management and responsible personnel) of the process and its controls, which might also indicate a procedure would be helpful?
Really good questions Andy - and more info is definitely needed here, in order to respond to this question helpfully. Otherwise I'd simply be guessing.
 
S

Sam4Quality

#10
Re: To write or not to write. That is the question. How many procedures should I writ

Originally Posted by unitedc

During our last audit it our auditor suggested/requested that we write more Procedures. Our procedures as of now are for the most part department only. My company does contract manufacturing in mostly PC Boards. He suggested we write procedures on things such as out SMT(surface mount) line. I recently wrote a Procedure on shipping.
To my question: Where do you say 'thats enough Procedures'? Should a company have a procedure for everything that has a start and end? I realize we don't need procedures for restroom visits. I think you will get my point so I'll stop there. Thanks all!
Writing procedures for a quality management system can be a tedious task, especially the ones apart from the six mandatory documented procedures.

Sometimes, just because the quality engineer/manager within the company has a crush on making new documents or usage of language, he would insist on a document being cooked up, to his liking and to the ire of the process-owner. It can be that outrageous!

A vice-chairman of one of my past clients, was so very involved in his company's QMS documentation, that he insisted on making excruciatingly detailed micro-procedures and forms that not only found frustation and anger amongst the users, but also gave the VC a vampiric status! I don't know if anyone has come across this, but their core procedure (planning for product realization) was a whopping 46 pages (font: tahoma, size: 10, full A4 size)! And no matter how much I tried in vain to convince him otherwise, the more his stubborness towards his micro objectives!

Anyway, the point of all this is - documentation is pointless, if not by the process-owners, for the process-owners. Further, devising non-value adding procedures will ensure that they are happily yellowed down the years of its stagnant and worthless life!

I may be slightly :topic:, but just wanted to make a point about documentation.

Ciao.
SAM:cool:
 
Thread starter Similar threads Forum Replies Date
K Looking for guidance to write an SOP on Statistical Methodologies? Statistical Analysis Tools, Techniques and SPC 7
A Document Change Notice vs complete System re-write Manufacturing and Related Processes 4
K PQ validation qualification - Asked to write a PQ protocol ISO 13485:2016 - Medical Device Quality Management Systems 6
L How to write a proper defect description in a NCR Nonconformance and Corrective Action 4
qualprod When to write up a nonconformance and require a NCR - We produce labels ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 14
D Validation of existing equipment - I have been asked to write a quality assessment for equipment ISO 13485:2016 - Medical Device Quality Management Systems 13
M Medical Device Directive - Seeking common nonconformance write up scenarios CE Marking (Conformité Européene) / CB Scheme 2
N How to Write and Compile a Technical File for CE Marking CE Marking (Conformité Européene) / CB Scheme 4
qualprod Write down same nonconformity in several processes? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 10
A What ISO 9001:2015 clause could be used to write nonconformance for not updating licensed driver list? General Auditing Discussions 8
GStough Have You Had to Write a NC Against a Quality Manual in a Supplier Audit? General Auditing Discussions 12
D What is the appropriate way to write a conclusion from a % contribution result? Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 4
M Who should write Departmental Work Instructions Document Control Systems, Procedures, Forms and Templates 6
L Requirement to write a Detailed Inspection Plan (DIP) APQP and PPAP 6
E How to write requirements for Medical App Validation and Verification IEC 62366 - Medical Device Usability Engineering 7
Z What to write on A3 Methodology Recognition Certificates? Six Sigma 2
T SOP for How to Write a Specification for Raw Materials and Finished Good ISO 13485:2016 - Medical Device Quality Management Systems 3
alonFAI Update an existing QMS manual or write a new one for AS9100C Certification? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 2
E How to write a Project Plan to Overhaul our QMS ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 17
C How to write a Post Market Surveillance REPORT (not procedure) EU Medical Device Regulations 4
E How to write an Aseptic Media Fill Validation Document Other US Medical Device Regulations 2
Q Who must write Quality Manual as per ISO 9001 Clause 5.5.2? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 23
J Can An External Auditor Also Write The Same Non-Conformance As An Internal Auditor? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6
C How to Write Procedures without too many Details ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 17
B How do I tell my boss to write neatly without offending her? Career and Occupation Discussions 8
W How to write an EASA 145 Quality Manual EASA and JAA Aviation Standards and Requirements 3
N Do I Need to Write a CAR for..... (All Opinions Wanted :) ) ISO 13485:2016 - Medical Device Quality Management Systems 7
B I'm trying to write detailed Customer Service Work Instructions Customer Complaints 10
T How do I control web-based asp forms/rpts that write to and pull from an Access DB Document Control Systems, Procedures, Forms and Templates 4
P Internal Audit Corrective Actions - Can a CB write an NC on an in-process CA? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 27
J How to Write the Planned Interval to Conduct Internal Audit, Management Review, etc.. ISO 13485:2016 - Medical Device Quality Management Systems 3
A How to write a US FDA proof MDR procedure? Other US Medical Device Regulations 5
Y New Guidance for the Industry - How to write a Request for Designation (RFD) US Food and Drug Administration (FDA) 0
Q How to write Statement of Purpose for a Law School Admission Career and Occupation Discussions 9
K How to Write a User's Manual for Peachtree - Seeking help Document Control Systems, Procedures, Forms and Templates 4
K ISO 22000 requirement to write a Food Safety Manual Food Safety - ISO 22000, HACCP (21 CFR 120) 2
E How to write a Validation Risk Management Plan for Equipment ISO 14971 - Medical Device Risk Management 5
A How to write Quality Manual? Point to consider Quality Management System (QMS) Manuals 2
M How to write a Nonconformance Report ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 16
S How to write a Prerequisite Program (PRP) for food industry ? Food Safety - ISO 22000, HACCP (21 CFR 120) 14
B How to write a SOP for a Medical Device Document Control Systems, Procedures, Forms and Templates 4
E Software to Write and Control Work Instructions? Document Control Systems, Procedures, Forms and Templates 7
A How to write quality policy? Basics of Quality policy ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
L Is it required to write a formal corrective action on any nonconformance? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 29
M How to write the Essential Requirements EU Medical Device Regulations 14
R How to write a Capacity Plan Quality Manager and Management Related Issues 2
N Four CMMs and would like to write programs for intermediate checks General Measurement Device and Calibration Topics 5
A How to write a Quality Policy Statement Quality Manager and Management Related Issues 11
Jen Kirley How does a Demingite write a good self evaluation? Career and Occupation Discussions 5
E Starting to write a Quality System Manual - Import/export medical devices - Need help ISO 13485:2016 - Medical Device Quality Management Systems 1

Similar threads

Top Bottom