By ChiefArchitectSoftware.net Editorial Team · Published 2026-10-28 · Updated 2026-10-28
Distinguish installed content from project-specific content
Identify which objects are supplied by the application and which are custom, imported, or modified. Do not assume an imported catalog exists on another workstation.
Name by purpose and source
Use descriptive names such as room, finish, supplier, or revision rather than “material 1.” Record enough identifying information to distinguish a concept texture from an approved specification.
Review image and texture dependencies
When textures or reference images are linked outside the project, locate the original source and confirm whether the recipient will be able to access it. Test the package on another workstation where possible.
Keep performance in mind
Very large textures and detailed imported objects may increase file size and rendering load. Use the level of detail needed for the decision and keep a lighter option when creating everyday working views.
Test restoration
Keep a dated project backup and a list of imported assets. Open a copied version after moving or restoring data; confirm materials, symbols, and thumbnails before archiving the source workstation.
Practical final checklist
- Save a dated backup or review copy before changing an active project.
- Check information against the relevant current software documentation and local project requirements.
- Test changes on a representative file, then inspect the resulting drawings and exports.
- Record unresolved questions and obtain qualified professional review when the deliverable requires it.
Related workflows
Continue with Floor plan workflow, Printing to scale, Backup and recovery.