Weekly CFB Workflow
Set the week, create the slate, prepare Discord, record results, and close out.
Before creating the week
- Confirm every approved member has the correct dynasty team.
- Confirm all required teams exist.
- Confirm conference assignments.
- Determine the current calendar year and dynasty week.
- Gather the full matchup slate, including byes.
Set season and week
- Open Administration → Games.
- Use the edit control next to Season.
- Enter/save the calendar year.
- Use the edit control next to Week.
- Select/save the intended week or postseason period.
- Confirm both values before creating games.
These values control the administration context and bot defaults.
Create the weekly slate
- Open Administration → Games.
- Create a single game or use the supported bulk-create flow.
- Select away and home teams carefully.
- Confirm each game’s season and week; leave both scores at zero until played.
- Mark the intended Game of the Week if applicable.
- Save.
- Review the public Games page for duplicates or reversed teams.
Prepare Discord
- Confirm member assignments.
- Confirm bot permissions.
- Choose channels or threads.
- Run
/cfbchannels create-gamesor/cfbthreads create-games. - Supply the correct week and naming options.
- Inspect every created space.
During the week
- Correct schedule mistakes before members use the game spaces.
- Share availability and agree on kickoff times in Discord game spaces.
- Update Game of the Week and let approved members pick winners before scores are entered.
- Add late-approved members and assignments before recreating access.
Record a result
- Open Administration → Games.
- Find the exact matchup.
- Open its edit/update control.
- Enter away and home scores.
- Save.
- Verify the public Games page and dynasty home.
A 0–0 game is unplayed. Any other score counts, including a nonzero tie; there is no separate completed switch. Reset both scores to zero to remove a result.
Close the week
- Confirm every final score.
- Review standings and records on dynasty pages.
- Update player season totals and publish the weekly Top 25 if your dynasty uses them.
- Delete or close weekly Discord channels/threads according to policy.
- Use Advance week (recommended), or edit Week to jump to any period.
- Create the next slate.
Recovery checklist
- Wrong teams: edit the game before deleting if possible.
- Duplicate game: confirm which record is unused, then delete the duplicate.
- Standings wrong: find missing/incomplete results.
- Private space missing a member: correct team assignment, then recreate or adjust the Discord space.
Postseason and next season
The default calendar is Week 0, Weeks 1–14, Conference Championship Week, Bowl Weeks 1–3, then Bowl Week 4 — National Championship. Week 0 remains available for the beginning of a season. These follow CFB’s terminology: EA’s Dynasty guide uses Conference Championship Week and Bowl Week 1; the community postseason calendar lists Bowl Weeks 1–4. The championship description makes the final period explicit.
Advance week follows this sequence. Commissioners may freely select another period or year, including moving backward to correct a mistake. Period names are standard, not customizable. Editing the current season/week does not move games; edit each game’s season/week to reassign it.
Existing Week 15 records remain Week 15. Commissioners decide whether to reassign those games to Conference Championship Week or a bowl period using Edit Dynasty Game. The recommended advance sequence skips legacy Week 15.
Use Start next season in Administration → Games to move forward one year to Week 0. It keeps teams, members and every previous game’s scores, votes and dates, and starts with an empty schedule and 0-0-0 records. A repeated stale request is rejected. If the next year already has games, select that year manually instead; the button never deletes an existing schedule.
Choose a Season in the public Games filters to view past schedules. Choose a Season above the home standings or in the Teams filters for that year’s W/L/T. Team names, conference assignments, members and manually assigned ranks remain current; historical W/L/T is calculated from games in the selected year.