Answers to the questions we hear most

RollCall gives school owners, principals and administrators a single view of what is happening across their school day: teacher attendance and punctuality, lesson delivery and note submission, assessment submission, substitute coverage, leave, and queries. Instead of relying on verbal reports, management can see operational reality as it happens.

No. RollCall tracks operational events — clock-ins, lesson submissions, assessment deadlines — not personal behaviour. It does not use cameras, audio recording or location tracking outside of the school compliance workflow it is built for. The goal is operational visibility and accountability, not monitoring individuals.

Each branch has a fixed kiosk display showing a QR code that rotates periodically. Teachers open the RollCall app and scan the code when they arrive. The scan is validated by the server, which checks the code's validity window before recording attendance and calculating status (on time, late).

No. RollCall does not require GPS location tracking, facial recognition, or selfie verification for attendance. Attendance is confirmed through the rotating QR code and server-side validation, which keeps the process fast, private and difficult to spoof.

Administrators can record attendance manually from the management dashboard, with the exception logged and visible in the Exception Center so patterns can be reviewed over time.

RollCall compares each teacher's timetable against actual lesson submissions. When a lesson period ends, the assigned teacher is expected to submit lesson notes (and photo evidence where required) within a set window. Missed or late submissions appear as exceptions for administrators to follow up on.

Each school sets its own submission deadline relative to the end of a lesson period. Submissions made after that window are flagged as late; submissions never made are flagged as missing. Both are visible in reports and compliance scoring.

Yes. Administrators can define assessments by class, subject, teacher and deadline. RollCall then tracks submission status for each assessment, distinguishing on-time, late and missing submissions.

When a leave request is approved for a given period, RollCall excludes that period from a teacher's attendance and lesson compliance calculations, so approved absence is not counted against them. Unapproved absence continues to appear as an exception.

When a compliance event needs a formal response (for example, repeated late lesson submissions), management can issue a query directly from the relevant record. The teacher acknowledges it, responds with context, and management reviews the response before closing the query. The full history is retained.

No. Compliance in RollCall is an operational metric — attendance, punctuality, lesson submission and assessment submission rates. It says nothing about the quality of a teacher's instruction and should never be treated as a substitute for pedagogical evaluation.

Yes. From the Professional plan up, RollCall provides a consolidated multi-branch dashboard so school owners and group administrators can compare attendance, compliance and exceptions across every campus from one place.

Access is role-based. School owners and administrators typically see school-wide or group-wide data; principals see their branch; teachers see their own attendance, timetable and submissions. Permissions are configurable per school.

RollCall is built around role-based access control, secure authentication, tenant isolation between schools, and audit trails for compliance-relevant actions. See the Security page for a full explanation of our approach.

Pricing depends on the number of teachers, branches and admin users, along with which modules a school needs. Our team will work out the right plan on a call — see the Pricing page for the plan structure.