Rewind a Mistaken Behavior Event Without Erasing the Session

A fast classroom can produce a fast mistake. A teacher may tap the wrong behavior category, choose the wrong learner, or notice that the point value does not match what happened. ClassSpark lets the teacher rewind that specific behavior event from the student card instead of abandoning the lesson or rebuilding the session. The important habit is to identify the exact history row, read its sign and timestamp, and remove only that record.

Open the student’s points history

Open the correct class, choose the affected student card, and use the RotateCcw action labelled Undo points. The dialog reads the newest 50 class-wide point records available for that student and active curriculum. Behavior entries show the category or title, whether the event was positive, its date and time, and a signed point value. The same list can also contain formative standard scores, so do not assume every row follows the behavior removal route.

Open the student’s points history.

Remove the event that owns the mistake

Match the visible row to the classroom moment before pressing Remove. A behavior point routes to the scoped behavior-incidents deletion path. An activity-owned standard score and a live standard score use their own Gradebook clear operations. Homework- or evidence-owned scores remain visible but are not removable here because their source workflow owns them. Game participation points from the supplemental points stream are a known gap and do not appear in this dialog.

Remove the event that owns the mistake.

Confirm the correction without erasing the session

After a successful behavior removal, ClassSpark reloads the authoritative roster so the displayed total reflects the remaining records. The action removes the selected event; it does not erase the active session, attendance, notes, other learners’ points, or unrelated history. If the request fails, treat the unchanged authoritative total as the result and investigate before trying again. A visual spinner or click is not proof that the record disappeared.

1. Confirm the active class and affected learner.
2. Open Undo points from the student card.
3. Check the category, signed value, date, and time.
4. Remove only the matching behavior row.
5. Wait for the roster total to reload.
6. Reopen history and confirm the row is gone.

Practical checks before removal

Correct a factual input error, not a fair consequence simply because a learner dislikes it. Use the timestamp when two behavior events have similar labels or point values. Explain the correction briefly when the learner already saw the original total. Avoid deleting nearby events while searching for the mistaken row. Remember that negative events may already have entered a configured notification workflow. Do not promise that administrator analytics will update in a particular way. If a score belongs to homework or evidence, correct it in its source workflow. Shared score pools may show another teacher’s locked entry without offering removal. A recording-teacher boundary protects standard-score corrections from unauthorized changes. The five-minute Gradebook Undo ledger applies to supported standard clear operations.

Rewind a Mistaken Behavior Event Without Erasing the Session