I think not really. Most of the time spent in the documents review and approval process is spent where a document awaits someone (the critical path or the weakest link) to stop procrastinating and just do it (they will tell you that they are very busy, have higher priorities blah blah blah, but usually it's just good-old procrastinating or bad time management). Second up is time spent in the actual review, when a document is long / complex / controversial / badly drafted and needs sorting out. Both these elements won't be significantly affected by the QMS being electronic rather than paper-based. The only element that will be significantly affected is the delivery/transfer of paper copies for wet-signing, and even that is not big unless the operation is very big or spread across multiple sites.
Hmmm.... I've seen implementations where users were very unhappy, either because the system was not easy to use or otherwise. It all depends on how well it's done (and in some cases it's just not worth the investment - not necessarily direct $$ spending - regardless of how well it's done).
In general I think that considering only the benefits of doing/having something, without giving account to the costs & downsides, is bad decision-making practice.
I'm not agree, because in the traditional method You hace Ro den the document
I think not really. Most of the time spent in the documents review and approval process is spent where a document awaits someone (the critical path or the weakest link) to stop procrastinating and just do it (they will tell you that they are very busy, have higher priorities blah blah blah, but usually it's just good-old procrastinating or bad time management). Second up is time spent in the actual review, when a document is long / complex / controversial / badly drafted and needs sorting out. Both these elements won't be significantly affected by the QMS being electronic rather than paper-based. The only element that will be significantly affected is the delivery/transfer of paper copies for wet-signing, and even that is not big unless the operation is very big or spread across multiple sites.
Hmmm.... I've seen implementations where users were very unhappy, either because the system was not easy to use or otherwise. It all depends on how well it's done (and in some cases it's just not worth the investment - not necessarily direct $$ spending - regardless of how well it's done).
In general I think that considering only the benefits of doing/having something, without giving account to the costs & downsides, is bad decision-making practice.
Sorry, but I'm not agree with you, because in the traditional method, in order to change a revision of documents,the document Is sent by email, for revision , afterwards, sent for approval, then to communicate to all people involved, converted to PDF, saved in special folder, also you have to make sure evidences are kept, while in a software with just fee clicks, everything is done and quickly.
On the other hand, well said "when Is done very well "
I have seen And tested very well designed systems that really makes the management more efficient.
Regards.