Identify each connector in the review
Use the current case revision and a clear location convention. Name which units the connector joins and include a view that makes the reviewed region visible. If a reviewer requests a change, the designer should not have to infer which connector or which earlier version the request concerns.
exocad documents connector size and shape controls and thickness visualization. Its manual also describes limits that can require manual attention. These are product capabilities, not evidence that a particular bridge meets every material or manufacturing requirement.
Name the actual instruction source
Record the prescribed material workflow and current requirement source used by the responsible team. Avoid borrowing a connector number from another material, indication or example case. A software preset should be checked against the actual approved process, not treated as a universal clinical answer.
When space or a competing design requirement prevents the proposed design from meeting the stated requirement, report the conflict. The responsible team must resolve the instruction; the designer should not quietly reduce the requirement to remove a warning.
Keep a connector review record
| Record | What it establishes |
|---|---|
| Location | The connector and design revision under review. |
| Requirement | Named current instruction source for the approved material/process. |
| View or measurement | The evidence used to discuss that region, including limitations. |
| Exception | Unresolved space, instruction or production dependency. |
| Approval scope | Who reviewed this question and which other checks remain. |
A color display or isolated measurement belongs with its context. It cannot alone establish the whole restoration’s clinical suitability or predict a patient outcome.
Review the effects of a revision
Illustrative handoff: a request changes the form near one connector after an earlier review. The return identifies the changed region and asks the receiver to recheck affected requirements. It does not claim that untouched files remain current if the package itself changed.
Use the release manifest to replace the affected output and the revision brief to explain why it changed. The receiving team determines the required downstream checks and manufacturing release. A connector annotation is part of that evidence, not a substitute for it.
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.