What a Printing Service Actually Needs From Your RPD File

When an outsourced framework comes back late, the delay usually happened before anything was printed. It happened at intake, when someone had to email you a question and then wait.

This is a list of what removes those questions.

Send the scan, not just the framework

Send the full arch scan, both arches if you have them, and the bite. A framework design in isolation cannot be checked against anything. With the arch and the opposing, the design can be verified against the case rather than taken on faith.

If the case came in as a physical impression or a model, say so and send the model. Both routes work. What causes delay is a design file arriving with nothing to check it against.

STL, OBJ or PLY are all fine. What matters is that the mesh is closed, watertight and in millimetres.

Survey before you export, not after

The path of insertion is a design decision, and it is yours. A printing service should not be picking it for you — that is the lab's clinical judgement about the case in front of it.

Before exporting, confirm four things:

Rest seats are prepared and readable in the scan. A rest that is not properly seated in the scan will be printed exactly as scanned, and the error only becomes visible at try-in.

Undercuts are surveyed and the retentive clasp tips sit where you intend. A clasp tip that lands above the survey line will not engage; one that sits too deep will not seat.

Relief is included where you want it. Relief under the major connector and around the retentive mesh is a design choice with clinical consequences. If it is not in the file, it will not be in the metal.

Minor connectors meet the major connector cleanly. Sharp internal junctions concentrate stress in printed frameworks the same way they do in cast ones.

The things that get files sent back

• Open meshes and inverted normals. Run a mesh check in your design software before exporting. Almost every CAD package has one.
• Wrong units. A file exported in centimetres arrives as a framework the size of a fingernail. Millimetres, always.
• The wrong object exported. Sending the model instead of the framework happens more than anyone admits.
• Wall thickness below what the alloy can carry. A lattice or a clasp thinned to a value that looks fine on screen may not survive finishing.
• No indication of the alloy. Cobalt-chrome and titanium print with different parameters. Say which one.

What a service can fix, and what it cannot

A service can nest the case, orient it, generate supports, print it, remove supports, heat-treat it, and finish and polish it. Those are manufacturing decisions, and a good service should own them completely — you should not have to think about build angle or support strategy.

A service cannot fix a survey. It cannot decide your path of insertion, invent a rest seat that was never prepared, or know that the abutment on tooth 24 is questionable and the design should compensate. Those are clinical judgements attached to a patient the service has never seen.

The boundary is worth stating plainly because a lot of outsourcing frustration comes from it being fuzzy. Manufacturing is ours. The case is yours.

What to include when you send it

• The framework design file, plus the arch scan and opposing
• Which alloy: cobalt-chrome or titanium
• Anything unusual about the case in one sentence — a compromised abutment, a tight interocclusal space, a patient who has broken clasps before
• Your deadline, if it is a real one

That is the whole intake. In our workflow, design and the resin model are included in the price, standard turnaround is six business days with a four-day rush option, and the completed case ships back to your lab, not to the dentist.

If you have never outsourced a framework and want to see the whole loop before you commit anything real to it, send one case. There is no minimum, no account setup and no volume commitment — a single framework is an ordinary order.