Scan completed exams¶
Prerequisite and access¶
Open the exam and select Scan. The page is pinned to the displayed Administration version. Until that version has printable labels from its published packet artifacts, Scan shows only a Print packets first prerequisite linking to Print; upload and status controls remain hidden.
Prepare the upload¶
Upload one PDF or one ZIP containing PDFs. Loose image files are not supported.
- Capture the full page, including QR labels and page edges, at readable quality.
- Pages from named or numbered packets can be in any order and can be separated.
- For a master packet, one student's group starts with exactly one title page, continues with that student's response pages in any order, and ends at the next master title page or the end of that PDF. A group cannot cross PDF/ZIP members.
- Do not duplicate a master title or response page inside one group.
- Ordinary packet pages and valid master groups may be interleaved, but one physical page cannot mix master and ordinary label systems.
Upload and processing¶
Choose the PDF/ZIP and select Upload and Process. The upload appears under the collapsible uploads history and moves through queued, processing, cancelling, complete, completed-with-issues, failed, or cancelled states. A ZIP is one visible upload; its PDF members run sequentially and cancel together.
If a master group does not follow the required grouping rules, the upload fails. QR-free pages are allowed when the same PDF contains at least one detected QR. A PDF with no detected QR creates a review item. Labels from another version, exam, or course produce an error.
Read Scan status¶
The status bar is measured against active roster students:
- Complete: the current packet has accepted scans for every response workspace. Numbered and master-derived packets also require an accepted handwritten-name crop.
- Partial: a current packet has at least one accepted response crop but not all expected work.
- Missing: an active roster student has neither a complete nor partial current matched packet. Unmatched packets are reported separately and do not reduce this count.
Select show details for the packet/workspace matrix. It shows accepted, missing, needs-review, archived, superseded, and noncanonical evidence. Show missing students lists the active-roster remainder.
Archiving a packet excludes it from matching and grading and can be reversed later. Use Show empty archived packets to display archived packets with no scanned work.
Match handwritten names¶
Under Scan Review & Matching, unresolved numbered and master-derived packets share one roster-match table. When clerical matching is available, Gradebird can request an AI roster suggestion. Suggestions fill the student selector but remain proposals.
Review the handwritten crop and roster choice. Save an individual row with its checkmark, or select valid rows and choose Save selected. Named packets normally already have a student match.
A numbered packet is not complete until its handwritten-name crop is accepted. Removing an accepted name crop can clear its match and return it to review.
Resolve duplicate or conflicting evidence¶
Only one accepted detected response is allowed per QR label. Duplicate evidence enters review; it is never silently substituted. Accept or reject using the displayed crop and original paper. If accepted evidence is removed and rejected alternatives remain, those alternatives return to needs-review rather than becoming accepted automatically.
If new work appears after any candidate or final grading exists for that packet/question, Gradebird holds the new crop as a graded late-scan conflict and preserves the old accepted crop. You may reject the new crop without changing grading. Replacing the accepted crop requires typing DELETE GRADING and permanently deletes all candidate and final grading artifacts for that packet/question. Replacement is blocked while related AI grading is active.
A student identity becomes a packet conflict only when multiple matched packets contain detected response work. Gradebird does not choose automatically. If exactly one candidate has active finalized grading it is recommended, not selected. Choose the canonical packet on the conflict page; no scan or history is deleted.
Delete an upload¶
Open uploads history and use the delete action only for accidental upload cleanup. Confirm with the exact upload code or original filename. This permanently removes the uploaded source, stored pages, incidents, detected responses, and grading artifacts derived from that upload. It is broader than rejecting one crop or archiving one packet.
Keep original paper until all uploads, matches, duplicate crops, packet conflicts, and grading queues are resolved.
Scan completed exams¶
The Scan page uploads completed exam PDFs for the displayed administration version and summarizes processing, matching, coverage, conflicts, and cleanup work. Use its review links to resolve uncertain evidence before grading. Starting or inspecting an upload does not silently accept ambiguous responses.
Scan upload details¶
This page explains one upload’s source, processing status, incidents, pages, packet contribution, and cleanup eligibility. It supports diagnosis and download/view actions; deletion requires the separate explicit confirmation shown for that upload.
Packet conflict¶
This page compares multiple matched packets that contain response work for the same student and version. Review the evidence and choose the canonical packet explicitly. Selecting a canonical packet changes which packet supplies work but does not delete the alternatives or their history.
Scan review¶
This page reviews uncertain or conflicting evidence for one expected response location. Compare the available crops and choose the documented accept, reject, or replacement action. Replacing evidence after grading requires the displayed destructive confirmation because related grading artifacts are removed.
Scan response¶
This read-only detail page shows one detected response, its scan source, label/workspace identity, status, and image evidence. Use the linked review workflow for decisions; inspecting this page alone does not accept or reject the response.