Admitted viewers read matchups; an authorized manager changes only unlocked slots.
Configured regular-season or applicable phase; a selected week without a matching projection source keeps forecasts unavailable.
HELP TOPIC // team
/lineups-locks-matchups-and-scoring · corpus 0.1 · verified 43c1c50
Lineups, locks, matchups, and scoring
Set the effective lineup before kickoff and read starter-only projections, AWAITING RELEASE, and final scoring honestly.
Sources
Who can use this answer.
Read the current gate
Team association, selected week, and current week/slot lock state control mutations; the matching projection source controls forecast visibility.
The label carries the consequence.
Upcoming, lineup-editable, lineup-locked, live-provisional, source-stale, degraded, final, corrected, bye, unavailable; a source-week mismatch or partial forecast is not a zero.
Use the runtime clock
Each player's kickoff and league timezone govern that slot.
Keep the right audience
Roster visibility follows league policy; projections are not private authority.
Take the next safe step.
- →
Open Team or Matchups and select the week you mean to inspect.
- →
Read the projection source/week label before treating a forecast as current; a mismatch leaves it unavailable.
- →
Read the starters-only projected total; the Bench disclosure is comparison context and never contributes to team score.
- →
Treat an em dash or partial/unavailable coverage as unknown, not zero; reread after the source refreshes.
- →
Before kickoff, use Team's Move / change or Start / replace control (or the transfer affordance when available) to place an eligible player in a starter slot.
- →
Save before kickoff and reread the saved lineup, lock, and scoring state.
- →
Use Matchups for provisional/final labels and reread after source change.
Know what changes.
What happens
Only configured starters contribute to matchup/team scoring; bench projections are comparison context and never inflate the starter total. Locked slots cannot be changed normally; closed weeks pin effective starters/results.
What can be undone
Unlocked Move / change and Start / replace controls can revise eligible destinations; kickoff locks the affected slot, and locked/final outcomes use commissioner correction.
What you should see
Local result names saved slot/player state and preserves week/team context; a projected total is numeric only when the selected week's required starter forecasts are known.
Keep context. Do not replay blindly.
Authorization, cross-week, lock, invalid-slot, and stale-state failures reject a lineup mutation; a projection-source failure, source-week mismatch, or missing forecast suppresses only the forecast, so a legal edit can still be saved, and unknown is never rendered as zero.
Return to Team or Matchups, inspect selected week, source week, lock reason, and last-success age, then retry only when available; use an eligible Move / change or Start / replace control before kickoff.
One concrete read.
Example: A selected week whose projection source names another week keeps projected totals unavailable, while a missing forecast for one starter leaves the total unknown and a bench forecast never adds to team score.
Runtime source: Roster config, schedule, lineup persistence, matching-week projection pool, stats ledger, matchup/correction state, and lineup movement processor.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.