> For the complete documentation index, see [llms.txt](https://welcome.orthosnap.com/get-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://welcome.orthosnap.com/get-started/what-to-expect-once-youve-submitted-a-case/receiving-your-case.md).

# Receiving your treatment plan

One of the most important items Orthosnap offers is a comprehensive treatment plan! With our treatment plans, you are able to see the costs and the length of the treatment. You are also able to see if any IPRs or attachments are needed, and the exact planned tooth movements for each sequential aligner step from #1 onwards. Let's take a look at the different sections.

## Understand**ing** the number of aligners and timeframe for the treatment

![](/files/-Md3I43Nxh7VHh6y5QOt)

#### 1. The Treatment Plan Heading

On the right part of the header the number of the steps and the length of the treatment, as this example shows 12 steps on the upper arch and none for the lower. Number of the steps varies depending on the complexity of the steps and can be changed upon clinical discussion with the doctor altering the treatment plan through through narrowing down the scope of movement and applying IPR's if desired for the purpose of step count reduction where possible. The treatment will also show the estimated cost to the doctor.

![](/files/-Md3IOmin7I70guNlzf3)

#### 2. The Case Mark-Out

In this section the exact vectors of movements per identified arch designed and marked out for each individual tooth throughout the treatment are marked out and can be followed by identifications of manipulations sequence throughout the steps following in the chart form following below.

![](/files/-Md3InAEIGc-fbjAbxnh)

#### 3. Tooth Movements

Each specific tooth movement per step is identified with descriptive and commonly used abbreviations in the teeth manipulated per step field. There are 8 different movements commonly seen in our treatments:

1. Extrusion
2. Intrusion
3. Mesial Rotation
4. Distal Rotation
5. Lingual Torque
6. Buccal Torque
7. Mesial Torque
8. Distal Torque

Depending on the chief complaint and RX instructions treatment plan will reflect the movements focused on the quadrants associated with the task of teeth alignment or bite adjustment. In addition the same treatment is visualised with supporting 3D animation with fewer clinical details but serving as a patient demo of the course of the treatment.

## Treatment plan example

Here is an example of a simple treatment plan:

![](/files/-Md3JDkZEAA7JlIuTBtz)

Attachments on the teeth #2, #6, #7, #11, and #15 are identified with blue squares and IPR ( interproximal reductions ) are specified with the sides mesial and distal measuring at .25 mm for each in the orange fields on the teeth 7 and 10.

Each horizontal roll in the main body of the treatment plan details a single step and represented with aligner set translating it in to the teeth movement as designed in corresponding step. Step numbers reflected on the aligners individual step packaging along with short instructions if any Attachments or IPR is associated with particular step.

Every treatment plan is custom designed for each patient and suggests doctor's approval or change request for treatment optimization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://welcome.orthosnap.com/get-started/what-to-expect-once-youve-submitted-a-case/receiving-your-case.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.