A 30-day Total Battle clan leader checklist
Use this 30-day Total Battle clan leader checklist to set roles, preserve history, establish fair targets, plan events, and build a review rhythm.
A new leader does not need a rule for every situation on day one. The first month should create a trustworthy baseline, a clear division of responsibility, and a small review rhythm the clan can repeat.
Days 1 to 3: secure continuity
List the people who can change clan settings, manage the tracker, publish event calls, handle member issues, and step in when the leader is unavailable. Use named roles instead of a shared admin password.
Preserve current chest, roster, RSS, and tournament exports before changing tools or standards. Record the timezone used for resets and the last complete date in each source.
- Leader and backup leader named
- Superior responsibilities written down
- Current exports preserved
- Reset timezone confirmed
- Private credentials moved out of chat
Week 1: establish the baseline
Check whether collection runs are healthy, verify the active roster, and compare several member totals with the source record. Do not set penalties from data the team has not validated.
Review chest sources, RSS contributions, tournament participation, Might movement, and recent joins or departures. The goal is to learn the clan's normal range before deciding what must change.
Week 2: publish fair standards
Choose a small number of expectations that connect to a real clan need. Separate chest goals from RSS quotas and event participation. Explain the date window, resource mix, scoring, exceptions, and review time.
Show members where progress lives and how to ask for a correction. Handle personal exceptions privately, but keep the measuring rule visible to everyone.
Week 3: run one event cycle
Choose one tournament or custom Clan Event and publish the objective, start time, checkpoints, and finish rule. During the event, watch pace and recent movement instead of waiting for the final board.
Afterward, compare the call with the result. Note which message changed participation, which members were close to the next threshold, and whether the chosen checkpoint cadence was useful.
Week 4: make the rhythm repeatable
Hold a short leadership review in the same order each week: collection health, roster movement, chest pace, RSS pace, tournament participation, member follow-up, and the next event window.
Remove reports nobody used. Assign each remaining action to one person with a date. The month is successful when the clan can repeat the routine without the leader rebuilding it from memory.
- One weekly review time
- One source for each metric
- One owner for each follow-up
- One public progress view
- One export and recovery routine