Free school evaluation tool
School Device Management Pilot Evaluation Scorecard
Evaluate the workflows your school needs before a wider rollout. Record what you actually tested, what happened and who owns the next action. This scorecard does not configure devices, approve a pilot or certify compliance.
School buyer acceptance workflow · Reviewed 13 October 2026
Which lesson must work before a school pilot can pass?
Evaluate the lesson that must work, not just the number of websites a rule can block. Agree the essential learning, restriction, support and recovery requirements before a pilot. Record classroom governance, web filtering and device management as separate layers; this scorecard does not certify compliance or promise to replace the school’s existing filter.
- Write the lesson task: Include sign-in, embedded material, submission and required accessibility tools. A homepage opening is not a complete lesson test.
- Identify the rule owner: Record the school administrator’s authority, group and review route. A teacher’s request or a parent receiving a report does not itself authorize changing every restriction.
- Test the narrow exception: If the task fails, document the supporting resource and request an approved scoped change. Retest the lesson and the intended restriction separately.
- Record effort and limits: Separate school setup/diagnosis time from vendor help; record platform, version, test conditions, support contact and reversal plan.
- Make the acceptance decision: A failed or untested essential requirement prevents a broader rollout decision. Set an owner and retest date rather than averaging the issue away.
These are proposed acceptance steps, not reported school results. Treat network conditions, off-campus behavior and native-app controls as separate tests where they are required. Do not infer them from a browser demonstration.
Entries stay in this page until it is closed or refreshed. They are not submitted or saved. Use a non-identifying pilot reference. Print your completed record or download the blank CSV; do not enter passwords, employee or student names, or sensitive browsing records.
Requirements and observed evidence
Agree what is essential before testing. Mark each result Pass, Fail or Not tested. Record the actual task, platform, version, time and observed outcome. A saved setting or vendor claim is not a device test. A desirable feature cannot compensate for a failed or untested essential requirement.
| Requirement | Priority | Result | Evidence / conditions | Owner / next action |
|---|---|---|---|---|
| Enrollment Devices registered in the correct organization and groups; record platform and version. | ||||
| Coverage List tested platforms, browsers and controls; mark untested network or off-campus conditions separately. | ||||
| Learning access Complete the actual lesson, including sign-in, embedded resources and required accessibility tools. | ||||
| Restriction Verify the agreed rule on the intended enrolled device; a dashboard setting alone is insufficient. | ||||
| Exceptions Identify the authorized owner, apply a permitted narrow exception where supported and retest the full lesson. | ||||
| Visibility Identify current activity, attribution and unresolved coverage; do not equate missing records with inactivity. | ||||
| Privacy review Record the actual school reviewer, roles, parent-report authority and unresolved data/access questions. | ||||
| Administrative effort Measure school setup and diagnosis time separately from vendor help; include ongoing support effort. | ||||
| Support and rollback Confirm a named support route and approved reversal process, including required learning access after the change. |
Continue, revise or stop
- Continue: Every essential requirement has acceptable observed evidence, and the responsible owner accepts the recorded limits.
- Revise: An issue has a named owner, a feasible retest and a review date. Keep the rollout within the tested scope.
- Stop: Required access, authority or recovery remains unresolved. Follow the approved reversal process; do not expand an unverified deployment.
Prepare a focused school evaluation
Bring your device mix, deployment permissions and unanswered questions to a compatibility discussion. A self-service trial and an approved supported pilot can have different terms. Availability and scope are confirmed individually; booking a call does not reserve a place.