Why Drawing Revision Numbers Matter in Customer Reviews
A technical drawing rarely stays the same throughout a project.
The first version may be issued for discussion. The next includes customer feedback. Later versions reflect corrections, new information, and agreed changes.
This is why revision numbers matter. They help everyone understand which drawing is being reviewed and whether previous comments have been addressed.
The Problem With Reviewing Old Drawings
Imagine a customer receives Revision B of a drawing.
The customer reviews it and sends five comments to the engineering company.
The engineers make the requested changes and issue Revision C.
A week later, someone from another department opens Revision B and submits another set of comments.
Some of those comments concern problems already corrected in Revision C.
Now the engineering company must spend time checking which comments are still relevant.
This work could have been avoided if everyone had used the same revision.
Make Revisions Easy to Identify
A drawing package should make it easy to find:
The drawing number and title.
The current revision.
The issue date and purpose.
What changed since the previous issue.
A short revision description is especially useful.
Instead of writing only "Updated drawing," explain which areas or details were revised.
This helps customers focus their review on the relevant changes.
Comments Need Their Own History
A new drawing revision shouldn't automatically mean a new review process.
Some comments may be closed, while others remain unanswered.
Keeping a comment register makes it easier to follow each issue from the first review to its final resolution.
For example, Xenmark allows teams to place comments directly on PDF drawings, carry feedback between revisions, and export annotated PDFs with Excel comment registers.
The aim is to preserve the review history while making new changes easier to follow.
Better Revision Control, Better Collaboration
Revision management doesn't need to be complicated.
Use consistent drawing numbers, identify each revision clearly, and maintain a record of open comments.
Most importantly, make sure everyone knows which version is being reviewed.
A clear revision history helps customers and engineers spend less time revisiting old questions and more time moving the project forward.