- Fusion 360 has a cloud version history, but no real revision management with status and part numbers.
- File names like
final_v3fail on uniqueness, status and traceability. - A clean solution needs: unambiguous states, a status workflow, part numbers, metadata and clean export.
- A local PDM add-in like CadRev brings this right into Fusion — no cloud required.
Fusion 360 is great at modeling — but it leaves the management of design states to you. The result is familiar to almost every engineer: file names like bracket_v2_final_new.f3d, part numbers in a spreadsheet and, in the worst case, the wrong revision ending up at the manufacturer. This guide shows why that happens and how to set up clean revision management in Fusion 360.
Does Fusion 360 have revision management?
Partly. Fusion 360 stores a version history per document in the cloud — you can return to earlier saved states. What is missing is real revision management in the engineering sense: unique part numbers, a status workflow, traceable approvals with a change reason, and an overview across all parts — not just within one document.
Why file names fail
File names carry the full weight of versioning — and collapse under it. The direct comparison:
| Criterion | File names | Structured revision management |
|---|---|---|
| Unambiguous state | unclear (final vs v3) | unique revision |
| Release status | not representable | WIP / released |
| Change reason | not documented | stored per revision |
| Part numbers | separate spreadsheet | assigned automatically |
| Write protection | none | released = frozen |
The status lifecycle of a part
At the core of any revision management is a clear status workflow. Every part moves through three states:
What good revision management needs
How to do it in Fusion 360
These criteria map directly into Fusion — with a local PDM add-in like CadRev:
- Register a part: on save, the next part number and a first revision are assigned automatically.
- Set status: "in progress" until done, then "released" — the state is frozen.
- Revise: each change creates a new revision with a reason; time travel back any time.
- Export: files carry part number and revision, e.g.
0089_Bracket_RevB.step.
Local, not cloud: CadRev stores revisions, numbers and metadata in a local database — without sending design data to third parties. Ideal for NDA projects.
Conclusion
Fusion 360 provides the version history, but not the structured revision management daily work needs. With unambiguous states, a status workflow, automatic part numbers and clean export you bring order to it — right inside Fusion and without expensive enterprise PDM.
Revision history, automatic part numbers and a status workflow right inside Fusion 360 — up to 10 active parts, free forever.
Download CadRev