Repair Documentation & Ticket Workflow

🎯 Learning Intention

Today, I will practice professional repair documentation by writing clear, step-by-step repair notes.

✅ Success Criteria

I can log a repair ticket that another technician could follow and reproduce without asking questions.

🌍 Why Are We Learning This?

Repair work is about more than fixing devices — it’s about documenting the process so the next technician (or district IT) knows exactly what was done. Clear tickets = professional credibility.

🧠 Warm-Up – Tech Journal Prompt

💡 What’s one thing you’ve seen in a repair log (or could imagine) that would make it hard for another tech to understand?

📚 Word(s) of the Day

• Triage
  • Definition: Sorting and prioritizing issues based on urgency and impact.
  • Why it matters: Helps decide what gets fixed first when multiple devices are waiting.
• Ticket
  • Definition: A written record of a repair request, including problem, diagnosis, and resolution.
  • Why it matters: Forms the official trail of repair work and accountability.

📣 Formative Lecture & Demo (10–12 min)

• Show a “bad” ticket example (unclear, missing steps).
• Show a “gold standard” ticket example (diagnosis, attempted fixes, resolution).
• Walk through the district ticketing format → what must be included.

✅ CFU #1: Students identify at least 2 issues in the “bad” ticket.