Simplifying High-Volume Admissions Review for BTT College
Overview
BTT College is a private career college offering healthcare-related programs. Every intake cycle, the admissions team receives 100–300 applications, each requiring document verification and a decision. The existing process had no shared workspace: admins opened applications one at a time, with no way to see status, flag missing documents, or act on more than one record at once. The project covered two connected pieces of work: an Admissions Admin System for the internal team reviewing applications, and a redesigned public-facing homepage and Open House landing page to support enrollment marketing on the front end.
Challenge
The challenge required turning a one-at-a-time review process into a structured, high-volume workflow admins could trust at speed.
No status overview: admins had to open each application individually to understand where things stood, making prioritization slow and manual
Missing documents weren't flagged anywhere in the list view, so admins wasted time opening records that weren't ready to review
No bulk actions; every application was processed one at a time regardless of complexity
Correction requests to students were unstructured, written from scratch each time with no templates or follow-up tracking
No confirmation step before irreversible actions like rejection, creating risk of accidental decisions at speed
No visibility into whether a student had seen or responded to a correction request without manually chasing
No way to resume a session after an interruption
Objective & Goal
Primary goal: Enable admissions admins to move through a high volume of applications quickly and confidently, reviewing documents, making decisions, and tracking status without losing context or missing critical information. Bulk actions and quick decisions need to feel effortless across an entire intake cycle.
Secondary goals:
Reduce decision friction by surfacing the most important application information (status, missing documents, program) without requiring admins to open every record individually
Support incomplete submissions gracefully, giving admins a clear way to request specific corrections from students without derailing the overall workflow
Build admin confidence at scale through status tracking, filters, and bulk actions that make it easy to know exactly where each application stands at any point
Process
Starting from the current-state pain points and the two personas, I framed the redesign as a set of testable hypotheses before moving into wireframes:
If we introduce a status-based dashboard with clear filters, admins can identify priority applications instantly without manually scanning the full list.
If we surface all documents and application details on a single review screen, admins can decide faster without switching between views.
If we add bulk approve and reject actions to the application list, admins handling 100–300 applications per intake can process similar cases significantly faster.
If we provide a structured "Request Changes" flow with pre-set correction categories, admins spend less time writing custom messages and students get clearer instructions.
If we show a document-completeness indicator on each application card, admins can skip incomplete submissions during peak load and return to them later without losing track.
If we add a confirmation prompt before irreversible actions like rejection, admins make fewer accidental decisions and trust the system enough to work at speed.
If we display a real-time status tracker per application, admins and students both have visibility into where things stand, reducing follow-up emails and back-and-forth.
From there, I mapped the end-to-end admin flow landing on the dashboard, filtering by status and program, opening an application, verifying documents, and reaching a decision (approve/request changes / reject) and designed the screens to answer each hypothesis directly: an Application Dashboard with status summary cards and status tabs for fast filtering, a Single Application view with decision buttons and per-document verification, pre-selected correction categories and pre-typed rejection reasons to remove custom typing, a confirmation step before approval/rejection, status-update notifications, and bulk operations for handling groups of similar applications at once.
On the front end, the same intake pressure showed up differently as a need to convert interest into registered applicants. I redesigned the BTT homepage and built a dedicated Open House landing page: a sticky nav CTA that keeps registration one click away at every scroll position; urgency indicators ("Seats Filling Fast") paired with real graduate outcome stats instead of a generic hero image; benefit cards addressing common hesitations (cost, time, value) side by side; testimonials pulled from BTT's own site placed immediately before the registration form to maximize intent at the highest-consideration moment; and a high-contrast registration section that reframes the form as a reward rather than a demand, listing free priority intake and an advisor session as tangible value.
Result
Redesigned the onboarding experience for a global CDN SaaS platform to improve user activation and retention. By simplifying the flow, refining plan categorization, and integrating customer segmentation, the redesign achieved 84% more direct purchases, 33% fewer inactive users, and a 78% boost in monthly revenue — proving the power of data-driven UX design in SaaS environments.
Learnings
Designing for two very different admin personas working the same queue — one optimizing for speed, one for thoroughness reinforced that a single interface can serve both if the defaults are fast but the detail is always one click away. Framing each design decision as a testable hypothesis (rather than a stylistic choice) made it easier to trace every dashboard feature back to a specific pain point instead of designing generically.
Additional learnings:
Bulk actions and single-record depth aren't in tension if the list view carries enough signal (status, completeness) to make bulk decisions safe
Structured, pre-set correction flows reduce admin effort and give students clearer, more consistent instructions than free-typed messages
On the marketing side, sequencing proof (stats, testimonials) right before the ask converts better than leading with it
You’ve seen the results now see
Figma File
I document everything in Figma the ideas, the iterations, the experiments.
Take a peek, it’s all there.
CLICK TO READ
How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights. How Delivery Hero streamlines marketing reporting across all their brands with Clarisights