We are currently putting together a team to "DEFINE" what criteria to use to determine what documents should be controlled and what doesn't need to be controlled. So if it meets this....controlled, if it doesn't meet this...doesn't need to be controlled. My personal opinion is that if an organization has a process that is critical to the end result customer (building something, contracts etc) it should be documented. Thoughts?
I feel for you Hillary. Best of luck in trying to come up with such criteria, but as you've perhaps seen from the range of answers, it's a ticklish question.
The broad criteria for things that DO require control have already been given along the lines of a document being one that has a bearing on the quality of your product or service, and where people need to have the correct information. But that, of course, is very broad! And you'll also have seen that many people will speak (not unsurprisingly) from their own context, be that aerospace, manufacturing, or whatever.
It really
will vary, depending upon the nature of your organisaton and the types of documents it deals with. It would be helpful if you provided some background information that gives me some idea of these. Then I can can give you some examples of the types of documents that typically need control in such an organisation.
But I still doubt you will be able to get the criteria beyond anything necessarily broad.