wubbery://learn/schools — WUBBERY LEARN for schools & districts
Students get help from their own teacher's guidance at home — scoped to the current unit, fully logged, and reviewed by the people accountable for it. Built for procurement from day one, not retrofitted for it.
Curriculum-scoped. Teacher-and-school-set boundaries. Full transcript visibility for staff.
Built for review, not just for launch
CONTROL 01
Every companion is limited to the unit and subject the teacher is currently teaching. There is no open-ended chat mode and no access to topics outside the assigned curriculum.
CONTROL 02
Every session is logged and visible to the teacher and to school administration. Nothing a student does with the companion is hidden from staff.
CONTROL 03
Scope, tone, and permitted topics are configured by the teacher and approved by the school — never left to a parent or student to loosen.
CONTROL 04
Administrators get a rollup view across classrooms: what's enabled, who approved it, and usage at a glance — built for the person who has to answer for it at a board meeting.
CONTROL 05
Student data stays inside the access and retention terms your district already has in place. No new data-sharing relationship, no surprise third party.
CONTROL 06
Data-handling summary, scope-of-use description, and a named contact for IT and legal review — ready before procurement asks, not assembled after.
Extends the teacher — never replaces them
Extends, never replaces
“Extends” is the operative word in every agreement, every onboarding screen, and every piece of documentation your district receives. The companion has no path to grading, no path to standing in for the teacher in any formal sense, and no scope beyond what that teacher has explicitly configured.
Rollout, on your terms
STEP 01
Start narrow — one teacher, one class, one unit — so staff can see exactly what the companion does and doesn't do before any wider rollout decision is made.
STEP 02
We walk your team through scope, logging, retention, and access controls directly, and answer procurement questions in writing.
STEP 03
Adoption stays teacher-led, one classroom at a time. No district-wide switch gets flipped without staff and administration signing off first.
Questions from procurement and IT
No. WUBBERY LEARN extends a teacher's presence to homework time at home — it never replaces the teacher, never issues grades, and never makes instructional decisions. The teacher remains the sole source of instruction and assessment.
The teacher, within limits your school sets. Every companion is scoped to the current unit and subject area. There is no setting that lets a parent or student expand that scope, and no general-purpose chat mode.
It is built to explain and ask guiding questions in the way that teacher already teaches, not to hand over finished answers. Every session is fully visible to the teacher, so usage patterns are never hidden from the classroom.
Session transcripts are visible to the teacher and to school administration and are handled under your district's existing data agreements and retention rules. We do not introduce a new third-party data relationship your legal team hasn't reviewed.
A generic AI tutor has no relationship with the student and no accountability to your school. This is built from an actual, employed teacher's guidance, scoped by that teacher and your administration, and fully auditable by staff — closer to a governed extension of the classroom than a consumer chat product.
One willing teacher, sign-off from whoever owns student-privacy review at your school or district, and a defined subject/unit to scope the pilot to. We'll bring the data-handling summary and scope documentation to that conversation.
We'll walk your IT lead, privacy officer, and pilot teacher through scope, data handling, and rollout together — and leave you with documentation, not just a demo.
