Tally Counter for Classrooms

Two modes, one common pattern

Single mode is the classic mechanical tally — one big number, +/− buttons, reset. Multi-counter mode is the same logic per label: paste your label list (one per line) and the page renders one counter per label in a grid. Both modes save automatically; close the tab and the counts are still there tomorrow.

Classroom uses

• Participation tallies— One + per substantive student contribution during whole-class discussion. At the end of class, you have an honest count for grading or for the "who hasn't spoken yet" question. Pair with the name picker to randomly extend the count to lower-participation students.
• Behaviour data for an IEP or 504— Multi-counter mode with one label per target behaviour (e.g., "Hand raised", "Out of seat", "Self-redirect"). The tally produces frequency-per-period data for IEP meetings and progress reports.
• Quick votes — Multi-counter with labels Yes / No / Maybe (or Agree / Disagree / Unsure). Tap as students raise hands. A 30-second classroom poll without an app or extension.
• Quiz wrong-answer tracking — Multi-counter with one label per question (Q1, Q2, …, Q10). As you grade, tap the question label every time you see a wrong answer. The highest tallies tell you which questions need re-teaching tomorrow.
• Attempt counting — Single mode for things students do many of (free throws, math fact attempts, fluency reads). The large readout works on a phone in your hand while you walk the room.
• Token economy — Multi-counter with one label per student (or per table). Award tokens visibly; cash out at end of period. The persistent storage means tokens carry across the period without resetting on reload.

Why "saves automatically" matters

Most browser-based tally counters lose state on reload, which is fine for one-off tally sessions but useless for in-period running totals. This counter writes to local storage after every tap, so:

• A tab that crashes mid-period doesn't cost you the morning's data.
• You can step away from the laptop, do something else, and come back to the same counter state.
• Across multiple sessions of the same activity (e.g., week-long behaviour-tracking experiment), the counter persists as long as you don't reset.

Phone-first design

The +/− buttons are sized for thumb taps and the readout scales down cleanly to phone screens. Practical use: open the page on your phone before class starts, log the URL, walk the room while tallying, and when you return to your desk, the same state is on the desktop too — as long as you're on the same browser profile. (Cross-device sync isn't supported because nothing is uploaded; the tally is local to each device.)

What this isn't

It's not a behaviour-management system like ClassDojo — there are no student-facing profiles, no parent-facing reports, no gamification. Use this when you want a simple, fast, private, signup-free tally counter and you'll record the data elsewhere. If you want full behaviour-management infrastructure, you'll outgrow this tool quickly.