documentation

New IATF 16949 Documented Policies and Documented Processes

3 Documented Policies required by IATF 16949:2016
#     Clause     Requirement
1      5.1.1.1       Corporate Responsibilities policies, including (minimum)
                         a.    Anti-bribery Policy
                         b.    Employee Code of Conduct Policy
                         c.    Ethics Escalation (“whistle-blowing”) Policy
2      5.2.1        Quality policy
3    7.5.3.2.1     Record Retention policy


21 Documented Processes required by IATF 16949:2016

#    Clause        Requirement
1    4.4.1.2       Product safety
2    7.1.5.2.1    Calibration/verification records
3    7.2.1    Competence - supplemental
4    7.2.3    Internal auditor competency
5    7.3.2    Employee motivation and empowerment
6    7.5.3.2.2    Engineering specifications
7    8.3.1.1    Design and development of products and services – supplemental
8    8.3.3.3    Special characteristics
9    8.4.1.2    Supplier selection process
10    8.4.2.1    Type and extent of control - supplemental (outsourced processes)
11    8.4.2.2    Statutory & regulatory requirements
12    8.4.2.4    Supplier monitoring
13    8.5.6.1    Control of changes - supplemental
14    8.5.6.1.1    Temporary change of process controls
15    8.7.1.4    Control of reworked product
16    8.7.1.5    Control of repaired product
17    8.7.1.7    Nonconforming product disposition
18    9.2.2.1    Internal audit program
19    10.2.3    Problem solving
20    10.2.4    Error-proofing
21    10.3.1    Continual improvement - supplemental
 

 

Lean Documentation

I was asked an interesting question this week from a colleague.  "Should I start over from scratch or fix my current mess of documents?"  This seems to be a theme lately that many of us are seeing.  I'd like to think of it as a very good question and a sign of good things to come.  When businesses start asking questions like this, my hopes are that they are no longer fighting to stay alive, but now in a mode to fight.  I'm hoping this by asking this question, a key player in an organization is taking his or her initial steps towards a lean document system that allows for quick reference to key documents, rather than system that is comparable to a needle in a haystack.  Now on to the answer I gave... At the most fundamental level, you need to start with standard requirements and/or the intial intent of documents.  What is the purpose?  What do you want to get out of these organized bits of words and wisdom?

Unless there is a special business requirement from a Customer, organizations need to keep in mind that every document created comes at a cost.

I see organizations on a regular basis with hundreds or thousands of different documents claiming to be of value.  Past experience with a "say what you do, do what you say and document it" approach sometimes makes one blind to the original intent.  As an example, ISO 9001 only requires 6 documented procedures. Unless there is a special business requirement from your Customer, organizations need to keep in mind that every document created comes at a cost. The cost can add up quickly in two ways - cost of maintenance and cost of distracting from (or "watering down of") more important documents.

Start at the highest level possible and create a blank slate for storing the Top 20 procedures (or whatever number makes sense that is less than 20). The "blank slate" could be a fancy database or literally a BLANK SLATE.  From there, clear ownership needs to be assigned for each document, ideally adopted and maintained by each actual process owner within the organization.  Secondary procedures, instructions, forms, etc. can be referenced from there.  We strongly recommend that each document, at all levels, have a parent procedure that is tied back to a specific requirement or business need.  (The preference is a link back to the business need such as a business plan line item or corporate guidance manual.)

Like any 5S exercise, the orphan documents without a home or business need should be sorted out and archived so the valuable documents have the best chance to be used as the valuable business tools that they are.