Working notes, not marketing.
Things we learned the expensive way, written down so you do not have to. Mostly about the parts of digital dentistry nobody demonstrates at a trade show — orthodontic, surgical and restorative alike.
The screw position is the treatment plan.
Software will happily place a miniscrew wherever you click. It will place one through a root, into a sinus, or into 0.9mm of cortical bone, and the render will look just as convincing as a good plan.
This piece walks through how we decide where a margin should be before we let anyone mark it, what to do when the scan genuinely does not contain the answer, and why “the software found it” is the most dangerous sentence in digital dentistry.
Recent writing.
Each piece comes out of a case that went wrong, or a question we get asked often enough to be worth answering properly. No product pushes and no sponsored posts — subscribe below and new ones land in your inbox.
Why your surgical wafer did not seat
Four causes, and how the pattern of the misfit tells you which one you are looking at before you reach for a bur.
Read ImplantsProsthetically driven, or just bone-driven with extra steps
Planning backwards from the restoration, and how to tell when a plan only pretends to.
Read SkeletalMSE, MARPE, or refer for SARPE
A decision framework based on age, suture maturation and the bone actually present.
Read exocadParameter sets that stop you fixing the same thing daily
Cement gap, minimum thickness, connector cross-sections, where the defaults quietly cost you.
Read AlignersStaging is where aligner cases are won
Movement order, anchorage, and why front-loading IPR quietly wrecks anchorage.
Read RecordsThe five record errors that cost you a re-design
Trimmed palates, casual construction bites, cropped CBCT fields, motion artefact and the scan nobody checked.
ReadOne email, when there is something worth saying.
Case breakdowns, workflow notes and the occasional admission that something did not work. No product pushes, and unsubscribing takes one click.
Reading is not the same as designing.
If a post raises a question about a case you have in front of you, send it over. We would rather look at the actual volume.