> 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/user-documentation/dashboard/creating-a-case.md).

# Creating a Case

This lesson will show you how to create a case in AgileCase.

{% stepper %}
{% step %}

### Enter client details

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

After clicking "create case" you will be prompted to enter the case details.

This allows you to fill in your standard case details as well as any custom fields you have made at the point of creation.

The first step is to select the practice area and subsequent case type that the new case will belong to. Then you can enter the client details: Contact name and client reference number are for your client, you can also apply any relationships you have set for the case type, in this case a primary client.

You can also select another contact as the source for the case.
{% endstep %}

{% step %}

### Enter case data

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

The case data and case contacts fields will be populated with any custom fields and case contacts that you have enabled in the "Set Custom Fields Appearance" option under "Case Types" which you can read about here.

Any fields marked as mandatory must be filled in at this point in order to proceed and create the case.
{% endstep %}

{% step %}

### Enter milestones

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

Your milestones will be automatically generated providing the date of creation is the parent of your first milestone.

However, if you have set any as visible in the "Edit Custom Fields Appearance" page, you can manually enter the information here, which will fill in the "actual date" field in the case itself.
{% endstep %}

{% step %}

### Enter information

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

Further case information includes a short case description, the ability to select the partner and fee earner of the case and the ability to set the fee, either as a fixed fee or hourly rate.
{% endstep %}

{% step %}

### Advanced options

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

At this stage you can also edit the advanced options of the case. Some of these will be autofilled: "Date Opened" will be set to the current date, "Case Status" will be open and "Case Permissions" will be set to "Everyone".

These can all be edited and you can choose to add a planned completion date and apply any system ables of you choosing to the case.

Once you have finished entering this information, click "Save Changes" to create the case.
{% endstep %}

{% step %}

### View case

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

You can now access and begin to work on your new case through the "Cases" tab on the toolbar.
{% 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/user-documentation/dashboard/creating-a-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.