A case can arrive digitally and still not exist.
Even if a scan is downloaded and a prescription is attached, a case isn’t “real” until it’s entered into your lab management system (LMS). Until then, it can’t be scheduled, assigned, tracked, or surfaced in production planning.
That’s the reality behind one of the most common bottlenecks in modern dental labs: manual case entry.
When case entry depends on humans typing information in, cases don’t move at the speed they arrive.
They end up in limbo:
And once that happens, everything downstream slows down:
Most labs treat intake like “quick admin.”
But the true cost isn’t the typing, it’s the compounding effect of three hidden losses:
If your LMS doesn’t reflect real-time incoming workload, your team is operating with partial information.
That leads to:
Manual entry creates:
Even minor errors trigger rework, back-and-forth communication, and avoidable remakes.
Your most experienced team members often become the “catch-all” for intake issues.
Instead of focusing on design, QC, or complex cases, they’re spending time:
At scale, manual intake becomes a hidden labor drain and many labs end up hiring for it, even though it doesn’t generate revenue.
Digital dentistry improved how cases are created and captured.
But most LMS systems still assume humans will manually input case details.
So labs are left bridging a gap between digital portals + scans + Rx files and a system that needs structured data to operate.
That gap is where invisible work grows.
The most efficient labs treat case entry as a system, not a task.
That means:
Instead of spending hours on data entry, the lab’s intake team focuses only on exceptions, not repetitive work.
If you answer “yes” to any of these, manual intake is already holding you back:
This whitepaper includes the complete breakdown of how labs eliminate manual case entry, reduce intake errors, and make every case “real” the moment it arrives.
Designs you order from EviSmart arrive in your Oqcam already formatted. Named the way your nesting rules expect, with shade and material attached, and pointed at the machine that case belongs on.
The routing is decided per case. An implant case sends the crown to the mill and puck you cut implant crowns on, and the model to the printer you print models on. Different case types, different machines, chosen automatically rather than by a tech working through a dropdown for every file.
The trigger is QC approval. EviSmart designs your cases your way. The same team works on all your cases and learns what a good case looks like to you. Once your case passes our QC, it triggers a greenlight to send the design directly into your Oqcam account in under a minute.
Once the file arrives in your Oqcam, all your CAD/CAM technicians can review the nested design before starting the mill. That final QC step does not change and is not meant to.
Setup is one session. We connect your Oqcam account and agree where each of your products should go, using the routes and materials you have already built there. Nothing new to create, and you only revisit it if something changes.
Automatic sending only works if you trust what is being sent. Once a case is nested it gets cut, and a design that was not right is wasted material.
You choose what flows. During setup we map only the case types you want moving on their own. Anything unmapped never sends. It waits for you exactly as it does today.
Most labs start narrow. Bread and butter work first, night guards and posterior single units, then widen once they have watched it run for a few weeks. The lab that has been live longest started exactly there and has added case types since.
Your approval stays. This removes the file shuffling between design and CAM. It does not remove your eyes from the build.
For labs outsourcing design work the math gets compelling somewhere north of 30 cases a day into nesting, because that is where the handoff stops being an annoyance and starts being a role.
Not touchless design. Touchless handoff. Every step in that chain that requires judgment should keep requiring judgment, and every step that never did should stop requiring a person.
Nesting requires judgment. Confirming a build requires judgment. Renaming a file so software can read it does not, and never did. It was a workaround that quietly became somebody's job.
Nobody pays you to rename files.
