Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the K–12 edition of September 6, 2026

Standards or public-body guidanceCautionaryRecent

Stanford tutoring brief distinguishes educator assistance from unsupervised student AI

SCALE Initiative and National Student Support Accelerator, Stanford University · K–12 primary and secondary education · United States guidance drawing on US and international research

Publisher
AI Tutoring is Not a Monolith: What We Actually Know
Original publication
August 20, 2026
Source retrieved
2026-09-07
Read original source

What happened

The brief distinguishes human-led AI-assisted tutoring from AI-led and AI-only models, arguing that evidence becomes thinner as sustained human involvement falls.

Why it matters

Relevant to fall district purchasing and tutoring program design. August publication is new to the checked archive, not a September event.

Evidence and measured results

Synthesis of tutoring research plus interviews with providers, developers and researchers; no new pooled effect estimate or representative interview sampling frame is reported.

Limitations and uncertainty

Practice guidance, not product certification or a new causal evaluation. Provider interview contributions are disclosed. One link attached to a two-trial claim opened a different UK study; this edition does not repeat that numerical claim.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-07; this does not change the original publication date. Labels below come from the analysis itself.

Sales

Role takeaway

District tutoring leaders, intervention teams, finance and family representatives need comparable descriptions of proposed services. Ask who maintains the student relationship, who notices disengagement, and what evidence matches the exact delivery model. Offer an options assessment distinguishing tutor assistance from direct student automation. The value hypothesis is avoiding a mismatch between a purchased service and the district's intended intervention. Do not transfer human-tutoring effect sizes to software or claim Stanford endorses a vendor. A short evidence review can identify a bounded pilot, but this guidance alone cannot establish educational return or local staffing capacity.

Pre-sales engineering

Role takeaway

Translate each tutoring model into a data-flow diagram with the human decision points visible. Reuse existing learning and identity systems where appropriate, with limited transcript access and a tested help route. Prerequisites include defined student groups, available adult support and usable curriculum materials. Validate the whole interaction: login, approved practice, disengagement detection, human handoff and deletion. A proof of value should measure participation and independent performance separately, including learners using accommodations. The brief does not establish a preferred model provider, hosting topology or infrastructure capacity; those require product documentation and local testing.

Delivery

Role takeaway

The intervention lead should own a pilot plan with teachers, tutors, privacy and accessibility staff. Identify who monitors attendance, contacts students and handles distress or inappropriate output. Train staff on those responsibilities before student access, and communicate the limits of AI assistance to families in accessible language.

Proposed acceptance
sampled students reach an empowered adult through the published route, transcript controls pass agreed tests, and independent outcome reporting accompanies usage data. Review staffing and equity findings before expanding. Risks include treating supervision as nominal, underfunding follow-up and allowing attractive engagement metrics to displace the learning objective.

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Classify who sees and approves AI output, then configure permissions and intervention routes for that workflow.

Governance

Who approves, reviews and stays accountable for outcomes?

Require buyers to name which parts of human tutoring a proposed service preserves or changes.

Security and privacy

What data, permissions and controls need testing?

Execute and verify data-use terms before student access; test transcript export and deletion and define who can inspect conversations.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Preserve accessible human help and test whether a student can summon it without relying on sophisticated self-advocacy.

Procurement

What should contracts, pricing and exit terms secure?

Compare services by evidence for their actual delivery model, not the generic label AI tutoring.

Operating model

Which teams own the service once it runs?

Assign attendance, engagement and escalation owners and include supervision costs in the service plan.

What changed

Not an archive repeat. Newly discovered source adds implementation or evidence-quality context for the 2026–27 school-year review; publication timing is stated separately.

Publication history

  1. 2026-09-06K–12 · Issue 014 resources
Read preserved resource versions (JSON)

Stable resource ID: stanford-ai-tutoring-spectrum-2026