Practice Workspace
See how practices prepare, send, and fix cases from one workspace.
Cases Is The Working Home
The practice workspace is built around Cases, not around scattered inboxes or separate draft areas.
Context Comes First
The practice should choose the lab, the dentist, and the case type before the packet feels finished.
Use PreCheck Before Send Time
PreCheck is most useful when the team uses it while building the packet, not only at the last second.
Where Practice Work Happens
Practices should treat Cases as the main home for day-to-day work.
For practices, the main place to work is Cases. That is where new work starts, unfinished work stays visible, and submitted work can still be reviewed without switching mental models.
LabPreCheck is designed so the case stays central. The practice should not need one page for new work, another page for draft cleanup, and a different page for the actual handoff story. The case itself should stay visible from preparation through submission follow-up.
How A Case Starts
Good practice cases start with routing and provider context before uploads take over.
A strong practice case starts with the destination and the responsible provider, not with a pile of files. Once the lab, dentist, and case type are set, the rest of the packet becomes much easier to organize and review.
This is one reason the practice side feels lighter than the old process when it is used well. The product can show what is still missing because it already understands where the case is going and who it belongs to.
Choose the receiving lab from Labs or from an existing connected-lab relationship.
Select the right dentist from Dentists so the case is tied to the correct provider context.
Set the case type before uploads and notes start to accumulate.
Confirm the practice is not blocked by incomplete billing or setup details before the packet is ready to send.
How PreCheck Should Be Used
PreCheck is a working tool, not just a last-screen label.
PreCheck is most useful when the practice uses it during preparation, not only as a final confirmation step. The goal is to surface the next missing piece while the case is still easy to fix.
That means the practice should clear obvious blockers first, then tighten warnings that are likely to trigger a callback, resend request, or avoidable clarification after submission. A cleaner send moment protects front-desk time, assistant time, and the practice-lab relationship.
Build The Packet
Attach files, notes, and selections for the chosen lab and case type.
Use PreCheck Early
Review PASS, WARN, and BLOCK while the practice still has everything in front of it.
Send A Cleaner Case
Resolve the issues that would make the lab stop and ask for basic clarification.
What Happens After Submit
The same case should stay central before and after submission.
Once a case is submitted, the practice should still think of the case as the source of truth. Status changes, review results, and return requests belong to that same case rather than being split into separate preparation and post-submission systems.
When a lab needs something corrected, the practice should update the case, resolve the issue, and resubmit with the same destination and context kept intact.
Submitted cases continue to live in Cases.
If a lab rejects or returns a case, the practice should fix that same case rather than rebuilding the story somewhere else.
Activity is useful after submission as part of the case history, but it is not the main place to prepare a packet.
What A Good Practice Routine Looks Like
A repeatable practice routine should feel calmer than guesswork, not heavier than the old process.
The best practice routine is simple: choose the destination, set the provider and case type, build the packet, use PreCheck before send time, and submit only when the packet makes sense for the receiving lab.
If your practice is still evaluating whether that routine is worth adopting, read For Practices. If you need pricing details before creating the workspace, read Pricing.