
Give a Rust volunteer their first lead shift
Give the acting lead a defined shift and the authority needed to keep volunteers working. Write down which changes still wait for the owner and who is next if someone needs an immediate answer.
Name the decisions, not just the title
For example, Jo can move a report to another moderator and approve a short pause to the evening event during Cairn Coast's Sunday shift. Jo cannot revise the player rules or change staff access. The owner names a backup reachable during the shift and an exact time when the owner takes decisions back.
Ask three volunteers to make practice requests
Jo should see the same staff reference and contact list they will have on Sunday.
| Request | What Jo does |
|---|---|
| A volunteer cannot finish a report. | Assign it to a named available moderator, who confirms receipt. |
| An event argument is getting in the way of play. | Pause the event if needed and assign the conduct report separately using the existing escalation route. |
| Someone needs broader staff access for a future duty. | Record the request with the work it would enable and pass it to the owner at handback. |
Keep people from making the same decision twice
Post the shift window privately, name Jo as the active lead and tell staff where to leave anything Jo cannot decide. Give Jo only the access the actual duty uses. Much of this lead job can be done in a private staff channel without changing server administration.
At the end, Jo gives the owner the open decisions, their current assignees and any player update owed. The owner confirms receipt. The rehearsal passes if a volunteer can tell who owns a pending request before and after that handback.