Examination Center logo Examination Center
Open student view

See how an instructor can create a coding exam, manage sections and rosters, monitor students live, review integrity evidence, and export exam records.

  1. 1Create exam
  2. 2Add sections & rosters
  3. 3Students join
  4. 4Monitor live sessions
  5. 5Review integrity evidence
  6. 6Export records

Integrity signals are evidence for instructor review, not automated accusations.

Overview

Python Lab Exam · Sections A & B · Fall 2026 · this platform does not grade — it monitors and records.

Customer model

How the institution maps onto the platform.

UniversityNorthbridge University
DepartmentMechanical Engineering
CourseME 341 — Computational Methods
SectionsSection A · Section B
ExamPython Lab Exam
Students184 enrolled

Create an exam

This is where a university creates exams. In the live dashboard you add the exam, sections & access codes, import the roster, and set the schedule (read-only preview here).

Sign in to create exams

Schedule

OpensNov 12, 10:00
ClosesNov 12, 11:30
Accommodations+25% time · 3 students

Interpreter packages

numpypandasmatplotlibscikit-learn

No AI assistant, no autocomplete.

Roster

Imported184 students
EnforcementOn

Live monitoring

Active sessions. Signals are evidence for review — not grades or verdicts.

StudentSectionStatusLast savedRunsCode versionsSignalsReview

Session status

Code runs over time

Integrity evidence

Captured automatically and shown for human review. The platform never makes an accusation or a grade.

Editor & activity signals

    Code similarity (evidence)

    Similarity evidence highlights code pairs that may deserve human review. It does not automatically accuse students or make misconduct decisions.

      Technical detail

      Computed as Jaccard similarity over normalized Python token 5-grams. High overlap is a prompt to review, not proof.

      Review & export

      Adjudicate sessions — set a status and notes, then export. No grades are assigned.

      1

      Open session

      See the code timeline, run history, and any integrity signals.

      2

      Weigh evidence

      Review paste/edit signals and code-similarity pairs in context.

      3

      Set status & notes

      Mark reviewed / needs-follow-up / escalated / cleared, with notes.

      4

      Export records

      Export session JSON, events CSV, and the integrity report.

      Review status

      Institution controls

      Institution-level controls.

      Departments

      Institutional controls

      • Role-based access (14 roles)Enabled
      • SSO sign-in (OIDC · Microsoft/Google)Configurable
      • Audit logEnabled
      • Exports (session JSON · events CSV · integrity report)Enabled
      • Retention & data deletionEnabled
      • LMS integrationPlanned