From the K–12 edition of October 19, 2026
Issaquah School District introduces grade-banded student AI: no core AI for K–5, Securly AI Chat for 6–12, Copilot set to Study and Learn for high school
Issaquah School District 411 · K-12 district student AI tool rollout and access control · Issaquah, Washington, United States
- Publisher
- Issaquah School District
- Original publication
- October 19, 2026 (district announcement)
- Source retrieved
- 2026-10-20
What happened
Beginning this fall, Issaquah is introducing district-supported AI tools for grades 6–12, selected for privacy, safety, age appropriateness and educational value. K–5 students have no access to core AI platforms and restricted access to others on district devices and network. Middle and high school students use Securly AI Chat; Securly also filters internet access and supports classroom screen monitoring. High school students also get Microsoft Copilot configured to default to Study and Learn. Teachers may use Colleague AI's Classroom feature (University of Washington National R&D Center of AI in Classroom Instruction) and decide when and how AI is used. AI literacy is taught in grades 6 and 9; a Tech Advisory committee will gather stakeholder input.
Why it matters
A concrete district configuration that ties student AI access to grade bands, a filtering and monitoring vendor, and a default study mode.
Evidence and measured results
District announcement; no outcome data, contract terms, cost or data-flow detail.
Limitations and uncertainty
Self-description by the district; no measured results. Specific product behavior (e.g., Study and Learn defaults) not independently verified.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A district rolling out monitored student AI by grade band must show families what is collected and that settings match policy.
- Stakeholders
- Educational technology director
- Privacy officer
- Principals
- Tech Advisory committee
- Families
- Discovery questions
- What does your monitoring vendor log from student AI chats, and for how long?
- Who can review student conversations?
- Can students change the default AI mode?
- How do you verify settings after vendor updates?
- Value hypothesis
- Documented, auditable grade-band configuration could build family trust and reduce surprise exposure; not measured here.
- Potential engagement
- A four-week student AI configuration and data-flow audit across grade bands, with a public summary.
- Unsupported claims
- No learning outcomes reported.
- Monitoring scope not disclosed.
- Product defaults not independently verified.
Pre-sales engineering
Role takeaway
- Fit
- Fits districts using filtering or monitoring vendors that also provide student AI chat.
- Architecture and integration
- Enforce grade-band access through device management, filtering policy and identity groups; record default modes per tool.
- Prerequisites
- Device management by grade group
- Vendor admin access
- Published policy per grade band
- Constraints
- Washington State student privacy requirements
- Vendor feature changes
- Teacher discretion within bands
- Security
- Minimize retention of student AI conversations and restrict reviewer access to defined roles.
- Proof of value
- Configuration baseline per grade band
- Retention settings documented
- Post-update configuration check passes
Delivery
Role takeaway
- Work
- Publish and maintain an auditable grade-band configuration for student AI tools.
- Dependencies
- Vendor cooperation on logging detail
- Privacy officer review
- Advisory committee schedule
- Ownership
- Educational technology department with the district privacy officer.
- Skills and adoption
- Teacher guidance on when to enable AI in class and AI literacy lessons in grades 6 and 9.
- Governance checkpoints
- Initial configuration review
- Advisory committee review
- Quarterly post-update check
- Acceptance criteria
- Proposed: per-grade tool list published
- Proposed: retention and access settings documented for each tool
- Proposed: quarterly checks show no drift
- Risks
- Over-collection through monitoring
- Default settings drifting
- Uneven teacher use
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?
Student AI is delivered through the same vendor that filters and monitors devices, plus a default-configured general assistant for older students. Interpretation: access is enforced at the device and network layer by grade.
Governance
Who approves, reviews and stays accountable for outcomes?
District policy and state and federal privacy law cited as guardrails; teacher discretion retained; advisory committee for ongoing input.
Security and privacy
What data, permissions and controls need testing?
Combining AI chat with filtering and screen monitoring concentrates student activity data with one vendor; the announcement does not say what is logged, retained or reviewed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
AI literacy taught in grades 6 and 9; teacher professional development promised but not detailed.
Procurement
What should contracts, pricing and exit terms secure?
Student AI bundled with a filtering and monitoring vendor plus a general productivity suite assistant.
Operating model
Which teams own the service once it runs?
Central grade-band configuration with teacher discretion and an advisory committee for feedback.
Publication history
- 2026-10-19K–12 · Issue 435 resources
Stable resource ID: issaquah-sd-grade-band-ai-tools-securly-copilot-20261019