(NWEA Testing Week – Extended Project Block)


🎯 Learning Intention

Today, I will practice Chromebook ticketing and diagnostics by learning how to access system tools and applying them to a sample support ticket.


Success Criteria

I know I’m successful when I can access the Chromebook diagnostics menu, run at least one test (battery, CPU, or memory), and record results as part of a sample ticket response.


🌍 Why Are We Learning This?

Interns are often the first line of tech support. Learning to triage tickets and use diagnostic tools prepares you to troubleshoot problems and communicate solutions professionally.


🧠 Warm-Up – Tech Journal Prompt (10 min)

💡 “If a student came to me saying ‘My Chromebook is slow,’ what questions would I ask first before touching the device?”


📚 Vocabulary (Ticketing & Diagnostics)

Term Definition Why It Matters
Ticketing System Software or workflow to log, track, and resolve support requests Keeps IT work organized and accountable
Triage Sorting requests by urgency and type Ensures critical issues are handled first
Diagnostics Built-in tools that test hardware/software Saves time by pinpointing issues quickly
Latency Delay between input and system response Helps identify performance problems
Log File Record of system events and errors Provides evidence for troubleshooting

📣 Mini-Lesson / Guided Check-In (15 min)