Start with the job definition
exocad’s DentalDB documentation describes the order entry point, construction/material definitions and a saved project folder holding case data. Use that distinction to ask what the receiver needs: the job definition and project context, a review output or a surface for a specified production route.
Record the relevant version and modules with the supported component and material workflow. The official page illustrates a particular interface; do not assume every current installation has identical buttons or configuration. A project package should be tested in the receiving environment before a regular queue depends on it.
Agree the package inventory
| Role | Question for sender and receiver |
|---|---|
| Job definition | Do case identity, restoration types and material choices match the brief? |
| Source records | Which scans and approved references belong to this revision? |
| Native design | What continuation or review task must remain possible? |
| Output surfaces | Which export is intended for the agreed downstream route? |
| Dependencies | Which configuration or library context must be confirmed separately? |
Avoid treating the project folder as proof that all dependencies will travel or that the receiver has every required module. Confirm the supported route with the installed product documentation and responsible receiving technician.
Test continuation, not file count
Use an authorized pilot package. The receiver should identify the case, open the agreed native state and perform the expected task. Report missing context with the package revision and observed failure point. Counting files alone does not show that the project can be continued.
Illustrative distinction: a mesh viewer displays an exported restoration, while the receiving technician cannot reopen the requested native design state. The geometry was delivered, but the agreed native handoff has not been accepted. Ask for the appropriate package rather than naming a mesh as an editable project.
Return a manifest with the design
List native and surface outputs separately and name superseded files after a revision. State whether each output is for review, continued editing or the agreed receiving process. Keep the instructions tied to the same case revision.
Pristine’s exocad service page describes the business workflow; this guide is a packaging framework, not an affiliation claim or a guarantee of compatibility across all installations. Discuss the actual configuration and deliverables before sending case records.
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.