Skip to content
RollCall by Breej
← All ResourcesSchool Operations

The Professional Case for a Formal Query Process

8 March 20265 min readRollCall Editorial

Most schools already raise concerns with teachers when something needs addressing — a pattern of lateness, a string of missed submissions. What's often missing is a consistent process: a record of what was raised, when, how the teacher responded, and how it was resolved.

Without that structure, two problems tend to appear. Teachers can reasonably feel that concerns are raised inconsistently, informally, or without a chance to respond. And administrators lose the ability to show, later, that a pattern was addressed appropriately and in good time.

A formal query process fixes both. It ties a query to the specific compliance event that prompted it, requires the teacher to acknowledge and respond, and keeps a record through to resolution. That record protects the teacher's right to respond as much as it protects the school's ability to demonstrate due process.

RollCall's query workflow follows exactly that sequence — issue, acknowledge, respond, review, close — with the full history attached to the relevant record, so neither side has to rely on memory of what was said in a hallway conversation.

See how RollCall applies this in practice

Book a short walkthrough to see the workflows behind this article, built for a school like yours.

Book a Demo