These are all excellent questions for follow up when in the process audit. They are the sorts of questions I would ask in order to determine if the dcument is current.Clause 7.5.3.2c mentioned: "the organization shall address the following activities, as applicable... control of changes (e.g. version control)"
The manual here is on its initial release and hasn't been revised, thus the auditee can assert that they deemed "not applicable". The primary intention of the clause statement is "control of changes" and not "version control" - that's why it is enclosed as an exempli gratia (for example). The manual may not have a document number/code and a version number but other means of knowing whether the manual is the current one can be verified by a competent auditor. Exempli gratia:
- first, ask the manager, or QMR or the document controller if there are other versions of the manual;
- or ask if the manual is the latest version;
- if in doubt or you don't trust any of the three auditee:
- compare the copy held by the auditor with the other copies;
- if the document controller maintains the master, compare it with the master;
- if it doesn't have a version number, look for its date of issue to compare with the other copies
I do feel the need to point out the standard's exact wording of 7.5.3.2c: "control of changes (e.g. version control)" so I do not feel free to interpret further.
The question I had (as yet unanswered) was how the organization's user would know if the document (we're talking process now, unless this manual is the sole example) is current. I was not told that the manual had a date, which would work fine. I am asking the question from the perspective of the user. What is the process? Is it effective?