What an empty week, a missing team, an unsaved pick or an odd grade actually means.
The schedule feed has not delivered that week yet, so there is nothing to pick and nothing missing from your picks — the rows appear as the feed catches up.
What you are seeing: no game rows at all, and a short message in their place. It reads either No games this week, or Week 15's schedule isn't out yet with a line confirming that nothing is missing from your picks.
Why: games arrive from a schedule feed on its own cycle. Your pool's owner does not enter games and cannot add one, so a week that is still some way off often has none of its games in the app yet.
A pool that runs on only part of a season shows chips for its own weeks only. Weeks outside that range are not yours to pick, and opening one puts you back on a week the pool covers.
Part of the week has reached the app and the rest has not, so pick what is listed now and come back for the other games before they kick off.
What you are seeing: an amber banner above the games reading This week's schedule isn't final, with a count of how many of about how many games are posted so far.
Why: the app compares the games it holds for the week against a full week for that season and says so, rather than letting a thin slate look complete. The count reads N of about M, so treat the second number as an approximation.
A Confidence pool cannot be submitted until every game of the week is picked and ranked, so a week that is still filling in needs a second visit before it can be saved at all.
A team on a bye has no row at all that week — a bye is never drawn as an empty or greyed-out matchup, so there is nothing to pick and nothing has gone wrong.
What you are seeing: you scan the week for one particular team and it is nowhere in the list.
Why: the picks page draws one row per scheduled game. A team that is not playing has no game, so it has no row and no placeholder of any kind.
This is the most common false alarm on the picks page. An absent team is a bye far more often than it is a fault, and nothing you can do will make a bye row appear.
The picks page does not label byes anywhere, so it cannot tell you which teams are resting. The amber schedule banner is the signal to check: if it is showing, games are still arriving and the team may yet appear. If it is not showing, the week is as complete as the feed has it.
In a Beat the Spread or Pick 'Em pool a pick saves the instant you tap a team; in a Confidence pool nothing is saved until you press Submit Picks, even though the counters above the games already include unsaved picks.
What you are seeing: a pick you made is not there when you come back, or the page told you the week was complete and the pool disagrees, or a tap does nothing.
In Beat the Spread and Pick 'Em pools there is no submit step. One tap saves immediately, and the toolbar above the games reads auto-saved beside your count. If the count moved, the pick is stored.
In a Confidence pool a tap only stages the pick in your browser. The toolbar counter, the hero tile and the progress bar all count staged picks, so the page can read a full week and All picks complete with nothing saved.
The footer of the Confidence Ranking panel is the one place that tells you which it is. It reads Unsaved changes until you press Submit Picks, and Saved afterwards. Leaving the page with staged picks warns you first.
In a Confidence pool, a game that kicks off before you picked it makes that whole week impossible to submit. The panel footer reads Submission unavailable and the week is refused from then on. Autopick, where the owner has turned it on, is what prevents this.
The owner has taken the pool offline, so members land on a Pool Paused page and cannot pick until it resumes, and weekly winners stop being recorded meanwhile.
What you are seeing: opening the pool sends you to a Pool Paused page instead of the picks board, and the pool's badge reads Paused.
Why: pausing is an owner control. Only the owner can pause a pool and only the owner can resume it. A pool that has been created but not launched yet sends members to the same page.
The owner keeps full access while a pool is paused, and still sees a working picks board with an amber banner across it saying members cannot make picks. That is why an owner may not realise you are shut out. Ask them to resume it.
Weekly winners are not recorded while a pool is paused. Recording restarts when the owner resumes it, so a gap in the Winners tab during a pause is expected rather than lost.
Completed follows the whole season finishing, not your pool's last week. A pool that covers only part of a season keeps reading Active after its own final week has played out.
Other players' picks stay hidden until their game starts: a grey check mark means that person has picked, and the team they chose appears once that game is under way.
What you are seeing: on the Weekly Standings grid, other members' cells show a check mark where you expected a team name.
Why: the grid reveals a pick only once its game is live or final. The check mark is labelled Pick submitted, so you can see that somebody has picked without learning what they picked. Your own row is always visible to you.
The reveal is per game, not per week. Early games can be showing everyone's teams while later games in the same week are still covered.
Survivor pools have their own setting for this. The owner chooses whether picks stay hidden until each game kicks off, which is the default, or are visible as soon as they are made.
A pick graded as a loss when your team won is almost always the spread or the push rule rather than a fault, and decided results are recorded on a repeating pass rather than the second a game ends.
What you are seeing: your team won and your pick carries a red cross. Or a finished week still shows no winner. Or a game reads LIVE with no score at all.
Why a winning team can be a losing pick: in a Beat the Spread pool your pick is graded against the line rather than the scoreboard, and an exact push goes to the underdog's side. In Pick 'Em and Confidence pools grading is straight up, and a tied game is a push for both sides — no point, but still a pick you made.
Check the push rule before reporting a bad grade
Why a result can lag: live scores land on the picks page by themselves, and a flash tells you scores have been updated. Decided winners work differently — they are written once and kept, on an hourly pass plus immediately when a week's last game goes final. Give it a cycle before treating a gap as wrong.
Why a game can read LIVE with no score: a game counts as started as soon as any score arrives or its scheduled time passes. A postponed game therefore reads LIVE, shows no score, and stays locked until the feed moves its date. There is no postponed or cancelled status in the product.
A completed game you never picked is scored as a loss and stays in the denominator of that week's accuracy, so blanks pull the figure down rather than being skipped. The row turns amber and carries a NO PICK chip.
Recorded winners do not quietly change. Only a deliberate score correction by an administrator re-opens a week and recomputes it, and a correction of that kind can change who won.
Two defects are confirmed: the Season Accuracy tile on the Make Picks page always reads 0%, and saving your profile sends the welcome email again.
Both of these are ours rather than yours. Neither needs reporting, and neither means your account or your picks are wrong.
Where your real record and accuracy live
Both are known and being worked on. We are not putting a date on either, and this card comes down when they are fixed.
Short questions are usually answered on the FAQ. If yours isn't, send us a message and we'll take a look.