> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/case-type-settings/creating-a-case-plan.md).

# Creating a Case Plan

This lesson will show you how to create a case plan in AgileCase in order to set milestones and manage your case timeline.

{% stepper %}
{% step %}

### Access case plans

<figure><img src="/files/Mei6t9stfpYMZrlUHXaO" alt="" width="177"><figcaption></figcaption></figure>

Case plans allow you to set a series of milestones for each of your case types in order to ensure that every case you open proceeds on schedule.

To begin creating a case plan, access the case plan page by clicking the "Milestones" button on the settings menu under "Case Type Settings".
{% endstep %}

{% step %}

### Add a new case plan

<figure><img src="/files/0DsPFTVu685iR1edrJig" alt=""><figcaption></figcaption></figure>

To add a new case plan, click "Add Case Plan". Any previous case plans you have created will be listed on this page so they can be edited.
{% endstep %}

{% step %}

### Name your case plan

<figure><img src="/files/V7zbPgGEnqqzRY0RuHUd" alt=""><figcaption></figcaption></figure>

Upon creating a new case plan you will be prompted to create a name for it. After you have done so, click "Save Case Plan" to return to the case plan page.
{% endstep %}

{% step %}

### Edit your new case plan

<figure><img src="/files/HrJ5n6CE8C3ME8z9NPvU" alt=""><figcaption></figcaption></figure>

In order to begin adding milestones to your case plan, use the dropdown menu opposite and select "Edit".

This can be done to any case plan at any time. In addition, you can also use the "Set Inactive" option to send the selected case plan to the recovery bin, which you can read more about here.
{% endstep %}

{% step %}

### Add a milestone

<figure><img src="/files/bbqJzDYAcXGZ7yLAwoCK" alt=""><figcaption></figcaption></figure>

With a case plan selected you can see the name and description as well as any milestones you have created. In order to create your first milestone, click the "Add Milestone" button to proceed.
{% endstep %}

{% step %}

### Fill out the milestone details

<figure><img src="/files/GBBrFKc5RTp2WeUuLetP" alt=""><figcaption></figcaption></figure>

You can now fill out the details of the milestone. First of all you must create a title which will be displayed in your case milestones tab.

The next step is to configure the parent of the milestone. The parent of a milestone is a preceding event from which you set a time scale for the milestone in question to occur.

For example your first milestone will have a parent of "Open Date". Setting the days difference to "0" will cause this milestone to be triggered on the day that you open the case. You can also select whether the "days difference" category is measured in working or calendar days.

At this stage you can also set whether or not a milestone is mandatory, which governs whether or not it is required for a case to progress.
{% endstep %}

{% step %}

### Create other milestones

<figure><img src="/files/qQIW9PhnAqxSIOFal2xH" alt=""><figcaption></figcaption></figure>

To create further milestones, follow the same process as the first.

From this point you can also use previous milestones as parents, allowing you to plot out a whole case on the system. For example the second milestone here uses the previous milestone as a parent with a days difference of "3" so it will be triggered 3 days after the case has been opened.

A future milestone will be use this as a parent with a difference of "14" days. This means that, even if this milestone is achieved late, the next will be triggered in 14 days time which allows you to have an accurate plan even for cases that have slipped behind schedule.
{% endstep %}

{% step %}

### Edit milestones

<figure><img src="/files/4YCNeM6s4o5zxIEO28yA" alt=""><figcaption></figcaption></figure>

If you need to edit or delete a milestone you can do so using the opposite dropdown menu, selecting either "Edit" or "Delete" as appropriate.
{% endstep %}

{% step %}

### Save your milestones and relate the case plan to a case type

<figure><img src="/files/lXVJ7MY4SrFyJ0xy06vN" alt="" width="207"><figcaption></figcaption></figure>

Once you are happy with your case plan, click "Save Changes" to complete it. In order to use it in a case you must relate the case plan to a particular case type, which is covered in the lesson [here](/administrator-documentation/case-type-settings/creating-a-new-case-type.md).
{% endstep %}

{% step %}

### View your case plan

<figure><img src="/files/9uzlYE17zLm4Os8zCa2A" alt=""><figcaption></figcaption></figure>

You can now see your case plan under the "Details" tab in any case of the specified type. All of the milestones are displayed along with an expected date of completion as well as an actual date field that you can fill in, in order to chart the progress of a case.

Once you have updated your progress use the "Save Changes" button to save the update case plan.
{% endstep %}

{% step %}

### Use timeline view

<figure><img src="/files/8OyV4dD2XM2ZJVumkdVp" alt="" width="336"><figcaption></figcaption></figure>

You can also view case milestone using the timeline view feature, which you can read more about [here](/administrator-documentation/system-settings/timeline-view.md).
{% endstep %}
{% endstepper %}


---

# 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://docs.agilecase.com/administrator-documentation/case-type-settings/creating-a-case-plan.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.
