Field Guide · The student lifecycle
From First Inquiry to Alumni, One Continuous Line
Students do not experience institutions as org charts. AI readiness has to account for handoffs across admissions, advising, registration, career, alumni, and beyond.
The student experiences one institution. The institution runs six. AI can finally connect them, but only if someone decides the student’s journey is a single thing worth owning.
Four weeks after graduation, a new alumna gets two emails on the same day. One, from the advancement office, warmly invites her to make her first gift as a proud graduate. The other, from the registrar, informs her that a hold on her account is preventing the release of her official transcript, which the employer who just offered her a job is waiting for. The hold is a $40 library fine from her second year. Nobody told her about it at graduation, because the library system does not talk to the graduation system, which does not talk to advancement.
She pays the fine. She does not make the gift. She also does not forget.
That is not a story about bad people or even bad offices. It is a story about an institution that is organized by function while the student lives it as a sequence. Recruitment hands her to admissions, which hands her to orientation, which hands her to advising, which hands her to career services, which hands her to alumni relations. Each handoff loses something: context, history, goodwill, sometimes a fact that mattered. The student has to re-introduce herself at every door.
The institutional question
Does your institution treat the student journey as one continuous relationship, or as a series of disconnected handoffs?
The last two issues looked at support and enrollment, each on their own terms. This one zooms out. AI is about to be deployed at every stage of the lifecycle, usually by a different office with a different vendor and a different idea of who the student is. Left alone, that produces six smart tools that do not know about each other, which is the old fragmentation made faster. Organized deliberately, it could produce something higher ed has rarely been able to offer: an institution that remembers you.
What this looks like in practice
Start with the seams, because that is where the value and the damage both concentrate. The moments that decide whether students stay and finish are disproportionately transitions: deposit to first day, first semester to second, the move into a major, the last term into a job. These are exactly the points where responsibility shifts from one office to another, and where nobody quite owns the student for a few weeks. An AI layer that carries context across those transitions, so the advisor knows what the admissions counselor learned and the career office knows what the advisor saw, does more for persistence than a smarter tool inside any single office.
That requires something unglamorous: the data has to connect. If the CRM, the SIS, the LMS, the degree audit, the career platform, and the advancement database each hold a separate version of the student, then each AI tool built on top of them inherits that fragmentation. This is not a problem the student journey can solve alone, and the operations stretch of this series will return to it. But it is the reason lifecycle ambitions so often stall. You cannot give a student one continuous experience on top of six disconnected records.
Onboarding is the stage where each dollar does the most good. The first thirty days shape whether a student believes they belong, and AI can now personalize that window in ways a stretched orientation team cannot: a different path for a transfer student than for a first-time freshman, a different sequence for a parent attending evenings than for a resident student, timely nudges about the deadline that actually applies to this student rather than a generic calendar. Done with care, onboarding stops being an event and becomes a guided month.
Career readiness is where the lifecycle meets the institution’s promise. Students and families increasingly judge an institution by what happens after graduation, and AI can connect the dots earlier than most career offices can staff: matching coursework and experiences to roles, flagging which skills a student has not yet demonstrated for the jobs they say they want, surfacing employer opportunities while there is still time to act on them. The trap is waiting until senior year. A career connection built across four years, or two, or however long the student is with you, is far more powerful than a résumé review in the final semester.
Alumni engagement is where most institutions reveal whether they actually believe in the continuous line. For many, the relationship after graduation is essentially a fundraising relationship, which is how the new alumna ended up getting a gift request alongside a transcript hold. The better framing is that the institution’s relationship with a graduate is lifelong and multi-directional: further learning as careers shift, mentoring for current students, employer connections, career support years later. AI that recommends the next credential to a ten-year alumna whose field is being reshaped is not a marketing tactic. It is the institution keeping its promise.
Underneath all of this is a governance question the institution has to answer on purpose: who owns the whole journey? On most campuses, no one does. Every office owns its stage, and the student’s experience across stages belongs to no one in particular. That is why lifecycle AI tends to arrive as six separate pilots. Somebody, a vice president, a cross-functional team, a named role, has to own the line from first inquiry to alumni, with the authority to make the offices share context and the standing to ask what the student actually experienced.
The Atlas connection
In Atlas, our AI operating map, this issue completes the Offense group — Serve — whose question is how we win, keep, and launch students. The group is the student journey drawn as four domains in order: Attract, Enroll, Succeed, and Launch & return, which is career, alumni, and lifelong learning. The last two issues covered the first three; this one adds the fourth and asks whether all four add up to one experience. The map puts them in a single group deliberately, so that no office can own its stage without seeing the line it belongs to. The connected records this needs come from infrastructure, data, and technology in the Capacity group — Run — which this series takes up next. And the next issue closes this part with advancement, which Atlas places in Run rather than Serve, because the question of whether the alumni relationship becomes a promise or stays a transaction is a sustainability question for the whole institution. If the Foundation group asked who decides and the Mission group asked what learning is now, the student journey asks a simpler question with a harder answer: does the institution remember who the student is?
Questions worth putting on the agenda
Best answered by enrollment, student affairs, career services, advancement, and IT in the same room, which is itself the point.
- Who owns the student’s journey from first inquiry to alumni, by name, with authority across offices?
- At which transitions do our students most often fall through, and does any AI tool we use carry context across them?
- How many separate versions of a student exist across our systems, and which AI tools are built on which version?
- When does career preparation actually begin for our students, and could AI help it begin earlier?
- After graduation, is our relationship with alumni mostly an ask, or is it a promise we keep?
The bottom line
The alumna with the transcript hold did not need a better fundraising email. She needed an institution that knew, on one day, both that she had just graduated and that something was standing between her and her first job. That is not a sophisticated capability. It is a connected one.
Students experience one institution. The work now is to become one.
Also published on LinkedIn: read this guide on the newsletter .