Design a participant feedback loop
Set up a feedback system where participants know their input actually moved something.
Fill in the details
5 placeholdersType your details in and we'll drop them into the template. Empty slots stay as tokens so nothing goes missing.
Prompt template
Design a feedback loop for {{programme_name}} at {{association_name}} so participants know their input actually changed something. Participants: {{participants}} Frequency of contact: {{contact_frequency}} Tone: {{communication_tone}} Return: 1. Three low-friction ways to collect feedback in the moment (not surveys) 2. A monthly "you said, we did" cadence — including what to do when the answer is "no, and here's why" 3. Ways to hear from participants who leave or drop off 4. How to prevent feedback becoming performative 5. What we commit to publishing openly Do not suggest NPS.
Replace each highlighted placeholder with real context. Keep names and safeguarding details out.
Human review checklist
Tick each before you send or publish the output.
When to use this prompt
Reach for this prompt when you need to set up a feedback system where participants know their input actually moved something. It's designed for Programme lead, Ops lead, Youth worker. Typically used within Programme design work.
How to use it
- 1
Gather your inputs
You'll need: programme_name, participants, contact_frequency. - 2
Fill in the highlighted placeholders
Copy the template above and replace every highlighted placeholder with real, local context. - 3
Run it in your AI tool
Paste into your preferred AI assistant. Ask a follow-up if the output misses your association's tone. - 4
Work through the checklist
Tick every item before you send, publish or act on the output.
Why this prompt works
Bans NPS and demands the "no, here's why" answer — the two things that make feedback loops feel real.
Was this useful?
Sign in to leave feedback and shape which prompts stay in the library.