Scorae › Guides › Grading discussion posts without losing your week
Grading discussion posts without losing your week
Thirty students, one initial post and two replies each: that is ninety items in every graded thread, every week, before you have graded a single essay. Discussion grading gets manageable through design decisions made before the thread opens, not through reading faster.
Design decisions that do most of the work
- Two deadlines, not one. Initial post by midweek, replies by the weekend. With a single deadline everything lands at 11:50 p.m. on the last night, replies become impossible to write meaningfully, and you cannot fairly grade what your own deadline made impossible.
- A small point scale. A weekly thread is worth 20 or 25 points, not 100. Fine-grained scales invite fine-grained disputes over work that should take five minutes to score. Our 25-point discussion rubric is built for exactly this cadence.
- Prompts that require the reading. "Share your thoughts on this week's topic" is answerable without opening the book, and the posts will prove it. Ask students to take a position on something specific in the assigned material and the low-effort post becomes visibly low-effort.
- Published reply standards. "I agree, great post" persists exactly until the rubric names it as the bottom level. Once "adds a new example, question, or disagreement" is the standard, replies change shape.
Grading the thread once it closes
- Grade in chronological view, not collapsed view. You see who actually engaged whom, and reply chains read as conversations instead of orphaned fragments.
- One pass, one thread, all students. Score initial posts on one pass, replies on a second. Keeping one criterion in mind across ninety items is fast; keeping four criteria in mind per student across ninety items is what eats the evening.
- Feedback to the thread, scores to the student. Write one paragraph to the whole class about what the strong posts did, post it in the thread where the next week's posters will read it, and keep individual comments to one line except where a student needs a real intervention.
- A timer, again. Two minutes per student is three hours for a section of ninety items. Decide the number before you start and let the rubric carry the judgment.
What this looks like at scale
With the two-deadline structure, the 25-point rubric, chronological single-criterion passes, and thread-level feedback, a 30-student weekly discussion settles at 60 to 90 minutes. Scorae shortens the last long part: highlight a post in Canvas, Blackboard or Moodle and it drafts the rubric-based comment for you to approve, which matters at item 61 in a way nothing else does.
Ninety items, drafted one by one
Scorae applies your rubric to student work in Google Docs, Canvas, Blackboard and Moodle and drafts criterion-by-criterion feedback for you to review, edit and approve. You decide every grade. Student work is never stored.
Add to Chrome — free30 days free, then $9 a month. Cancel any time and keep a free plan of 15 essays a month. Works on desktop Chrome.