Version Control & Branching
Onshape's Git-like version control system with branches, merging, and complete design history for CAD collaboration.
Definition & Context
Onshape provides Git-like version control natively: Versions capture immutable snapshots, Branches allow parallel work, and Merge combines branches, all backed by a complete, immutable edit history you can restore or compare — built into the cloud document, not a separate PDM add-on.
Because history is automatic and immutable, you can always return to or branch from any prior state, and Releases/workflows manage revision states for controlled data.
In contemporary engineering practice, Version Control & Branching represents a critical interdisciplinary methodology. By replacing manual heuristics with rigorous digital simulation and parametric constraints, engineering teams establish an unbroken digital thread from initial concept through detailed physical realization.
Achieving high-quality results in Version Control & Branching requires a thorough understanding of geometric tolerances, material behavior, and coordinate governance. Digital models serve not merely as graphical representations, but as authoritative engineering databases driving downstream analysis, procurement, and robotic fabrication.
Why It Matters
Native branching and merging let engineers explore alternatives and manage revisions without copy-and-rename chaos or a separate PDM system — a distinctive Onshape strength.
An immutable, always-on history means changes are traceable and recoverable by default.
Best Practices
- Create Versions at meaningful milestones for clear restore/compare points
- Use Branches for experiments or variants, then Merge back deliberately
- Use Releases/workflows to control revision states for production data
- Compare versions to review what changed between milestones
Common Pitfalls
- Never creating named Versions, leaving only granular history to sift
- Long-lived divergent branches that become painful to merge
- Confusing lightweight Versions with a formal release/revision process
Core Commands & Practical System Operations
Executing Version Control & Branching effectively relies on specialized CAD/BIM command workflows and system variable configurations: BIM & CAD tools: WALL, FLOOR, ROOF, FAMILY, XREF, IFCEXPORT. Setup: Coordinate shared project base points, configure Level/Grid datum.
Standard Engineering Workflow for Version Control & Branching
1. Spatial Programming & Shared Georeferencing
Establish project base points, survey coordinates, building storeys, and column grid systems coordinated across architectural, structural, and MEP consultants.
2. LOD 200 - 300 Parametric Component Assembly
Model multi-layer architectural assemblies (curtain walls, structural framing, floor slabs, MEP risers) using intelligent parametric family components.
3. Interdisciplinary Clash Detection & Coordination
Federate discipline models in Navisworks or Solibri. Run automated hard/soft clash tests and track issues using BCF (BIM Collaboration Format) workflows.
4. 2D Construction Documentation & Quantity Schedules
Extract live plans, building sections, elevations, and automated component schedules (doors, windows, concrete volume) linked directly to the central model.
Common Failure Scenarios & Troubleshooting
| Failure / Geometric Issue | Root Cause & Mitigation Strategy |
|---|---|
| Architectural and Structural models do not align when linked | Shared coordinates were not acquired. Ensure both teams use 'Acquire Coordinates' from a designated master site model. |
| Wall joints and multi-layer materials do not clean up cleanly | Layer core priorities are misconfigured. Ensure structural cores have Priority 1, substrate Priority 2, insulation Priority 3, and finishes Priority 4/5. |
| IFC export drops custom attributes and scheduling properties | Map property sets using custom IFC export translation tables before exporting to external coordination software. |
Industry Standards & Compliance Codes
- ISO 19650-1/-2 (Organization of information about construction works - BIM)
- buildingSMART openBIM & IFC 4x3
- AIA Document E202 (Building Information Modeling Protocol)
- National CAD Standard (NCS)
References & Further Reading
Related Concepts
Explore more Onshape topics in our Onshape knowledge base, or browse the full terminology index.
For structured learning, see our Onshape learning path.