From the Student Success edition of October 5, 2026
Tyton Driving Toward a Degree 2026: advisors at four-year publics carry 339 students; 21% of advisors use AI daily, and built-in AI in campus systems sits largely unused
Tyton Partners (anchor partners Lumina Foundation and Riipen; research partners UERU, NACADA, PeopleGrove, Stellic) · Higher education advising and student support operations / AI-augmented advising · United States (1,200+ staff at 750+ colleges and universities)
- Publisher
- Tyton Partners
- Original publication
- Released 5 October 2026 (survey fielded May–July 2026)
- Source retrieved
- 2026-10-06
What happened
Survey of 1,200+ administrators, advisors and frontline support staff at 750+ U.S. institutions (May–July 2026). High caseloads were the top barrier to improving advising for the sixth straight year (40%), with limited budget second (34%). Four-year public advisors average 339 students, up from 297 in 2024, and 35% of four-year publics expect support budgets to shrink. About one in five advisors (21%) use AI daily; they are the most strained (59% call their caseload unmanageable vs 46% of peers). Seven in ten staff would adopt an AI tool that improves student outcomes even if it changed their practice, and preference for a blended human–AI model rose to 42% from 32% in 2025. Across six core student-success systems (e.g., CRM, SIS, portal), 58% to 76% of respondents do not know whether their systems have built-in AI, and active use ranges from 2% to 7%. On career readiness, 84% of institutions offer job fairs but 23% rate them among the most impactful, and about 5% have a centralized employer-partnership strategy.
Why it matters
Released today. It gives the operating-capacity backdrop for AI in advising: caseloads are rising, budgets are flat or falling, and advisors adopting AI are doing so out of strain. The finding that built-in AI in already-licensed CRM/SIS/portal systems goes unknown and unused is a direct procurement signal.
Evidence and measured results
Cross-sectional survey of institutional staff; descriptive percentages and year-over-year comparisons from Tyton's annual series on the public release page. Staff perceptions, not student outcome data. Full report is behind a download form and was not inspected.
Limitations and uncertainty
Staff self-report; respondents may be skewed toward engaged institutions; sponsors and partners include vendors (Riipen, PeopleGrove, Stellic); no outcome data; the willingness-to-adopt figure is hypothetical; full report not inspected because it is form-gated.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Advisors face rising caseloads and flat budgets, while AI features in systems the institution already licenses go unknown and unused.
- Stakeholders
- Dean or AVP of advising
- CIO / enterprise applications
- Career services director
- Procurement
- Advisor representatives
- Discovery questions
- What is your current advisor-to-student ratio and its trend?
- Which AI features exist in your CRM, SIS and portal contracts, and are any enabled?
- What topics get crowded out of advising meetings?
- Value hypothesis
- Enabling and training staff on AI already licensed may free advisor time for higher-value conversations at lower cost than new tools; size of benefit unknown.
- Potential engagement
- License and workflow audit plus a one-term pilot of existing AI features with a volunteer advisor cohort.
- Unsupported claims
- Measured caseload reduction
- Retention or completion gains
- That advisors will adopt without training
Pre-sales engineering
Role takeaway
- Fit
- Institutions with modern CRM/SIS/portal platforms that include optional AI capabilities.
- Architecture and integration
- Existing CRM/SIS/portal AI features → advisor workflow (registration, scheduling, triage) → logging to IR for time and routing metrics.
- Prerequisites
- Feature inventory across student-success systems
- Privacy and contract review of AI features
- Advisor training plan
- Constraints
- Vendor-controlled AI features and data terms
- Advising notes as sensitive records
- Survey evidence only
- Security
- Review data residency, model-training terms and audit logging for each AI feature before enabling it.
- Proof of value
- Advisor time per routine task before and after
- Routing accuracy for student questions
- Share of meeting time spent on career and financial topics
Delivery
Role takeaway
- Work
- Inventory features, select pilot features, train a volunteer advisor cohort, and track time and meeting-content metrics for one term.
- Dependencies
- Vendor cooperation on feature enablement
- Advisor participation
- IR support for metrics
- Ownership
- Advising leadership with enterprise applications.
- Skills and adoption
- Role-specific AI training for advisors, named by Tyton as a prerequisite for AI that works.
- Governance checkpoints
- Contract and privacy review before enablement
- Student voice in AI policy
- End-of-pilot review before scaling
- Acceptance criteria
- Defined reduction in advisor time on routine registration tasks
- Share of meetings covering career or financial topics rises versus baseline
- Advisor satisfaction with tools above an agreed threshold
- Risks
- Enabling features without privacy review
- Training underfunded
- Mistaking staff willingness for proven value
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?
Before adding AI products, map AI features already present in CRM, SIS and portal contracts and decide which to enable, integrate, or switch off; advisor-facing AI should reduce registration and scheduling load first.
Governance
Who approves, reviews and stays accountable for outcomes?
Tyton points to clear policy, student voice in policy, role-specific training, and trusted data as prerequisites; enabling dormant vendor AI features should go through the same review as a new purchase.
Security and privacy
What data, permissions and controls need testing?
Dormant AI features in student systems may process advising notes and records once switched on; review vendor terms, data residency and logging before enabling.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Advisor strain and rising caseloads are a workforce risk; Tyton's companion Listening to Learners page, citing this survey, says advisors name staff training, not skepticism, as the top barrier to broader AI use.
Procurement
What should contracts, pricing and exit terms secure?
Audit existing licenses for unused AI capabilities before new RFPs; require vendors to show adoption and outcome data rather than feature lists.
Operating model
Which teams own the service once it runs?
Use AI for routine registration and scheduling so advising meetings (20 to 30 minutes on average, per the companion Listening to Learners report) can cover career and financial topics; pair any AI rollout with the role-specific training Tyton names as a prerequisite.
Publication history
- 2026-10-05Student Success · Issue 294 resources
Stable resource ID: tyton-driving-toward-a-degree-2026-advising-ai-20261005