When the alliance spreadsheet stops scaling.

Spreadsheets are the universal first answer to alliance tracking, and for good reason. They're free. Everyone knows how to use one. They handle simple lists of members, simple tables of donations, simple records of attendance. For a 20-person alliance with one R5 doing all the tracking, a spreadsheet is genuinely fine.

The trouble starts when the alliance grows past the point where one R5 can hold the whole picture in their head, and the spreadsheet has to be the source of truth for multiple officers, multiple events, and multiple weeks of history.

Five patterns we see consistently:

• The retyping tax. Every event leaderboard gets retyped from a Discord screenshot. For a 50-person alliance running Marshal's Guard every two days, Alliance Duel daily, donations daily, and Desert Storm weekly, that's easily an hour a day of typing.
• Schema drift. Every officer who edits the sheet adds a column or shuffles a row. After three months the sheet has 14 columns, two of which everyone has forgotten the meaning of.
• Conflicting edits. Two officers editing at the same time. One overwrites the other. Nobody notices for a week.
• No history. “What was their donation rank in week six?” The sheet got cleared for week seven. The data is gone.
• No reminders. The sheet doesn't know what time DS starts. Members miss matches because nothing pinged them at 6pm.

For a 50-member alliance running the full event roster (Marshal's Guard, Alliance Duel, donations, Desert Storm, Zombie Siege, General's Trial), the typing tax alone is 5–10 hours per week of officer time. A serious R5 doing it themselves loses a working day every week. Splitting across R4s shifts the load but doesn't reduce it — and burns out R4s instead of R5.

Plus the indirect costs: members miss DS matches because no reminder fired, promotion debates drag because nobody can cite week-on-week donation history, and silent drift goes unnoticed because the spreadsheet doesn't flag a member who's been quiet for three weeks.

Concretely, here's what moves out of the spreadsheet into Last Command:

• Member roster. Profile per member, with power, role, attendance, hero builds, and absence flags. Searchable and filterable.
• Event leaderboards. Marshal's Guard, Alliance Duel, Zombie Siege, donations, General's Trial — all entered via the AI screenshot scanner, so the typing tax goes to zero.
• Desert Storm coordination. Sign-ups, roster, building assignments, attendance, results, and a running leaderboard.
• Train rota. Auto-generated weekly from the latest rankings (Pro), with manual day overrides.
• Officer Pulse. The weekly scorecard that surfaces who's carrying the alliance and who's drifting — without an officer having to compile it by hand.
• Diplomacy records. NAPs and treaties with other alliances, with expiry reminders.

A handful of alliances keep a spreadsheet for one or two specific things — usually a custom hero-build tracker with formulas the R5 has spent six months tuning, or a payout calculator for Desert Storm prize splits. That's fine. Last Command isn't trying to replace every spreadsheet ever; it's replacing the ones that exist because the alliance had no better option for tracking structured data over time.

The migration path most alliances take:

1. R5 creates the alliance in Last Command. Five minutes.
2. R5 imports the in-game alliance roster as placeholder members via the AI scanner. Every member exists in Last Command immediately, even before they've signed up.
3. R5 shares the invite link in the alliance Discord. Members sign up over a few days; their accounts merge into the placeholders an officer has been tracking.
4. For the next event cycle, run it in Last Command instead of the spreadsheet. Use the AI scanner to enter results from the in-game screenshot.
5. Archive the spreadsheet. Keep it as cold storage for historical reference; stop editing it.

Already have the data in the sheet? You don't have to re-type it. Download a free CSV template — roster, event rankings, or an all-in-one workbook — paste your columns across, and import your whole alliance with a preview of exactly what will be created before anything saves. No sign-up needed to grab the templates.

Most alliances we've worked with complete this in one week of normal use. The R5 reports their evening back.