Docs / Collaborate
Product data and revisions
Organize project files, capture revisions, and hand off design context without filename archaeology.
Work inside a project
A project is the boundary for designs, assemblies, manufacturing artifacts, and revision history. Keep related native .step+ files under the project root so Chudware can connect them without relying on absolute paths.
Revisions are not duplicate files
Save meaningful checkpoints when a design decision is ready to preserve. Use the revision note to explain why the design changed and what evidence you checked. Do not create names such as bracket_final_v7; keep one design identity and let history carry the sequence.
Add supporting artifacts
Specifications, photos, reports, and supplier files can be tracked alongside designs. Native Chudware design files register through their save and checkpoint flow; supporting non-design files are added as project items.
Hand off context
Before a handoff, checkpoint the design, confirm referenced parts are available, and include the relevant drawing, neutral export, or manufacturing output. The recipient should see both the deliverable and the decision trail that produced it.