Grades 8–12 · Career Readiness

Workplace skills for high school CTE: handoffs, tickets, quality control and onboarding

Short answer: High school CTE students build workplace skills fastest through short simulations of everyday work documents: a shift handoff that separates verified from expected counts, a support ticket with reproduction steps, a quality control check against a stated trigger, an onboarding checklist with dependencies, and a schedule-change request with a confirmation step.

  • Grades8–12
  • Units5 workplace simulations plus an evidence portfolio
  • Documents practicedHandoff notes, tickets, QC notes, checklists, requests
  • Per unit4 × 90-minute double lessons, 16 slides, answer keys
Get Workplace Shift Handoff Simulation – $24.99

Employers often describe the same gaps in new workers: notes that do not say what was finished, problem reports that just say 'it doesn't work,' and confusion about what to do first in a new job. These are writing and reasoning skills, and they can be taught in a classroom before students ever start a placement.

TeachLessons has a set of workplace simulation units for exactly this. Each uses a fictional workplace and a short document students have to write or fix. The documents are generic enough to fit many CTE pathways, from manufacturing to IT support to retail.

Units for this topic

Shift handoffs: verified versus expected

Workplace Shift Handoff Simulation starts with a fictional job. Checklist items A and B are done. Box count C is pending: 8 expected, 6 verified. A damaged cart is tagged out of use, and the supervisor checks at 4:30. Students build a three-line status note with a clear action owner for the next shift.

The learning check asks why a shift note should distinguish 6 verified from 8 expected. That distinction is the whole skill. A later case has a forklift tagged unavailable, and students place it in the handoff without authorizing its use. Another has a later worker confirm that an unopened carton contains the missing box, and the note's evidence status has to be updated.

Support tickets that someone can act on

Write a Support Ticket at Work turns 'It doesn't work' into a testable report. In a fictional tool, clicking Export then PDF on Project 12 gives Error 204 every time, CSV works, and a teammate can reproduce the issue in a practice account. Students draft a ticket with reproduction steps, impact and a temporary work-around if acceptable, and they leave out private credentials.

Later cases add a second account that cannot reproduce the bug, a problem that only happens in one browser, and a screenshot that shows a private contact. Each one teaches a field good tickets include.

  • Steps to reproduce
  • Expected result and actual result
  • Scope: which accounts, which browser
  • Impact and a work-around
  • Nothing private in attachments

Quality control without jumping to causes

Workplace Quality Control Case Files uses a classroom packing standard: a box should hold five cards. Ten sample boxes contain 5, 5, 4, 5, 6, 5, 5, 5, 4, 5. Review is triggered if 2 or more of 10 differ from standard. Students count under- and over-counts, decide whether the trigger is met and write a short process note.

Then a recount corrects one of the original 4s to 5. Does review still trigger? A later sample shows only overcounts, and students must state a useful next investigation without asserting a cause. That restraint is a valuable workplace habit.

Onboarding and schedule requests

First Week Onboarding Checklist Lab gives students an onboarding memo: badge before entry Monday, safety briefing before equipment use, practice login Tuesday, supervisor check-in Friday. Two tasks have dependencies. Students build a checklist with owners and verification marks, then adjust when the badge pickup moves to Wednesday or the safety briefing is rescheduled.

Request Schedule Changes Professionally covers a situation most working teens meet quickly. A shift starts Thursday at 3:00, a school exam ends at 3:10, Sam can work from 3:45, and a colleague may cover the first 45 minutes, pending supervisor approval. Students write a concise request that states the conflict, a proposed alternative and a confirmation step, and mark the coverage as tentative.

Pulling it together in a portfolio

Each simulation produces a short document students can keep. Career Skills Evidence Portfolio shows how to turn those into precise skill statements for a résumé or placement interview, separating individual from team contributions.

Over a semester, a student who completes all five simulations has a handoff note, a ticket, a quality note, a checklist and a request letter, each revised after peer review. Those are concrete samples to discuss in a placement interview, and they show an employer the habits that matter in a first job: saying what is verified, naming who acts next, and confirming before assuming.

A five-step sequence

  1. Introduce the workplace

    Present the fictional job setting and the document students will write, using the slides.

  2. Analyze a weak example

    Show a vague note or ticket and have students identify what is missing.

  3. Draft the document

    Students write the handoff, ticket, QC note, checklist or request from the case.

  4. Apply a change

    Introduce the follow-up case and have students update the document.

  5. Peer review against criteria

    Use the peer review and revision pages before the learning check.

Common mix-ups and what to try

Instead of

A handoff note just lists what was done.

Try

It should separate completed, pending and urgent work and distinguish verified from expected.

Instead of

A screenshot is enough for a support ticket.

Try

Tickets need steps, expected and actual results, and screenshots must not expose private details.

Instead of

An odd sample means something is broken.

Try

Check against the stated trigger first and investigate before naming a cause.

More Career Readiness units

Related teaching guides

Frequently asked questions

Which CTE pathways do these units fit?

The documents are general workplace skills, so they fit many pathways, including IT support, manufacturing, logistics and retail.

What grades are the workplace simulations for?

Most are written for Grades 8–11 or 8–12. The onboarding checklist lab is Grades 9–12.

Do students need workplace experience?

No. All cases use fictional workplaces with complete information, so students can practice before any placement.

How are the units assessed?

Each has mini-checks, a 20-point learning check with model responses, a 100-point scoring sheet and peer review pages.

What if a unit does not fit my CTE 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.

Where can I see all career readiness units?

The career readiness collection includes these simulations plus pathway research and job offer comparisons.

Ready for your next lesson?

Pick the workplace document your students will meet first in a placement, and have them write and revise one this week.

View Workplace Shift Handoff Simulation

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.