# Review a report that a Rust moderator misused staff powers

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md)

Have an uninvolved lead review the staff action and the underlying player complaint separately. A player can have broken a rule and still be entitled to a fair review of how staff responded.

## Capture what the report can show

Suppose a player on Longford reports that a moderator moved them away from a build contest after an argument. The clip shows the player in a different place after a cut and the moderator's name nearby. Ask for the world, time with time zone and the original sequence. Preserve relevant history available to the reviewer. Record unavailable evidence as unavailable.

Tell the moderator privately what action is being reviewed and ask them to describe what they did and under which rule. Let a different lead take the case if the usual reviewer was involved. Keep the reply to the initial player short and give them a time when they can expect an update.

## Separate the observations from the decision

Say Longford's reviewer gets the full clip and a staff note that agrees with it on the time and the action.

| Question | Finding and next move |
| --- | --- |
| Did the moderator move the player? | The moderator confirms it in their note, and the sequence matches. Record the evidence supporting that finding. |
| Was it an agreed event action? | The staff guide allows a reset after a heat. This happened during a personal argument outside the course. The lead addresses the staff action separately. |
| Was the player's original conduct a violation? | The clip does not establish the player's alleged conduct. Keep that question open only if another proportionate evidence check is available. |

## Give both people a private outcome

Tell the player what the lead found about their concern and what remedy is relevant. Tell the moderator which duty or access has changed, who is responsible for it and when it will be reconsidered. If evidence could not establish who acted, record the unresolved point and avoid filling it with assumptions.

Close the review when the staff decision has an owner, both people received their own reply and the lead verified any agreed access change. General wording about the event can go in a public update if players need it. Leave private statements and identifying evidence in the restricted case record.

## Sources

- [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams)
- [Discord: confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation)
- [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust)

## Related resources

- [Who handles a report involving a Rust moderator’s own team?](https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/index.html.md)
- [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md)
- [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md)

---

HTML version: https://rustsc.com/learn/community/review-a-rust-moderator-staff-powers-report/
