Define what must remain editable
Before design starts, name the work the receiving team intends to continue: reviewing the case definition, reopening the design or producing the agreed outputs. Ask which files and dependencies are needed for that specific task. A mesh that opens in a viewer is not evidence that the native project can be continued.
Record software version, relevant licensed modules and agreed component or material configuration. These are test inputs, not a promise that any two installations of the same software can exchange every case. Use current product documentation for the installed workflow.
Run a representative acceptance check
| Check | Evidence to retain |
|---|---|
| Identity | Case ID, design revision and package match the delivery manifest. |
| Open | The intended receiving application opens the supplied package. |
| Context | Named records and case definition correspond to the agreed brief. |
| Continuation | The receiving task can be performed without unexplained missing dependencies. |
| Review | Restorative questions and release status are recorded separately from import success. |
Do this with an authorized, representative pilot before relying on the route for a busy queue. If the lab changes a software version or production setup, reconsider whether the earlier acceptance test still describes the current environment.
Separate technical failures from design feedback
An import error should be reported with the exact message, source and receiving versions, package revision and observed failure point. Avoid altering order metadata simply to silence an error. Consult product support when the supported import route is unclear.
A project that opens but differs from the agreed brief is a different exception. Capture the mismatch with the relevant view and request a design review. Keeping these categories separate makes it easier to see whether the issue is packaging, configuration or the design itself.
Acknowledge only what was tested
Illustrative acceptance note: “Revision D opened in our agreed receiving setup and the listed input roles were present. Restorative review is pending.” This records a useful result without implying manufacturing release.
If the agreed continuation task cannot be completed, hold the affected output and explain what is missing. Agree a recovery route with the sender; do not substitute a surface export unless both teams confirm that it meets the actual task.
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.