Case tracking for dental labs: the register is the bottleneck
A lab running twenty cases a day on a hardbound register is not disorganised. It is at the limit of what a register can do, and every extra case costs more than the last.
Product·3 September 2026·7 min read
Walk into a busy dental laboratory in Lahore or Karachi and the register is usually the most important object in the building. Cases in, cases out, dentist names, dates, and a column of ticks. It works, and it has worked for years.
It also explains most of what frustrates the lab: the status phone calls, the case that was promised for Tuesday and shipped Thursday, and the argument at month end about what was actually delivered.
What the register cannot do
- Be read by two people at once, which is why status questions become interruptions.
- Show what is due tomorrow across all technicians without someone reading every line.
- Record which technician had the case at which stage, so a quality issue can be traced.
- Attach the dentist's instructions, the shade photograph and the digital file to the case.
- Tell you how long each stage actually takes, which is the number that runs a lab.
Give every case an identity and a stage
The two structural changes that matter are a unique case number that everyone uses, and an explicit stage the case is in right now.
Stages differ by lab and by work type, but the shape is consistent: received, design or wax up, casting or milling, ceramic or finishing, quality check, ready, dispatched. Once every case sits in a named stage, the question of where is it stops being a search and becomes a lookup.
Assign work to people, not to the bench
Cases assigned to the lab in general are cases nobody is responsible for. Assigned to a technician at each stage, you get accountability, an even workload, and a traceable history when something needs to be investigated.
This is also the fastest way to discover that one technician is carrying half the difficult work, which is usually true and almost never visible in a register.
Due dates that mean something
A promised delivery date is a commitment made to a clinic that has booked a patient. It deserves to be a field with a report behind it, not a note in a margin.
The single most useful screen in a lab system is due today and due tomorrow, sorted by stage. It converts a day of firefighting into a plan made at eight in the morning.
Keep the inputs with the case
Digital files, shade photographs, the prescription slip, the scan, and every subsequent instruction from the clinic belong on the case record. Labs lose more time to hunting for a file or clarifying an instruction than to any production step.
It also matters when a case goes wrong. A remake conversation is very different when you can show exactly what was received and when.
What changes once it is in place
DLMS is built around this: case tracking with stages, technician workflow, digital file handling, delivery management and invoicing that follows production. Labs that move from a register typically notice three things in the first month. Status calls drop, because clinics can see for themselves. The due list is planned rather than discovered. And month end billing stops being an argument, because what was delivered is recorded rather than remembered.
The register is not the problem, it is the ceiling. Give each case an identity, a stage, an owner and a date, and a lab can grow past the number of cases one person can hold in their head.
Frequently asked questions
What should a dental lab case record contain?
The clinic and dentist, the patient reference, the tooth numbers, the work type and material, the shade, the date received, the promised delivery date, the technician assigned at each stage, the current stage, and every dated note or instruction from the clinic. Anything less and you cannot answer the two questions labs get asked all day: where is it, and when will it be ready.
How is a lab case different from a manufacturing job?
It is one off, patient specific, time critical and dependent on inputs the lab does not control, such as an impression that may be unusable. That combination means a lab system needs stage tracking and exception handling more than it needs batch planning.
Do small labs need software, or is a register enough?
A register works up to the point where more than one person needs to know the state of a case at the same time. Past that, the register becomes a queue for whoever holds it. Most labs feel the tipping point somewhere between ten and twenty cases a day, or as soon as they serve more than a handful of clinics.