> 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/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/send-back-applications.md).
# Send Back Applications
DV sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.
To send back applications to the counter employee, navigate to the Inbox page. Search for the application you want to verify by entering any of the search parameters. Click on the **Take Action** button available at the bottom of the page. Click on the **Send Back To Citizen** option.
Select the **Assignee Name** who will be responsible for verifying the application. Enter any **Comments** stating why the application is sent back. Click on the **Choose File** button to upload any files or images in context and then click on the **Send Back To Citizen** button.
The application is assigned back to the selected assignee for verification of documents and at the same time**,** the citizen is allowed to edit the application to update the missing details.
---
# 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/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/send-back-applications.md?ask=&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.
