Commissioner Roster Lock Policy: Should Lineups Lock by Game or by Week?
A roster lock policy is a fairness rule, not a platform footnote: it decides whether managers win by reacting to current news or by committing to one full-week lineup before the first kickoff. There are two common approaches, and the choice has real strategic consequences. Under individual game lock, each player locks at the kickoff of his own game, so a manager can keep swapping players whose games have not started yet, even mid-week. Under weekly lock, the entire lineup locks at the start of the week’s first game, so all decisions must be made up front. Neither is wrong, but they reward different things — individual lock rewards active, informed managers who react to news, while weekly lock rewards locking in a plan and removes a late-week advantage. The lock policy is a setting many commissioners never think about, but it shapes the league’s strategy and fairness.
Setting a Roster Lock Policy
| Lock option | What managers can change | Best fit | Risk to manage |
|---|---|---|---|
| Individual game lock | Any player whose game has not started | Competitive leagues with active managers | Late news favors managers who can monitor Sunday morning reports |
| Weekly lineup lock | Nothing after the first weekly kickoff | Casual leagues or office pools | Injuries after Thursday can create unavoidable zeroes |
| Hybrid clarity rule | Platform default plus written exceptions | Leagues with occasional manual rulings | Managers assume exceptions exist when none were published |
| Midseason change | Avoid except for platform error | Rare emergency correction | Changing lock rules after lineups were built damages trust |
The two main lock options:
How each works: (1) individual game lock (player lock) — each player locks at the kickoff of his specific game, so a manager can change any player whose game has not yet started, including making swaps on Sunday morning, Sunday afternoon, and even into Monday night for players in later games; this is the most common modern setting; (2) weekly lock (kickoff lock) — the entire lineup locks at the start of the week’s first game (typically Thursday night), so every lineup decision must be finalized before any games are played, and no in-week swaps are allowed; (3) the practical difference is how much in-week maneuvering a manager can do — individual lock allows reacting to inactives and news as the week unfolds, while weekly lock forces a single up-front commitment; (4) most platforms default to individual game lock, but weekly lock remains an option some leagues prefer.
The strategic and fairness trade-offs:
What each rewards: (1) individual game lock rewards active management — managers who monitor inactive reports and game-time decisions can swap out a player who is ruled out for one whose game starts later, which rewards engagement and reduces zeroes from surprise inactives; the trade-off is that it advantages managers with the time and attention to work the slate all week; (2) weekly lock rewards planning and levels the playing field — everyone commits up front, so no one gains an edge from late-week swaps, which some leagues see as fairer and truer to “set it and forget it,” but it punishes managers when a player is unexpectedly ruled out after lock; (3) individual lock can create a perceived advantage for late-game players, since a manager can stream decisions across the slate, while weekly lock removes that; (4) the choice reflects whether your league values active management or up-front commitment.
How to choose and publish the policy:
Making the decision: (1) match the policy to your league’s competitiveness — a serious, engaged league often prefers individual game lock because it rewards skill and reduces avoidable zeroes, while a casual league may prefer weekly lock for simplicity and fairness; (2) consider how it interacts with inactives — individual lock lets managers avoid starting a surprise inactive, which many see as a feature, so leagues that want to minimize bad-luck zeroes lean toward it; (3) be consistent and clear, since the lock policy affects every lineup decision all season, so it must be set before the season and not changed mid-year; (4) publish the exact lock rule in your league rules (see our league rules guide) so managers know precisely when their decisions are final.
Worked Example: The Late Inactive
Two managers start the week with questionable players. One player plays in the Thursday game, while the other is a Sunday afternoon starter who is ruled inactive during the late-morning report. In an individual-lock league, the Sunday manager can move that player to the bench and use a later-game reserve. The Thursday player was already locked once his game began, so no retroactive change is available. That outcome is not favoritism; it is the chosen setting doing what it was designed to do.
In a weekly-lock league, both managers would be stuck with whatever lineup was submitted before the first kickoff. The Sunday inactive becomes part of the risk of the format, just like a Thursday injury would be. This may feel harsh, but it is fair if every manager knew the policy before the season and built habits around it. The real problem is not which model you choose. The problem is choosing one model in the platform and describing another in chat.
Common mistake: treating roster lock disputes as judgment calls instead of setting calls. If the platform and written rules say individual game lock, the commissioner should not manually rescue a manager from a late inactive just because the matchup is important.
Before Week 1, post the exact lock language in one sentence: “Each player locks at his scheduled kickoff” or “all lineups lock at the first game of the fantasy week.” Then add the one operational note managers actually need: platform timestamps control. That short policy prevents most Sunday morning arguments because the commissioner can point to a rule, not a personal preference.
For the broader setup framework, see our commissioner league setup guide and commissioner tips hub. Start at the commissioner hub for all resources.