Feedback — Guild Leader Guide

← All Guides

Your Role

As a guild leader or moderator, you are the bridge between your guild's members and the site administrators. You help ensure that feedback from your guild is heard, properly scoped, and acted upon.

Encouraging Feedback

Good feedback helps the whole community improve. Encourage your guild members to:

• Use the green feedback button (bottom-right corner) for quick submissions.
• Visit the full feedback form for more detailed submissions.
• Select "A guild" as the area when the feedback relates to guild activities.
• Vote on the suggestion board to help surface important ideas.

Guild-Scoped Feedback

When members submit feedback with the scope set to "A guild", it signals to administrators that the feedback is about guild activities, structure, or governance. This helps administrators route it to the right people.

As a guild leader, you can help by:

• Periodically browsing the suggestion board and filtering for guild-related items.
• Adding context by submitting your own feedback that references or builds on member submissions.
• Discussing popular suggestions in your guild meetings.

Handling Sensitive Issues

If a guild member comes to you with a sensitive matter:

• Encourage them to submit it as a Concern. Concerns are always private and only visible to administrators.
• If the matter involves safeguarding, ensure it reaches the appropriate administrator immediately — do not attempt to handle safeguarding issues within the guild alone.
• Never share private concern details with other guild members.

Escalation

If you notice a pattern of feedback from your guild (e.g. multiple members reporting the same issue), consider:

1. Submitting a consolidated feedback item yourself that references the trend.
2. Contacting an administrator directly to flag the pattern.
3. Raising it in any cross-guild or community-wide meetings.

If you are also a shepherd

Being a guild leader and being a shepherd are separate things — the second is granted deliberately, and it is not implied by this role. If you do hold it, you get a queue of reports that are already eligible for an AI-drafted fix, with the reporter's identity withheld: you are judging a report, not a person.

Two bounds apply, and they are enforced rather than advisory: at most three drafts in flight at once, and at most two attempts per report ever. If a coder stands down on something, it appears in the declined queue and needs one of three answers — clarify and re-arm, hand it to a person, or close it with a written reply. Nothing may be closed silently.

Arming asks for a draft. It never merges and never publishes; a human always approves what goes live.

What You Can See

Guild leaders have the same feedback permissions as regular members unless an administrator has granted additional access. You can:

• View all public feedback on the suggestion board.
• Submit feedback and vote on items.
• See the status of feedback items as they progress through the lifecycle.

You cannot see private concerns submitted by others, change statuses, or access analytics — these require the "administer feedback" permission.

Best Practices

• Lead by example — Submit your own thoughtful feedback to set the tone.
• Acknowledge contributions — When a guild member's suggestion gets implemented, celebrate it in your guild.
• Close the loop — If you know the status of a suggestion, share that context with your members.
• Be constructive — Help members frame issues as actionable suggestions rather than complaints.
• Respect privacy — Never pressure members to share feedback publicly if they prefer a private concern.