release scores in pear assessment

Release Scores vs Mark as Done in Pear Assessment

Two buttons sit near the end of every grading session in Pear Assessment, and confusing them causes a very specific kind of teacher regret: either your students see nothing when they should see their results, or they see everything before you’ve finished grading. Understanding release scores in pear assessment — and how it differs from Mark as Done — takes about three minutes, and it will save you from both mistakes for the rest of your career.

Here’s the one-sentence version. Release Scores is the student-facing step: it makes results visible to students. Mark as Done is the teacher-facing step: it closes out your grading workflow for an assignment once you’ve reviewed everything. They are separate actions, done in a deliberate order, and skipping one while doing the other is where the confusion lives.

What Release Scores actually does

By default, students do not automatically see their results the moment they submit — and for most graded work, that’s a feature. Holding scores back lets you finish grading the human-scored questions, check for answer-key problems, and make sure the numbers are final before anyone reacts to them. Release Scores is the moment you lift that curtain.

When you release scores for an assignment:

  • Students can see their score for that assignment when they log in.
  • Depending on your settings, students may also see the detailed view — the questions, their answers, and the correct answers — or just the score itself. That detail level is a separate control (the “show detailed report to students” style setting), and choosing it thoughtfully matters: showing answers is wonderful for a formative quiz students should learn from, and a problem for a test form you plan to reuse with another section tomorrow.
  • Nothing about releasing changes the scores themselves. It’s a visibility switch, not a grading action.

Think of Release Scores as publishing. Everything in the grading workflow before it is drafting; this is the step where results become official as far as students are concerned. If you’ve ever had a student say “I can see my score but my friend can’t,” the answer is almost always that release happened per class or per assignment and one group is still waiting — or that a related detail setting differs, which our companion guide on students can’t see their scores in Pear Assessment untangles fully.

Release scores in Pear Assessment - a teacher releasing finished scores to the whole class

What Mark as Done actually does

Mark as Done is housekeeping for you. It signals that you’ve finished reviewing and grading an assignment — that the work on your side of the desk is complete. Teachers use it to clear finished assignments out of their active grading queue so the “needs attention” pile only ever shows what’s genuinely outstanding: ungraded responses, missing submissions to chase, reviews not yet done.

Crucially, Mark as Done does not release anything to students. Marking an assignment done while scores are unreleased leaves students exactly where they were: unable to see results. And the reverse is equally possible — you can release scores while the assignment still sits in your active list. Neither action implies the other, which is precisely the design decision that confuses people: two independent switches for two independent jobs.

how to release scores to students in pear assessment

The release itself is simple; the professionalism is in the sequence around it. Follow this order for graded assignments:

  1. Finish grading everything. Auto-graded items score instantly, but constructed responses, partial-credit reviews, and any flagged responses need your eyes first. Releasing scores while essays are still ungraded shows students a provisional number that will change — a reliable way to generate email.
  2. Sanity-check the results. Glance at the score distribution and the item analysis. A question everyone missed, or a top student with an implausible score, usually means a key or rubric issue — fix it now, before release, while fixing is quiet. After release, the same fix is a public correction.
  3. Confirm the detail setting. Decide whether students see just their score or the full question-by-question report, per the guidance above.
  4. Release the scores for the class or assignment.
  5. Then Mark as Done, once you’re satisfied nothing remains — no ungraded stragglers, no pending regrades, no student you intended to give feedback to first.

That final order — release, then done — is the habit to build. Release is the last student-facing act; done is the last teacher-facing act. If you mark done first, you risk mentally closing the assignment and forgetting the release entirely, which is how a class ends up asking in week three why the quiz from week one has no score.

Release scores in Pear Assessment - what a student sees the moment scores are released

When to hold scores back on purpose

Not every assignment should release immediately, and some shouldn’t release on the normal rhythm at all:

  • Multi-section tests. If your third period takes the test on Thursday and your fifth period takes it Friday, hold Thursday’s release until Friday’s class finishes — especially if the detailed view shows answers. Early finishers talk; protect the form.
  • Make-up windows. While make-ups are outstanding, partial releases create a two-tier information environment. Many teachers release once the window closes for everyone.
  • Anything with a suspected key problem. If results look off, holding release while you investigate is not delay — it’s diligence. A score released and retracted teaches students to distrust every future score; a score released once, correctly, doesn’t.
  • Benchmarks and district tests. Common assessments often have centrally decided release timing so every school’s students learn results together (and after the window fully closes). If you’re running one, follow the district’s plan rather than your classroom habit — see how this fits the wider cycle in our guide to district benchmarks in Pear Assessment.

What students actually see at each stage

It helps to picture the student’s side of the glass, because most confusion in this area is really a student-view misunderstanding. Before release, a student who opens a submitted assignment sees that their work is in — submitted, awaiting results — but not how they did. There is no score to find, no answers to review, no partial peek. This is why “I submitted it but there’s no grade” is not a bug report; it’s the system working as designed until you act.

The moment you release, that same view transforms: the score appears, and if your detail setting allows it, the student can open the full report — each question, their response, the correct answer, and your feedback where you’ve left it. Students experience release as a single event, which is why timing it after all grading is finished matters so much. A score that appears Tuesday and silently changes Wednesday (because the essays were graded overnight) reads to a student as either carelessness or favoritism, depending on the direction of the change. Neither impression is fair to you — and both are avoidable with one disciplined release, done once, after everything is final.

Parents, incidentally, mostly experience your release decisions secondhand, through whatever the student reports at home. A clear classroom routine — “scores post Friday after I’ve graded the written section; you’ll see the full report with my comments” — sets expectations that travel home accurately. Half the confused emails teachers get about “missing grades” are really about an unstated release rhythm; state yours, and they largely stop.

One more student-view nuance: release applies to an assignment as a whole. Students who submitted late, or whose work you’re still grading individually, are part of the same picture — another reason make-up and straggler grading should finish before the release moment rather than trail behind it.

Release scores in Pear Assessment - adding written feedback before students see their grades

The feedback order that works best

There’s one more sequencing question teachers ask: feedback before or after scores? Research and classroom experience agree on the practical answer — when students see a score and comments simultaneously, most read the score and skim the comments. If you’ve written substantive feedback on written work, consider releasing with a plan: tell students the feedback is there and give the first two minutes of class to reading it, or stage the release so comments get a moment of attention before the number becomes the whole conversation. The platform’s controls — release timing plus the detailed-report setting — give you the levers; how you use them is pedagogy, and it’s worth deciding deliberately rather than by default.

Underneath all of this sits the Live Class Board in Pear Assessment, where much of the review-and-release workflow happens while a class is active — worth knowing if you tend to grade and release in the same sitting.

For the authoritative rundown of grading and release options, the official Pear Assessment documentation reflects the current interface.

Frequently asked questions

I marked an assignment as done, but students say they can’t see scores. Why?
Because Mark as Done doesn’t release anything — it only closes your grading task. You still need to release the scores for students to see them.

Can I release scores for one class and not another?
Release is handled per assignment/class context, so yes — teachers with multiple sections routinely release on different schedules, especially around make-up windows.

If I release scores, then fix an answer key, do students see the corrected score?
Once the regrade lands, the updated score is what students see. Tell the class a correction happened and why — transparency here builds trust rather than confusion.

What’s the best routine for a weekly quiz?
Consistency beats ceremony for low-stakes work. Grade the same day where you can, run the two-minute sanity check, release with the detailed view on (weekly quizzes are learning tools, and students should see what they missed), then mark done and move on. When the rhythm is predictable, students stop asking when scores post — they already know — and your grading queue stays at zero instead of becoming a weekend project.

Can I un-release scores after releasing them?
Treat release as the point of no return for planning purposes: students may have already seen and discussed their results. That’s why the checklist order — grade fully, check, then release — matters.

Release scores in Pear Assessment - release scores versus mark as done compared side by side

The bottom line

Release Scores controls what students see; Mark as Done controls what remains on your plate. They’re independent on purpose — one publishes results to the class, the other clears your own desk, and neither substitutes for the other no matter how similar the buttons look side by side at the end of a long grading session. Do your grading completely, sanity-check the results, choose the right level of detail, release the scores — and only then mark the assignment done. Two buttons, one order, and a class that always knows when and where its results will appear — which adds up to zero “why can’t I see my grade?” emails, all year long.

Leave a Comment

Your email address will not be published. Required fields are marked *


Math Captcha
96 − = 86


Scroll to Top