# Knowledge check results > How journey knowledge checks are graded, where to review every attempt and each question's results, and what reaches your LMS or LRS. - Plans: All plans - Canonical: https://docs.devlin.ai/journeys/knowledge-check-results Every time a learner finishes an attempt at a knowledge check in a published journey, devlin.ai records it: the score, whether it passed, and each question with the options the learner chose. The journey editor's **Results** stage shows these results, and an LMS package reports each question to the LMS. ## How knowledge checks are graded - A knowledge check is graded when the learner selects **See results** after the last question. The score is the percentage of questions answered correctly, and the check is passed when the score reaches the check's pass mark. - A question is correct only when the learner chose exactly its correct options. A question that allows several answers gives no partial credit. - The learner sees whether each answer was correct after **Check answer**, and the score after the last question. - devlin.ai grades every recorded attempt again on its own servers, against the published journey. The score, the pass and which answers were correct in **Results**, in the CSV and in the xAPI `answered` statements come from that grading, never from the learner's browser. The passed or failed statement for each check, and the SCORM interactions, use the result the journey shows the learner, graded by the same rules. - A knowledge check also counts toward the journey's scorecard, and can be required by a checkpoint or start a path. See [Building a journey](https://docs.devlin.ai/journeys/build-a-journey). What is recorded: - Attempts in the published journey, from its learner link or from an LMS package. The draft preview, review links and the editor's canvas record nothing. - Each attempt is recorded once, also when the learner's browser sends it again. - The prompt and option texts are kept with each attempt as the learner saw them, so editing a question later does not change what an earlier attempt shows. - Who the learner is follows the simulations' rules. When your workspace collects learner identity, an attempt keeps the name or ID the learner typed on the journey's identity card, or the learner an LMS package named, and the learner details the journey asks for. Otherwise it keeps only the random identifier the journey creates in the learner's browser. See [Publishing and sharing a journey](https://docs.devlin.ai/journeys/publish-and-share-a-journey). ## Review results 1. Open the journey in the editor. 2. Select **Results**. For each knowledge check in the journey, in reading order, **Results** shows where it sits (chapter and page) and: - **Attempts**: every recorded attempt. - **Learners**: the learners who made them. A learner is counted by the name or ID they gave, else by their browser's identifier. - **Learners passed**: the share of those learners who passed at least once. - **Average score**: the mean score of every attempt. - **First-attempt average**: the mean score of each learner's first attempt. **Questions** opens each question with the share of answers that were correct, and how many times each option was chosen. The correct options are marked. A question most learners miss, or a wrong option many learners choose, points at a question to reword or a topic to teach again. **Latest attempts** lists the newest 200 attempts with the score, the result, the learner, the check, the attempt number and when it was made. Open an attempt to see each question, the learner's answer and, for a wrong answer, the correct one. A knowledge check that is no longer in the journey still shows its results, marked "No longer in this journey". Before anyone has answered, **Results** shows "No knowledge check attempts yet. Attempts appear here when learners answer a knowledge check in the published journey, from its learner link or an LMS package. Previews and review links are not counted." **Results** reads the newest 5,000 attempts of the journey. When there are more, it says so, and the figures cover those newest attempts. Who sees what: - Any member of the workspace can open **Results**. - Learner names, IDs and details are shown only to members allowed to see learner identity, under the workspace's learner identity visibility setting. Others see each learner as an anonymous learner. - When the workspace pseudonymizes learner IDs, the browser identifier is pseudonymized in **Results** and in the CSV. ## Export to CSV **Export CSV** downloads the attempts **Results** reads, with one row for each question of each attempt: when the attempt was made, the learner (identity columns only for members allowed to see learner identity), the check, the attempt number, the attempt's score and result, the question, the learner's answer, the correct answer, and whether the question was answered correctly. It is suited to item analysis in a spreadsheet. ## LMS and LRS reporting - **SCORM 1.2 and SCORM 2004** packages record each question of every attempt as an interaction in the LMS: a choice question with the learner's response, the correct response and whether it was correct. SCORM 2004 also records the question's prompt as its description. SCORM 1.2 records each option as a letter, in the order you wrote the options: a, b, c and so on. LMS reports that list interactions, or question analysis, show them. - **xAPI** packages, and a workspace LRS, receive an `answered` statement for each question of the learner's latest attempt at each check when the journey is finished, alongside the passed or failed statement for the check. Each one describes the question as a choice interaction, with its options, the correct response and the learner's response, and names the check as its parent. A workspace LRS receives them only for a run in which the learner also practised a simulation or talked to a coach (see [Sending statements to your own LRS](https://docs.devlin.ai/integrations/workspace-lrs)). - SCORM packages record interactions only when they are downloaded from this version on: export the journey again and upload the new package to get them. An xAPI package that already sends devlin.ai's journey statements receives the `answered` statements without a new download. See [Publishing and sharing a journey](https://docs.devlin.ai/journeys/publish-and-share-a-journey) for everything else a journey reports. ## Learner data Knowledge check attempts follow the same rules as simulation attempts: - A workspace retention window clears the learner identifier, the learner details and the random browser identifier from each attempt once it is older than the window. The scores and answers stay, so the figures in **Results** keep working. - For a learner listed on the Learners page, **Download all data** includes the learner's knowledge check attempts with each question and answer, **Delete all data** deletes them, and **Merge into…** moves them to the learner you merge into. **Undo** moves them back. A learner who has only answered knowledge checks is listed there too, and the learner's knowledge check attempts appear under **Knowledge checks**. See [Learner history and AI summaries](https://docs.devlin.ai/results-and-analytics/learner-history). - The workspace export includes every knowledge check attempt. See [Data privacy, retention and learner data requests](https://docs.devlin.ai/workspace-and-team/data-privacy-and-retention) and [learner history and AI summaries](https://docs.devlin.ai/results-and-analytics/learner-history). ## Ask devlin and AI tools devlin, on the Core, Team, Enterprise plans, and AI tools connected over the [MCP server](https://docs.devlin.ai/integrations/mcp-server-and-ai-tool-connectors) in a workspace whose plan includes it and where an owner or admin has turned it on, can read the same results with `get_journey_check_results`: each check's figures, each question's share of correct answers and option counts, and optionally the latest attempts with every answer. Learner identity is hidden from members who may not see it, as in **Results**. ## Related - [Building a journey](https://docs.devlin.ai/journeys/build-a-journey) - [Publishing and sharing a journey](https://docs.devlin.ai/journeys/publish-and-share-a-journey) - [LMS packages: SCORM and xAPI reporting](https://docs.devlin.ai/publish-and-embed/lms-packages-scorm-and-xapi) - [Evaluators, scoring learner-submitted work](https://docs.devlin.ai/evaluators/evaluators-scoring-submitted-work)