Choose the intake path based on where the work currently lives: local files, the LMS, pasted text, camera capture, or a scanned paper stack.
Step by step
- Open the assessment detail page and decide whether the submissions should come from upload, LMS pull, paste, camera capture, or stack processing.
- Use Upload Submissions when the work is sitting in files outside the LMS and you want to import a class set manually.
- Use Pull From LMS when the work already exists in the connected LMS and you want Classwise to import it for grading.
- Open a single student row if you want to use the one-student upload flow, paste text directly, or capture work by camera.
- Use Upload Submission Stack only when you are processing a scanned pile of paper work for multiple students at once.
- After intake finishes, refresh the assessment table and confirm that the right student rows now have submissions attached.
You should see
Submissions enter the assessment through the intake path that best matches the source of the work.
Keep in mind
- Single-student upload, paste, and camera capture do not use exactly the same grading path.
- Stack submission is PDF-only and is meant for paper workflows at class scale.
Common blockers
- The right intake path depends on whether the work is already in your LMS, still on paper, or sitting in files outside the gradebook.
Once submissions are attached, the next job is to run the right grading action and then use the states to decide what still needs attention.
Step by step
- Open the assessment detail page and review which rows are ready to grade.
- Use Grade to open the menu with Grade All and Grade Ungraded.
- Choose Grade All when you want to process every gradable row, or choose Grade Ungraded when you only want untouched or cancelled rows.
- Confirm the action in Grade All Submissions? or Grade Ungraded Submissions?.
- Let the jobs run, then watch the table for rows moving from Not graded or In progress into Completed or Needs review.
- Use Cancel Grading only if the batch is already running and you need to stop it before the job finishes.
- Open any row that lands in Needs review before you publish or email anything outward.
You should see
You can tell which submissions are still processing, which need teacher review, and which are ready to share.
Keep in mind
- Grade All ignores rows that are not gradable right now.
- Needs review is a teacher checkpoint, not a failure state.
Keep in mind
Completion grading does not replace the review logic for accuracy grading. It layers alongside it when enabled.
Use the single-student page to inspect the grader output, make teacher edits, and confirm the result before you publish, email, or download anything.
Step by step
- Open one student row from the assessment table.
- Use Previous Student and Next Student if you want to move through the class without returning to the table each time.
- Click Grade if the submission has not been processed yet.
- Wait for the grading view to finish loading, then review the question-level breakdown, feedback, and totals.
- If the page shows Review Required or Needs review markers, read those first before you decide the result is ready.
- Edit scores, comments, bonus points, or completion values where needed.
- Click Save or Save & Next when the feedback looks right.
- Use More if you need Copy Link, Download, or a one-student feedback action.
- Use Regrade, Replace, or Delete only when the source submission or grading result really needs to change.
You should see
You use teacher review as the control point before feedback leaves the product.
Keep in mind
- Replace is not available for pasted submissions.
- Unsaved teacher edits can trigger a confirmation flow before you navigate away.
Common blockers
- Regrading, replacing the file, or deleting the row changes what is safe to publish or email next.
Use stack submission when a class set of paper work has already been scanned into one or more PDFs and still needs to be assigned to students.
Step by step
- Open Upload Submission Stack from the assessment.
- Upload one or more PDF files and set Pages per student.
- Move to the review step so Classwise can group the scan into student-sized chunks.
- Review the page groupings, then assign each chunk to the correct student.
- Add or remove placeholder pages only when you need to fix scan alignment.
- Confirm the stack so Classwise creates the student submissions and returns you to the assessment.
- Run grading only after you confirm that the chunks were assigned to the right students.
You should see
Large paper-based batches can be processed in one workflow instead of grading every student one by one.
Keep in mind
- Stack submission only accepts PDF files.
- Changing pages per student resets existing chunk assignments and placeholder offsets.
Limitations
- Stack submission still depends on clear file organization and readable uploads.