Old procedure review and training requirements

[jmaxwell]

Our company is currently reviewing procedures that have not been updated in the last 5 - 10 years. Some of them do not require any changes but we are updating the Rev level (making notes that it was only reviewed with no changes) and updating the approval dates.
For ISO 9001 & IATF 16949 compliance are we required to train everyone since it is a new rev level & new approval dates?

 

[Jim Wynne]

Why do you want to change the revision level when nothing has been revised? Document the review and results and let it go.

 

[Miner]

We have an internal software driven process to review X% of our procedures each year based on how long it has been since the last review. The reviews are documented within the software. We do not change the revision levels.

 

[jay747]

Why do you want to change the revision level when nothing has been revised? Document the review and results and let it go.

Could you suggest how we can capture the document review has been conducted without changing the revision number of the document. We only use hard copies of these documents.

 

[John Broomfield]

Could you suggest how we can capture the document review has been conducted without changing the revision number of the document. We only use hard copies of these documents.

No need to change the document rev unless you have changed the doc.

The process owner could engage the process team in reviewing the documented procedure for accuracy and clarity.

Record this review wherever you can retrieve it, for example, on a copy of the procedure after archiving records of earlier reviews.

 

[Jim Wynne]

Could you suggest how we can capture the document review has been conducted without changing the revision number of the document. We only use hard copies of these documents.

How do you document a revision change?

 

[jay747]

How do you document a revision change?

It is initiated using the 'Document change control' form by the user department or quality department. The change required is to be approved by the user department head and the quality department head. The draft copy is created and the revision change would be captured in the header of the doc which has the 'Revision Number'. Once the draft is approved the master copy is created and document is be distributed. The "change" would be mentioned (in a single line) in the 'Change History' at the end of the document along with respective revision number. Once everything is completed the document change control is closed with the verification for each process by a quality member and a final approval by the Quality head.

 

[FRA 2 FDA]

I can't speak to 16949 requirements, but we simply have "Last Reviewed" and "Next Review" columns in our Master Document List. I update these every time a document is revised. If a document hasn't been revised in two years, the review date will come up and the document will get reviewed. The date changes to reflect that it has been reviewed, or when the new rev comes out if the review results in revision.

 

[QChas]

"We simply have "Last Reviewed" and "Next Review" columns in our Master Document List. I update these every time a document is revised. If a document hasn't been revised in two years, the review date will come up and the document will get reviewed. The date changes to reflect that it has been reviewed, or when the new rev comes out if the review results in revision."

We are ISO, not IATF nd do the same thing but have the revision review set at 3 years instead of 2 years.

 

[Funboi]

Our company is currently reviewing procedures that have not been updated in the last 5 - 10 years

Really? A business hasn’t had any issues of ineffectiveness, or changes or even improvements to its documented procedures? That‘s impossible - or at least highly improbable. What were the internal audits looking at during this time?