Running a Smooth Activity in Class

Classroom Management Tips for TeachSpark

A TeachSpark resource

---

The activity itself only takes 5-7 minutes to generate — how it plays out in your classroom depends on a few small logistics decisions. This guide covers the practical side: getting it in front of students, keeping things moving, and following up afterward.

---

Before Class: Pick Your Sharing Method

TeachSpark gives you three ways to get an activity to students — pick based on your setup, not just habit:

• Class code — best when students are used to entering a code themselves, and you want to reuse the same access method every time
• Direct link — best if you're posting to an LMS, a class website, or messaging it directly, since it's one click for students rather than typing anything
• QR code — best for younger students, or any moment where a projected code is faster than students navigating to a website

If you teach multiple sections of the same course, the same generated activity can be shared with every class — you don't need to regenerate it per period unless you want a different version for each.

Check the Estimated Duration Against Your Class Period

When you set up the activity, you gave it an estimated duration. Before class, sanity-check that estimate against how much time you're actually giving it — a 20-minute estimate doesn't leave much room if you're also handling attendance, a warm-up, and transitions. If it's tight, decide in advance whether you'll extend into the next segment or have students finish for homework, rather than deciding mid-class.

During the Activity

• Walk the room. Since students access activities through a link or code rather than logging into anything, walking around and glancing at screens tells you more in the moment than anything you can check afterward.
• Have a backup plan for tech hiccups. A student with a dead device or connectivity issue can usually pair with a neighbor for the activity rather than losing the whole period — decide your policy on this ahead of time so it's not a mid-class scramble.
• Let early finishers know what's next. Since activities are self-paced, some students will finish well before others. Decide in advance what early finishers should do (a related question, quiet reading, helping a neighbor) so you're not improvising in the moment.

For Absent or Catching-Up Students

Because activities live at a stable link, a class code, or a QR code rather than a live, in-class-only session, they work just as well for a student completing the work later — send the same link, no need to regenerate anything or set up a separate version for makeup work.

After Class: Checking Results

Head to Results to see submissions as they come in, and Analytics for a wider view across activities. A couple of things worth building into your routine:

• Check completion status before the next class, especially if some students were still working when the bell rang — you'll know who needs to finish versus who simply didn't start.
• Look at unusually fast completions alongside everything else, not in isolation. TeachSpark flags submissions completed much faster than the estimated time so you don't have to go hunting for them — treat that as one signal worth a second look, not a verdict on its own (see the Academic Integrity resource in this library for more on that).

---

None of this needs to be complicated. The activity itself is already built — these are just the small decisions that make it run smoothly once it's in front of students.