EDHREC Publishes Step-by-Step Guide to Building a Regular Commander Pod
EDHREC published a step-by-step community guide to help players move from ad-hoc games to a steady weekly or biweekly Commander pod, with practical, in-person and organizational tactics.

EDHREC published a step-by-step community guide titled "How to Form Your First Regular Commander Pod," aimed at players who want to move beyond ad-hoc metagames and establish a consistent weekly or biweekly pod with practical guidance. The guide walks through organizing cadence, recruitment, rules, hosting responsibilities, and how to keep a pod sustainable over time.
The guide went live February 24, 2026, and frames the whole process around turning occasional meetups into predictable, repeatable play sessions that build relationships and a local metagame.
1. Decide your cadence and goals
Start by choosing whether your pod will meet weekly or biweekly, EDHREC framed the guide specifically for players aiming at those cadences so your choice should reflect time availability and local demand. State upfront whether the pod’s purpose is casual social play, competitive testing, cube nights, or a mix; that clarity prevents friction later. EDHREC emphasizes that cadence is the organizing axis: a weekly group needs stricter scheduling and rotation rules than a biweekly group.
2. Recruit a stable core
EDHREC’s guide stresses assembling a core group of committed players who understand the cadence and will show up regularly, because consistency beats size for a first pod. Look for players who have compatible expectations about politics, table talk, and winner etiquette; a reliable core reduces no-shows and schedule churn. The guide suggests prioritizing local players who can attend physically rather than relying on fleeting online acquaintances if your goal is a regular in-person pod.
3. Pick a dependable location and backup sites
Secure one primary meeting place and at least one backup; EDHREC points out that stability of venue is often the difference between a club that lasts a season and one that fizzles out. Choose locations with consistent table space, acceptable noise levels, and a predictable calendar (private home, community center room, or a game store with a standing booking). Make sure players know any venue rules in advance, food, drinks, hours, so logistics don't derail future meetups.
4. Agree on clear rules and a deck policy
The guide advises codifying the pod’s expectations: time limits, combat-trick etiquette, target rules, and whether dice or third-party proxies are allowed. Define a deck policy that handles problematic commander pairings, power-level expectations, and banned cards specific to your pod, EDHREC frames this as essential when moving from ad-hoc chaos to a repeatable weekly or biweekly schedule. Put the rules in a single message or document so new members can read them before their first game.
5. Set scheduling and absence policies
EDHREC recommends explicit scheduling mechanics: a shared calendar, a rotation of hosts who confirm the session 48 hours out, and a consistent start time. Decide how to handle absences (e.g., sub players, reshuffle, or reschedule) and whether players will be responsible for finding replacements. Having a simple “if you can’t make it, give 24 hours’ notice” guideline reduces the friction that kills recurring meetups.
6. Establish communication channels
Use one primary channel for scheduling and a secondary channel for side conversations; EDHREC’s guide recommends centralized communication to keep attendance and rules visible. Options include a Discord server, a group chat, or a shared calendar, pick whatever the group will actually use rather than what looks best on paper. Keep rule updates, metagame notes, and host responsibilities pinned so the group can reference them quickly.
7. Rotate roles and hosting responsibilities
To prevent burnout, EDHREC encourages rotating hosts, snack duties, and responsibilities like rule arbitration or coin-flip tie-breaking. When hosting rotates, venue availability and setup time distribute across the group, making weekly cadence sustainable for more people. A simple schedule (host A: week 1, host B: week 2) or a monthly rotation works well for biweekly pods and keeps ownership shared.
8. Track the pod metagame and adapt
The guide frames regular play as the chance to develop a local metagame, and it recommends keeping a lightweight record of frequently seen commanders, archetype imbalances, and recurring problems. Use a shared note or Discord channel to log problematic matchups or cards so the pod can make informed policy changes rather than reactive bans. Over time, this living record helps the pod evolve without surprises and preserves institutional memory as members come and go.
9. Build onboarding for new players
EDHREC highlights onboarding: when someone wants to join, give them the deck policy, cadence, and a quick rundown of common pod norms before their first game. Pair new players with a mentor or invite them to a designated “trial session” so they see the cadence and rules in action. Clear onboarding keeps new additions from unintentionally disrupting the rhythm you’ve worked to create.
10. Keep the culture intentional and revisit rules
Finally, the guide recommends revisiting your rules and cadence periodically, for example, every three months, to adjust to life changes, new members, or emerging play patterns. EDHREC frames this as part of moving beyond ad-hoc play: habits that form around a weekly or biweekly pod should be intentionally maintained and refreshed. Make rule reviews a short agenda item at the end of a session or a quick poll in your group chat.
- Keep documentation short and accessible: a single pinned message or document is easier to consult than a long wiki.
- Use simple scheduling confirmations (e.g., “Yes/No/Maybe by 48 hours”) to reduce late cancellations.
- Prioritize accessibility, clear directions to the venue and reasonable start times make regular attendance realistic.
Practical tips from the guide
EDHREC’s step-by-step framing turns the abstract idea of “starting a pod” into a practical checklist you can act on this week. If you want reliably scheduled Commander nights that build a local metagame, weekly or biweekly, the guide’s approach emphasizes predictable cadence, shared responsibilities, and written expectations as the foundations of a pod that lasts.
Know something we missed? Have a correction or additional information?
Submit a Tip

