> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/quizzes/creating-a-quiz/question-types/spreadsheet-questions.md).
# Spreadsheet questions
Creating spreadsheet questions for your quizzes
Spreadsheet questions allow you to gather user responses in the form of a spreadsheet embedded within the answer box.
The system cannot mark these questions. If you are using spreadsheet questions in an exam, you should not set results to release 'Always automatically' as users will receive their results before you have marked them on the quiz configuration.
After selecting the spreadsheet question type, you will need to enter the question stem, i.e., what question you want users to answer.
On the answer tab, you won't be adding options. You only need to add a text box title, something like `Your answer:`
You can also pre-fill cells within the spreadsheet to provide data for the candidates to use to answer their questions
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
The question will appear to the user as below:
Additional spreadsheet tools can be accessed on the question building and answering side by hovering over the three dots icon to the right of the toolbar
---
# 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://academy.synap.ac/doc/quizzes/creating-a-quiz/question-types/spreadsheet-questions.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.
