The phrase usually arrives with a spreadsheet and a meeting. By the second data meeting, many teachers have learned the wrong lesson, which is that data is something that gets collected for other people. The useful version is much smaller. It answers one question you already have on Sunday evening: what do I do differently on Monday because of what students showed me?
A routine that survives a real week
- Look at one thing. One quiz, one practice set, one exit question. Not everything.
- Sort it by skill, not by student. Which skill did most students miss? Which did only a few?
- Make three decisions. What gets reteached to the whole class, who gets a small group, and who needs a one-to-one check.
- Write down what you expect. "By Thursday most of them should get problem 4." This is the step that makes it a loop.
- Check on Thursday. Did it move? If not, change the approach, not the volume.
That takes ten or fifteen minutes when the data is already sorted by skill, and a lot longer when it is not. The sorting is where most of the time goes.
Know what your data can and cannot say
- A score says how a student did on a task. It does not say why.
- A low score on a long quiz might be one weak skill and four strong ones, or the reverse.
- Multiple choice shows recognition well. It shows reasoning and written explanation less well.
- One data point is a prompt for a question, not a conclusion.
Pair numbers with a minute of listening. Ask a student why they chose an answer. The two together are worth far more than either alone.
What ClassSense gives you
The data arrives already sorted by skill, which is the expensive step. Every practice answer updates mastery for that student on that skill, and the Students tab shows the whole class as a grid, one row per student and one column per skill, coloured by state: Struggling, Developing, Approaching or Mastered. Mastery needs at least five answers at about 85%, so a single lucky guess does not turn a cell green. Click a student for every skill and their recent activity.
Your dashboard answers "what needs me today" in four cards: students who need you (with the skill, and often a line such as a question they keep missing or hints used), skill packs to review, parent messages and what was mastered this week. Mastered skills come back later for a quick check, so you see whether something stuck. That makes steps 1 and 2 of the routine nearly free, and leaves you the decisions. The guide to reading mastery data and the mastery tracking page go deeper.
You can override. If you know a cell is wrong, use Override and give a reason. The data is evidence you weigh, not a verdict.
Limits worth knowing. The grid reflects only practice students have done in ClassSense. It does not import grades from elsewhere and it is not a gradebook. It cannot see paper work, discussion or effort, and a quiet student can look better or worse than they are. It describes what happened in the practice, not what a student can do with an open-ended task. Treat it as one input next to your own.
The risk to watch
More data does not mean better teaching. If you find yourself checking the grid more than you teach from it, cut something. The goal of the routine is a decision for Monday, not a report.
See formative assessment for the idea behind this, and small-group instruction for what to do with the groups you decide on.
Common questions
What data does ClassSense actually collect?
Student answers in practice and games, with correctness, hints used and attempts, rolled up into mastery per skill. It does not import grades from other systems.
Is it a gradebook?
No. It tracks mastery of skills from practice. Official grades are transferred by hand.
Can I export student data?
Data export and deletion are available on request. See the data practices page for the details.
How do I avoid spending all evening on the dashboard?
Decide the question first. Look for the weakest skill, the students who need you today, and stop. Ten focused minutes beats an hour of scrolling.