> 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/learn/functional-capabilities/manage-learn/what-is-observation.md).

# What is Observation?

Observations consist of questionnaires tailored for specific entities like school blocks or clusters. Users with roles such as Teachers, HT and officials can record observations whenever needed and access them accordingly. On Manage Learn, Content Creators have the capability to create three types of observations.

{% embed url="<https://drive.google.com/file/d/1MXPefXTzkZ40BZnBIqmbE4uSDx0DbojD/view?ts=64dc66db>" %}

{% embed url="<https://docs.google.com/presentation/d/1nOswAk7_b5DpqfKP5MvN_rH2UersACecECzzoHzu0Vk/edit#slide=id.p>" %}

### Observation with rubrics

Creators have the flexibility to define particular domains, criteria, and scores for each Observation. Based on the scores users get on taking up an Observation, they are shown the level (L1, L2, L3) their school is at concerning the Observation that was conducted. Any logged-in user can use the Observations.

### Observation without rubrics

The questionnaire is straightforward and does not include any domains.

### Observation led Improvement project <a href="#observation-let-imporvment" id="observation-let-imporvment"></a>

These are Observations with rubrics with Improvement Projects mapped to each level. Users get suggestions for starting an Improvement Project based on the level they are at after completing the Observation.

{% embed url="<https://youtu.be/Itooozolui0?list=PLUrm4D0K_7nxlaZZYirokpx5Mo-jMd64M&t=1511>" %}


---

# 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/learn/functional-capabilities/manage-learn/what-is-observation.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.