Separate size from position
Scale describes how coordinate distances are interpreted; orientation and placement describe how a record is positioned. A file can have the expected size and still appear in an unexpected location. Record which symptom you observe before changing either property.
Autodesk’s mesh-import documentation describes STL and OBJ as unitless and asks users to match import units to the source. This is a general file/import concept, not a claim about a particular dental application’s default behavior. Confirm the actual source and receiving setup.
Ask for a documented comparison
| Question | Useful evidence |
|---|---|
| Which units were intended? | Source export context and receiving import settings. |
| What dimension is being compared? | A documented reference measured consistently in the authorized source and receiver. |
| Which record role is this? | Working arch, opposing arch, reference or other named purpose. |
| What relationship should be preserved? | Approved alignment/reference context from the original package. |
| What changed? | A separate named copy and a record of any authorized transformation. |
Do not use a generic “average tooth size” to decide a patient-specific transformation. The responsible teams should establish the intended interpretation from the actual records and workflow.
Keep a changed copy traceable
If a transformation is authorized, preserve the original, name the copy and record the reason and receiving task. Recheck the affected relationships after the change. Avoid presenting the transformed file as the untouched source.
Illustrative exception: the receiver reports a different measured size while the sender’s documented reference remains unchanged. The next action is to compare the export/import interpretation, not to apply a convenient scaling factor based on appearance.
Test the next task after resolution
Confirm that the replacement package supports the actual CAD or production handoff. A corrected display in a general viewer is only a display check. Native case context, aligned records and the intended receiving workflow may need separate acceptance.
Log the cause and resolution so the same route can be checked on the next pilot. If the issue cannot be traced, consult product support and hold affected work rather than hiding the discrepancy through repeated conversions.
Source notes
Primary documentation checked October 6, 2026. Software details describe the cited product documentation; the handoff frameworks and illustrative examples are original editorial guidance. Confirm current version and account requirements with the publisher.
Prepared by Pristine Dental Design · October 6, 2026. Guidance for professional case communication and review. Actual prescriptions, manufacturer requirements and receiving-team approvals govern design and production.