> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/cms-v2.11/access/pgr-user-manual/citizen-user-manual/file-complaints.md).

# File Complaints

The **File A Complaint** option allows citizens to register their complaints.

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/dBen8ujcYwMKKbtH994a/image.png" alt="" data-size="original">                     | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/hlLC5blJHtluoXRVrMYW/image.png" alt="" data-size="original"> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| To file complaints navigate to the **Complaints** Home page. Click on the **File a Complaint** tab on the screen. This will open the complaint form page. | Select the applicable **Complaint Type** from the given list.                                                                         |

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/uHTL8EfSM23wjaY3u3Hw/image.png" alt="" data-size="original">                                                                                       | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/6n5BKUrRSenZPztmAXPa/image.png" alt="" data-size="original"> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Select the relevant **Complaint Sub-Type** from the given options. Refer to the [list of complaint types](/complaints-management/cms-v2.11/access/pgr-functional-specifications/complaint-types-list.md) available in CCRS. | Move the pin to the property location on the given map. **Skip And Continue** in case this is not available.                          |

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/qBt6WK9iOxLWo8Stg1Rn/image.png" alt="" data-size="original">               | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/ZESjfhHRuRVu3aGmKKr5/image.png" alt="" data-size="original"> |
| --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Enter the **Pincode** to indicate the location of the complaint. Click on **Skip and Continue** to proceed in case you do not have the PIN details. | Select the **City** and the **Locality/Mohalla** from the drop-down list. Mohalla details are available for the selected city.        |

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/r0hfmIatGHx4QS2EME32/image.png" alt="" data-size="original"> | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/nCT48lSJM1HrCAKeQeWP/image.png" alt="" data-size="original">                               |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enter a suitable **Landmark** to help reach the location easily.                                                                      | Upload a photo as evidence. Use the camera icon to click pictures and upload them directly. Click on **Skip and Continue** if you do not want to upload any photos. |

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/sehmf1XehyaWdBGXQsez/image.png" alt="" data-size="original"> | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/JkcdPHxD1y6eVV5SOtZY/image.png" alt="" data-size="original"> |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Enter any additional information if required.                                                                                         | The complaint is filed and submitted. Make a note of the complaint number.                                                            |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/complaints-management/cms-v2.11/access/pgr-user-manual/citizen-user-manual/file-complaints.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.