Process Documentation Formatting - Requirements

S

shieldingintl

We are in the process of 'chopping' some content from our canned QMS. Under Section 4.2.1 of ISO 9001:2008 it states under NOTE 3 that the documentation can be in any form or type of medium. Does this mean that we can format our documents as we see fit - for example by no longer having numbered sections and subsections in the document - and replacing with bolded captions and bullet points throughout?? If not, is there a sequential formatting requirement in ISO?
 

Stijloor

Leader
Super Moderator
Re: Process Documentation Formatting

No. ISO 9001 does not specify a particular medium or document format/layout. Present information in a manner that is beneficial and user-friendly to the user community at your organization.
 

howste

Thaumaturge
Trusted Information Resource
Re: Process Documentation Formatting

Does this mean that we can format our documents as we see fit - for example by no longer having numbered sections and subsections in the document - and replacing with bolded captions and bullet points throughout?? If not, is there a sequential formatting requirement in ISO?
Yes, you can do it however you want. No, there has never been a requirement for specific format or numbering.
 

normzone

Trusted Information Resource
Re: Process Documentation Formatting

Things you may or may not choose to do...

Have a revision history at the end of the document. Rev. B, added additional requirement for inspection record to section 3.5, etc. This lends some help to the requirements of 4.2.3.

I have gone away from most of the formal formatting requirements I inherited when I moved in to my new home, but since my predecessor was a guy who wouldn't use 3 pages when 10 would do, that was easy.

Microsoft Word pushes you towards numbers and bullets, but depending on your skillset and training, the previous formats inherent in the document, and the version you are using your mileage may vary. I find some numbering and bulleting useful for referencing certain requirements in audit reports, etc.

But simpler is usually better. If it gets too big, split something out into a seperate document and cross reference the two.

:bonk:
 
Top Bottom