T-Marker clinic-to-lab handoff: organize the files before design

A T-Marker capture should reach the lab with enough context for the technician to identify the case, arch and intended export. Agree on that handoff before the first appointment. A file that arrives without its role or revision can leave the team waiting even when capture is complete.

TruAbutment's T-Marker produces multi-unit abutment location data in STL format. Its manual provides export choices and a way to save the case. The clinic and lab still need to agree on the rest of the case package and who reviews it before design begins.

Agree on the receiving workflow first

Ask the lab which export representation it expects. The manual lists HS Cap Small, HS Cap, MUA Cone and Dual Align Scan Body. Put the agreed choice in the lab's intake instructions so the capture operator does not have to infer it from the name of a CAD program.

Have the lab identify the software and component library it plans to use, then review a non-patient training case together. An STL extension alone does not establish a complete workflow for every library or software configuration. The receiving technician should confirm that the intended file opens and can be used in the planned case setup.

Make the file names useful

Use your existing case identifier, the arch, the file's role and a revision marker. For example, a training file named TRAINING-042_upper_MUA_r01.stl tells the receiver more than export.stl. Keep real case information within your practice's approved secure transfer process.

When the lab requests additional scans or records, name them by their role as well. Let the receiving lab define that list for the case. The T-Marker MUA position file should be clearly identified within the package rather than treated as a label for every file associated with the restoration.

Separate saving from sending

The manual distinguishes exporting the STL for sharing from accepting the results to save the case in TruSuite T-Marker. Saving a case in the app does not tell the clinic whether the laboratory has received the exported file.

Add a short receipt check to the handoff: the lab confirms the case identifier, upper or lower arch, expected export representation and readable file. Assign someone to follow up on missing files before the case enters the design queue. This is an administrative check, not a substitute for clinical or technical verification.

Handle revisions as a complete package

If a file is replaced, tell the lab which revision supersedes the earlier one. Keep the original in your case history and identify the current working version. Avoid a message that says only "use the new scan" when several attachments are circulating.

A brief change note can state what was replaced and whether the rest of the package remains current. Have the lab acknowledge the revision before design resumes. The clinic should also know who to contact when the technician finds a mismatch, so questions return to the person who can resolve them.

Test the handoff before routine work

Run a training case through capture, export, transfer and laboratory receipt. Record where the team had to stop for clarification. Turn those points into a short intake checklist shared by both teams; keep the manufacturer's capture instructions as the technical reference.

For the export options themselves, read T-Marker export types. For the physical kit decision, see AOT, URIS and Straumann kit selection. Dentcore lists the URIS kit and Straumann kit separately from AOT.

For reference only. Specifications, pricing and availability may change. Follow the current manufacturer instructions and verify the product configuration before purchase. For professional dental use; clinical decisions remain with the treating dental professional.