Interview the workflow, not just the software brand
Use this question list before agreeing a new lab pilot. Ask who prepares records, defines the prescription, reviews designs and owns production release. A lab's preferred software name does not tell you who can answer a missing-record question or whether returned files can be used.
The what-to-send guide addresses the case package; this interview addresses how the lab will operate the receiving process across cases. Record an answer as an assumption until the appropriate person confirms it with an actual requirement or bounded pilot observation.
Convert broad answers into specific commitments
If the lab says “we handle all implants,” ask which tasks and configurations belong in the initial pilot and who confirms component identity. If it says “just send the final STL,” ask who will inspect the output, what companion context is required and how revisions are labelled.
Discuss turnaround only after the inputs, held decisions and available review capacity are defined. Pricing and commercial terms must be agreed for the actual scope; this worksheet contains no default price or delivery promise.
| Check | Evidence or next decision |
|---|---|
| Work scope | Which indication/task is included in the first pilot, and what remains excluded? |
| Records and defaults | Who supplies current inputs and approves the preference-packet revision? |
| Receiver | Which application/release and agreed file role will be tested? |
| Exceptions | Who resolves missing clinical/reference/component evidence, with which dependency held? |
| Review and release | Who accepts the delivery, requests changes and authorizes production? |
| Communication | Which internal route carries the current brief and superseded-output list? |
Test one high-value assumption
Hypothetical example: the lab expects to edit a native project while the proposed service scope is a manufacturing-mesh delivery. The interview identifies that mismatch before work is accepted. The parties either define a verified native-package pilot or keep the task bounded to the agreed mesh role.
Select one test that resolves an actual uncertainty: current inputs, revision communication or receiving usability. Do not use a successful routine handoff as evidence that every specialist case type or software route is supported.
Leave the interview with a versioned brief
Summarize agreed scope, accepted inputs, required deliverables, reviewer and unresolved questions. Link the actual preference packet, manufacturer instruction log and test plan rather than copying unversioned settings into a chat message.
An unanswered question should name the decision owner and next action. If it blocks the pilot, keep the affected task held while another independent task proceeds only by explicit agreement. No contact, outreach or external message is sent by this tool or worksheet.
Validation and limits
Louie validation pending — unverified locally. Louie must validate the interview against actual Pristine service scope, receiving capabilities and responsibility boundaries. The worksheet is an internal planning tool, not outreach, a service promise, clinical acceptance or a new contractual term.
The worksheet is blank and contains no patient data or executable settings. Examples are hypothetical, not tested Pristine cases. Actual prescriptions, applicable manufacturer instructions and responsible approvals govern design and production.
Editorial basis
Original internal workflow interview and hypothetical examples, prepared October 6, 2026. This guide asserts no new software capability or verified Pristine configuration. Resolve technical questions through the current applicable vendor documentation and the linked pilot/receiving guides.
Prepared by Pristine Dental Design · October 6, 2026.