A short agenda, a notice before and a summary after. Meetings end on time and everyone knows what was decided.
Most alliance meetings run long because nobody wrote down what they were for. An agenda fixes that. Below: one for your officers, one for a call with the whole alliance, the post to send beforehand and the summary to post after. Change the times and the brackets to fit your alliance.
Copy-ready
Officer meeting, 20 minutes
[TAG] OFFICER MEETING — [date], [time] [server time / UTC]
Chair: [name] Notes: [name]
1. Check-in (2 min): anything urgent? Who is away?
2. Last meeting's actions (3 min): done, not done, who has it now
3. Applications and roster (4 min): who applied, who is quiet, who needs a message
4. The next event (5 min): goal, jobs, times. Name one owner for each job
5. One problem (4 min): pick only one. Decide it or assign it
6. Actions (2 min): read back every action with a name and a date
Rule: if an item runs over, it gets a named owner and goes to chat. It does not eat the next item.
The chair keeps time. The note-taker reads back the actions at the end, out loud.
Whole-alliance call, 30 minutes
[TAG] ALLIANCE CALL — [date], [time] [server time / UTC]
Place: [voice channel]. Recording: [yes/no]. Listen-only is fine.
1. Welcome and thanks (3 min): new members, and one thank you by name
2. Where we are (5 min): results since the last call, in plain words
3. What is next (10 min): the plan and each person's part
4. Questions (10 min): taken in the order raised. Long ones go to chat
5. Close (2 min): the one thing to remember, and the next call date
Ground rules: one voice at a time, kind words, no blame for results.
Hold it at a time the most members can make, and post a short written version for those who cannot.
Notice before the meeting
[TAG] MEETING — [date], [time] [server time / UTC]
Who: [officers / everyone]. Where: [place].
It will take [20/30] minutes.
We will cover: [item], [item], [item].
Please send questions to [officer] by [time] so we can answer them.
If you cannot come, a summary will be posted in [channel].
Post it a day ahead, and again an hour before.
Summary after the meeting
[TAG] MEETING SUMMARY — [date]
Decided:
• [decision]
• [decision]
Actions:
• [name]: [what], by [date]
• [name]: [what], by [date]
Next meeting: [date, time]
Questions: ask [officer].
Post it the same day. A decision that is not written down is easy to dispute.
Keep the meetings short
Send the agenda early. Officers who have seen the items arrive ready.
One problem at a time. A meeting that tries to settle five arguments settles none.
Every action gets a name and a date. Without both it is a wish.
End on time. Members forgive a short meeting. They do not forgive a long one.
Questions people ask
How often should an alliance meet? As often as the work needs. A weekly officer meeting and a whole-alliance call only before a big event or a change is a common pattern, but your alliance sets its own. If a meeting has no agenda items, cancel it.
Do members have to join a voice call? No. Make the call optional and post a written summary, so members in other time zones or at work are not left out.
Who should chair? Someone who keeps time and stays calm. It does not have to be the R5, and rotating the chair can help the officers share the load.
Where do I keep the notes? In one pinned place that officers can find, for example a note in the officers channel. Update the same note each time.