TLDR: A technician approves the trim line, confirms the occlusal plane, and reviews, adjusts and approves the final design before it goes to production. Those three gates are required rather than optional, and the case does not advance past a stage a qualified person has not signed off.

The five stages, and which three stop

A case moves through prescription intake, scan-quality checks, trim line and occlusal plane confirmation, design proposal, and final design approval. The third and fifth require technician sign-off, and the scan-check stage puts flags in front of a technician who decides what each one means.

1. Submission. The clinic scans and submits the case. Nothing about the clinician's existing workflow changes.
2. Prescription intake. SmartRX reads the prescription on upload, cross-references it against the scan files, and populates the case. Missing or contradictory information surfaces here, before design work starts.
3. Scan-quality checks. SmartScan flags distortions, missing mesh, contamination artifacts and unclear margins. The technician decides what to do with each flag. The software does not approve or reject the case.
4. Trim line and occlusal plane. The technician reviews and approves the trim line, then confirms the occlusal plane. Hard stop.
5. Design proposal and approval. SmartCAD proposes the full-arch design. The technician reviews, adjusts and approves it, then sends it to production. Hard stop.

What is the technician actually judging at the trim line?

Where the denture base meets tissue, which governs fit, retention and comfort. A proposed trim line is a reading of anatomy that the technician either agrees with or corrects, and the correction is often about this patient's case rather than about the geometry being wrong.

This is the clearest example of why the gate exists. Two cases can present near-identical scans and call for different trim lines because of what the prescription says, what the referring office prefers, or what the lab knows about a particular practice's cases. None of that is in the mesh.

The technician can adjust rather than only accept or reject, which matters more than it sounds. Accept-or-reject forces a binary on work that is usually a small correction, and in practice it pushes technicians to reject and rebuild, which removes the point of the tool.

Why confirm the occlusal plane as its own step?

Because everything downstream depends on it. An occlusal plane confirmed early is cheap to change; the same correction discovered after a full design has been proposed costs the design. Separating it into its own gate puts the decision where it is least expensive.

The general principle behind the ordering of gates is that judgement should happen before the work that depends on it, not after. This is the same argument that makes intake checks worth more than bench checks: the earlier a decision is confirmed, the less work is built on top of an assumption.

What does final approval involve?

The technician reviews the proposed full-arch design, including margins and anatomy, adjusts what needs adjusting, and approves it for production. The design that reaches manufacturing is the one a qualified person signed off, not the one the software produced.

That last sentence is the whole regulatory and professional position in one line, and it is worth stating precisely. SmartCAD proposes. The technician completes the design. The software does not design the denture independently of the technician, and it is not a diagnostic or treatment-planning tool.

The practical consequence for a lab is that accountability does not move. The person who has always been answerable for a design leaving the building is still the person answerable for it, which is the arrangement your referring offices already understand.

Why build the gates in rather than make them optional?

Because an optional gate is one a busy lab skips on a bad Friday, and then the exception becomes the process. Required review also keeps the product in a classification that depends on human-in-the-loop operation, which is a deliberate design decision rather than a constraint.

SmartCAD's classification as a technician-operated design aid rests on the human review being mandatory. A version with a skip button would be a different product with different obligations, and it is not the product being built.

There is a plainer argument too. The scarce resource in this industry is trained judgement, not throughput. A workflow that spends that judgement on the decisions that need it, and less of it on repetitive setup, is using the scarce thing well. A workflow that removes the judgement is throwing away the only part that was hard to get.

What this means for how you staff a shift

• Plan review capacity, not design capacity. If proposals arrive in minutes, the number that governs output is how many cases your technicians can review well in a day.
• Review quality degrades with volume. A technician approving a large queue at the end of a shift is a different reviewer from one at the start. Build that into the plan.
• Keep a sample second review. On a small share of cases, including senior work. It is how drift gets caught before a referring office catches it.
• Record what technicians changed. The pattern of adjustments is the most useful quality signal a lab running this workflow has.

Related reading

• the digital denture workflow end to end
• what 30 cases an hour actually means
• how to get a new CAD designer productive faster