Re: Master List - Does anyone have an equivalent method that they would care to share
Well, this is a very old thread, but I have to reply anyway since Document Control is my primary job at this time.
"Document Control" is an FDA requirement, and makes good business sense as well. It is difficult to control a document if you don't know what the most current revision is. It is also difficult to control your documents if you don't really know "what" and "how many" you really have. This is especially true if you're going to migrate to an electronic system. How will you know when you're finished? Are you sure you got them all?
A Master Document Register can be as simple as an Excel spreadsheet, which is what we're currently using. The information is put in when an ECO is processed. Everyone can read it, but only Doc Control can write to it.
We have tabs for DMRs, drawings, components, forms, protocols, reports, customer supplied documents, etc. - all controlled documents, all in the same spreadsheet.
It is SO MUCH faster to look at a MDR that you know is correct and current than to have to try to find - either on the PC or physically - a document that can very well be misplaced, misfiled, at the wrong revision, or just missing. It's also very easy to search to see if there already exists a document that you need, or are thinking of creating because you don't know it's there, and everyone else forgot about it too. This is easy to do if you have enough documents.
Electronic systems make this easier as most of them will have an automatically created MDR.
So, what's in our MDR? We have the following fields:
Doc number, Doc title, revision, Customer's doc number if applicable, last author, date of last revision, customer name, and engineering project file number. Most of this doesn't change, so you put it in one time only. We also change the text to red if the document or component has been obsoleted. It's very easy to see what's been obsoleted, which has come in handy many times when engineers are researching documentation.