Grades 8–12 · Career Readiness

How do you teach students to write a clear support ticket in Grades 8–12?

Short answer: Give students a fictional software problem and have them write a ticket with numbered reproduction steps, the expected output, the actual output, the impact and a temporary workaround if one exists. They leave out private credentials, attach screenshots only after removing private details, and add comparison fields when the problem appears on one setup but not another.

  • Grades8–12
  • TimeFour 90-minute double lessons
  • Materials42-page PDF, 16 slides, 5 worksheets with answer keys
  • Learning check20 points, model responses included
Get Write a Support Ticket at Work – $24.99

'It doesn't work' is probably the most common support request ever written, and it is almost impossible to act on. The person receiving it does not know what was tried, what should have happened or what happened instead. They have to write back and ask, and the problem waits.

The Write a Support Ticket at Work unit teaches students to write the ticket that gets fixed. Using fictional tools and practice accounts, students describe a problem so someone else can reproduce it, state clearly what they expected and what they got, and include the context that narrows down the cause. It is a workplace writing skill that applies far beyond IT, and it builds careful observation habits that help in any technical course.

Units for this topic

The parts of a testable ticket

In the starting case, clicking Export then PDF on Project 12 in a fictional tool gives Error 204 every time. CSV export works. A teammate can reproduce the issue in a private practice account. Students draft a ticket with reproduction steps, impact and a temporary workaround if acceptable, and they omit private credentials.

The CSV detail is easy to overlook and very useful. It tells the support team that export in general works and the problem is specific to PDF. Students learn to include what does work as well as what fails.

A useful classroom rule: every ticket gets tested by someone who did not write it. The tester follows the steps exactly as written, with no help from the author. If the tester cannot reach Error 204, the steps are missing something. Students find this more persuasive than any rubric, because the gap shows up in front of them.

  • Steps to reproduce, numbered
  • Expected output
  • Actual output, including any error code
  • Impact: who is affected and how much
  • Workaround, if one exists
  • Environment: account, browser or device

When the problem is hard to reproduce

One case uses a training bug: press Save twice, then reopen the task, and comments are duplicated. Students report reproducible steps and the expected result. Then a second account cannot reproduce the issue, and students add a comparison field that shows the difference between the two setups.

Another task says the issue happens only on one browser. Students decide what the report now needs, usually the browser name and version and a note that other browsers work. The learning check item gives a ticket that reads 'It doesn't work' and asks students to add two fields that make it testable.

Point out that 'cannot reproduce' is information, not a dead end. The comparison field turns a frustrating result into a clue about where the problem lives, which is exactly how support teams narrow things down.

Handling private information

The transfer case shows a screenshot that includes a private contact. Students decide how it should be attached, for example by cropping or covering the private detail before sharing. Combined with the rule to omit credentials, this teaches a habit that matters in every workplace: support tickets often travel further than the writer expects.

All tools, accounts and errors in the unit are fictional, and the cases contain no real personal data.

Connections across subjects

The unit fits career readiness, CTE and computer science courses. It pairs well with Repair a Broken Web Form, where students specify form behavior that helps users recover from errors, and with Workplace Shift Handoff Simulation, which uses the same verified-versus-assumed thinking for shift notes.

The four double lessons move from the first error case to a model ticket, then a revised case and new context, then testing and transfer, and finally the learning check and feedback. Support and extension cards cover different readiness levels, and stronger students can triage several tickets by impact.

A five-step sequence

  1. Show a bad ticket

    Display 'It doesn't work' and ask what the support team would need to ask back.

  2. Read the Error 204 case

    Students list what happens, what works, and who else can reproduce it.

  3. Draft the ticket

    Write numbered steps, expected and actual output, impact and a workaround.

  4. Test the steps

    A partner follows the steps exactly. If they cannot reach the error, revise.

  5. Add environment and check

    Handle the one-browser and private-screenshot cases, then complete the learning check.

Common mix-ups and what to try

Instead of

A short ticket is a good ticket.

Try

'It doesn't work' is short but untestable. A good ticket is as short as possible while still letting someone reproduce the problem.

Instead of

Only describe what fails.

Try

Noting that CSV export works narrows the problem to PDF. What works is useful information.

Instead of

Attach screenshots as they are.

Try

Screenshots can contain private details. Students crop or cover them before attaching, and never include credentials.

More Career Readiness units

Related teaching guides

Frequently asked questions

Do students need computers for this unit?

No. The cases describe fictional tools on paper and slides. If you have devices, students can test each other's reproduction steps on a practice task you set up.

Which grades is it for?

Grades 8–12, in career readiness, CTE or computer science courses.

Is it only for students heading into IT jobs?

No. Clear problem reports are used in offices, retail, healthcare, manufacturing and schools. The skill transfers to any workplace with shared tools.

How is the unit assessed?

Through five worksheets with answer keys and a 20-point independent learning check with model responses and a 100-point scoring sheet.

Can the unit be changed to fit our standards?

Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

What other workplace skills units are there?

The career readiness collection includes shift handoffs, onboarding checklists, quality control and schedule change requests.

Ready for your next lesson?

Write 'It doesn't work' on the board and ask students for the two fields that would make it testable.

View Write a Support Ticket at Work

Instant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.