A drawing can have the latest revision number and still contain outdated information.
It's something worth paying attention to when 3D design moves into technical drawings and manufacturing.
Take a custom kitchen cabinet.
The CAD drawing says Rev C. The cabinet dimensions are correct. Everything looks ready.
But the appliance schedule still lists the old oven model.
Or the material sample has been approved, while the shop drawing still references the previous finish.
Nothing looks obviously wrong until someone compares the files.
The file isn't always the problem
In a typical interior project, information lives in different places:
- 3D models and CAD drawings
- Material and finish schedules
- Hardware specifications
- Product data sheets
- Approval comments
Updating one file doesn't automatically update the others.
And a newer file doesn't necessarily mean every decision inside it is current.
What actually needs tracking?
For custom joinery, I think these details matter just as much as the drawing revision:
- Which material and finish are approved?
- Has the hardware model changed?
- Are the dimensions verified?
- Are there unresolved comments?
- Is this item actually released for production?
A simple status record connecting these decisions to the correct product or drawing can prevent a lot of confusion.
More drawings won't necessarily fix it
The difficult part isn't always producing more detailed CAD drawings.
It's making sure the drawing, specification, sample and approval record all describe the same thing.
That gets harder when several people are working on different parts of a project.
I'm curious how people in software, CAD or manufacturing handle this.
How do you keep important decisions in sync when they're spread across different files and teams?
Top comments (1)
Different trade, same shape. Rev C tells you the file changed and says nothing about whether the oven did. In design systems it's the Figma file saying one thing, the code another, the spec page a third.
The only thing that held for us was picking one artefact as the source and generating the rest from it, so they can't disagree. Colour values live in a single token file, and the Figma variables, the CSS and the docs page are all built from that. Drift didn't stop because people got more careful. It stopped when typing a hex straight into Figma stopped being possible. Discipline loses to a deadline.
That only works where generation is possible, and your case has things where it isn't: a physical sample, an approval email. For those we gave up on keeping them in sync and went for making disagreement loud instead. Every approval records which version it approved, and a nightly job flags anything whose approval is older than the last edit of the thing it approved. It doesn't prevent the mismatch, but it means nobody finds out about it at the factory.