> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/respondents-management/response-status.md).

# Respondents Status

## ✅ Completed

Completed respondents are respondents that have finished and submitted the survey.

## ⏳ In progress / pending

In progress respondents are respondents that started the survey but did not yet finish the survey by submitting the results. 

{% hint style="info" %}
The [progress completion](/form-management/form-designer/form-settings/progress-completion.md) feature must be enabled on your survey to let your respondent save and restore their session at a later point.  
{% endhint %}

## 📚 Archived

 [Archived](/form-management/respondents-management/archived-respondents.md) respondents are respondents that have finished and submitted the survey but that are taken out of any [security item](/form-management/security/security-items.md) access checks.

## 📵 Offline

 [Offline](/form-management/publish-deploy/offline-survey.md) respondents are respondents that have been collected while being [offline](/form-management/publish-deploy/offline-survey.md) and that are stored locally on your browser. It is strongly recommended to upload your offline responses as regularly as possible to avoid any data loss.


---

# 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.ngsurvey.com/form-management/respondents-management/response-status.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.