EdVisorly: Navigate - Transfer Credit Evaluation
Company
Role
Year
Overview
Navigate is an embeddable tool that lives on a university's transfer page. A student uploads their transcript and sees how their credits would transfer, before they apply. I redesigned the core evaluation flow across four stages and defined the white-label framework that lets the tool live inside any university's brand.
Problem
Transfer students get burned. They apply, get in, then find out half their credits don't count. Every transfer student has heard that story from someone, so they arrive at a tool like this already skeptical.
The existing flow made that worse. The review step showed every parsed course as an open input field outlined in the school's brand color, so correct data looked like a screen full of errors. On mobile, course cards scrolled sideways one at a time with the confirm button below the first one, meaning a student could confirm sixteen courses having seen one. And with no progress indicator, the question "how long will this take" sat unanswered on every screen.
The challenge was to design a flow that proves itself at every step, for a student looking for a reason to quit, while wearing a brand that isn't the product's own.
The white-label framework
Schools need it to feel like theirs. EdVisorly needs it to keep working everywhere.
Schools pick one color, used as an accent on buttons, links, and the active step. It never fills a surface. Brand color marks where you act; it doesn't paint the room.
Schools set the corner radius from a range, since some sites are soft and rounded and others are sharp and squared off.
EdVisorly protects layout, interaction patterns, form styling, and status colors. Error red never changes, because an error has to mean the same thing at every school.
Contrast is automatic. The school keeps their color, and the text flips to black or white, whichever passes.
What I learned
The temptation in a tool like this is to design the feature list. Upload, parse, review, send.
But Jordan doesn't care about parsing. She cares whether her credits will count, and whether she can believe the answer. Once I saw that, the decisions stopped being separate. The summary card, the honest flag on the uncertain course, the confirm button placed after the list, the email ask that comes after the work instead of before it. None of those are features. They're the same decision, made four times.
The white-label constraint taught me something too. The instinct is to treat brand customization as a color-picker problem. It isn't. It's about deciding what a school actually needs in order for the tool to feel like theirs, and what has to stay fixed for it to keep working everywhere. Color turned out to be the smallest part. Matching a school's corner radius did more for "this feels like ours" than any hex value.