To me, it would make sense to grandfather old documentation into the new system, as it is. In my previous experience when Quality Systems were changed, it was required that all previous, in-process projects be updated to fit the new system. In hindsight, this seemed like the direction to go since it would save time later, but ultimately it did not. A great deal of time and money was spent on updating the information from in-process projects but unfortunately, a majority of these projects did not make it through the pipeline to production or launch. Updating these files only caused a waste of time that could have been better spent on other activities. Unless there is a major reason to change to the new Quality System (for example, changing from a paper process to an electronic one), it may not be efficient to spend time on updating paperwork for products that may not make it to market.