The change itself is nothing much. The customer wants a heavier motor, so the motor mount shifts over and gets two extra holes: ten minutes of modeling, fifteen at most. The week after, you find out what was really attached to that mount. The assembly drawing still shows the old version, the new fastener set is missing from the BOM, and the laser cutter is sitting on a DXF with the old hole pattern. Three phone calls, two rush emails and one awkward conversation later, the "minor change" has eaten a week.
That is how it almost always goes: it is not the modification that costs time, it is the chain reaction behind it. Treat design changes in Inventor as a fixed route instead of a loose collection of actions and that reaction stays short. A toolbox like Thundercad takes the searching and repetition out of the individual steps, but the routine itself costs nothing and delivers the most.
In this article: why one change lands in four places at once, the five steps to run through in a fixed order, and the checklist that proves nothing was left behind.
Why one change lands in four places
Every model drags a shell of derivatives behind it: drawings that show the geometry, a BOM that counts the contents, and exports such as PDF, DWG, DXF and STEP that were created as snapshots somewhere along the way. Model and drawing still keep an eye on each other, because the drawing references the model and flags itself when something is out of date. But the BOM in Excel and the PDF in your customer's mailbox know nothing. Every derivative that has left the building keeps telling the old truth until someone actively replaces it.
"Just adjusting the model" is therefore never the end of a change, at best the beginning. The question that matters: which derivatives exist of this model, and which of them are outdated after the change? Answer that question before you start modeling and you will not have to reconstruct afterwards what is floating around where.
Step 1: map the scope before you touch anything
Do not start inside the part, start around it. A motor mount can easily live in three assemblies: the machine in this project, a variant running in parallel, and an old project it was once copied from. Answer four questions and write the answers down, even if it is on a sticky note:
- Which assemblies use this part, including ones outside this project?
- Which drawings show it: the part drawing, assembly drawings, a customer drawing?
- Which exports have already gone out the door, to whom, and when?
- Is purchasing or production currently running on the present state?
The third question is the one people skip, and it is exactly the one that decides whether the change stays an internal matter or hits a supplier who is already cutting material.
Step 2: make the change and watch the edges
Only then go into the model. Push the modification through and look deliberately at its edges: do the neighboring parts still fit, do features that build on the changed geometry survive, and do any errors pop up in assemblies you did not have in view? This is where scope creep starts: the longer stroke of a cylinder calls for longer hoses, and before you know it you are changing five parts instead of one. That is fine, as long as you decide it consciously and update the list from step 1 to match. Unconscious expansion is exactly how changes get out of hand.
Step 3: update the BOM before anyone orders from it
Downstream, the BOM hurts first: purchasing orders by quantities, work preparation plans by descriptions. So refresh the list right after the model change with Update BOM, which brings the BOM up to date so that late changes actually land in it. Then walk through the affected positions deliberately: are the quantities right, did descriptions driven by parameters grow along, and did the new fasteners get a position of their own?
An error that stays behind here propagates into every document that follows. Why that ripples so hard, and how to keep the source clean, is covered in clean, reliable data into production.
Refreshing the BOM, collecting the drawings, exporting the new set: most of the work in a change is repetition. Thundercad turns it into a few clicks, so your attention goes to checking instead of collecting.
Try 30 days freeStep 4: collect every drawing that belongs to the model
Now the drawings. The tricky part: the reference runs one way only. Every drawing knows its model, but the model keeps no list of its drawings. For a part drawing sitting next to the part that is no problem; for an assembly drawing two levels up, or a customer drawing in another folder, it is. Get Drawings solves exactly that: it collects the drawings that belong to the assembly and the parts underneath it and opens them in one go, so you know the set is complete before you start checking.
What to check per drawing, from out-of-date views to dangling dimensions, is a story of its own; we work that out in every drawing updated after a model change. For automatically updating complete drawing sets, Drawing Updater is on the Thundercad roadmap as well.
Step 5: replace outdated exports and announce the change
Everything exported before the change is now suspect. Take the list from step 1 and work it off: export the affected documents again, give them a higher revision marker, and remove old files from folders where the shop floor or a supplier might find them. Send the new set actively and name the change explicitly ("motor mount hole pattern changed, revision C replaces B"), so the recipient knows that carrying on with the old state is not an option.
This is also the moment for the reverse check: is there an export you are not replacing? Then you must be able to explain why it falls outside the change. If you are in doubt, it belongs on the list.
The checklist: anything left behind?
After the five steps, close out with six questions. Two minutes of work:
- Have all assemblies containing the part been opened and are they error-free?
- Has the BOM been refreshed with Update BOM and have the affected positions been checked?
- Has the drawing set been collected completely and brought up to date?
- Do all affected documents carry the same new revision marker?
- Have all outdated exports been replaced, including the copies sitting with external parties?
- Does everyone who worked with the old state know there is a new one?
Six times yes means: chain reaction stopped. Every "not sure" is a job for the next ten minutes, not for next week.
Frequently asked questions
Does a small change really need the full five steps?
Yes, but the lead time shrinks along with it. For an extra hole in a plate, step 1 is a thirty-second glance and step 5 a single fresh export. It is precisely the small changes that cause chain reactions, because nobody feels they deserve a procedure.
How do I know which exports are outdated?
You cannot tell from the file itself, and that is exactly the problem. Compare the export date with the modification date of the model: anything older than the change that shows the affected part is suspect. A fixed export folder per project turns that comparison into a matter of sorting.
Which steps can a toolbox take off my hands?
The gathering work: refreshing the BOM with Update BOM, bringing the related drawings together with Get Drawings, and exporting the new set in one go. Guarding the order and walking the checklist remains human work. To see what that saves in practice, try Thundercad free for 30 days.