Re: Names versus Job Titles?
I have been given the task of setting up a schedule for SOP reviews by listing all the procedures for the different manuals and setting an "Owner" and due date. Is there anything within ISO that sets a requirement when listing the "Owner" by just Job Title or their Names? I know this sounds kinda... well, dumb I guess, but I was presented with this question by one of my bosses so I figured I would ask. The schedule is just for this year so it is not something that is necessarily set in stone and would change year to year (or when a new procedure is added/removed).
Thank you in advanced!
Nope, not a dumb question at all!

I think many of us have struggled with this dilemma at least once and, as much as this does not answer your question, it really depends on what works for your organization.
A smaller company may prefer to use names. A larger company may prefer to use titles.
I am one of those people who is quite happy to sit on the fence, right in between both opinions. Why? Because people come-and-go, and having the title is good way for a new person replacing the former person to know which documents fall under his/her umbrella. A title is also an excellent way to show that the person reviewing/approving a document is the most suitable person. For example, in most organizations, the Quality Manager would not be the most suitable candidate to approve the content/format of the HR Orientation Checklist.
Having names, however, is good to include that bit of a "personal touch" and accountability. To show that the HR Manager must approve something is great, but to show "Jane Doe, HR Manager" is responsible...wow, now that's something.
And should Jane leave, to be replaced by John Smith, don't worry about having a mass blitz to change your documentation. Simply include, in your document control protocols, the process that the correct name/title will be added at the time of the next review.
That's my take on your situation.
