While overdocumenting a process is also a problem, it is much easier to apply lean practices to an inflated documentation package than to run an organization with processes that are not defined and clear to the workforce.
I must disagree.
Presumably, the OP is not starting a business. They are merely inquiring about IATF documentation requirements, a few of which are new with this revision. The organization is busy running, so hjoul can focus on documenting only
what makes sense.
If you document anything and everything, hoping to get back to it later and shave the volume of documentation down to a more sensible level, that may never happen, and then you're stuck with a bloated documentation system that is draining your organization of resources and causing non-conformances. Heh, just like the documentation system of the company I was just hired on with. Less than 100 people and highly-automated, robot technology on the shop floor, but almost 600 controlled procedures, work instructions, process flows and forms, rife with duplicate information and often rendered useless by oversimplification.
These days, documentation systems should be light on the documentation and heavy on the training records. Gone are the days of documenting every last step because, "What if someone is hit by a bus?" I am presenting to my new company on Thursday, the first step in what will be a loooooong process of turning this ship around and getting these bad habits broken.
Hjoul, it is best to just not pick up the bad habits to begin with. There is an AIAG PowerPoint presentation that runs through the new version of the standard clause by clause. This should assist in your mission to define what is required. I can't link you to it because I am too new, but google "Automotive QMS Update IATF 16949:2016 September 2016 - AIAG
" and that should do it.
Yes, you must document those things the standard requires you to document. But how you do that is not up to a registrar, and don't you let them tell you otherwise. Do what is most effective for YOUR organization. If your organization is small, and you keep your documentation minimal, it might make sense to ask the end users what format would be most useful to them.