Weekly Alliance Leadership Checklist
The easiest way to reduce alliance admin is to stop rebuilding the process every week. Assign a small number of checks to predictable points in the week and keep the output in one shared place.
At the start of the week
Confirm the current member list, known absences and leadership cover. Review last week’s results before publishing rewards or selecting seats. Generate the first version of the train and event schedule early enough for members to raise conflicts.
- Update arrivals, departures and rank changes.
- Record final results from the previous week.
- Check cooldowns and eligibility.
- Publish the initial weekly plan.
Before major events
Confirm registrations, reserves, start time and any team-specific instructions. Avoid hiding important information in a long general announcement. Use one clear event post and link or repeat only the critical time and action.
During the week
Record substitutions when they happen, not days later. Check whether scheduled conductors or event leads are available inside the agreed window. Capture only exceptions that matter; routine success does not need a lengthy note.
At the end of the week
Complete the agreed performance records and identify repeated issues. Thank members for strong contributions and contact anyone requiring a private check-in. Prepare the result sources that feed next week’s schedule.
Share responsibility
The platform works best when R4 responsibilities are divided. One officer can own schedules, another events and another member reviews, while R5 retains oversight. Shared access prevents the process stopping when one person is unavailable.
Leadership checklist
- Member list and absences checked.
- Previous results finalised.
- Schedule published with times.
- Event registrations and reserves confirmed.
- Substitutions recorded.
- Repeated performance issues reviewed privately.