12 Questions to Ask Before Buying Observation Software
Updated
The questions that surface problems before a contract, not after — each with what a good answer sounds like and what should worry you.
In short
Twelve questions covering workflow, rubric fidelity, data ownership, and renewal. Each one has a good answer and a warning sign — the warning signs are the useful part, because vendors rarely volunteer them.
Ask these twelve questions in the first demo, not the last. They cover the four areas where observation software deployments actually fail: workflow fit, rubric fidelity, data and procurement, and what happens at renewal. Each has a good answer and a warning sign.
Most buying guides list features to look for. That is the wrong instrument, because every vendor will say yes to a feature question. These are phrased so that a vague answer is itself informative.
Questions about workflow
The goal here is to find the handoffs — the moments where an observation leaves the tool and has to come back. Handoffs are where observations stall for a week.
| Ask | Good answer | Warning sign |
|---|---|---|
| Can you show me one complete observation, start to finish, in real time? | They do it, in one sitting, without switching tools | "Let me show you the modules instead" |
| How many clicks from opening the app to the teacher receiving feedback? | They know, or count it live with you | The number is unknown, or the demo skips the sending step |
| What does this look like on a phone in the back of a classroom? | A live demo on a phone | A tablet screenshot and a promise about the roadmap |
| What happens if the observer loses connection mid-observation? | Work is retained locally and syncs later | Uncertainty, or an answer about how reliable school wifi usually is |
Questions about your rubric
You are testing whether your district's language survives contact with the product, or whether observers will have to translate on the fly.
| Ask | Good answer | Warning sign |
|---|---|---|
| Can you build one of my domains, with my criteria, right now? | They do it live and it takes minutes | "Our implementation team handles that during onboarding" |
| Can I change scoring levels and their labels? | Yes, configured by us, without a support ticket | Fixed 1–4 scale, vendor language only |
| Can I run different forms for walkthroughs and formal observations? | Yes, and both feed the same record for a teacher | One form type, or two systems that do not talk |
| What happens when we revise our rubric next year? | We edit it ourselves; historical scores stay tied to the old version | A paid change request, or historical data silently re-mapped |
Questions about data and procurement
These decide whether the contract clears legal review. Ask them early — a tool that fails here in March has wasted a whole evaluation cycle.
| Ask | Good answer | Warning sign |
|---|---|---|
| Do you have a school data protection addendum we can review today? | They send an existing one immediately | It has to be drafted, or their standard MSA is offered instead |
| Who owns the observation data, and what do we get back if we leave? | You own it; full export in a usable format, on request | Export is PDF-only, chargeable, or unmentioned in the contract |
| Can a department head see only their own team's observations? | Role-based access demonstrated live | Everyone with a login sees everything |
| How long is data retained, and can we set that? | Configurable, and they ask what your evaluation agreement requires | Indefinite by default with no control |
Voxento publishes a school data protection addendum and a security page for exactly this reason, including which certifications it does and does not hold. These should be documents you can read before a call, not artifacts of a negotiation.
Questions about cost and renewal
Model the total at real headcount over three years. The headline number is almost never what a district ends up paying.
- Is the quoted rate introductory, and what is the standard rate at renewal?
- Does pricing change if we add coaches or department heads as observers?
- Are implementation, training, and support billed separately?
- What is the cost at full district headcount, not pilot size?
Per-teacher and per-observer pricing scale very differently once a pilot becomes a district rollout. Per-observer pricing in particular creates a quiet disincentive to add the coaches and department heads you probably want observing. Flat pricing avoids that — Voxento's schools plan includes unlimited users for this reason.
What is the one question people skip?
"Which districts stopped using you, and why?" Vendors expect reference customers. Almost nobody asks about churn.
A vendor who answers this honestly — naming a real reason, like a district consolidating systems or outgrowing the tool — is telling you they have nothing to hide. A vendor who claims no district has ever left is either very new or not being straight with you, and both are worth knowing.
For the weighted scorecard to use alongside these questions, see how to choose teacher observation software. If your framework decision is still open, the Danielson, Marzano and CLASS comparison covers that first.
Frequently asked questions
- Who should be in the room for a vendor demo?
- At least one person who will actually conduct observations, not only administrators making the purchase. The observer will spot workflow problems that a buyer will not.
- How many vendors should we compare?
- Three is usually enough. More than that and demos blur together, and the decision drifts toward whoever presented most recently rather than whoever fits best.
- Should we ask for a free pilot?
- Yes, and run it with sceptical, time-poor observers rather than enthusiastic ones. A pilot that only proves early adopters will use it has not told you anything about adoption.
- What if legal review is the bottleneck in our district?
- Start it in parallel with the instructional evaluation, not after. Ask for the data protection addendum in the first conversation so review can begin while demos are still happening.
Written by
Muhammad Amin — Co-founder, Voxento
I co-founded Voxento and build the platform. I work directly with the schools and training teams running observations and AI roleplay on it, which is where most of what I write here comes from.
Related reading
- How to Choose Teacher Observation Software in 2026
Score tools on workflow fit, rubric fidelity, follow-up speed and procurement readiness — in that order. Includes a weighted scorecard for demos.
- Classroom Observation: A Guide for School Leaders
What classroom observation is, which type answers which question, and how many observers a rating needs before it means anything. With a coverage plan.
- What Is Observation Studio? A Simple Guide for School Leaders
The workspace where an observation runs end to end: pick a structure, capture evidence, score, and share next steps — without handoffs between tools.
Put these ideas into practice with Voxento.
See how observations, evaluations, coaching, and walkthroughs work in one workspace.