> ## Documentation Index
> Fetch the complete documentation index at: https://docs.k16solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review course reports

> Use an AI Detection course report to find and open submission results.

A course report connects dashboard patterns to individual student submissions.

<Note>
  AI Detection reports are embedded workbooks. Their tabs, filters, and summary metrics can vary by
  workspace and report version. Follow the labels and metric descriptions in your report; the
  examples below may not all appear.
</Note>

## Open a course report

<Tabs>
  <Tab title="From K16">
    Open **AI Detection Dashboard**, open the course summary provided by your workbook, and select
    the course you want to review.
  </Tab>

  <Tab title="From Canvas">
    If your institution configured the AI Detection LTI, open the Canvas course and select **AI
    Detection** in course navigation.
  </Tab>
</Tabs>

<Note>
  The Canvas entry appears only where your institution has installed and enabled the LTI. Students
  do not receive reporting access through this faculty workflow.
</Note>

## Read the submission list

A course report can include:

* submission title
* submission type, such as assignment, discussion, or quiz
* AI classification
* AI probability or confidence
* student's name
* submission date
* read status

Some course reports initially focus on **AI Only** and **Mixed** results. If available, turn on **Display All Submissions** when you need the full processed population, including **Human Only** results.

## Review a course consistently

<Steps>
  <Step title="Confirm the course">
    Check the course title, code, and term before you review results.
  </Step>

  <Step title="Confirm the visible population">
    If your report offers **Display All Submissions**, check whether it is on. Note any other active
    filters.
  </Step>

  <Step title="Sort your review queue">
    Use classification, date, submission type, or read status to organize work. Do not use the
    probability alone as a disciplinary cutoff.
  </Step>

  <Step title="Open the submission">
    Select a row to inspect the overall result and sentence-level highlighting.
  </Step>

  <Step title="Record your review state">
    Use the available read status and your institution's case process so another reviewer can
    understand what remains.
  </Step>
</Steps>

## Avoid common comparison errors

* Compare submissions from the same course and assignment context when possible.
* Do not compare percentages across different filters without confirming both populations.
* Treat short, formulaic, heavily quoted, translated, or accessibility-assisted writing with extra care.
* Check whether the assignment allowed generative tools and how students were asked to disclose them.
* Keep the original submission and other evidence central to the review.

<Warning>
  A course-level list is a triage tool. It does not replace an instructor's review or your
  institution's academic-integrity process.
</Warning>

Continue with [Submission results](/ai-detection/submission-results).