Scheduling Dental Labs by Case Due Date

A dental lab runs thousands of unique, short-lived cases at once, and the only schedule that helps is one built backward from each ship date against the real load of the mill, the ceramist bench, and the finishing line. EDGEBIC by User Solutions treats every case as its own routing, works backward from its promised day, and routes each step only to a technician qualified to do it. Cases that cannot make their date surface at planning time, while there is still room to act, instead of at the packing table.

A lab is a high-mix, low-volume shop in its purest form. Volume of one, due date of tomorrow, mix that changes hourly. The scheduling problem is not any single case: it is holding the whole book to its promises when the constraint moves around the floor day to day.

Backward From the Ship Date, Every Case

Most lab work has a hard delivery day driven by the practice's appointment. Forward scheduling from "now" answers the wrong question. Backward scheduling from the ship date answers the right one: given this delivery, when must each step start, and does the calendar have room.

The engine places each case's steps backward from its due date onto finite capacity. When the calendar has room, the case is confirmed. When it does not, the case is flagged as at risk before anyone touches it. That single distinction, confirmed versus at risk, is what turns a pile of trays into a plan you can staff and promise against. The general mechanics live in forward versus backward scheduling, and the make-to-order angle in backward scheduling for make-to-order shops.

Because every case schedules against shared capacity, the cases due tomorrow claim mill and bench time ahead of the cases due Friday automatically. You are not triaging one tray at a time. You are scheduling the entire day's intake at once.

The Bottleneck You Do Not Have to Declare

On Monday the crush is at the mill. On Wednesday it is the ceramist bench. On Friday it is finishing and packing. A lab bottleneck floats with the case mix, and a schedule that assumes a fixed constraint is wrong most days.

Finite capacity scheduling does not require you to name the constraint in advance. Each step is placed against the real load of its work center, so the queue forms wherever the day's mix concentrates work, and it moves as your floor moves. Read the schedule and the bottleneck is simply visible: the station where cases stack up is the one to add an hour to. For the underlying idea, finite versus infinite capacity scheduling is the fundamentals read, and high-mix low-volume scheduling covers the pattern a lab shares with other short-run shops.

Routing Work to Qualified Technicians

Not every seat is interchangeable, and pretending otherwise is how labs over-promise. A zirconia layering step needs a certified ceramist. A high-value implant case belongs with your two most experienced technicians. A software model that treats every bench as equal will happily schedule work nobody on shift can competently do.

Model the qualification as a skill, assign it to the technicians who hold it, and require it on the routing step. The scheduler then places that step only in a shift where a qualified technician is rostered. If the ceramist works Tuesday through Saturday, layering steps land on those days, not on the Monday the bench sits empty. If both implant specialists are booked solid through Thursday, an implant case is honestly promised Friday rather than promised Tuesday and quietly handed to someone who cannot finish it.

You can also pin one case to one technician, and that pin beats the routing rule and survives every later reschedule. That is the mechanism for "this practice's premium cases run with Maria, no exceptions." The certification model is the same one used in operator certifications for medical devices, a neighboring regulated environment.

When the Day Changes

Labs live with change. A rush case arrives, a technician calls in sick, a mill goes down for an hour. The schedule has to reflow without discarding the morning's finished work.

Cases already completed are never moved by a reschedule. The crowns that shipped this morning stay exactly as recorded. Only unfinished steps re-evaluate against the new picture: a sick ceramist removed from the roster pushes layering steps to a day the skill is covered, and any case that can no longer make its ship date is flagged at once. You get the smallest honest change, not a wholesale reshuffle that erases what already happened.

A Worked Case

A crown-and-bridge case arrives Monday, due to ship Thursday.

If the ceramist bench is already full Tuesday, the case is flagged Monday as at risk of missing Thursday, and the planner adds a bench hour, splits the layering, or calls the practice. The point is the flag arrives with three days to act, not on Thursday afternoon.

Heritage in Complex, Deadline-Driven Work

User Solutions has scheduled deadline-driven, high-task-count operations since 1991, more than 35 years. The lineage behind EDGEBIC, including the RMDB heritage, handled work at the scale of the Nimitz refit with 26,000-plus tasks and drove GE Railcar on-time delivery from 30 percent to 90 percent. A lab holding hundreds of same-day promises is a smaller version of the same discipline: many short jobs, hard dates, finite hands.

Where to Start

Model one day's intake as cases with real ship dates, add the two or three skills that actually gate work, roster your technicians, and schedule backward. The first at-risk flag pays for the exercise.

For the fundamentals, what is production scheduling is the plain-language start and job shop scheduling challenges covers the high-mix pattern. The nearest neighbor is another lab scheduled by a person's calendar rather than its own: scheduling orthotics and prosthetics fabrication around patient due dates. The industry fit guide maps neighboring sectors and EDGEBIC is the product hub. Ready to hold every case to its promised day? Contact US for a demo.