When a number is attached to a teacher's name, it is tempting to read it as a verdict. A compliance score resists that reading if it's built correctly, because it only ever measures a small, specific set of operational events: did attendance happen on time, were lessons submitted on schedule, were assessments submitted by their deadline.
None of those inputs say anything about how well a lesson was taught, how engaged students were, or how a teacher handled a difficult classroom moment. A teacher can be an excellent educator and have a lower compliance score during a term with genuine scheduling disruption. A teacher can have a perfect compliance score and still need pedagogical support. The two measurements are answering different questions.
The useful way to read a compliance score is as a starting point for a conversation, not the end of one. A dip in lesson-note submission might point to an unclear deadline, a timetable clash, or a genuine performance issue — the score tells you where to look, not what you'll find.
This is why RollCall treats compliance as an operational metric, displayed alongside context — trends over time, related exceptions, approved leave — rather than as a single number presented in isolation. Administrators are meant to investigate what a score is telling them, not act on the number alone.