Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the College Athletics edition of September 11, 2026

Vendor claimMixedUndated source

BYU project deck exposes the implementation work behind sports-video AI

BYU-hosted Data-Driven Athletics / Sports Research Institute project · Collegiate athletics · United States; Utah, including a reported Weber State case

Publisher
Data-Driven Athletics: AI Athletics & Outreach
Original publication
2026; exact publication date unknown
Source retrieved
2026-09-12
Read original source

What happened

The deck describes an implemented video-analysis pipeline and coaching interface, but does not establish causal athletic improvement.

Why it matters

Direct university-linked athletics development; includes outreach beyond college sport, which is not treated as collegiate evaluation.

Evidence and measured results

Appendix: 96.9% step-detection accuracy using stratified five-fold cross-validation. Main slides name MLP as best; appendix names HistGradientBoosting. A Weber State slide claims 13% boys' and 22% girls' top-speed increases over October–April without sample size, control or causal baseline.

Limitations and uncertainty

Operator evidence uses vendor-claim as the available category. Athlete-level validation split and independent replication are unreported. PDF screenshots failed; extracted text supported inspection. No injury-reduction conclusion is established.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-12; this does not change the original publication date. Labels below come from the analysis itself.

Sales

Role takeaway

The customer problem is the effort required to turn practice footage into usable feedback. Engage the coaching lead, athletics analyst, campus IT and athlete representatives. Ask which measurements influence decisions, how manual review performs today and whether existing camera workflows already suffice. A bounded engagement could validate one movement metric on authorized footage before adding advice generation. The value hypothesis is reduced preparation effort at acceptable measurement quality. Include annotation, correction and support costs in discovery. The deck does not justify promised speed improvements, injury prevention or a claim that a named institution is seeking a supplier.

Pre-sales engineering

Role takeaway

Treat this as a candidate architecture, not a validated product specification. Map approved video ingestion to a job queue, versioned outputs and a coach review interface. Check camera geometry, calibration, input rights and retention before processing. A proof of value should hold out athletes and sessions, compare against independently annotated video and report measurement error and correction time. Reconcile the conflicting best-model descriptions with an immutable evaluation manifest. Assess the advice layer separately using a coach-approved rubric. Select cloud, local or hybrid placement from institutional requirements; the deck does not establish a compliant deployment boundary.

Delivery

Role takeaway

An athletics analytics lead should own the pilot, with coaches adjudicating output quality and IT supporting deployment. Begin with a data inventory, consent and access review, annotation guidelines and a manual baseline. Train users to identify unusable video and record overrides. Proposed acceptance criteria include complete source-clip traceability, held-out errors within coach-approved tolerances, lower total review time and successful deletion tests. Review governance before expanding sports or adding sensitive health data. Document model changes and arrange support beyond student-project turnover. Risks include calibration drift, correlated training examples, unreviewed advice and apparent time savings erased by corrections.

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?

Reported stack includes FastAPI, PostgreSQL, Celery, Docker and video models, with a Claude coaching layer. Interpretation: validate measurement and generated advice separately.

Governance

Who approves, reviews and stays accountable for outcomes?

Freeze the evaluated model and dataset version before approving a coaching use; reconcile conflicting model descriptions.

Security and privacy

What data, permissions and controls need testing?

Restrict identifiable footage and prohibit secondary training without an approved purpose; test deletion across derived files.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Provide readable metric descriptions and train analysts to recognize calibration and annotation errors.

Procurement

What should contracts, pricing and exit terms secure?

Require data export, model-version documentation, maintenance ownership and full hosting costs before purchase.

Operating model

Which teams own the service once it runs?

Budget annotation, technical support and coach adjudication as ongoing service work.

What changed

Absent from all 217 canonical archive records scanned at offsets 0, 100 and 200, including URL and related-title checks. Newly archived historical evidence; no new-since-last-run publication or update to an existing resource is claimed.

Publication history

  1. 2026-09-11College Athletics · Issue 063 resources
Read preserved resource versions (JSON)

Stable resource ID: byu-athletics-video-api-project-update-2026