Version control means keeping earlier versions, knowing what changed, and knowing which version someone used. That matters for a drawing, a quote, a budget, or a company document—even if you manage the files by hand.
A simple example · Revisions by hand · Who received what? · Two small records · Keeping your project safe
You have Rev 5. Your vendor has Rev 3.
A drawing has gone back and forth a few times. You call the vendor about the mounting holes. They say the holes are too close together. You look at your drawing and say they are not. The conversation goes in circles because you both think you are discussing the same file.
But the vendor is looking at Rev 3, and you are looking at Rev 5. The hole spacing changed in Rev 4. You are each describing the drawing in front of you—and those drawings are different.
This happens. Before trying to resolve the disagreement, ask one simple question:
“We’re on Rev 5. Do you have a copy of that?”
Have them check the revision shown on the drawing. If they have Rev 3, arrange to send the intended Rev 5 and confirm they have opened it. Then discuss the holes with both of you looking at the same information.
Keep Rev 3 too. It explains the earlier conversation, and it may be the version behind the vendor’s quote. Record the new handoff so the next call starts from a known revision.
Keep three questions separate
- What are we working on? The current draft.
- What is approved for this job? The agreed version for a particular use (released revision).
- What did this person receive? The exact version sent, with the date and purpose (transmittal record).
A higher number does not automatically mean approved. A file sent for a quote is not automatically approved for manufacturing. Put the purpose and status beside the revision so people can tell.
If you manage revisions by hand
- Give the item a stable name. For example,
enclosure-drawing. Use that same identity as the design develops. - Number the versions. Save
enclosure-drawing-rev01.pdf, thenenclosure-drawing-rev02.pdf, and so on. Put the revision inside the document too, where a printed or forwarded copy still shows it. - Keep working drafts separate. A working name could be
enclosure-drawing-rev03-draft-01, thendraft-02. Number the important checkpoints; every keystroke does not need a new issued revision. - Freeze what you share or approve. Keep the exact files as they were, including a draft if you shared it for review. Do not edit that saved copy. Make a new revision or a uniquely identified new draft for further changes.
- Write down what changed. Name the previous revision, the reason for the change, who prepared it, and its review status. “Moved mounting holes to fit bracket” is more useful than “updated.”
- Keep older versions retrievable. Separate working files from issued copies and mark older ones as superseded in the records. Keep a recoverable backup. Avoid names such as
final-final-new.
These are our recommended habits. If your designer or customer already uses letters or another revision system, keep that system and record the mapping. Do not rename their issued files and lose the original identification.
Remember what people had when you talked
For each handoff, record the person or organization, the date, the exact file and revision, the purpose, and a link to the preserved package. Keep the sending email or other evidence when available. Record receipt or acknowledgment separately; sending a file does not prove someone received, reviewed, or used it.
Before a call, your Project Manager Bot can check: “The vendor was last sent Rev 3 for quoting. Our intended version for this discussion is Rev 5.” Start by asking, “We’re on Rev 5. Do you have a copy of that?” Have the other person check the revision on their actual file and record the answer.
When you issue a replacement, say what it replaces and why. Track which affected recipients still need the update or need to acknowledge it. Keep the earlier handoff record so you can reconstruct the previous conversation.
Different documents can have different revision numbers
The budget might be Rev 7 while the enclosure drawing is Rev 3 and the test plan is Rev 2. That is normal: each item changes at its own pace. You do not need to renumber every document because one changed.
For a prototype or manufacturing handoff, keep a small package list (release manifest) that names the exact revisions that belong together. For example: “Prototype package 2 uses enclosure drawing Rev 3, bracket drawing Rev 5, and test plan Rev 2.” List the matching CAD model and exported drawings explicitly; a matching filename alone does not prove they describe the same design.
The engineering role checks the technical match. Your Project Manager Bot records the reviewed package and its intended use. Keep big technical packages in technical/releases/ and the small lists and links in shared/releases/.
Two small records make this manageable
The revision log answers “What changed?” Keep one entry for each identified revision or shared draft: item, revision, previous revision, date, reason, owner, review status, and the exact saved files. Record who approved it for which use, if anyone.
The handoff log answers “Who was sent what?” Keep the recipient, date, purpose, exact revisions or package list, sending evidence, confirmed receipt if known, and any replacement or follow-up. Keep unknowns visible.
Your Project Manager Bot maintains the project-wide logs. Each assistant supplies the facts for its own work. Start with a few entries and add them as work happens; do not turn an empty log into a setup obstacle.
Download a blank revision log · Download a blank handoff log. These open in a spreadsheet.
Read the revision instructions the bots receive
Where saved history helps
Your project folder never writes over a file: every update is a new dated file, and a dated copy is kept before any big change (on GitHub, every commit too). Link a human revision such as “Rev 3” to its exact dated file. Keep the same clear revision labels on files you send out.
Saved history does not tell you who received an email, whether a shop used the right drawing, or whether a draft was approved. Those facts still belong in the logs. To inspect an old version, open a separate retrieved copy so you do not replace today’s work. To return to an earlier design, record that as a new decision and revision, preserving the intervening history.
More in Keeping your project safe.
Everything here is a starting point. Work with artificial intelligence always needs tuning, so test it and dial it in for your own work, data and model before you rely on it.