AI Adoption and Learning Plan Hub

Getting Started: Using AI at Questar

Questar is using AI to improve clarity, consistency, and efficiency in the work we already do every day. This work is grounded in why we exist. Our mission is changing lives, realizing dreams, and doing together what can’t be done alone. Our vision emphasizes a student-centered culture rooted in excellence, leadership, service, and innovation.

Used well, AI supports that mission by reducing rework, improving the quality of communication and planning, and helping us respond more consistently to districts. It frees up time for professional judgment, relationship-based work, and direct support of students and colleagues.

AI also aligns with Questar’s Leading Edge framework. Change is inevitable. The Leading Edge is how we approach innovation and growth: clear expectations, practical application, and continuous improvement as platforms evolve. This page is part of that approach.

What This Document Provides

This document is the starting point for using AI at Questar. It explains the expectations that apply to everyone, establishes a shared training baseline, and outlines our AI platforms, role-based examples, safety guidance, and implementation support. This document is intended to be a living document that will be updated regularly.

Core Expectations for Using AI

These expectations apply to all staff, regardless of role or platform:

• AI supports your work; it does not replace professional judgment. You are responsible for reviewing, refining, and approving any AI-assisted content before it is used or shared.
• AI Can Hallucinate – Accuracy Matters. AI may produce information that sounds accurate or authoritative but is incorrect, incomplete, or made up (including names, dates, policies, citations, and “facts”). Treat AI output as a draft. Verify anything important, especially content tied to students, staff, finances, compliance, or public communication.
• AI is a drafting and thought partner. It is appropriate for brainstorming, organizing, summarizing, and improving clarity. Final decisions, evaluations, and conclusions remain a human responsibility.
• Use AI responsibly and protect sensitive information. Do not enter sensitive or confidential information into AI platforms unless the workflow is explicitly approved for that platform and account type.

AI works best when staff understand what platforms are available, what each one does well, and how to use them effectively in their role.

Questar AI Platforms: When to Use Them and What to Watch For

Click the table preview below to interact and view links.

AI Safety and Security

This section outlines how we use AI responsibly to gain benefits while protecting students, staff, families, and the organization.

Default Rule

• Do not enter sensitive information into an AI platform unless the workflow is explicitly approved for that platform and account type.
• When unsure, assume the information is sensitive and redact or do not use it.

Accuracy and Hallucinations

• AI platforms can produce responses that sound accurate but are incomplete or incorrect and are considered hallucinations.
• Any AI-generated content that matters must be verified, especially facts, names, dates, numbers, quotations, and content that appears official.
• If it affects students, staff, finances, compliance, or public messaging, AI output must be treated as a draft and reviewed before use.

Three Categories to Guide Use / Do Not Enter by Default

Green – Generally OK

• Drafts based on your non-sensitive notes
• Generic templates and checklists
• Rubric language
• De-identified scenarios
• Rewriting for tone and clarity

Yellow – Caution/Slow Down

• Anything that could be interpreted as an official statement
• Anything with numbers or requirements
• Content going to families, districts, or the public
• Anything tied to compliance or HR processes

Red – STOP

• Student PII (IDs, addresses, disability/IEP details, health, discipline)
• Personnel info (evaluations, medical, investigations)
• Financial or legal documents not meant for broad sharing
• Anything confidential
• Anything you wouldn’t read aloud at a public meeting

Implementation and Continuous Improvement

Training and learning opportunities provide the foundation. Implementation is where AI begins to save time, improve quality, and support consistent work across the organization.

We are approaching AI using the Questar Leading Edge framework. This means staying grounded in our purpose, being clear about expectations, focusing on practical work that improves service, defining success, and adjusting as the technology evolves.

What We Are Doing Now

• Building clear, consistent expectations so staff can use AI without guessing.
• Focusing on practical use cases first, including clearer writing, better summaries, repeatable templates, and stronger planning documents.
• Maintaining this guidance as the single source of current expectations as platforms and features change.

What’s Next

• Continuing Lunch and Learn sessions using real Questar scenarios, with short, practical demonstrations and time for questions.
• Expanding MagicSchool use through Model Schools, partnering with instructional teams to support classroom-ready practices and shared examples.

How We Scale Responsibly

Scaling does not mean using AI everywhere. It means building shared patterns that are safe, consistent, and useful.

• Identifying a small number of workflows that consistently save time.
• Turning effective outputs into reusable templates or starting points.
• Sharing examples across departments to reduce duplicated effort.
• Maintaining consistent safety, verification, and review expectations as use expands.

What Team Leaders and Directors Can Do

• Model responsible, everyday use of AI in your own work.
• Share one or two examples of how you use AI, including how you review and verify outputs.
• Encourage teams to start with low-risk tasks and retain what works.
• Surface examples worth standardizing so they can become shared resources.

Keeping This Guidance Current

AI platforms and features will continue to change.

• This guidance will remain stable in structure.
• Examples, links, and recommended workflows will be updated as platforms and expectations evolve.