Procurement without guesswork
Evaluate the product before your school depends on it.
This center separates verifiable product behavior from claims that still require a contract, security review, or real school pilot. It is designed to help technology leaders make a defensible decision.
Plain-language commitment: Classroom Guardian does not claim customers, certifications, independent audits, response guarantees, or accuracy percentages that have not been publicly verified.
Evidence available now
Controls you can inspect during a pilot.
These statements describe current product behavior. Schools should confirm configuration, performance, and contract terms in their own environment.
Role and school boundaries
Teacher, school, district, and platform routes enforce role and organization checks. Teachers are limited to assigned classes; school records remain school-scoped.
Verify with separate test rolesExplainable policy priority
Explicit school allow rules take priority, followed by explicit blocks, classroom rules, managed catalogs, and automated signals.
Verify with conflicting test rulesConservative unknown-site handling
Unknown websites remain reviewable. Automated uncertainty does not silently publish a global category decision or block an unknown site by itself.
Verify with uncategorized domainsTargeted classroom screens
Live frames are requested for authorized, active teacher viewing and are intended to remain ephemeral unless recording is explicitly enabled and started.
Verify viewer start, stop, and expiryServer-enforced plan access
Plan entitlements change both visible controls and API authorization. A hidden button is not treated as the security boundary.
Verify denied API accessFail-open filtering behavior
When the policy service cannot be reached, the extension is designed to stop imposing stale automated blocks so unrelated academic access is not silently disrupted.
Verify in a controlled outage testHuman writing review
Essay Detection can abstain and presents probabilistic evidence rather than a misconduct verdict. Teachers retain responsibility for academic decisions.
Verify with known and ambiguous samplesVisible service operations
Component status, recent availability, response times, incidents, and updates are published instead of being represented by a static uptime badge.
Inspect the live status pageAuditable safety review
The Safety Center combines teacher reports, student reports, and deduplicated sensitive browser signals with assignment, status transitions, resolution notes, and an event history.
Verify role scope and every transitionDeployment fit
Know the tradeoffs before the trial starts.
No platform is the right default for every district. Use this fit check before investing staff time.
- Managed Chrome or Edge is the primary student browser on ChromeOS, Windows, or macOS.
- Your team wants explicit school rules to outrank automation.
- Teachers need live visibility, timed scenes, tab limits, assessment mode, and access requests in one workflow.
- You value public list pricing and a no-payment pilot.
- You want essay signals to support teacher judgment rather than replace it.
- You require native system-wide Windows or macOS filtering, iOS coverage, full MDM, or a network appliance rather than managed-browser enforcement.
- Procurement requires a specific independent certification or audit report.
- You require a contractually defined 24/7 response time or uptime commitment.
- You need an independently validated large-district reference.
- Your safety program requires an external 24/7 human-monitoring or emergency-response service rather than a school-operated review queue.
30-day evaluation
Turn the free pilot into evidence your team can use.
Set the pass criteria before deployment. The same scorecard can be used for Classroom Guardian and competing products.
- Before day 1Define the decision
Choose student groups, teacher roles, required workflows, privacy reviewers, comparison products, and school-owned pass thresholds.
- Days 1-7Prove deployment and policy
Measure extension coverage, identity mapping, rule precedence, permitted academic resources, unknown-site behavior, and outage handling.
- Days 8-18Run real classroom workflows
Test live screens, class scenes, tab limits, messages, assessment mode, access requests, and teacher learning time.
- Days 19-25Review evidence quality
Compare category recommendations and essay results with staff review. Record false positives, abstentions, overrides, and decision time.
- Days 26-30Make the go/no-go decision
Review service health, support experience, privacy findings, total annual cost, unresolved risks, and staff willingness to use the platform.
Suggested scorecard
Use school-owned thresholds, not vendor-selected success.
Data and responsibility
Understand what is handled, why, and who decides.
This summary supports review but does not replace the Privacy Policy or a signed school agreement.
Schools remain responsible for legal authority, required notices or consent, student supervision, safeguarding, account security, and appropriate human review. Classroom Guardian remains responsible for the service commitments it accepts in public policies and signed agreements.
Vendor-neutral review
Ask every filtering vendor the same questions.
Which controls are independently assessed? What evidence can procurement review? What is excluded from the assessment?
What happens when policy, screen, identity, or command services are unreachable? Which commitments are contractual?
Which student data is stored, where, for how long, by which subprocessors, and under whose deletion instructions?
How are false positives, false negatives, uncertainty, human overrides, and model changes measured and communicated?
Who answers during deployment and incidents? What response times, escalation paths, and training are included in the quote?
Which modules, staff accounts, devices, services, onboarding fees, renewals, and minimum terms are included?
Procurement resources
