A bizarre error in the NBA’s official injury reporting system has sparked confusion ahead of the Los Angeles Lakers vs. Milwaukee Bucks game at Fiserv Forum on Sunday, November 16, 2025. According to the 6:30 PM Eastern Time update on Saturday, Marcus Smart was listed as Out with a viral illness for the Los Angeles Lakers. But here’s the twist: Smart hasn’t played for the Lakers since 2023. He’s been a key guard for the Memphis Grizzlies since being traded from Boston on June 28, 2023. The error didn’t just slip through—it was broadcast on the NBA’s own CMS system, leaving fans, analysts, and even broadcasters scratching their heads.
How Did This Happen?
The NBA requires teams to submit injury reports twice on game days: once by 2:30 PM and again by 6:30 PM Eastern Time. The earlier 2:30 PM report on November 15 listed Smart as Questionable—still under the Lakers’ name. By 6:30 PM, his status changed to Out, but the team affiliation remained unchanged. That’s when things got weird. Journalist Carlos Yakimowich tweeted the initial update, and outlets like ClutchPoints and Sportskeeda ran with it, citing the Lakers’ roster. But Erikas Polockas of TalkBasket.net published a piece that same day titled, “Marcus Smart not surprised by Grizzlies’ current dysfunction,” clearly identifying him as a Grizzlies player. The discrepancy wasn’t a typo—it was a systemic mix-up.Why does this matter? Because the NBA’s injury report is more than a formality. It’s used by fantasy leagues, betting platforms, broadcasters, and even team medical staff. When a player’s team is mislisted, it creates ripple effects. Imagine a fan placing a bet on Smart’s minutes—or a coach preparing a defensive scheme based on the assumption he’s out—and finding out he’s actually playing for Memphis. The error isn’t just embarrassing. It’s potentially costly.
Who Is Marcus Smart, Really?
Born March 6, 1994, in Houston, Smart has spent his entire NBA career as a defensive pest and floor general. Drafted 17th overall by the Boston Celtics in 2014, he became a fan favorite for his grit, leadership, and relentless energy. After eight seasons in Boston, he was traded to Memphis in 2023 in exchange for draft picks and cash considerations. Since then, he’s averaged 8.4 points, 4.9 assists, and 1.8 steals per game, playing 31.2 minutes a night. He’s been a starter for the Grizzlies in 67 of 72 games this season.So why would the Lakers’ front office—or the NBA’s CMS—list him as one of their own? One theory: a data entry error during roster updates. The Lakers’ roster has changed dramatically since LeBron James and Anthony Davis were last healthy together. With Rui Hachimura and now Smart (falsely) listed as out, the Lakers’ depth chart looks even thinner. But Smart? He was active for Memphis just hours before the Lakers’ report was published, playing 33 minutes in a win over the Oklahoma City Thunder on Friday night.
The Real Lakers Injuries
Even if Smart wasn’t hurt, the Lakers are in trouble. LeBron James, 39, is out with right sciatica—a recurring issue that’s sidelined him three times this season. Rui Hachimura, 27, is out with a left calf strain, and the team’s new head coach, JJ Redick, is now managing a lineup with no true point guard and a depleted frontcourt. Redick, a former All-Star shooter turned coach, took over after Darvin Ham was fired in October. He’s now forced to rely on 21-year-old rookie Gabe Vincent and 36-year-old Austin Reaves to run the offense.The Bucks, meanwhile, are keeping Giannis Antetokounmpo’s status under wraps. While the NBA’s report doesn’t specify his availability, sources close to the team say he’s “day-to-day” with a mild ankle sprain. If he plays, it’s a major boost for Milwaukee. If not, the game becomes a battle of backups—and the Lakers’ injury chaos makes them even more vulnerable.
What’s the Bigger Problem?
This isn’t the first time the NBA’s injury reporting system has glitched. In 2021, a player from the Miami Heat was mistakenly listed as out for the Golden State Warriors. In 2022, a rookie from the Charlotte Hornets appeared on the Chicago Bulls’ report. But those were minor. This is different. Marcus Smart is a high-profile, All-Defensive Team-caliber player. His name being attached to the wrong franchise suggests deeper issues with data synchronization between team rosters and the league’s central database.The NBA’s CMS is supposed to pull directly from team rosters. So either the Lakers’ front office accidentally updated Smart’s status in their system (despite him not being on their roster), or the league’s backend system is pulling from an outdated roster file. Either way, the fix is overdue. Teams are spending millions on analytics and AI-driven injury prediction tools—but still rely on manual data entry for something as critical as injury reporting?
What Happens Next?
The NBA has not issued a public correction as of Monday morning. The game between the Lakers and Bucks went ahead as scheduled, with Smart playing for Memphis and the Lakers starting Reaves and Reaves again. The league typically corrects errors internally, but rarely acknowledges them publicly. Fans have already started memes: “Marcus Smart joins the Lakers… in the injury report.”But behind the jokes, there’s real concern. If this system can misidentify a star player’s team, what else is wrong? Are medical records being mislinked? Are salary cap calculations at risk? The NBA has a $10 billion media deal and global viewership—but its injury reporting system still runs on spreadsheets and human input. That’s not just outdated. It’s dangerous.
Frequently Asked Questions
How did Marcus Smart end up on the Lakers’ injury report if he plays for the Grizzlies?
The NBA’s injury reporting system, the CMS, pulls data from team rosters. It appears the Lakers’ front office accidentally submitted Smart’s status under their roster—likely due to a data entry error or outdated roster file. Smart was traded to Memphis in June 2023 and has been active there since. The league’s system didn’t auto-update the affiliation, leading to the error.
Was Marcus Smart actually injured during the Lakers vs. Bucks game?
No. Smart played 33 minutes for the Memphis Grizzlies in their game against the Oklahoma City Thunder on Friday, November 14, 2025, and was active for their game against the Indiana Pacers on Saturday, November 15. He did not play in the Lakers vs. Bucks game because he wasn’t on the Lakers’ roster at all. The illness listing was a false report.
What impact does this error have on fantasy basketball and betting?
Fantasy leagues and sportsbooks rely on official NBA injury reports to set lines and player availability. If bettors or fantasy managers assumed Smart was out of the Lakers’ lineup, they may have made poor decisions—like drafting a Lakers guard as a starter or betting against Lakers depth. While the NBA doesn’t void bets, the error could lead to complaints and calls for better system integrity.
Why wasn’t this caught before the game?
Broadcasters and media outlets often rely on the NBA’s CMS as the authoritative source. Journalists like Carlos Yakimowich and Sportskeeda reported the error because they trusted the official system. It wasn’t until independent sources like TalkBasket.net confirmed Smart’s actual team that the discrepancy became undeniable. The system lacks real-time cross-checking with official rosters.
Has this happened before with other players?
Yes. In 2021, a Heat player was incorrectly listed as out for the Warriors. In 2022, a Hornets rookie appeared on the Bulls’ report. But those were minor players. Marcus Smart is a two-time All-Defensive selection and a household name. This is the most high-profile error of its kind in recent memory—and it underscores how fragile the NBA’s data infrastructure remains.
What’s the NBA doing to fix this?
So far, nothing publicly. The league typically corrects errors internally without comment. But with the NBA’s new media rights deal and growing reliance on data-driven analytics, this kind of error is unsustainable. Experts are calling for an automated roster sync between team systems and the NBA CMS, with human verification steps before publication.
