These settings are related, but they do not do the same job. Choose them based on what should happen after student work arrives.
Setting | What it does | Best for |
|---|---|---|
Accuracy grading | Scores student work against the answer key and any rubric or AI instructions you configured. | Most graded assignments where correctness matters. |
Completion grading | Adds a separate completion score path without replacing the accuracy score. | Homework or practice work where you still want useful feedback and a completion measure. |
Auto-grade | Starts grading automatically after eligible submissions arrive. Microsoft Teams submissions are checked on a 5-10 minute polling cycle. | Trusted recurring workflows where assessment setup is already stable. |
Auto-publish | Pushes results onward automatically after grading finishes and the workflow is eligible to publish. | Highly repeatable LMS-connected workflows where you already trust the downstream publish path. |
LMS final score type | Chooses whether the LMS should receive the accuracy score or the completion score when both exist. | LMS-linked homework workflows using completion grading. |
Run analytics after grading | Automatically generates or refreshes class analytics as soon as batch grading completes. If analytics have never been run, this creates the first run. If they already exist, this refreshes them with the latest data. | Classes where you want analytics ready to review immediately after a grading batch finishes, without having to trigger the run manually. |
Run integrity check after grading | Automatically queues an integrity check across all eligible submissions as soon as a batch grading run completes. | Assessments where you want every batch automatically screened for academic integrity concerns without a manual trigger. |
Enable this toggle to let Classwise generate or refresh class analytics automatically as soon as a batch grading run completes. This removes the manual step of opening the analytics page and triggering a refresh after every grading session.
Step by step
- Open the assessment and go to More Settings (inside the Basic information step of the assessment wizard).
- Scroll to the Run analytics after grading toggle and turn it on.
- Save the assessment.
- Run batch grading as usual. Analytics will be generated or refreshed automatically once all submissions in the batch have been processed.
- Open the analytics page for the assessment to see the updated results.
Keep in mind
- This setting only fires after a batch grading run completes. Single-submission grading does not trigger it.
- If analytics have never been run for this assessment, the first run is created automatically. If results already exist, they are refreshed with the latest graded data.
- Analytics generation runs in the background — you do not have to wait on the grading page for it to finish.
- The 2/3 grading threshold still applies: analytics will not generate if fewer than two thirds of enrolled students have been graded.
- You can still trigger analytics manually at any time from the analytics page, regardless of whether this toggle is on.
Enable this toggle to automatically queue an integrity check across all eligible submissions as soon as a batch grading run completes. This removes the need to manually trigger an integrity check from the submission view after every grading session.
Step by step
- Open the assessment and go to More Settings (inside the Basic information step of the assessment wizard).
- Scroll to the Run integrity check after grading toggle and turn it on.
- Save the assessment.
- Run batch grading as usual. An integrity check will be queued automatically once all submissions in the batch have been processed.
- Open the integrity check results from the submission view once the check is complete.
Keep in mind
- This setting only fires after a batch grading run completes. Single-submission grading does not trigger it.
- On credit-based plans, credits are consumed per submission at the standard integrity check rate. Institution-managed accounts draw from the shared pool instead.
- If an integrity check is already in progress for the assessment when grading completes, the automatic trigger is skipped to avoid duplicate checks.
- Only submissions with a graded status (completed or needs review) are included in the check.
- You can still trigger an integrity check manually at any time from the submission view, regardless of whether this toggle is on.
- The Integrity Checker produces an Integrity Report for each submission — results are available in the submission panel under the Integrity tab.
Most confusion comes from settings that sound independent but actually affect one another.
Decision checklist
- Use only accuracy grading when you want one correctness-based score and no separate homework-completion score.
- Use completion grading when students still need meaningful feedback but the LMS should track completion separately. It uses 2 credits per graded submission.
- Turn on automation only after you have tested one small grading loop manually.
Key points
- Completion grading adds a second score path; it does not replace accuracy grading.
- Turning off completion grading clears the LMS final-score choice because there is no second score to publish.
- Auto-publish only makes sense after you trust both the grading setup and the LMS publish behavior.
- Google Classroom automation depends on the assessment already being published to the LMS.
Most teachers do not need to invent a custom configuration. Start with one of these common patterns and only add complexity when the workflow really needs it.
Scenario | Recommended setup | Why this is usually the best fit |
|---|---|---|
Standard quiz or test | Use accuracy grading only and keep automation off until you test one sample run. | This keeps the grading path predictable and makes teacher review straightforward. |
Homework where completion matters | Turn on completion grading, then decide which score should be sent back to the LMS. | Students can still receive meaningful feedback while the LMS tracks the score path you care about. |
Recurring LMS-connected workflow | After you trust one manual cycle, consider auto-grade and then auto-publish. | Automation is safest only after the assessment inputs and LMS behavior are already proven. |