When Are NBA Starting Lineups Announced Before Tip-Off?

The starting-lineup rule sets an obligation to supply the scorers with the names and numbers of the players who will begin the game. Its reference point is the scheduled start. This is a submission rule inside the game’s administration, not a promise about the precise time a public website, search result or third-party feed will display those names.

A reader should therefore separate the event described by the rule from the evidence available on a page. A clock reaching thirty minutes before tip-off does not prove that this site has obtained the lineup. Confirmation needs an actual source containing the starters. If that source has not arrived, the page should remain Pending or Projected according to what evidence it does have.

The rule also states that a failure to comply is reported to the League Office. That wording should not be expanded into an invented automatic penalty, a guarantee about a public-feed delay or a claim about why a particular coach has not appeared in a data service. The site’s job is to report what its source supports.

Submitted describes the names being provided to the scorers. Published describes those names becoming available in a source a reader or data service can access. Those events may be close together, but they are not the same event. A source can also publish a projection before either event, which is why a lineup badge is more useful than an unlabeled list of familiar players.

This website uses Confirmed only for a named source listing the opening unit. The source timestamp needs to accompany the selection so that a reader can understand what version is being shown. A more recent page-render time cannot replace the source time. Rebuilding a static page is a publishing operation, not new evidence about the coach’s decision.

There is no starter feed operating in this preview. A game page can still show a verified schedule and venue, but its player slots remain Pending. That separation is intentional: useful game information should not be withheld just because starters are unknown, and unknown starters should not be filled simply to make the card look complete.

Consider a scheduled game whose page lists a plausible five in the afternoon. If that list is based on recent starts, it is a projection. Later, a report changes one player’s availability. The projection may change, but the revised list is still a projection unless an actual starter source has been obtained. Finally, a source identifies the opening unit. Only that final evidence supports a Confirmed badge. The sequence illustrates why one timestamp and one unlabeled list cannot describe every stage of the process.

An injury report can restrict the set of plausible starters without identifying the final five. An Out entry provides participation information for a specific matchup; it does not name the replacement. Available means that the report does not rule the player out in that version, but the coach may still choose to begin with a different unit.

A projection should use the report relevant to the game being discussed. A historical file from another month cannot safely be copied onto a future fixture, even when the roster contains the same player. A team-level missing submission is another coverage issue: it should remain visible rather than being summarized as no injuries.

Timing matters because a later file can change the availability context. A supported projection may need revision after a Questionable player is declared Available or Out. The revision should identify the source change and retain the Projected badge until the actual opening unit is sourced. A changed injury status and a confirmed replacement starter are separate pieces of evidence.

A source mismatch can be subtle. A report may cover several upcoming dates, while a team page may be displaying only its nearest imported fixture. A correct player name is not enough to join those records. The pipeline needs the game identity, team and report context as well. The public page should then expose enough of that context for a reader to understand the association. If the match cannot be verified, the player’s availability should remain unknown for that fixture rather than inherit the nearest-looking record.

The intended method combines recent verified starters, the rotation and the relevant availability report. A recent starting role provides a useful baseline, while roster and minutes context can help identify plausible alternatives. Every input must refer to the right team and season. A model cannot repair a stale roster by guessing where a player moved.

The depth-chart view on this site currently groups source roster positions alphabetically. It is not the planned last-ten-game ranking, and its first listed player should not be read as first string. Broad G and F position labels remain broad when the source does not supply a more specific role. That protects the distinction between source information and a site calculation.

No prediction accuracy percentage is claimed for this preview. There is no published history of evaluated projections or running automated model behind the Pending cards. When a projection pipeline is available, its assumptions, source window and comparison method need to be documented. Until then, an empty supported-data state is more useful than a plausible-looking lineup with no evidence.

Evaluating a projection also requires a stable target. The opening five recorded for a game is not the same as the five players with the most minutes, the closing unit or a frequently used combination during the game. A model that predicts starters should be checked against starters. Minutes-based context may inform an estimate, but it should not redefine the thing being predicted after the result is known. Keeping the definition fixed makes any future accuracy report interpretable instead of merely impressive-looking.

The planned schedule is to check starter sources every ten minutes from ninety minutes before tip-off through the start, followed by a final verification pass when the source contains the opening unit. This is a site publishing plan. It is not a claim that the league releases a new lineup every ten minutes, nor that the current preview is performing those checks.

A check can return unchanged information, incomplete information or no usable source. Those outcomes should not all display the same green updated badge. The source timestamp and the check state serve different purposes: one identifies the evidence being shown, while the other describes whether a retrieval attempt succeeded. The current preview does not display a fabricated live-check history.

If a source fails, the safe publication behavior is to keep the last known information clearly dated or show a missing-source state. A failure should not silently erase a player or switch a projection to confirmed. A user comparing two versions needs to know whether a name changed, a status changed or only the page was rebuilt.

The final verification pass serves a different purpose from pregame checking. It can attach the recorded opening unit to the dated document and preserve the result as archive evidence. It should not erase the distinction between what was projected before the game and what became known later. A publication system that retains versions can explain a correction or a prediction change without rewriting history. That behavior is planned; the current snapshot does not claim to have stored a live sequence of pregame decisions.

A loaded schedule can support tomorrow’s fixture page before a reliable starting projection exists. The date, opponents, venue and tip-off time belong to the schedule layer. A starting unit belongs to the later selection layer. A page existing at a future date is not evidence that the five has been chosen.

The dated pages in this preview show the imported fixtures and mark unknown player information as Pending. They retain their game date instead of silently rolling forward when the visitor reloads. A future live home page can select a current basketball day in ET while the dated documents continue to preserve their own context.