Post-event feedback that isn't a survey nobody opens

A workshop organizer emails a Google Form survey the morning after every session — twelve questions, a five-point scale, a text box at the end. Response rate: about one in twenty. Of those, half are one-word answers and one is someone venting about parking. Six months of this and the organizer still doesn't know whether the new format is actually working, because the form arrives late, asks too much, and leads nowhere anyone can see.

The form arrives too late and asks too much

A next-morning survey is competing with everything else in someone's inbox on a day they've already mentally moved past the event. Twelve questions is a chore, not a favor, and a five-point scale on 'overall satisfaction' rarely tells an organizer anything they can act on by next week. The response rate isn't a mystery — it's a rational reaction to a form that costs more than it's worth to the person filling it out.

And even a perfect response rate wouldn't fix the deeper issue: a generic satisfaction score doesn't tell an organizer which specific decision to make next. 'It was fine' is a real answer nineteen times out of twenty, and it's useless.

What a lighter loop looks like

• One specific question, not twelve general ones — "was the new start time better or worse?" gets answered; "how did we do?" doesn't.
• Asked same-day, ideally at the door on the way out, while the event is still the thing on someone's mind.
• A single tap or a QR code, not a form with a login wall or ten required fields.
• A visible close of the loop — "you told us the room was too loud, so we moved it" — so the next ask doesn't feel like shouting into a void.

Attendance is already feedback

Long before anyone fills out a survey, the RSVP and check-in data has already said something: who came, who said yes and didn't show, who's been at every session for two months, and who quietly stopped after one. That pattern is feedback an organizer usually has and rarely looks at, because it's shaped like a spreadsheet instead of a survey response. It's also the exact signal RunOS's Pacer uses to flag a member drifting toward churn before they've said a word about why.

Your attendance sheet has been telling you what's working for months — nobody read it because it wasn't shaped like a survey.