ScholarKeep: Track applications, deadlines & success

Inspiration

ScholarKeep was born from a real and recurring problem. People around me, and even myself, often struggled to keep track of multiple applications. Questions like “Did I already apply?”, “When is the deadline?”, or “Which documents did I submit?” came up frequently. I saw missed deadlines, duplicate submissions, and lost opportunities. I wanted to build a simple system that brings clarity, organization, and accountability to this process.

What it does

ScholarKeep is a web application that helps users organize, track, and manage all their applications for opportunities in one place.

Key Functions

• Tracks applications: Users can monitor every application they submit and see its current status (e.g., pending, accepted, rejected).
• Manages deadlines: It helps users keep up with important dates so they don’t miss opportunities.
• Stores documents: Each application has its own space for uploading and organizing related files.
• Prevents duplicates: It reduces the confusion of not knowing whether an application has already been submitted.
• Supports review: Users can easily revisit past applications, especially when preparing for interviews or next stages.
• Tracks progress: It gives users an overview of how many applications they’ve made and their outcomes, helping them reflect and improve.

How we built it

I designed ScholarKeep as a web application focused on simplicity and usability. The core features include:

• Application tracking dashboard
• Deadline monitoring system
• Document storage per application
• Status updates and progress tracking

The system is structured such that each application becomes a record with linked attributes: Application = (Status, Deadline, Documents, Notes)

I focused on creating a clean workflow where users can easily input, update, and revisit their applications without friction. The goal was not just functionality, but clarity.

Challenges we ran into

• Defining scope: Avoiding feature overload while keeping the app useful
• Data organization: Structuring application data in a way that is both flexible and intuitive
• User flow design: Ensuring users can navigate without confusion
• Consistency: Maintaining a smooth experience across different parts of the app

At times, it was tempting to add too many features, but I had to stay disciplined and focused on the core problem.

Accomplishments that we're proud of

• Successfully designed and built ScholarKeep as a working end-to-end application tracking system.
• Created a centralized dashboard that helps users manage applications, deadlines, and documents in one place.
• Implemented a structure that reduces duplicate applications and missed deadlines, solving a real and common problem.
• Built a system that supports self-evaluation, allowing users to track their application success rate and improve over time.
• Focused on a clean and simple user experience, making it easy for users to stay organized without confusion.
• Turned a real-life problem into a practical, usable digital solution that improves productivity and accountability.

What we learned

Building ScholarKeep taught me several key lessons:

• Problem-first thinking: The best solutions come from real problems people face daily.
• User experience matters: Simplicity is more powerful than complexity.
• Iteration is key: Improving small features consistently leads to a strong product.
• Data organization: Structuring information properly makes retrieval and insights easier.

I also learned how to think beyond just building an app, to designing a system that helps users evaluate themselves.

What's next for ScholarKeep: Track applications, deadlines & success

ScholarKeep is more than a tracking tool—it’s a personal accountability system. By helping users monitor their application activity, it introduces a simple success metric:

Success Rate = Successful Applications/Total Applications

This allows users to reflect, improve, and approach future opportunities more strategically.

Built With

• googlestudio