> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/lams/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/lams/tools/scratchie/student-view.md).
# Student view
Once students land on the Scratchie activity, they can see the title, the instructions set by the teacher, the group or team leader and the list of questions to be answered:
If the **Scratchie is part of a TBL lesson (tRAT)** and if the teacher enabled the option to [display the answers from the iRAT](/lams/tools/scratchie/create.md#importing-answers-and-confidence-levels-from-irat), then students will be able to see the answers that all of the members of their team have selected in the iRAT and their confidence levels.
## Selecting answers
{% hint style="warning" %}
**Team Leader!**\
\
As the Scratchie activity is a team assessment, **only the leader of the team can answer the questions on behalf of the team.**
{% endhint %}
**As the leader selects an answer, the whole team can see what selection the leader has chosen** and the immediate feedback (as to whether the selected answer is correct or incorrect).
If the answer is correct, then the team can move on to the next question.
## Raising Challenges or Burning questions
## Asynchronous Scratchie
If this is an asynchronous team test (meaning that the teacher selected the option to include "[discussion pads](/lams/tools/scratchie/create.md#advanced-settings)"), then all the team members can stated their preference for answers in the discussion.
Then the leader, taking into account everyone's comments, can make the selections on behalf of the team.
## Report review
Once the team has finalised all the answers in the Scratchie, they can **view their team assessment report** that will display their **overall score**, the **order in which answers were selected** per each question and all the **challenges and burning questions raised by all teams**.
At this stage, the team can **read the burning questions or challenges raised by other teams** and then like them if they want to let the teacher know that these burning question should be prioritised.
---
# 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.lamsfoundation.org/lams/tools/scratchie/student-view.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.