Reporters need acknowledgement and outcome feedback

What it is

A reporting feedback loop confirms receipt, explains next step and expected timing, and returns an appropriate outcome and protection update. Silence after submission leaves people unable to judge whether to seek other help and weakens future reporting.

Why it happens

Reporters bear emotional and retaliation risk. Immediate confirmation removes uncertainty about delivery; progress supports safety planning; outcome shows whether rules operate. Privacy can limit disclosure of a target’s sanction but does not justify no response.

Studying it

• Paradigms: compare confirmation, progress, and outcome designs on repeat report, help-seeking, trust, and recurrence.
• Variables: confirmation delay, status, outcome detail, handling time, satisfaction, later report, and safety.
• Methodological caution: low satisfaction can reflect an unwanted outcome rather than procedural failure.

Where it stops holding

Some investigations need confidentiality; explain that work is underway, available protection, and the next update. Feedback must not reveal retaliation-enabling details.

Applying it

• Provide a safe receipt, case ID, emergency resource, and safe contact choice.
• Show stages and review point, explaining delay proactively.
• At closure, state publicable decision, protection, and next appeal.
• Verification: test whether reporters know case state, self-protection options, and when to seek help again at each stage.

Related

• Same group: V7.05.1 The reporting entry must appear with the reportable content · V7.05.3 Appeal needs review by someone other than the original decision maker · V7.05.4 Malicious reporting must be constrained · V7.05.5 Misjudgment needs executable remedy, not only reversal
• Nearby: V7.06 Harassment and protection · V7.04 Content governance
• Search terms: reporting feedback · case status · trust repair