Dates: August 18th, 2025 to September 25th, 2025
Eligibility: Open for All
Submission Must Include
- Feature Name + Abstract
- Problem Statement Addressed: Problem-solution-benefit breakdown
- Proposed Solution: what it does, how it adds value
- UX Mockup / Prototype
- Workflow / API Logic
- Tech stack or tools planned (if applicable)
- System fit: Where in TRAVEL-WIZARD’s flow it would sit
- Potential Challenges and Implementation Risks
- Post-hackathon roadmap (how it can evolve)
- Flow diagrams, user personas, prompt engineering samples, LLM/RAG plans.
11. Potentially identify partnership or monetization features
- Architecture or data pipeline sketches
Judging Criteria
ü Value for platform users
o Who is your target user?
o How does your add-on make their work faster, easier, or more effective?
o Does it offer broad value to many or deep value to a specific group?
ü Innovation ("uniqueness")
o Is your feature creative or unexpected in tech, design, or workflow?
o If similar ideas exist, how is yours better?
o What’s original or delightful about it?
ü Feasibility and Intent to Build
o How have you confirmed the feasibility of the features?
o Did you make a prototype or mockup?
o What’s your plan for launching if you win?
o Do you have the skills and motivation to deliver?
Judging Criteria and Winner Selection
Key Considerations & Evaluation Criteria
|
Category |
Sub-Criteria |
Weight |
Details |
|
Architectural Solution (20%) |
Tech Stack Selection |
5% |
Choice of tech stack – AI model (open/proprietary), AWS services, vector DB, Guardrails, etc. |
|
Innovation & Key Features |
9% |
3% – Unique viewpoint on an existing issue 3% – Practical real-world application 3% – Clear additional value |
|
|
Feasibility |
6% |
3% – Implementation feasibility and scalability 3% – Suitability of proposed tech |
|
|
Potential Impact (15%) |
Business Value |
10% |
5% – Addresses significant market need5% – Cost reduction or revenue generation |
|
Potential for Disruption |
5% |
Potential to significantly change or improve existing processes or industries |
|
|
Prototype Technical Implementation (40%) |
Clean Coding & Best Practices |
10% |
5% – Code is easy to understand and reproducible 5% – Well-tested, error-free |
|
Deployment Strategy |
5% |
Strategy for deployment (infra-as-code, automation) |
|
|
Intuitive Interface |
5% |
Ease of use and accessibility of the interface |
|
|
Performance Metrics & Scaling |
20% |
10% – Accuracy & precision10% – Inference time efficiency |
|
|
Presentation (25%) |
Clarity and Communication |
15% |
5% – Clear problem statement and objectives 5% – Concise presentation 5% – Technical clarity to non-tech audience |
|
Engagement and Impact |
10% |
5% – Use of visuals, prototypes, or demos 5% – Impact conveyed effectively to stakeholders |
Rules
Participants need to adhere to the following rules and regulations:
1. Participants must register before the deadline and can compete individually or as a Team of up to 3 members.
2. All team members should have valid identification documents.
3. Basic programming knowledge required. Experience with AI/ML frameworks is beneficial but not mandatory.
4. Code should be submitted to the designated repository by the submission deadline.
5. Participants are allowed to use open-source libraries or APIs, but they must disclose them in the idea submission phase.
6. Teams must submit their project before the deadline. Late submissions will not be considered.
7. Organizers have the right to take necessary actions, including providing a warning or disqualifying participant(s) to ensure a safe, inclusive and fair environment.
8. Solutions will be judged based on innovation, functionality, user experience, technical implementation, and presentation.
9. The organizing team reserves the right to modify the rules if necessary and will notify participants of any changes.
10. Any disputes or concerns will be handled at the discretion of the hackathon organizers, and their decision will be final.