For teachers and lecturers

In a practical lesson the hardest question is the simplest one: is everyone actually with me? Workshopy answers it continuously. You write the lesson as one Markdown file, students join with a 6-character code and no account, and a live grid shows you who is on which step and who has marked themselves stuck — so you intervene while it still matters instead of finding out from the marks.

Last updated

What goes wrong today

The quiet student stays quiet

Students who are lost rarely say so in front of the class. By the time the silence registers, twenty minutes of the lesson have gone. A per-step 'stuck' signal is a private way for them to ask, and it reaches you immediately.

The room splits into fast and slow

Half the class finishes in five minutes and the other half needs fifteen. Without visibility you either hold the fast group back or leave the slow group behind. Seeing the spread lets you pick the moment to move — or let people roam ahead while you help the ones who need it.

Accounts and installs eat the first ten minutes

Anything that needs a student login, an app or a school-IT exception costs you lesson time. Students join a Workshopy session with a code and a display name, on whatever device they have.

How a session runs

  1. Write the lesson as one document

    Every top-level # heading becomes a step. Standard Markdown for everything else: explanation, code blocks, images, links. A step tagged #[quiz] becomes a graded check. You can write it yourself, import an existing .md, or have an AI draft it — it is only text.

  2. Start the session and read out the code

    Starting a session snapshots the content, so edits to your template never disturb a class in progress. Students go to the join page, type the 6-character code and a name, and they are in.

  3. Watch the grid, not the room

    Each student marks every step in progress, done or stuck. Your dashboard sorts stuck students to the top and shows completion per step, live. Raised hands and help requests queue up separately so nothing gets lost.

  4. Keep the class together when you need to

    Advance everyone to the next step, jump the whole room to a specific one, or send a broadcast — an announcement, an acknowledge prompt, or a quick poll — and watch the answers aggregate live.

  5. Review afterwards

    The post-session report gives you a timeline, engagement stats, broadcast results and the annotations students left. Export it as Markdown. Run the same template with next year's class and compare where people got stuck.

What you get

  • Students join with a code — no account, no install, any device
  • Live per-step status: in progress, done, stuck
  • Stuck students sorted to the top of the dashboard
  • Graded quiz steps authored in the same file
  • Edit, insert or hide a step mid-lesson without restarting
  • Reusable templates — one lesson, many cohorts, a report each time

Frequently asked questions

Do my students need accounts?

No. They join with a 6-character code and pick a display name. Only the teacher needs an account. Note that this also means joins are anonymous-capable — there is no mode today that requires a verified student account, so Workshopy suits classwork rather than formal, identity-assured assessment.

Can I see individual students' answers?

Yes. Progress and status are per-participant and attributable by display name, quiz responses are recorded per participant, and the post-session report breaks results down by person.

What if a student joins late?

They join the running session with the same code and land on the current step. Their earlier steps simply show as not started, and they can work back through them if the session allows lookback.

Is the free plan enough for a class?

For most classes, yes: 30 participants and 45-minute sessions with the full live feature set. A double period or a class over 30 needs Pro.

Also built for

Run your next workshop with the room visible.

Set up your first workshop in minutes — free, no credit card.