4 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 and no suggestion box on the wall.

Available on: Basic.

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 on a phone: pick the closest match for what the feedback is about, then type it in your own words with no word limit. Each completion is one record, and no name is captured unless the person chooses to put one in the text themselves.

In practice: Take a three-site garden centre. A weekend till assistant has an idea about moving the card readers to ease the Saturday coffee queue. They would never raise it in a team huddle, but on a quiet break they pick "An idea or suggestion", type two sentences, and submit. The duty manager sees a new idea land in the activity log with no name on it. The thought that would have evaporated is now a record someone can act on.

Why it works: The barrier to raising something is almost always social, not practical. People stay quiet because speaking up feels risky, not because typing is hard. Stripping the name off the record removes the risk, and 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)

When to upgrade:

1. Add written guidance (#2) once more than a handful of people use it, so everyone knows what stays confidential before they type.
2. Add a photo step (#3) once people start describing things that would be clearer shown than written.
3. Add a manager review signature (#4) once you need to prove every submission is actually being read and triaged.

#2 - With written guidance

Who it's for: Businesses that want a consistent, guided submission every time, so nobody hesitates over what is captured or what happens next.

Available on: Standard.

What it is: The basic channel plus two guidance panels woven around the inputs. The first sits before the questions and spells out what stays confidential: no name is captured unless the person types one, and the duty manager sees the feedback but not the sender. The second sits at the end and explains what happens next: every submission gets read, good ideas reach the next team meeting, and concerns get triaged. A first-week starter gets the same reassurance as a ten-year veteran without anyone briefing them.

In practice: Take a 40-bed care home with carers across three floors. A night carer has a concern about a handover routine but has heard a rumour that "anonymous" boxes are not really anonymous. The confidentiality panel, right there before the questions, tells them plainly that no name is captured and the duty manager sees the feedback but not who sent it. They submit. The "what happens next" panel had also said the concern would be triaged, so when the routine quietly changes a fortnight later, they connect the dots. Trust in the channel goes up, and so do submissions.

What it adds to the previous template:

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 exact moment of hesitation. The doubt that kills a feedback channel ("is this really anonymous?", "does anyone even read these?") is answered on the same screen, a second before the person decides whether to submit. It is not a policy document in a shared drive that nobody opens.

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)

When to upgrade: Move to Anonymous Feedback #3 once people start describing things that are easier to show than to write. A photo of a notice board, a worn-out sign, or a cluttered area says in one tap what a paragraph struggles to.

#3 - With photo evidence

Who it's for: Teams that want to let people attach a photo to feedback, so a submission can show the thing it is about, not just describe it.

Available on: Standard.

What it is: The guided channel plus an optional photo step at the end. The person can attach a single photo if there is something to show (a poster, an unsafe area, a piece of kit) and skip it if there is not. The photo lands in the same record as the typed feedback. It stays optional on purpose: praise rarely needs a picture, but a "this area is a trip hazard" concern is far more useful with one.

In practice: Take a logistics business with three depots and a rotating warehouse crew. A picker on the late shift keeps noticing a pallet stacked too high near a walkway. Describing the exact spot in words is awkward, so they pick "A concern or complaint", type one line, and attach a photo of the leaning stack. The site manager opens the record and 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 previous template:

1. An optional photo step after the feedback, attached to the same record.
2. The ability to show a thing (a board, an area, a piece of kit) instead of describing it in a paragraph.
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 ideas and praise the words are usually enough, which is why the step is optional, but 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 guidance panel (what's confidential)
• 1 single choice (what the feedback is about)
• 1 text input (the feedback)
• 1 guidance panel (what happens next)
• 1 photo step (optional)

When to upgrade: Move to Anonymous Feedback #4 once you need to prove the channel is not a black hole. Once a senior team, a board, or your own conscience needs evidence that every submission was actually read and triaged, a manager review signature closes that loop.

#4 - With photo and signature

Who it's for: Businesses that want an audit that every submission was read and triaged, with proof attached to each record.

Available on: Standard.

What it is: The photo-enabled channel plus a manager review signature on every record. This is the one place the framing flips: the submitter still stays anonymous, and the signature is not theirs. The duty manager signs once they have read and triaged the feedback. The signature is the audit that the submission was read, not a name on who sent it. A senior team can pull any record and see at a glance that a manager engaged with it.

In practice: Take a four-branch retail chain whose head office wants to know the staff feedback channel is real, not decorative. Each branch manager reviews submissions at the end of the week and signs each record on the touchscreen. The submitter's anonymity is 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 previous template:

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 or an external reviewer 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 protects the credibility of the channel. One says it is safe to speak. The other proves someone listened.

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)
• 1 photo step (optional)
• 1 signature step (manager review sign-off)

When to upgrade: The next variations layer Poppi on top. A Poppi briefing that summarises the week's submissions before review. A Poppi gate that routes a serious concern straight to the senior team instead of the weekly pile. A Poppi action that drops a triaged idea into the right channel automatically. Coming in the next post update.

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. You only need to answer three questions about how your team runs.

Is it just you running this, or do other people run it too?

If your team is small and everyone already knows the channel is safe, the basic check-in (#1) is enough. Two fields, no name, straight onto the record.

If the channel needs to win over people who are unsure, or new starters keep joining, go to #2 onwards. The confidentiality and "what happens next" panels build trust without anyone explaining the channel by word of mouth. You write the guidance once; everyone reads it inline.

Do you need a photo as proof, or is the typed record enough?

If the feedback you expect is mostly ideas, praise, and process concerns, the typed record is enough. Go to #1 or #2.

If people will sometimes need to show a physical thing (a notice, an area, a piece of kit), go to #3. The optional photo lets them show what they mean in one tap, and across multiple sites it surfaces patterns that scattered descriptions would hide.

Do you need someone to sign off at the end?

If the channel is informal and nobody needs proof it is being worked, stick at #3.

If a senior team or your own standards need evidence that every submission was read and triaged, go to #4. The manager review signature is the lock. The submitter stays anonymous; the signature proves a manager engaged with the record.

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. The version a multi-site business runs adds a manager review signature on every record, so a senior team can prove every submission was read and triaged while the person who raised it stays anonymous.

Pick the version that matches how your team runs today, not the most sophisticated one you can imagine running someday. Open each template in the playground above and open the channel this week.