Workshop Feedback Form Template

Feedback for hands-on sessions — the lecture-to-practice balance, skill-level fit, what participants actually built, and which follow-up they would attend.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

Hands still chalky? Perfect — that is exactly when workshop feedback is worth the most. Five quick questions.

press Enter ↵

A workshop is judged by a different standard than a talk: nobody minds a lecture that merely inspired them, but a workshop that ends with nothing built is a broken promise. This template audits that promise. Its questions orbit the two failure modes unique to hands-on formats — the balance between explanation and practice, and the skill-level spread of the room — because those two variables decide whether participants leave with a thing they made or a tab they never reopened.

Why these fields. The balance question names the workshop facilitator's eternal dilemma in its options: too much talking versus rushed practice. Aggregated across a cohort, it tells you which way to move the clock, which is the single highest-leverage revision between runs. The skill-fit question maps the room's spread — a run where answers split between "too basic" and "over my head" is not a facilitation failure but a prerequisites failure, fixable with better signup screening. Rating "what you built or learned by the end" anchors evaluation to output rather than enjoyment, which is the honest metric for the format. Facilitator support is scored separately because room management — unblocking the stuck, pacing the fast — is a distinct skill from content design. The follow-up multi-select converts satisfaction into a scheduled pipeline, and the change-one-thing field feeds the revision loop directly.

What we left out. Venue and catering ratings (real but secondary — they crowd the questions that improve the craft), pre/post self-assessed skill gains (self-report inflation makes them decorative), and testimonial fishing, which belongs in its own form with proper permissions.

Who uses this. Independent trainers revise their flagship workshops between runs, developer-relations teams score hands-on labs at conferences, maker spaces and art studios tune class difficulty, and corporate facilitators justify the next booking with the follow-up votes.

Make it yours. Swap the follow-up options for your actual pipeline of planned sessions — this turns the question into demand testing. Keep one form per workshop title across runs; the CSV export then shows the balance question trending toward "right mix" as your revisions land, which is the clearest craft-improvement chart a facilitator can keep.

Fixing the room before the room. When the level-fit answers pull toward both extremes in the same run, stop editing the workshop and start editing the signup page. Pull the concrete verbs out of your change-field responses — "I didn't know we needed the command line", "I had done all this before" — and turn them into a two-line self-check beside the register button: you will be comfortable if you can do this; skip it if you already do that. Then track the share answering "pitched just right" across subsequent runs as your targeting score. Most facilitators discover the room's spread was decided weeks earlier by a vague event description, and one honest paragraph at signup buys more built-by-the-end ratings than any amount of live improvisation.

Frequently asked questions

Paper forms at the door get more responses — why digital?

QR the form on the final slide and fill rates match paper, but the answers arrive structured: exportable, trendable across runs, and readable without deciphering handwriting.

How do we use the follow-up votes?

Treat the multi-select as pre-registration demand — schedule whichever option clears your viability line, and email the link to attendees who voted for it.

Can we compare two runs of the same workshop?

Keep one form for the title and export the CSV after each run; timestamps split the cohorts, and the balance and level answers show whether revisions worked.

Should feedback be collected before people leave the room?

Yes — the final ten minutes, while laptops are open and the build is fresh. Response quality drops steeply once participants disperse.