Grandfathering a project due to changes in a quality system usually consider the following components: project scope (ex. changes to processes, documentation, drawings, validations) + area of grandfathering (document control, quality, engineering) + Date.

The date aspect is key because when moving over changes to a new quality system you are saying anything before this date may be scrutinized as it doesn’t follow our new updated system changes. In reality there is no right time to have the cut off date from moving from the previous system to the new system as most companies have many high priority high impact projects going on simultaneously. I would believe, the best way to handle this challenge, is to outline all the projects that are being done and segregate them into which projects have the highest impact and priority. From there look at estimated date of completion of the projects. The highest impact and priority project with the furthest completion date, should be the date in which you move to the new system. This idea works for a company in which the time constraint to switch over is willing to be flexible to wait that length of time.