You misunderstand me. Yes it should be in that procedure but what I was saying was presumably you have a list of current documents with the issue number and date? Could you add a review date and reviewed by column to this to prove a document has been reviewed? Electronic signatures would be ideal but if you can't do that you could keep one copy of the document in a file signed and dated by the reviewer when it's reviewed. That way you don't have to change all your documents (and hence revision numbers) every time they're reviewed if there are no changes.
While you were talking about the "list" of current documents with the revision number and effective date, perhaps I was talking about the "actual" documents. I am sorry to cause confusion on this. Maybe my question was not clear and I need to elaborate a little bit more.
4.2.2 Control of documents says
a) to approve documents for adequacy prior to issue,
b) to review and update documents as necessary, and re-approve documents,
From the above statement, perhaps the process of first/initial approval doesn’t call for a review but for adequacy. Let say we released the document:
(Header)
Rev. 0
Effective date 01-30-2011
(Footer)
Prepared by: Approved by:
xxxxxxxx xxxxxxx
Said document was implemented by the process owner from the document took its effect, 01-30-2011, and being implemented until a need for review comes up. Let me show the “proposed footer” followed by my question:
(proposed footer)
Prepared by: Reviewed by: Approved by:
Xxxxx xxxxxxx xxxxxx
Now, my questions are:
1) Do I need to add "reviewed by" to show that the document is still valid and fit for the purpose?
2) Do I need to revise all existing documents and add "reviewed by" in the
actual documents?