> 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/trade-license-tl/tl-user-manual/employee-user-manual/process-application/field-inspection.md).

# Field Inspection

Log in with Field Inspector credentials.

The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.

Click on the **Application Number** hyperlink to open the application.

Scroll through the application details and review the details.

Click on the **Take Action** button and click on the **Verify and Forward** option if all details are found complete and satisfactory.

![](https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/KbRUZ4L77Wo2Df2pyjA3/image%20\(226\).png)

Select the **Assignee Name**. The application will be forwarded to the selected assignee for approval.

In case, the documents and details are found incomplete or missing, click on **Send Back to Citizen** option. This will send back the application to the citizen for necessary action.

Click on the **Reject** option if the application details are found inaccurate. This will reject the application.

Click on **Send Back** option to send the application back to the previous employee (document verifier in this case) for further action.


---

# 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/trade-license-tl/tl-user-manual/employee-user-manual/process-application/field-inspection.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.