In one sentence
The real planning question is rarely “What am I allowed to take?” It is “What combination gives me the semester I can actually carry?”
What Project Ardi showed
In Project Ardi, the practical priorities were consistent: students wanted to improve their grades, balance demanding semesters with easier classes when workload mattered, and find courses they would genuinely care about or enjoy. Easy-A language appeared in 19.2% of typed conversations, and those conversations ran 1.8 times deeper than the rest. The transactional opening often led to a richer planning discussion.
The job students are hiring planning to do
A degree audit answers an important compliance question: what is complete and what remains. A class search answers an availability question: what is being offered. Neither one, by itself, resolves the student's decision. Students still have to weigh progress against difficulty, time of day, work, health, finances, instructor fit, and the desire to take something meaningful.
That is why “easier class” should not be dismissed as laziness. It can mean a student is protecting a scholarship, pairing a requirement with a demanding lab, returning from a difficult term, or preserving time for paid work. Institutions need enough context to distinguish healthy load-balancing from avoidance without moralizing about either one.
- Show how each option advances a requirement or goal.
- Make workload and uncertainty visible without pretending they are exact.
- Let students express nonacademic constraints in ordinary language.
- Offer alternatives so the student can compare tradeoffs.
What a good planning conversation looks like
Deep engagement does not look like obedient acceptance. In the pilot, the strongest conversations included students supplying context, challenging a suggestion, changing a constraint, and checking the result. Those behaviors are evidence of agency. A system should invite them explicitly: What feels wrong? What are you optimizing for? What changed since your last plan?
The system also needs an honest stopping rule. Policy exceptions, distress, financial-aid consequences, disability accommodations, and other high-stakes circumstances require a human pathway. Planning technology is most useful when it prepares the student and the advisor with shared context, not when it impersonates institutional authority.
What institutions should measure
Completion of a schedule is not enough. A useful evaluation asks whether students understood why a choice fit, whether they compared alternatives, whether they could identify unresolved risks, and whether they arrived at human advising better prepared. Longer conversations are not automatically better; productive revision is more informative than message count.
Outcome measurement eventually requires institutional data and a comparison design. Registration completion, persistence, credit accumulation, and academic outcomes cannot be inferred from chat behavior alone. Product behavior can show how students deliberate. It cannot prove the educational effect of the choice.
Decision framework
Five questions to take into the room.
- 01
Begin with the student's objective, not the institution's menu.
- 02
Combine progress, workload, schedule, and interest in one view.
- 03
Explain the reason and uncertainty behind every suggestion.
- 04
Invite pushback and make alternatives easy to compare.
- 05
Escalate consequential exceptions and distress to a person.
Questions this note answers
- Why do students ask for easy classes?
- What makes an academic plan feel personalized?
- How should universities balance student agency and degree requirements?
- What should an AI planning conversation hand off to an advisor?
About the evidence
Project Ardi was one 44-day product pilot at CU Boulder with no comparison group. It measured conversations and product behavior, not academic outcomes. “2,000+” is Ardvarq's company-reported estimate of student users; 903 is the tracked conversation count. Read the research notes and study limits.