> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/release-6.0.0/misc/misc-pages/app-manage-learn-component-diagram/observation-and-survey.md).
# Observation & Survey
### [Observation](https://sunbird-ed.github.io/docs/mobile/modules/ObservationModule.html)
[Observations](https://ed.sunbird.org/misc/templates-1/overview/what-is-observation) are a set of questionnaires that are specific to a particular entity (such as a school block or cluster). Observations can be recorded at multiple instances, whenever necessary.
### [Add Entity](https://sunbird-ed.github.io/docs/mobile/components/EntitySearchLocalComponent.html)
The user will only be able to add [entities](https://ed.sunbird.org/misc/templates-1/overview/what-is-an-entity) to which he has access and also the entity type to which the observation is targeted. Add entity flow is only available for the observation flow.
### [Survey](https://sunbird-ed.github.io/docs/mobile/modules/SurveyModule.html)
The main difference between a [survey](https://ed.sunbird.org/misc/templates-1/overview/what-is-a-survey) and observation is that survey does not have an entity tagged to it.
### [Questionnaire](https://sunbird-ed.github.io/docs/mobile/modules/QuestionnairePageModule.html)
The questionnaire is used for rendering different types of questions. Seven different types of questions are supported by the questionnaire. Once the observation or survey is started, all the questions are saved locally, and only upon submission, the data will be submitted to the backend. Both survey and observation use the same questionnaire component to render the questions.
---
# 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://ed.sunbird.org/release-6.0.0/misc/misc-pages/app-manage-learn-component-diagram/observation-and-survey.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.
