What an alliance officer is expected to do, as a checklist you can pin, plus a handover note for when the leader changes.
Ranks tell you who can do what in the game. They do not tell your members what an officer is expected to do day to day. That is agreed inside each alliance, and when it is not written down officers do too much, too little, or different things. The checklist below is a starting point. Change it to fit your alliance.
Copy-ready
Officer (R4) duties checklist
[TAG] OFFICER (R4) DUTIES
Every day
• Check alliance chat and Discord for questions and new applicants
• Greet new members and point them to the pinned rules
• Tap alliance help, and remind others to
Every week
• Review the roster: who has not logged in for [5] days? Send a check-in before anything else
• Post the week's event times in [channel]
• Answer applications within [24 hours]
Before an event or KvK
• Confirm who leads each rally and who fills each role
• Remind members what to prepare: [train troops, bank speedups, shield when away]
• Post the times in [server time / UTC]
When there is a problem
• Talk to the member privately first
• Follow the written rules. Do not invent a new one on the spot
• If it means a removal, or affects the whole alliance, take it to the R5 first
Never
• Promise a reward, a seat or a role you do not control
• Share the Discord admin login or anyone's account details
• Argue in alliance chat
Pin it where officers will see it. Change the [brackets] and the duties to fit your alliance.
R5 handover note
[TAG] LEADERSHIP HANDOVER — [date]
From: [outgoing R5] To: [incoming R5]
1. Rules: pinned in [place]; last changed [date]
2. Roster: kept in [sheet link]; last reviewed [date]
3. Discord: owner moved to [name]; admins are [names]
4. Events: next [event] on [date]; rally leads are [names]
5. Allies and agreements: [alliance names and what we agreed]
6. Open matters: applications waiting [names]; disputes [short note]
7. Things only the outgoing leader knows: [list]
After the handover: announce it in alliance chat and Discord, and thank the outgoing leader.
Fill it in together, in one sitting, before the change is announced.
Running the handover
Write the note first, together. Sit down with both leaders and fill in the note line by line. The seventh line, the things only one person knows, is the one that hurts if it is left out.
Move the Discord ownership before you announce. The server owner can hand ownership to someone else in the server settings. Do it first, so the new leader is never locked out of the place the alliance talks.
Announce it in both places. Post it in alliance chat and in the Discord announcements, and say who to ask about what.
Stay reachable. The outgoing leader should be easy to ask for as long as the new one needs.
Questions people ask
Who decides what an R4 does? Your alliance does. Ranks tell you who can do what in the game; they do not tell members what an officer is expected to do each day. Write the duties down, so every officer works from the same list.
How many officers do we need? Enough that someone is around at your event times and when recruits apply. Add officers where you have gaps, not to fill a number.
How do we choose who becomes an R4? Use the same questions for everyone. The free R4/R5 promotion criteria generator builds a short list of criteria you can publish in advance.