> 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/getting-started/creating-a-case-plan.md).
# Creating a Case Plan
Case Plans allow you to set milestones for each Case Type, allowing you to dictate your business processes and plot a timeline for every case to ensure each is followed up in a timely manner.
You can access case plans through **Milestones** under the **Details** tab in a case or through the settings menu under **Milestones**.
When you add a new Case Plan, you can enter a name and description to help you keep track of it when using multiple case plans.
With a Case Plan created, you can begin to add milestones. Milestones are the key actions that should be taken in every case. The milestones you use essentially define the process that you want each case to follow. Your initial milestone will likely be something along the lines of **Open Case**, with subsequent ones signposting the appropriate actions to be taken on your chosen timescale.
An initial milestone will likely be **Open Case** or similar.
You can also mark milestones as mandatory. Mandatory milestones must be completed for the case to progress. This option allows you to provide optional milestones that account for variation between cases if necessary, preventing you from implementing too concrete a structure while maintaining a strong basic plan for progress.
All milestones rely on a parent to form a Case Plan. The parent of a milestone is the previous milestone from which the timescale of the case is worked out. After selecting a parent, you select a number of days difference which governs when the milestone is due.
For example:
* The first milestone will have the parent **\[Open Date]** and a days difference of zero.
* The second milestone, if it must occur three days later, will have the first milestone as its parent and a days difference of three.
With this simple system, you can build Case Plans as complex as you need to ensure that each case is followed through promptly.
To link a Case Plan to a Case Type, access the **Case Type** menu in the settings screen and select your Case Plan from the dropdown.
You can relate your Case Plan to a Case Type under the **Case Type** screen in the **Settings** menu.
Once your Case Plan is linked to a Case Type, you can view your milestones in the **Details** tab along with expected dates of completion. These dates show when each task is due, and the **Actual Date Completed** box allows you to enter the date the task was actually completed so you can view at a glance whether or not a case is on schedule and chase up overdue work.
You can view milestones and enter the actual date they are completed under the **Details** tab.
With a Case Plan in place, you have successfully set up the basics of AgileCase. Our documentation will introduce you to more complex functionality so you can further improve and automate your workflow. For a more detailed explanation of Case Plans, consult the documentation topic [here.](/administrator-documentation/case-type-settings/creating-a-case-plan.md)
In the final part of this guide, we will look at how to toggle the visibility of case tabs and core data in order to control what aspects of a case can be viewed.
---
# 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/getting-started/creating-a-case-plan.md?ask=&goal=
```
`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.