←   Back to Projects
EducationDashboardWorkflowResearch

HCAP

A college application planning platform for homeschool families navigating an admissions process built entirely for traditional students.

HCAP is a planning platform for homeschool families navigating college admissions. Homeschool students face a structural disadvantage: the admissions process is built for traditional transcripts, structured course records, and standardized testing sequences. HCAP addresses this not by solving admissions itself, but by making the required artifacts manageable, with the transcript, the most feared document in the process, as the primary onboarding surface.

Role
Lead Product Designer
Timeline
10 weeks
Tools
Figma, FigJam
Team
Solo
Status
Concept / Portfolio project
Primary Users
Homeschool parents (primary), homeschool students (secondary)
Core Challenge
Reduce anxiety in a high-stakes multi-year planning process with no established template
WHY THIS PROBLEM MATTERED

The failure mode isn't ability. It's artifact format.

HCAP is a planning tool for families educating through high school at home and preparing for college admissions. Homeschool students face a structural disadvantage: the admissions process is designed for traditional school transcripts, standardized testing sequences, and structured extracurricular records that don't map to non-traditional educational paths. HCAP helps families translate their educational record into the artifacts admissions offices require.

Homeschool families preparing for college applications have no trusted, structured resource for building required artifacts: transcript, course records, activity logs, and standardized testing plans. The process is fragmented across spreadsheets, homeschool community forums, and generic college prep resources that don't account for non-traditional records. The dominant emotional state is not confusion. It is anxiety. Families understand what they need to do; they are afraid of doing it wrong with no reset and high consequences.

There are approximately 3.3 million homeschool students in the US. College application rates are significant and acceptance rates at selective institutions are comparable to traditionally schooled applicants, but only when application materials meet specific format expectations. A tool that structures the production of correct artifacts reduces the anxiety-driven avoidance that causes families to miss deadlines or withdraw applications. Avoidance is the primary failure mode, not lack of ability or preparation.

MY MANDATE

Design conditions.

No direct access to homeschool families as research participants; community forum analysis had to substitute for interviews. The product must serve families with widely varying curriculum choices. There is no standard course structure to template against without also building flexibility into every template. Most critically: the emotional register of the product matters as much as its functional completeness. A tool that feels bureaucratic or intimidating will be abandoned regardless of how well it solves the functional problem. Form and tone are functional requirements here.

WHAT SHAPED THE STRATEGY

Key inputs.

Review of admissions guidance materials from 20+ college admissions offices on homeschool-specific requirements. Analysis of homeschool community forums (HSLDA, Reddit r/homeschool) for recurring pain points across application cycles. Secondary research on homeschool student college outcomes and application patterns.

  • 01 Anxiety is the dominant emotional context, not confusion. Families understand what they need. They are afraid of producing it incorrectly. The design problem is anxiety reduction, not information delivery.
  • 02 The transcript is the most feared artifact. It is the highest-stakes document, the least templated, and the one with the most institutional variation in what admissions offices consider acceptable. It is also the first thing families avoid.
  • 03 Progress visibility across a multi-year timeline is critical. Families lose track of completion state across a 2–4 year process. The question "am I far enough along" is a persistent source of anxiety that no existing tool addresses directly.
KEY PRODUCT DECISIONS

Three decisions that shaped the system.

The transcript builder is not buried behind onboarding. It is the onboarding. The platform opens with a visual dashboard showing all four planning tracks (transcript, testing, activities, applications) so the full scope of work is visible immediately. Progress is the primary information layer, not tasks. The structural bet: families who can see their progress across a long horizon are more likely to continue than families who only see the next task. Completion visibility reduces the anxiety about falling behind more effectively than better task management does.

Progress as a first-class information layer, not a sidebar metric
Why
Families working across a multi-year horizon lose track of completion state. Making progress the primary visual feature of the dashboard addresses the anxiety about "am I far enough behind" before users have to go looking for it.
Alternative considered
Task list as the primary dashboard feature (standard productivity tool model: Notion, Asana pattern)
Tradeoff
Progress-first requires a more complex data model to calculate meaningful completion percentages for non-linear educational paths. Harder to build correctly, but matches the actual mental model of families navigating a long-horizon planning process more closely than a task list does.
UI consequence
Dashboard opens to a four-track progress view. Tasks are nested inside tracks, not surfaced at the top level. The visual hierarchy signals: you are here in the larger arc, then here is what to do next. The track completion state must be visually unambiguous at a glance.
Transcript builder as guided structure, not blank form
Why
A blank transcript form produces paralysis. The transcript is what families fear most. Presenting it as an empty document to fill amplifies that fear rather than reducing it. A guided builder with category templates gives families a structure to fill, not a white page to invent.
Alternative considered
Free-form text entry or a template download that families fill in independently
Tradeoff
Templates impose a structure that may not match every curriculum. It requires enough flexibility to avoid feeling like a mismatch for families with non-standard educational paths. The risk is that structure feels constraining; the benefit is that structure replaces the paralysis of starting from nothing.
UI consequence
Step-by-step builder with curriculum category defaults (core subjects, electives, extracurricular credits). Each category pre-structured but fully editable. Entry mode must feel more like completing a form than writing a document. The cognitive load difference is significant for anxious users.
Student task view as a separate daily planning layer
Why
Parents and students have different planning horizons and different tasks. Mixing them in one view produces irrelevant noise for both. A student-specific task layer surfaces only what the student needs to do today or this week.
Alternative considered
Unified parent and student task view, using one dashboard for the whole family account
Tradeoff
Requires role separation within a family account: a more complex account model and session management, but significantly cleaner task UX for each user. The account complexity is a real implementation cost; the payoff is a product that students will actually use rather than ignore.
UI consequence
Toggle between parent planning view and student daily task view within the same account. Student view is stripped to: next three tasks, upcoming deadlines, and one progress signal. The reductive information hierarchy for the student view is intentional and must not creep back toward the parent view's complexity.
SYSTEM WALKTHROUGH

Selected interfaces.

HCAPPlanning Dashboard: Four-Track Progress OverviewFour planning tracks visible at once, giving families a progress overview across the full application arc.
Planning Dashboard: Four-Track Progress Overview
HCAPTranscript Builder: Guided Category EntryStructured category templates replace the blank transcript form, reducing the friction of starting from nothing.
Transcript Builder: Guided Category Entry
HCAPTimeline View: Multi-Year Deadline ManagementDeadline visibility across a multi-year horizon prevents missed milestones during the application process.
Timeline View: Multi-Year Deadline Management
HCAPStudent Task View: Daily Planning LayerA focused daily view for students, separated from the parent planning layer to reduce noise and scope.
Student Task View: Daily Planning Layer
VALIDATION, RISKS, AND WHAT REMAINS UNPROVEN

What this proves and what it doesn't.

Validated
  • Anxiety-first product framing is appropriate for high-stakes planning tools, supported by research on avoidance behavior in high-consequence, long-horizon planning contexts.
  • Progress visibility as an anxiety reduction mechanism has precedent in behavioral psychology: completion visibility across long timelines improves continuation rates in habit and goal tracking research.
  • Guided transcript builders exist and are used; HSLDA and other homeschool organizations offer structured transcript templates, validating that families accept structured guidance over blank-form entry.
Still unproven
  • Whether the transcript builder would satisfy the specific format expectations of admissions offices across institutions; this requires validation with actual admissions officers, not community forum analysis.
REFLECTION

The hardest thing I learned.

I designed the function before I fully internalized the emotional register. The first version of the transcript builder was technically complete but felt like filling out a government form. The insight that this needed to feel like a first win, not a task, came late in the process. Product design for anxious users requires that every interaction either reduces uncertainty or confirms progress. Treating this as a purely functional planning tool missed the emotional contract the product needs to fulfill. The functional requirements and the emotional requirements are not separate specifications. They are the same specification expressed differently.

Other Projects