nexy

Use case

Confirm who collects feedback forms after a workshop

Workshop participants complete feedback forms before they leave, but someone needs to collect them, read through the responses, and prepare a short summary for the team. Without a clear owner, forms can be forgotten on tables or mixed with other materials.

Use one Nexy thread for one agreement: One person will collect all the feedback forms when the workshop ends, read through them, write a brief summary of the main points, and send that summary to the organisers by an agreed time. The other person receives a message in the chat they already use, without installing anything or creating an account; reminders stop for a task that is already done.

Try this in Nexy, freeStarts on the web. The other person installs nothing.

What it looks like

An example of people making one clear agreement and confirming when it is done.

How to do it

  1. Start one Nexy thread for the agreement. Agree who will stay until the workshop finishes to collect the forms—this person should be comfortable asking participants to hand them in before leaving.
  2. Decide what the summary should include: overall satisfaction, common suggestions, any concerns raised, and whether responses were mostly positive or mixed. The other person receives a message in the chat they already use and needs no new account.
  3. Set a deadline for the summary—Saturday morning works well if the workshop is midweek, giving time to reflect without dragging into the next week.
  4. Confirm how the summary will be shared: a short message to the organising group, a document everyone can read, or a brief call with the facilitators. A reminder is most useful while you could still act, usually the evening before.
  5. Agree what happens if forms are incomplete or illegible—whether to note the missing information or follow up with specific participants if contact details are available. Once the task is done, there are no more reminders for that completed task.

Why it works

One clear agreementOne agreement per thread keeps this specific commitment separate from the rest of the conversation.
People choose the ownerAn unclaimed task is announced to the whole group. Nexy does not choose a person or assign it for you.
Done means no remindersA person who has already completed the task is left alone. Finishing is different from receiving another reminder.

Where it stops

Keep the agreement narrow and let the people involved make the decisions.

One agreement per threadUse this thread for the specific agreement, rather than treating it as an entire project.
No automatic assignmentNexy announces unclaimed tasks to the group; the people decide who will act.
No reminders after doneCompleted tasks are not a reason to keep reminding someone.

Questions people ask

Who should collect the feedback forms?

The person collecting should plan to stay until the last participant leaves, so they can gather forms from tables, chairs, and anyone handing them in late. A co-facilitator or event organiser works well because they already know the layout and can check all the spaces participants used. If the collector needs to leave early, agree a handover point where another team member takes responsibility. Avoid assuming forms will be left in one neat pile—participants place them in different spots, and some forget until reminded at the door.

What should the summary include?

Focus on patterns rather than listing every individual comment. Note how many forms were returned, the overall tone—mostly positive, mixed, or critical—and the most common suggestions or complaints. Highlight any urgent issues like safety concerns or accessibility problems that need immediate attention. Include a few direct quotes if they capture a recurring theme clearly. Keep the summary short enough that organisers can read it in two or three minutes and decide what action to take. Avoid interpreting or defending responses—just report what participants wrote.

When should the summary be ready?

Within a few days works well, while the workshop is still fresh in everyone's mind and any follow-up can happen quickly. If the workshop is midweek, a Saturday or Sunday deadline gives the collector time to read carefully without rushing. If it's a Friday workshop, Monday or Tuesday morning lets organisers act on feedback before planning the next session. Agree the deadline when confirming who collects, so the person knows whether they need to prioritise it over the weekend or can fit it around other commitments during the week.

How many feedback forms should we expect back?

Not every participant will complete a form, even if you hand them out and explain why they matter. Some people leave early, others forget, and a few simply choose not to respond. Collecting half to three-quarters of the possible forms is realistic for most workshops. If far fewer come back, consider whether the forms were easy to find, whether participants had time to fill them in before leaving, or whether the questions felt too long or unclear. Note the response rate in your summary so organisers understand how representative the feedback is.

What if the feedback is mostly negative?

Report it honestly without softening or dismissing the concerns. Organisers need to know what participants actually thought, even if it's uncomfortable. Note specific complaints—timing, content, venue issues, facilitation style—and whether they came from several people or just one or two. Distinguish between fixable problems like unclear instructions and deeper concerns about the workshop's purpose or approach. Negative feedback is useful for improving future sessions, but only if the summary presents it clearly enough that organisers can decide what to change. Avoid adding personal opinions about whether complaints were fair.

Should we follow up with participants who gave critical feedback?

Only if you offered that option on the form itself, such as a space for contact details and a question asking whether they'd like to discuss their response. Following up without permission can feel intrusive, especially if someone expected their feedback to remain private. If several people raise the same issue, consider sending a message to all participants explaining what you'll change, rather than contacting individuals. That shows you took the feedback seriously without putting anyone on the spot. Always follow through on what you say you'll do with responses.

What happens if forms go missing?

If someone else cleared the room quickly or participants took forms home by mistake, you'll have an incomplete picture. Note in your summary how many forms you expected versus how many you found, so organisers know responses might not represent the whole group. Check with venue staff or other helpers in case forms were collected separately. If forms contained sensitive comments and you can't locate them, let organisers know immediately in case any confidentiality concerns need addressing. For future workshops, agree a visible collection box and remind participants where to leave completed forms.

Can we use the same person to collect forms every time?

Yes, if that person is available and willing, and if it doesn't create a pattern where only one perspective shapes the summaries. Rotating the role between team members means different people notice different themes in the feedback and bring fresh attention to what participants say. If one person always collects, they build skill in spotting patterns quickly, but they might also start filtering responses through assumptions about what matters. Discuss with your team whether consistency or variety serves your workshops better, and respect either choice as long as summaries remain accurate and complete.

Do this with Nexy

Start free on the web. Tell Nexy what the two of you agreed on and it takes it from there: it asks, reminds whoever still has to act, and tells everyone when it is done.

Start free

No app needed to begin, and nothing at all for the other person.

Related use cases

New here? How Nexy works explains the whole thing in a minute, and the index lists every use case.

Stay posted on Nexy

We add a new use case most days and test what actually works. Get the short version by email, or a notification the moment something ships. No account, and one click to stop.

Agree who collects feedback forms after a workshop