Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the College Athletics edition of September 12, 2026

Vendor claimEmergingRecent

Morgan funds student-athlete support chatbot; benefits remain prospective

Morgan State University Athletics · Public university athletics · Maryland, United States

Publisher
Morgan State University Athletics
Original publication
August 27, 2026
Source retrieved
2026-09-13
Read original source

What happened

Morgan announces a $100,000 NCAA AASP grant for an AI chatbot supporting student-athletes, particularly freshmen and transfers.

Why it matters

Direct athletic-department athlete support and eligibility-navigation relevance. Newly archived background, not a post-last-run announcement.

Evidence and measured results

The planned service connects students with academic resources and personnel. Expected retention and eligibility benefits are prospective. No chatbot trial, sample, comparator, answer-quality measurement or operating cost is reported; the cited prior academic performance predates the initiative.

Limitations and uncertainty

Institutional promotional announcement, classified vendor-claim to distinguish operator assertions from evaluated evidence. The September 10 IT recap is not a new grant event. Exact award and launch dates are unknown.

Put this evidence to work

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

Sales

Role takeaway

Ask athletics academic-support leaders, compliance staff, IT and student representatives where students struggle to find timely help. Which questions recur outside office hours, which require a specialist, and how long does a successful referral currently take? A bounded engagement could define the approved information set and test one referral workflow with volunteer users. The value hypothesis is easier access to the correct person or resource. Funding is evidence of an initiative, not a purchasing opportunity or available services budget. Do not promise higher retention, improved eligibility, savings or fewer staff. Establish the existing support baseline and include review effort before discussing expansion.

Pre-sales engineering

Role takeaway

A read-only information assistant is a reasonable initial fit; autonomous record updates need separate justification. Prerequisites include authoritative content owners, document permissions, identity decisions and a working human handoff. Prototype source-linked responses in a sandbox and test outdated policies, conflicting dates, unsupported eligibility questions and wellness escalation. Use synthetic records to test cross-user disclosure and prompt injection. Compare approved cloud, local and hybrid designs on privacy, latency, maintainability and cost; the announcement selects none. Proposed proof of value should score correct referrals, severe answer errors, response delay and total staff handling time against the existing service. Developer copilots may help implementation but are not evaluated here.

Delivery

Role takeaway

Assign academic support as service owner, IT as operator and compliance as reviewer of consequential content. Inventory and version the approved knowledge base, prepare accessible orientation and rehearse handoffs before a limited pilot. Dependencies include counselor availability, content maintenance, privacy review and student feedback.

Proposed acceptance criteria
every critical eligibility test reaches an authorized reviewer; all sampled permission tests pass; users can complete key tasks with assistive technology; unresolved severe errors block release. These are proposed gates, not reported outcomes. Track referral completion, corrections and staff effort alongside adoption. Preserve a non-chat route and fund maintenance beyond the grant period.

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?

Begin with read-only retrieval over approved support information and a staffed referral route. Hosting, model, integrations and production status are unspecified; compare cloud, local and hybrid options only after mapping data flows.

Governance

Who approves, reviews and stays accountable for outcomes?

Academic-support and compliance owners should approve content and escalation rules. A generated answer must not itself determine eligibility.

Security and privacy

What data, permissions and controls need testing?

Minimize sensitive student and wellness data, separate support access from coaching access, and test retention, disclosure and malicious-input handling.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Test screen-reader and mobile access and preserve appointments and human help; budget content review and referral capacity.

Procurement

What should contracts, pricing and exit terms secure?

Require processing terms, exportable content and logs, model-change notification and a sustainable support budget. Grant size is not total cost or ROI.

Operating model

Which teams own the service once it runs?

Keep academic advice, eligibility authority and technical operation explicitly assigned; measure completed assistance rather than chat volume.

What changed

Absent from the full 247-resource archive checked at offsets 0, 100 and 200. Adds an athletics-specific support plan, distinct from the archived Morgan research-capacity collaboration. August announcement backfill; September IT recap does not establish a substantive update.

Publication history

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

Stable resource ID: morgan-athletics-aasp-chatbot-plan-2026