File Management and Version Control for Design Projects
Manage design files professionally — using consistent naming conventions, version tracking, and backup strategies that prevent lost work and confusion.
Learn — read and understand
File naming conventions: professional standards
Professional file naming format: [project_name]_[version]_[key_dimension or note].[extension]. Example: ruler_holder_v1_80x40mm.stl, ruler_holder_v2_wider_slot.tinkercad. Rules: (1) No spaces — use underscores. (2) Always include version number. (3) Never use 'final' until the project is truly complete (and even then, it is still a version). (4) Include the date for long projects: ruler_holder_v3_20260901.stl. (5) Never overwrite a previous version — always save as new.
Version control: keeping a design history
Version control means keeping every version of your design. Why: (1) If V3 breaks something that V2 had right, you can return to V2. (2) Your version history is the evidence of your design process. (3) Comparison between versions shows specific improvements. Version log: maintain a simple text file or table listing version, date, and changes made. This is the 'commit message' for your design — same concept used in professional software development.
Folder structure: organising a design project
Recommended project folder structure: project_name/ → cad/ (all Tinkercad exports), exports/ (STL files), prints/ (photos of prints), docs/ (brief, ECRs, evaluation rubrics). Every file goes in one designated folder — never on the desktop. Why: (1) Files don't get lost. (2) Sharing the project folder shares everything. (3) When submitting work, everything is findable.
Export checklist: what to save for each version
Every time you complete a design version, run the export checklist: (1) Export STL at fine resolution. (2) Save Tinkercad share link. (3) Take a screenshot of the model from 3 angles. (4) Note the version in the version log. (5) Move all files to the correct project folder. This takes 5 minutes and prevents the common problem of 'I can't find my design file.'
Explore — version control best practices
Tap to reveal
Never overwrite
When saving a new version: always 'Save As' with a new version number. Never save over the previous version — you lose the ability to go back.
Tap to reveal
Version log
A simple text table: version, date, what changed. One row per version. This is your design process evidence.
Tap to reveal
Cloud backup
Always save project folders to cloud storage (Google Drive, OneDrive). Local files on school computers are often wiped. Cloud backup prevents total loss.
Tap to reveal
Anti-patterns to avoid
'final_FINAL.stl', 'new_version2.stl', 'copy of copy.stl' — these are signs of poor version control. Use a consistent versioning system.
Activity — match each version control action to its correct purpose
Drag or tap a label, then drop/tap on a zone
Never overwrite — save as new version
Maintain version log
Consistent naming convention
Cloud backup
Preserve the ability to go back to V1
Evidence of the design process
Find the right file immediately
Prevent total loss if computer fails
Quiz — File management and version control, 5 questions
1The professional file naming convention for a 3D design file includes:
2Why should you NEVER overwrite a previous version file when saving changes?
3A version log should contain at minimum:
4Which folder should STL export files be saved to?
5The MOST important reason to use cloud backup for design files is: