5 ways to automate anonymous feedback

#1 - The basic check-in

Who it's for: Small teams opening up a feedback channel for the first time, with no formal process.

What it is: Anonymous feedback is a safe channel that lets any team member raise an idea, a concern, or a piece of praise without their name attached. This basic version is two fields: pick the closest match for what the feedback is about, then type it in your own words. Each submission is one record, and no name is captured.

In practice: A four-person veterinary clinic opens a feedback channel on a quiet Wednesday. Within two weeks, a junior vet raises a concern about the appointment booking system, a receptionist suggests a staff meeting change, and someone leaves a note of thanks for the new coffee machine. None of it came with a name. The practice manager now has three real thoughts she would never have heard in a team huddle.

Why it works: The barrier to raising something is almost always social, not practical. Stripping the name off removes the risk. Cutting the form to two fields removes the friction. What is left is the lowest-effort way to get a real thought in front of a manager.

Steps included:

• 1 single choice (what the feedback is about: idea, concern, praise, or other)
• 1 text input (the feedback, no word limit)

#2 - With written guidance

Who it's for: Teams where new starters or sceptics need to hear what stays confidential before they type.

What it is: The basic check-in plus two guidance panels woven around the inputs. The first explains what is captured and what is not: no name, just the thought. The second tells people what happens next: every submission gets read, and good ideas reach the next team meeting. New starters get the same reassurance as ten-year veterans, on the same screen, without anyone explaining it by word of mouth.

In practice: A care home with carers across three floors opens a feedback channel with guidance. A night carer hesitates before submitting a concern about handover routines, unsure if "anonymous" really means anonymous. The confidentiality panel, right there on screen, tells them plainly that no name is captured. They submit. A month later when the routine quietly changes, they connect the dots. Trust in the channel goes up, and so do submissions.

What it adds to the basic check-in:

1. A confidentiality panel before the questions, so people know what is and is not captured before they type
2. A "what happens next" panel after the feedback, so people know the submission is read, not dropped into a void
3. A consistent framing for every submission, so the channel does not rely on word of mouth to explain itself

Why it works: Written guidance sits inline at the moment of hesitation. The doubt that kills a feedback channel ("is this really anonymous?") is answered on the same screen, a second before the person decides whether to submit.

Steps included:

• 1 guidance panel (what's confidential)
• 1 single choice (what the feedback is about)
• 1 text input (the feedback)
• 1 guidance panel (what happens next)

#3 - With a signature

Who it's for: Businesses where a senior team needs proof that every submission was read and triaged, not filed away unseen.

What it is: The basic check-in plus a manager review signature on every record. The submitter stays anonymous, and the signature is not theirs. The manager signs once they have read and triaged the feedback. The signature is the audit that the submission was actually engaged with, not a name on who sent it.

In practice: A hotel group wants to know their staff feedback channel is real, not decorative. Each manager reviews submissions at the end of the week and signs each record on a tablet. The submitter's anonymity is completely untouched: there is still no name on who raised it. What the signature adds is accountability on the manager's side. When the area manager visits, they pull ten records at random and see a review signature on every one. The channel proves itself.

What it adds to the basic check-in:

1. A manager review signature on every record, signed once the feedback has been read and triaged
2. A clear audit that submissions are not ignored, without ever identifying the submitter
3. A defensible record for a senior team that the channel is genuinely worked, not just open

Why it works: An open channel only earns trust if people believe it leads somewhere. The submitter's anonymity protects the person raising the issue. The manager's signature proves someone listened. One says it is safe to speak. The other proves the channel works.

Steps included:

• 1 single choice (what the feedback is about)
• 1 text input (the feedback)
• 1 signature (manager review sign-off)

#4 - With photo evidence

Who it's for: Teams where feedback is sometimes about something physical that needs to be shown, not just described.

What it is: The basic check-in plus an optional photo step. If there is something to show (a broken fixture, a cluttered area, an unsafe spot) the person can attach one photo. If the feedback is an idea or praise with no physical thing to show, they skip the photo. The photo stays optional on purpose: ideas and praise rarely need a picture, but a "this area is unsafe" concern is far more useful with one.

In practice: A logistics business with three depots opens a feedback channel. A picker on the late shift notices a pallet stacked too high near a walkway. Describing the exact spot in words is awkward, so they pick "A concern", type one line, and attach a photo of the stack. The site manager sees instantly what and where. Because the canvas rolls up across all three depots, the operations lead spots two other sites logging similar photos that month, and a pattern words alone would have hidden becomes obvious.

What it adds to the basic check-in:

1. An optional photo of the specific issue mentioned in the feedback, attached to the same record
2. The ability to show a thing instead of describing it in words
3. A multi-site rollup where photos from different sites surface the same recurring issue side by side

Why it works: A description is one person's words. A photo is the thing itself. For a concern about a physical place, a photo removes all ambiguity about what and where, and gives a manager enough to act without a follow-up question.

Steps included:

• 1 single choice (what the feedback is about)
• 1 text input (the feedback)
• 1 photo of the specific issue mentioned (if applicable)

#5 - With Poppi checking the photo

Who it's for: Multi-site teams where photos get taken but nobody looks at them until weeks later, if at all.

What it is: The basic check-in plus a photo that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the photo clearly show the issue the feedback refers to? A single, specific spot is something an AI can actually judge, where a wide shot of the whole area is not. If the answer is no, Poppi posts what it spotted to the team chat, so the problem can be sorted straight away.

In practice: A three-site quick-service business closes at 6pm. A closer photographs a broken fridge door as feedback. Poppi reads the photo the moment it's uploaded: yes, the damage is clear. Nothing changes. On a Friday when someone photographs a cluttered storage area, Poppi answers no and posts the reason to the team chat: "The photo shows the area still contains loose boxes and debris." A manager spots it while still on site and has it cleared before lockup.

What it adds to the basic check-in:

1. A photo that gets checked the moment it is saved, not days or weeks later
2. A team chat message with Poppi's reason the moment a photo fails the check
3. The manager stops being the only person who ever looks at the photos, or they don't get looked at at all

Why it works: The check happens in the seconds between the photo being taken and the person leaving the site. That is the only moment a problem is still cheap to fix. A manager reviewing photos the next week can only record that the feedback showed a problem. Poppi catching it on the spot means it gets fixed immediately.

Steps included:

• 1 single choice (what the feedback is about)
• 1 text input (the feedback)
• 1 photo of the specific issue mentioned
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. Every version here is the basic check-in plus one addition, so pick the additions your team needs.

Do new starters need reassurance the channel is safe?

If your team is small and everyone already knows the channel is confidential, the basic check-in (#1) is enough. If new people join regularly or sceptics need to hear it spelled out, #2 adds guidance panels right on the form so nobody hesitates.

Does someone need to sign off that they've read each submission?

If the channel is informal and nobody needs an audit trail, skip this. If a senior team or a board needs to see that every submission was actually read and triaged, #3 adds a manager review signature, closing the loop without identifying the person who submitted it.

Is feedback sometimes about something physical you can show?

If the feedback you expect is mostly ideas, praise, or process concerns, the typed record is enough. If people will sometimes need to show a photo of a broken fixture, a cluttered area, or an unsafe spot, #4 adds an optional photo so they can show what they mean in one tap.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get filed away unseen, #5 has Poppi (AI) check each one the moment it lands and post to the team chat when something is not right.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That is how the product works anyway: every option here is one step added to the same channel.

Related workflows

• How to run an exit interview
• 4 ways to automate customer complaint logs
• 4 ways to automate near-miss reports
• 4 ways to automate hazard spotting
• 4 ways to automate lone worker check-ins

Conclusion

Anonymous feedback is a safe channel that lets any team member raise an idea, a concern, or a piece of praise without their name attached. Every version above is the same basic channel plus one addition: written guidance to build trust, a manager signature as an audit trail, a photo so people can show what they mean, or an AI check on the photo so problems get fixed on the spot.

Pick the version that matches how your team runs today. Open each template in the playground and get feedback this week.

→ Build your own anonymous feedback channel on Pilla.