From the College Athletics edition of October 7, 2026
Wake Forest women's basketball adopts ShotTracker Pulse and Scout for live bench analytics and natural-language film queries
ShotTracker / Wake Forest University Women's Basketball · NCAA Division I basketball performance analytics and scouting (ACC) · United States (Winston-Salem, North Carolina)
- Publisher
- ShotTracker
- Original publication
- October 7, 2026
- Source retrieved
- 2026-10-08
- Event date
- 2026-10-07
What happened
ShotTracker announced on Oct 7, 2026 that Wake Forest women's basketball will use Pulse, which ingests live broadcast feeds and delivers synchronized analytics and video to the bench during games, and Scout, which lets staff query performance data and film by natural language or voice. An assistant coach said the platform supports a more data-driven approach. ShotTracker says it is used by more than 100 organizations across 20 NCAA conferences. No accuracy, usage or outcome data is given.
Why it matters
Why now: announced the day of this edition, it is a concrete example of conversational AI moving onto the bench during live competition, beyond back-office content drafting. Interpretation: in-game use raises questions about latency, broadcast-feed rights and whether answers can be checked before they inform decisions.
Evidence and measured results
Vendor press release dated Oct 7, 2026 with one coach quote. Describes features only. No model, accuracy testing, query examples, error handling or results.
Limitations and uncertainty
Vendor press release; no performance data; one program; vendor customer counts are self-reported.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Basketball staffs want faster access to stats and film during games and scouting, but analyst time is limited.
- Stakeholders
- Head coach
- Assistant coaches
- Video coordinator
- Director of basketball operations
- Athletics IT
- Discovery questions
- What questions do staff ask of film and data during games?
- How quickly is an answer useful on the bench?
- How will staff check an answer is correct?
- What do conference rules allow on the bench?
- Value hypothesis
- A natural-language query tool may cut time to find relevant clips and stats, if answers are accurate and linked to source video.
- Potential engagement
- A practice-season pilot evaluation of query accuracy, latency and staff adoption for one program.
- Unsupported claims
- Improved game outcomes
- Measured query accuracy
- Time savings figures
- Use across all 100-plus customers
Pre-sales engineering
Role takeaway
- Fit
- Programs with tracking data, broadcast or film access and a video staff.
- Architecture and integration
- Live broadcast ingest synchronized with tracking and play data; natural-language and voice query layer over data and video.
- Prerequisites
- Broadcast feed access
- Reliable venue connectivity
- Tagged play data
- Constraints
- Conference rules on in-game technology
- Away-venue connectivity
- Broadcast rights
- Security
- Limit vendor access to scouting data; prohibit cross-customer use; log queries.
- Proof of value
- Answer correctness on a fixed question set
- Feed-to-bench latency measured at venues
- Clip citation for every answer
Delivery
Role takeaway
- Work
- Operate the live analytics and query tools as a supported game-day workflow with fallbacks.
- Dependencies
- Vendor support
- Video staff
- Venue network
- Ownership
- Director of basketball operations or video coordinator.
- Skills and adoption
- Train coaches and video staff to phrase queries and verify answers against clips.
- Governance checkpoints
- Conference rule check before first game
- Broadcast-rights confirmation
- Season-end usage and accuracy review
- Acceptance criteria
- Proposed: at least 90% of test queries return correct, clip-linked answers before game use
- Proposed: documented manual fallback used whenever the feed fails
- Risks
- Wrong answers acted on under time pressure
- Connectivity failures at away games
- Scouting data exposure
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Live broadcast ingest synchronized with tracking and play data, with a natural-language query layer over data and video. Interpretation: in-game reliability depends on feed latency and connectivity at venues, and answers from a query layer need links back to the underlying clips so staff can verify them.
Governance
Who approves, reviews and stays accountable for outcomes?
Programs should check conference rules on in-game technology on the bench and confirm rights to ingest and store broadcast feeds.
Security and privacy
What data, permissions and controls need testing?
Scouting data and film are competitively sensitive; vendor access, retention and cross-customer data use should be contractually limited.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Shifts some analyst lookup work to coaches through natural language; video staff become tool operators and verifiers.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should address data ownership, broadcast-feed rights, uptime during games and cross-customer data use.
Operating model
Which teams own the service once it runs?
Bench decisions gain a live data channel, which needs a named operator and fallback procedure.
Publication history
- 2026-10-07College Athletics · Issue 314 resources
Stable resource ID: wake-forest-wbb-shottracker-scout-pulse-2026-10-07