TRAE Re{Vibe}
All that you need to know about TRAE Re{Vibe}
Hackathon Structure & Flow:
Stage 1: Pre-Hackathon Workshop:
Workshop conducted by a TRAE International Speaker
Mode: Online / Hybrid
Introduction to the TRAE platform
Industry insights and innovation mindset
Guidance on building impactful hackathon projects
Explanation of evaluation criteria
This session prepares participants both technically and strategically
Stage 2: PPT Submission Round (Screening Round):
Teams Must Submit:
Problem Statement
Proposed Solution
Basic Architecture / Workflow
Expected Impact
Evaluation Criteria:
Idea clarity
Innovation
Feasibility
Presentation quality
Selected teams qualify for the prototype development phase
Stage 3: Pre-Hackathon Project Building Phase:
Shortlisted teams receive preparation time before the main hackathon
Teams begin initial development of their prototype
Focus Areas:
Core functionality
Basic UI/UX
Working demo foundation
This phase ensures higher project quality on the final hackathon day
Stage 4: Main Hackathon – Offline Event Day Flow:
Registration & Check-in:
Participant verification
Seating allocation
Lab access provided
Orientation Session:
Welcome address
Rules and judging criteria explanation
Final instructions
Schedule briefing
Prototype Enhancement Phase (With Mentors):
Teams enhance and refine their pre-built prototype
Mentors guide teams on:
Optimization
Feature improvement
Debugging
Presentation strategy
Focus: Make the project industry-ready
Project Submission:
Final code submission
PPT submission
Demo readiness confirmation
A strict deadline will be followed
Lunch Break:
Short refreshment break before the final round
Final Round Presentations:
Only the Top 10 shortlisted teams will present
Each team gets:
5–7 minutes for presentation
3–5 minutes for Q&A
Evaluation Criteria:
Innovation
Technical depth
Impact
Scalability
Presentation skills
Result Announcement:
From the Top 10 Teams, Top 3 winners will be selected:
1st Prize – ₹12,000
2nd Prize – ₹5,000
3rd Prize – ₹3,000
The judges’ decision will be final and binding.