Can Extent of Documentation differ due to the Competence of Personnel?

L

Luwak

#1
Clause 4.2.1 Note 1 of ISO 13485:2003 states that "the extent of the quality management documentation can differ from one organization to another due to a) the size of the organization and the type of activities,
b) the complexity of processes and their interactions, and
c) the competence of personnel."

I wonder how the competence of personnel relates to the extent of the documentation.. does less competent personnel need more detailed documentation? Or is it the other way around and can more competent personnel handle more extensive documentation?

Does anyone have an idea what is the reasoning behind this point and why it is in the norm? I asked our auditor last week and he did not have a direct answer.

Thanks!
 
Elsmar Forum Sponsor

Wes Bucey

Quite Involved in Discussions
#2
Sometimes organizations use MORE simplified documents- pictures, cartoons, etc. to avoid confusing workers who may have vocabulary or literacy problems in the language used by bosses in the organization.

I've seen industrial settings for mentally challenged folks that get along well with a combination of simple documents and instructions combined with individualized training and frequent evaluation of the adequacy of documents and training.
 
P

phloQS

#3
This point is in the standard, because of the diversity of companies in the medical devices industry. There are companies like "one man shows". and companies like multicorporate enterprises. It is obvious that things in bigger companies must be written down to work the same way around the world (one goal of QM). But a single person does not need to have special procedures for everything.

Regards,

phloQS
 
L

Luwak

#4
Size and complexity are pretty straightforward, but competency seems to me to be varying from individual to individual and changing over time. It doesn't make sene to me to base the extent of the documentation on such a changing factor. I have to admit that this doesn't have much impact in practice but I was just wondering why it is mentioned in the norm. As Wes' comment shows, the interpretation can go in two directions and therefore it can always be used to defend either an overly simple or an overly complicated documentation..
 
S

sathishthantri

#5
This is a good point to ponder !
The Information marked as “NOTE” is for guidance in understanding or clarifying and the same notes are exisiting in ISO 9001 as well.
It is true this can lead to any direction but it is same for points 1 and 2, since in a dynamic situation we can expect changes in these two as well.
The idea of these notes is to bring in diversity (if needed) and making documentation easily understandable to all employees within the organisation (and to other external stakeholders). without compromising in compliance to the requirements of the standard. It may be noted that "notes" are not NORM (requirement / standard).
 
L

Luwak

#6
What my question boils down to:
Larger organization -> logically requires more extensive documentation
More complex product/process -> logically requires more extensive documentation
More competent personnel -> ??

A case can be made that more competent personnel can 'handle' more extensive documentation, but also that they don't need a lot of documentation because they are already competent. But as mentioned earlier, competency is also partly a function of the documentation..

Maybe this note should be read as a warning not to blindly copy an existing quality system from another organization, which would be a silly idea anyway.

Thanks for the feedback everyone!
 

somashekar

Staff member
Super Moderator
#7
What my question boils down to:
Larger organization -> logically requires more extensive documentation
More complex product/process -> logically requires more extensive documentation
More competent personnel -> ??
No, need not be this way
It depends upon the maturity levels of the organization and no two will be same and no two will be as smart.
Take a case of a big organization with a complex process. You are inclined to find the extent of documentation to be extensive.
No, A photo copier machine is assembled by one person and he knows all the parts and sequence to the correct details. Very less documentation.
Such a photo copier machine can also be assembled in a conveyor line with several people building the product as the conveyor moves and each stage has needed work instructions (documentation). The extent of documentation is vast here.
So in response to your subject :
Can Extent of Documentation differ due to the Competence of Personnel?
YES
 
Q

Quality_Steve

#8
You have to remember that competency can be gained through appropriate education, training, skills, and experience.

If the company has been around awhile and has a large number of veterans then the overall experience level of the company will be high and will require less documentation as these individuals will know what needs to be done and pass that along to the younger generation. As for a start up or a relocated company the overall experience will be very low which will require more documentation to fall back on.

Our company relocated 9 years ago. After the relocation they feverish pumped out flowcharts and work instructions. Now several years later, our work force has matured and the over documentation is less necessary and some what of a burden.

When hiring new personnel, if the time is taken and the right money is offered you may get applicants that already have high skill sets and educated in the field in which they are hired for and they will require less documentation of how to perform their job.

That's my take on documenting to account for competency.
:2cents:

Steve
 

Marcelo

Inactive Registered Visitor
#9
One of the main problem in this discussion, in my opinion, is that people forgot one simple thing - what is the purpose of the documentation and how it fits systemically in my QMS.

For example, the QMS generally expects that people perform theirs tasks correctly.

This can be solved in some ways

1 - detailed procedures to be followed - because of this, requirements for personnel can be somewhat "low" because they will always need to read and follow exactly what is written. In this case, the purpose of the documentation is to be a mandatory checklist to be followed.

2 - a generic procedure, let´s say, a general flowchart - because there´s already a "high" requirement for personnel. If you require that you personal is a PHD in the subject he´s dealing with, why would you need very detailed procedures? The guy already know because you required him to know. In this case, the objective of the documentation could be to be a reminder of the general flow of the process.

If the effectiveness of the proces is obtained by 1, 2 or any other solution related to competence and documentation, things would be ok.

You can also read more on this general approach on Introduction and support package: Guidance on the documentation requirements of ISO 9001:2008
 
S

Sequence_Barry

#10
In many of the organizations that we work with, we see different levels of instructions for "expert" and "novice" operators. These differences typically revolve around best practices, e.g., soldering, crimping, etc. Managed in an appropriate way,e.g., via electronic deployment, these two different sets of instructions can be presented in an appropriate fashion to the two different groups. Novice employees see all of the details while expert employees only see the high-level steps. Presentation can depend on assigned skill level.The thought process here is that the standard work will include all of the critical steps but doesn't include best practices for "expert" employees. The Instruction might read "solder the 9-conductor wire to the D-connector based on the wiring diagram" for the expert while the novice might get step x step and visuals showing how a wire is to be stripped, inserted, fluxed and soldered.
 
Thread starter Similar threads Forum Replies Date
C 8.5.1.1 Control of Equipment, Tools, and Software Programs - Questions about the extent of control of NC programs AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 5
J Extent of 2017/745: providing 3rd party mass produced devices to NHS patients EU Medical Device Regulations 0
M SI #7 8.4.2.1 Type and extent of control_supplemental IATF 16949 - Automotive Quality Systems Standard 3
J Extent of Validation - New machine installed in manufacturing ISO 13485:2016 - Medical Device Quality Management Systems 8
A IATF Sanctioned Interpretation No. 7 - Type and Extent of Control (supplemental) IATF 16949 - Automotive Quality Systems Standard 4
DuncanGibbons To what extent are NASA standards applicable to commercial aviation? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 14
I AS9100 8.4.2 Type and Extent of Control - External provider test reports Manufacturing and Related Processes 24
B Documented process for type and extent of control IATF 16949 - Automotive Quality Systems Standard 6
Q ISO 9001:2015 - Extent of Policy and Scope with Context and Interested Parties ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
S Complying with IATF 16949 Cl. 8.4.2.1 - Type and extent of control IATF 16949 - Automotive Quality Systems Standard 1
E IATF 16949 Cl. 8.4.2.5 - Supplier Development Type and Extent IATF 16949 - Automotive Quality Systems Standard 2
N Extent of Product Traceability Required by ISO 13485 (Low Level Class I Devices) ISO 13485:2016 - Medical Device Quality Management Systems 3
V What are the criteria for determining extent of requalification (hardware upgrade) ISO 13485:2016 - Medical Device Quality Management Systems 2
I Definition Insubordination in Organizations - Definition, extent; vis-a-vis employee's rights. Definitions, Acronyms, Abbreviations and Interpretations Listed Alphabetically 14
E Extent of modification to be considered as Modified Adoption Other ISO and International Standards and European Regulations 1
M TS 16949 Cause 7.4.1: Type of Control vs. Extent of Control (Definitions) IATF 16949 - Automotive Quality Systems Standard 5
R 820.50 (A) (2)Define the Type and Extent of Control to be exercised over Vendor Misc. Quality Assurance and Business Systems Related Topics 5
P Risk Management - To what extent is Risk Management required by AS9100? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 17
A Extent of Gage R&R necessary on two Digital Height Gages Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 1
J Extent of information required in COC (aka C of C and Certificate of Conformance) AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 9
O Information on the extent of Statistics in the Six Sigma Green Belt Exam Professional Certifications and Degrees 9
R Extent of Recognition of ISO 10993-1 US Food and Drug Administration (FDA) 5
R FDA recognition standard - Extent of Recognition 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
T Raw Material Verification - AS9100 Rev. B - 7.4.3 - To what extent must a company go? AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 6
T Traceability SOP Audit Finding - SOP does not describe the extent of the traceability ISO 13485:2016 - Medical Device Quality Management Systems 15
S Extent of Site manager (SM) Commitment - Upper Management issues Quality Manager and Management Related Issues 8
hogheavenfarm Extent of certification - Companies sharing manufacturing space in a building ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
Sidney Vianna Outsourced Processes - Type and Extent of Control to be Applied - ISO 9001:2008 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 40
F Need help about being more socialized - Hard to fit into my groups to some extent Career and Occupation Discussions 4
M Document Control Database - To what extent do document control requirements apply? Document Control Systems, Procedures, Forms and Templates 12
C To what extent should ppap be repeated according to the European Union ELV? APQP and PPAP 3
G Document Control - Extent of Responsibility Document Control Systems, Procedures, Forms and Templates 7
F Controlled Forms - To what extent do forms need to be controlled? Document Control Systems, Procedures, Forms and Templates 41
J To what extent does Emergency Prepardness need to be extended Miscellaneous Environmental Standards and EMS Related Discussions 2
S Need ISO 15189:2012 Documentation toolkit. Document Control Systems, Procedures, Forms and Templates 0
H MD Technical Documentation and SALES possibility EU Medical Device Regulations 0
A DMDIV-Variants : definition and technical documentation CE Marking (Conformité Européene) / CB Scheme 4
NDesouza COTS Items CoC for FAI Documentation AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 12
P MDR/IVDR Annex III - Technical documentation on PMS EU Medical Device Regulations 1
I IATF Lab Scope Testing Qualification and Competency Documentation IATF 16949 - Automotive Quality Systems Standard 3
C Documentation hold during submissions? ISO 13485:2016 - Medical Device Quality Management Systems 0
K SOUP (Software of Unknown Provenance) Anomaly Documentation IEC 62304 - Medical Device Software Life Cycle Processes 2
C Gobys for operations documentation plan Oil and Gas Industry Standards and Regulations 4
C Refreshing an old and boring topic - Job descriptions and Roles vs Process Documentation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 38
C Documentation for items used for Design Verification 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
P Does anyone have a API Q1 Documentation Package? Quality Management System (QMS) Manuals 1
J Documentation structure - Do I need Work Instructions? Document Control Systems, Procedures, Forms and Templates 23
J Where to Place Process Maps in our Documentation? Process Maps, Process Mapping and Turtle Diagrams 4
C Manufacturing overages & nonconforming material documentation ISO 13485:2016 - Medical Device Quality Management Systems 3
Robert Stanley Required Documentation Templates ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4

Similar threads

Top Bottom