Separate three instruction scopes
A standing preference applies to an agreed group of future work. A case exception applies only to a named case or stage. A proposed update is not active until the responsible team approves its scope. Label these categories explicitly in revision communication.
Clinical prescriptions and applicable manufacturer requirements govern the actual work. A lab preference packet organizes communication; it does not override those requirements or authorize a designer to fill in missing decisions.
Create a preference change record
| Field | Question to answer |
|---|---|
| Preference identifier | Which existing instruction is being changed? |
| Current version | What did the designer receive? |
| Proposed wording | What exact instruction replaces it? |
| Scope | Which supported case types or stages does it cover? |
| Exception boundary | When must the team ask instead? |
| Approval | Who authorized the change and when? |
| Effective point | New cases only, or named work already in progress? |
Illustrative exception-to-default decision
Illustrative example: a reviewer requests a different presentation on case LAB-021. Record it as a case exception first. If the lab wants it applied more broadly, ask for a separate approved preference update identifying the affected scope. Do not infer that the same change applies to unrelated indications.
When a default changes mid-case, identify whether the current revision should be reopened. A date alone may not settle this: one case may be awaiting review while another is already released. List affected cases or state explicitly that the change applies only to new intake.
Distribute one active packet
Give the packet a version and an effective date. Retain the superseded version for traceability, while making the active version easy to find. The case intake record should identify the version supplied to the designer.
Avoid parallel instructions in email, chat and a worksheet that disagree. Consolidate the approved change in the packet and link the clarification record. If instructions conflict, hold the affected decision and ask the responsible team which instruction governs.
Review preferences using observed issues
Use repeated clarification questions to identify unclear wording. Review whether the preference actually describes an observable action and whether its scope is understandable. Do not turn a single unusual case into a universal rule.
Periodically remove obsolete instructions and verify that examples remain authorized and relevant. Confirm substantial technical changes with Louie and the receiving team before adopting them as operating practice.
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.