🎯 Learning Intention

Today I will explore system event logs and practice documenting how errors are diagnosed and fixed.

✅ Success Criteria

I can use an OS tool (Event Viewer or Task Manager) to locate a system issue and record a troubleshooting entry using the Cause → Fix → Result (CFR) format.

🌍 Why Are We Learning This?

IT support requires both technical skill and careful documentation. By practicing with event logs, you’ll learn how real technicians track errors — and how this mirrors the debugging process in coding.

🧠 Warm-Up – Tech Journal Prompt

💡 “Think about the last time technology failed you (computer, phone, Wi-Fi, etc.). How did you figure out what was wrong? Did you guess, research, or ask someone?”

→ Write 3–5 sentences.

📚 Word of the Day

Log

• Definition: A recorded history of system events, warnings, and errors.
• Sentence: “The Event Viewer log showed me that the app crashed because of a missing file.”
• Why it matters: Logs help technicians and coders trace problems and decide on solutions.

📣 Formative Lecture & Guided Demo (10–12 min)

• Walkthrough: Open Event Viewer / Task Manager.
• Show where errors and warnings appear.