How to Track Commander Games, Win Rates, and Deck Stats

The practical answer

Start with the players, decks, winner, and table size. Add timing or turn details only when the group has a question for them. Most importantly, save the result before the cards go back into their boxes and the person with the spreadsheet goes home.

Questions players are asking

• How can our playgroup track Commander wins and losses?
• What should an EDH stats spreadsheet include?
• Can a Commander life tracker keep player and deck history?
• How do we include guests without asking everyone to create an account?

Anonymized PodLog data

• 186 games — Completed history: One anonymized group recorded 647 player-seats across nine months.
• 126 decks — Deck history: Deck-level records show why a player win rate alone is incomplete.
• 101 three-player games — Table mix: The same group also logged 81 four-player and four five-player games.

Anonymized sample from one rotating PodLog group, October 17, 2025 through July 10, 2026. No player, group, or deck names are used. The sample shows what consistent tracking can answer; it is not a benchmark for every Commander group.

Start with the argument you want to settle

“Who keeps winning?” is a good reason to track Commander games. So is “Do we actually have time for another?” Trying to record every spell, attack, and priority pass is a good way to make sure nobody records game two.

Pick the questions your group will enjoy answering. Player and deck records need a winner. Game-length questions need start and finish times. Turn-order questions need seats. A short complete record beats an ambitious one with three weeks missing.

• Required: date, players, decks, player count, and winner.
• Useful: starting seat, duration, final turn, and loss condition.
• Optional: threat votes, detailed turn timing, and notes about unusual endings.

Paper, spreadsheets, forms, and one shared screen

Paper and dice are hard to beat for speed. The catch arrives later, when a page full of life totals has to become a game record. A spreadsheet gives you complete control, but it usually gives one organizer a second job too. Post-game forms spread that job around, right when everyone is least interested in filling out a form.

A life tracker with history takes the opposite approach: save the players, decks, time, and winner from the screen already on the table. You trade some spreadsheet freedom for fewer missing nights. There is no perfect method. The winner is whichever one survives after the initial burst of enthusiasm.

Why I wanted the history inside the life counter

The awkward part was never calculating a win rate. It was capturing a clean result without turning game night into bookkeeping. That is why I built PodLog around one phone or tablet for the whole table instead of asking every player to install something.

Commander groups change from week to week. A regular misses a night. A friend borrows a deck. Somebody fills the fourth seat at the last minute. The organizer can add that guest by name, finish the game, and keep the seat in the group history without an account-creation intermission.

A percentage without games played is gossip

A 60% deck record can mean three wins in five games or thirty wins in fifty. Those are not the same story. Keep games played beside every percentage, separate draws from decisive results, and set a minimum before declaring a leaderboard winner.

Use the same honesty when sharing findings outside the group. Say how many games you counted and which dates they cover. If a field was optional, say how often it was filled in. Limitations do not ruin a good result; they tell the reader how much weight it can carry.

Where this leaves the table

If tracking creates homework after every game, the history will eventually lose. Capture a small, complete result while the table is already together.

Once that habit sticks, add the details your group is genuinely curious about. That is how 186 finished games become stories instead of rows nobody remembers entering.