The Crown That Wasn't There

The Day the Crown Wasn’t There

Here is a sequence every dental practice has experienced at least once. A patient books their crown seat appointment weeks in advance. The lab case was sent two weeks ago. Nobody has checked on it since. The patient arrives. The assistant goes to pull the case. It is not there. A phone call to the lab reveals it was delayed and will arrive next week. The patient, who took time off work or rearranged childcare, is told to come back.

This is a clinical disappointment. The patient’s tooth has been prepped. They were ready. The trust they placed in the practice has been tested by something they cannot distinguish from carelessness. From where they sit, the distinction between a lab delay and a practice failure is invisible. They showed up. The thing was not ready. That is the full story they will tell.

The cause, in almost every case, is not the lab being late. It is the practice not knowing the lab was late in time to do anything about it.

The Sending-and-Forgetting Pattern

Lab case management in most practices follows what could be called the sending-and-forgetting pattern. The case goes out. The return date is noted somewhere, informally, often as a date on a paper lab slip or entered into an appointment note. Nobody tracks the case actively against that date. Nobody contacts the lab before the due date to confirm the case is on schedule. The assumption is that the lab will deliver on time because it usually does.

When the lab is late, the practice finds out one of two ways: either the case does not arrive on the expected day and someone notices, or the patient arrives for their appointment and the case is not there. The first outcome means a scrambled phone call and a rescheduled appointment with at least some lead time. The second means a patient already in the chair being told to come back.

Both outcomes are preventable. The prevention is proactive contact with the lab several days before the linked appointment, far enough ahead that if the case is delayed, the appointment can be adjusted before the patient makes the trip.

What Tracking Actually Means for Lab Cases

A working lab case tracking log is not complicated. It captures, for every open case: the case identifier, the lab, the date sent, the promised return date, the linked appointment date, and the current status. That is the minimum. The log is reviewed on a defined cadence, not on the morning of the appointment, but several days before. Any case whose return date falls within the upcoming review window gets a proactive contact with the lab to confirm status.

If the lab confirms the case is on schedule, the appointment stands. If the lab reports a delay, the practice has time to make a decision: reschedule the appointment before the patient arrives, or escalate if the delay creates a clinical urgency. Either way, the patient does not show up to an appointment that cannot proceed.

The gap between “we track lab cases” and “we actually know where each case is” is almost always a gap in review timing, not in intention. Most practices know which cases they have out. The failure is not tracking that a case was sent; it is reviewing that log proactively against upcoming appointment dates and making contact with the lab before the due date. These are two different activities, and only the second one prevents the crown-that-wasn’t-there problem.

The review cadence is the key element. A log reviewed only when someone thinks of it, or reviewed on the day cases are due, does not provide enough lead time to act. A log reviewed on a defined schedule, cross-referenced against upcoming appointments, does. The difference between a log that prevents problems and a log that merely documents them is the frequency and timing of the review.

The Remake Tracking Gap

When a restoration comes back and does not fit, a remake case goes out. In most practices, it goes out with the same informal non-system as the original. Nobody logs which lab generated the remake. Nobody tracks whether the remake arrived on time. Nobody reconciles the lab invoice for the remake against the original case. When a third case is needed because the second did not fit either, there is no record that this lab has now produced two failed restorations for the same patient.

Remake tracking closes this gap. Every remake is logged against the original case: which lab generated it, the date sent, and the expected return date. Invoices for remakes are reconciled against the original case record. If a lab produces remakes at a higher rate than others, or if a specific lab consistently has fit problems with a particular procedure type, that pattern becomes visible in the tracking log.

Without the log, lab quality problems are visible only at the individual case level. Everyone notices when a crown does not fit. What is invisible is the pattern. Whether the problem is systemic, and whether it is concentrated at a specific lab or a specific procedure category, is information that only a tracking record can produce. A practice that does not track remakes by source pays the cost of poor lab performance repeatedly without ever identifying that it is the same lab causing the same problem.

Invoice Reconciliation as a Natural Extension

A lab case tracking log that also captures the associated invoice creates an opportunity for reconciliation that most practices miss. Lab invoices arrive. The cases they bill for exist in the log. Comparing the two answers a set of questions that otherwise go unasked: is the practice being billed for remakes that were the lab’s fault? Are invoices arriving for cases that have not been confirmed delivered? Are the fees being charged consistent with the contracted rates for each lab relationship?

Without reconciliation, lab invoices are processed as they arrive, and the assumption is that the billing is accurate. That assumption is usually right, and occasionally wrong in ways that cost the practice money that nobody notices. A log with invoice data adds a verification step that takes minimal additional effort and produces an auditable record of what was paid against what was delivered.

Why This Is an Excellent Early VA Assignment

Lab case management is one of the strongest early assignments for a VA working with a dental practice, and the reason is specific: the benefit is felt by the clinical team directly and immediately. When restorations are present and confirmed before the patient arrives, the assistant and the provider experience that outcome at the chair level. When a remake is flagged early and an appointment adjusted before the patient makes the trip, the provider notices the difference. The clinical team’s confidence in a VA is built fastest through work that makes their day smoother in ways they can see.

The work itself involves no patient health information in the clinical sense, requires no clinical judgment about treatment decisions, and uses a simple tracking tool: a spreadsheet or a designated field in the practice management system. Any organized person can maintain it. The result is measurable: the number of appointments that cannot proceed because the case was not present trends toward zero as the tracking log becomes active and the proactive review cadence holds.

Lab invoice reconciliation is a natural extension of the same role. The tracking log already contains the cases and the expected dates. Adding invoice verification to the same workflow requires no additional access or expertise, and produces an ongoing audit of lab billing accuracy that the practice currently does not have.

The Signal to Watch For

In a practice that does not run a lab case tracking system, the problem is usually described not as a systematic gap but as an occasional unfortunate coincidence. “We had a crown not come back last month.” “This almost never happens.” “We just had bad luck with that lab.”

That framing is worth examining. A lab case that arrives late and is not caught before the patient arrives is an information failure, not a luck failure. The information that the case was delayed was available from the lab. Nobody asked for it until it was too late to act on. That is not bad luck. It is a missing process. When the same thing happens three months later, the framing will be exactly the same: bad luck, unusual, almost never happens.

The tracking log converts “almost never happens” into a measurable rate. Once the rate is visible, the pattern is manageable. Once the pattern is managed, the appointments that used to fall apart become the appointments that do not, because someone checked the log four days earlier and made a call.