> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/assessments/editing-forms/analyze-exam-attempts.md).

# Manually Analyze Assessment Attempts

How the system analyzes an assessment attempt automatically and how to trigger the analysis manually

**When an Assessment Attempt is submitted, the system automatically Analyzes a users attempt. During the Analyze process, the following occurs:**

1. Sets final score, i.e. Pass or Fail.
2. Sets attempt tag from Venue Location Name (if being used).
3. Updates comments in Assessment from Attempt (if comments for learners are enabled).
4. Saves scores to the gradebook (if an Gradebook is attached to the Assessment Bank and Form).

Assessment Attempts with Composed Essay question types need to be Graded by an administrator after the user submits their Assessment Attempt. After grading the Composed Essay questions, the administrator needs to click the Analyze button to instruct the system to go through Analyze steps mentioned above.

When doing a **Force Complete** for an uncompleted Assessment Attempt, an Administrator can click the Analyze button to instruct the system to go through the analyze process.


---

# 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.shiftiq.com/help/assessments/editing-forms/analyze-exam-attempts.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.
