@Jannie Smal Hi Jannie, see the picture at the bottom of my reply, this is how I keep track of the modifications that I do. This is very simple because I am a one person team! I put my assembly in a dedicated folder and use "Save as" and give it another name which is simply changing the "v number" after the name of the assembly, like v2... v3... v4 etc... Then I add a short description of the modification after the "V number". As I explained at the beginning, sometimes I modify a component WITHIN an assembly using "Open part" or "Edit part". When I do that I usually do not change the component name or the assembly name. I just save the component and rebuiild the assembly and keep all the same names, this is when I need to correct minor issues. However, when I add a component to the assembly or make a major change to a component, then I rebuilt the assembly and save to a new name describing the change some... As you can see by the names, I got a bit better at it. Now I found that changing the name of the assembly, or the name of the modified component may cause some issues, like the one that I describe at the beginning of this thread. My undestanding is that when you draw on a part WITHIN an asssembly, that drawing keeps that relation as a reference much like a fillet on an edge or a mirror... I did not answer your question at first because I though you wanted to use a feature of SW that allows to track the history of changes on a assembly or part, like I believe Jesse is discussing. Imagine a large number of drafters working on their own components of an assembly, there has to be a way to track everything for sure. I kinda like the way Jesse is showing because it makes the assembly totally independent. However, if I wanted to go back, let's say to my version 7 of my assembly, and "Branch off" of that one to make a different path, all I would have to do is reopen that one and proceed. But again, one may run into lost references...