Describe the disagreement before moving a mesh
A visual discrepancy is an observation, not a diagnosis. Record which arches, relationship file, revision and view were compared. Distinguish a missing relationship record from disagreement between two supplied references and from a suspected software assignment issue.
Preserve the imported state and avoid arbitrary movement to make the display appear plausible. Ask the responsible team which reference governs the current stage. A designer should not independently replace the clinical relationship with a preferred visual arrangement.
Use a discrepancy brief
| Field | Example information to record |
|---|---|
| Observed state | View, object names and exact revision |
| References compared | Supplied bite/relationship and approved reference |
| Uncertainty | Missing, conflicting or possible assignment issue |
| Held work | Specific dependent design decision |
| Requested answer | Governing record and authorized next step |
| Resolution evidence | New revision, reviewer and remaining limits |
A request should be narrow enough to answer. Instead of asking whether the bite is right, identify the two references that disagree and the design decision that cannot proceed. Record a response in the case brief rather than relying on a transient chat.
Software correction follows record authority
exocad documents an antagonist-position correction workflow using a new alignment scan. That is a software procedure for a defined input, not permission to choose a clinical relationship. See the linked troubleshooting guide for the specific software scope and locally-unverified status.
If an authorized correction is performed, retain before/after evidence and record which reference was used. Review dependent design work against the updated relationship before continuing. When disagreement remains unresolved, return the question to the responsible case team rather than applying successive undocumented adjustments.
Review boundary
Technical review pending — unverified locally. Unverified locally: Louie must validate terminology, actual workflow dependencies and practice-case applicability. Source review is not software or clinical validation.
Use these worksheets to make uncertainty visible. They do not authorize a clinical decision, repair, production release or unsupported software configuration. Preserve original records and record who approved each change.
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.