Inspiration

Many students don’t fail because they don’t study—they fail because they realize problems too late. Burnout, poor time allocation, and hidden weak subjects often appear only days before exams, when stress is already high and options are limited. We were inspired to build ExamShield after noticing how common last-minute panic and academic burnout are among students worldwide. We wanted a solution that acts as an early-warning system, not just another study planner.


What it Does

ExamShield predicts academic failure risk and burnout before exams happen.
Students enter their subjects, exam dates, daily study hours, missed study days, topic difficulty, and stress level. ExamShield analyzes this data and outputs:

  • Academic risk level (Low / Medium / High)
  • Burnout probability
  • Subject-wise weakness insights
  • Clear, actionable prevention recommendations

The goal is to help students fix problems early, not react when it’s too late.


How We Built It

We designed ExamShield as a lightweight, beginner-friendly web application focused on clarity and usability.

Tech stack:

  • Frontend: HTML5, CSS3 (Flexbox & Grid), JavaScript (ES6)
  • UI & Visualization: Chart.js for risk indicators, Google Fonts for accessibility
  • Logic & AI: A rule-based scoring model combined with AI-generated insights
  • Data Storage: Browser LocalStorage (no backend required)

The risk model calculates an overall score using weighted factors such as study consistency, remaining time, topic difficulty, and self-reported stress: [ \text{Risk Score} = w_1(\text{Missed Days}) + w_2(\text{Topic Difficulty}) + w_3(\text{Stress Level}) - w_4(\text{Study Hours}) ]

This score is then mapped to a clear risk category and paired with personalized recommendations.


Challenges We Ran Into

One major challenge was balancing simplicity with meaningful insights. We wanted ExamShield to be easy to use while still providing accurate and useful predictions. Another challenge was designing the system to feel supportive rather than judgmental, since students under stress can be easily discouraged by harsh feedback. Time constraints also pushed us to carefully prioritize features that delivered the most impact.


Accomplishments That We're Proud Of

  • Turning a common problem into a predictive, preventive solution
  • Creating a clear risk-analysis flow that’s easy to understand at a glance
  • Building a complete, demo-ready product within a short hackathon timeframe
  • Designing an interface that feels calming and student-friendly

What We Learned

We learned that impactful solutions don’t have to be complex. Clearly identifying a real problem and solving it early can be more powerful than adding many features. We also gained valuable experience in user-centric design, risk modeling, and explaining technical ideas in a simple, relatable way.


What’s Next for ExamShield

Next, we plan to:

  • Improve prediction accuracy with real student data
  • Add offline-first support for low-connectivity regions
  • Integrate calendar syncing and long-term progress tracking
  • Partner with schools or learning platforms to expand real-world impact

ExamShield’s long-term vision is to help students everywhere succeed by knowing the risks before exams do.

Built With

Share this project:

Updates