TECHMESH - Rule Book (Technical Core)

Important Participation Summary

To avoid confusion: all Technical Core module tasks must be performed during the official competition window at the venue. Teams should bring required devices and materials listed for each event, but pre-made final projects, pre-solved competition tasks, or copied templates are not accepted for scoring. Submission format is digital unless organizers announce a physical requirement for a specific module.

MODULE: WEBATHON

TechMesh 2026 | Technical Module

Category: Technical Core

Format: Team-Based Web Development Challenge

Duration: 1 Day (Live Competition)

1. Overview

Webathon is a live web development competition in which teams design and build a functional web solution based on a problem statement announced on the event day. Teams will be assessed on functionality, user experience, code quality, creativity, and presentation.

2. Team Composition

3. Event Day Flow

4. Challenge Requirements

Teams must develop a responsive web solution for the assigned problem statement. The solution must include, at minimum:

• A home page
• A core feature workflow representing the main user action
• Basic data handling, including form input, validation, and display
• Error handling for invalid input
• A mobile-friendly and responsive layout

Teams may choose to build:

• A frontend-only solution using mock or static data
• A full-stack application, which will be considered a bonus if a working backend is included

All core code must be written during the competition hours.

5. Allowed Technologies

The following technologies are permitted:

• HTML, CSS, JavaScript, and TypeScript
• React, Vue, or other frontend frameworks
• Node.js, Express, Firebase, Supabase, or similar backend tools
• UI libraries and CSS frameworks
• Open-source packages
• AI tools, provided they are used only as assistance and not for full project generation or blind copy-paste

6. Internet and Resource Policy

• Internet access is allowed for documentation, package installation, and debugging references.
• Copying complete templates, cloned projects, or full repositories is strictly prohibited.
• Teams must be able to explain every major part of their code during evaluation.

7. Submission Requirements

Each team must submit the following:

• Source code as a ZIP file or repository link
• A README file containing:
• Project overview
• Setup instructions
• Tech stack
• Team member names
• Demo evidence, which may include:
• A live project link, or
• A recorded walkthrough of 2 to 4 minutes, or
• An on-site runnable project
• Optional supporting material:
• Architecture diagram
• Known limitations

8. Judging Criteria (100 Marks)

9. Penalties

10. Tie-Break Policy

If two or more teams achieve the same score:

• The team with higher Functionality marks will rank higher.
• If still tied, the team with higher UI/UX marks will rank higher.
• If still tied, judges may conduct a short technical Q&A to decide the final ranking.

11. Code of Conduct

All participants must:

• Respect organizers, judges, and fellow participants
• Refrain from harassment, abuse, or disruptive behavior
• Accept that judges' decisions are final

12. Organizer Notes

• Organizers may adjust the schedule according to event flow.
• Any rule changes will be communicated equally to all teams before implementation.

Speed Coding

Task

Participants will be given a coding task on the spot during the competition.

Rules

• Participants have 2 hours to complete the task.
• Participants must bring their own laptops.
• Participants must arrange their own internet connection.
• Use of AI tools and the internet is allowed.
• All code must be written during competition time.

Winning Criteria

• Completion Time: Faster solutions are preferred.
• Efficiency: Optimized and well-structured code.
• Uniqueness: Creativity and originality in solving the problem.
• Interface and Presentation: Quality of user interface and usability of solution.

Speed Wiring

Materials Provided

• Electronic wires
• Breadboard
• Required ICs and basic components

Rules

• Maximum 3-4 members in one team.
• Task will be given on the spot.
• Teams must use only provided components.
• Participants have 30 minutes to complete the circuit.
• External materials or components are not allowed.

Winning Criteria

• Completion Time
• Workable Circuit: Circuit must function correctly.
• Logic: Proper understanding and implementation of electronic design.

Tech Debate

Format

Competition is conducted in debate format where participants present arguments on technology-related topics.

Rules

• Debate topics are announced on the spot.
• Participants are given short preparation time before debate starts.
• Each participant or team gets fixed time to present arguments.
• Discussion must remain focused on technology-related aspects.
• Respectful and professional communication must be maintained.

Winning Criteria

• Argument Strength: Logical and well-supported arguments.
• Technical Knowledge: Understanding of the technology topic.
• Confidence and Communication: Clarity, confidence, and presentation skills.
• Rebuttal Ability: Effective response to opponent arguments.

Graphic Designing (Flyer or Poster)

1. Format

Individual competition. Each participant will create one original design based on the event theme announced on competition day.

2. Theme and Task

The organizing team will announce a design brief at the start of the event.

Participants must design either:

1. A flyer, or
2. A poster

3. Time Limit

Total competition time: 2 hours.

4. Allowed Software and Tools

Participants may use software such as Adobe Photoshop, Adobe Illustrator, CorelDRAW, Canva, Figma, or equivalent tools.

Use of stock assets is allowed only if they are royalty-free and properly credited where required.

Use of AI tools is allowed for assistance (idea generation, background cleanup, etc.) but full auto-generated submissions are not allowed.

5. Rules

• All participants must bring their own laptop and charger.
• Internet may be used for references and royalty-free assets only.
• All design work must be created during the competition window.
• Plagiarism or direct copying from existing designs will result in disqualification.

Participants must submit final output in:

1. High-resolution image format (PNG or JPG), and
2. Source/editable file format (PSD, AI, CDR, FIG, etc.)

Late submissions may receive penalty marks as per organizer policy.

6. Submission Requirements

Each submission must include:

1. Final design file
2. Editable/source file
3. Short design note (3 to 5 lines) explaining concept and visual choices

7. Judging Criteria (100 Marks)

8. Code of Conduct

Participants must maintain professional and respectful behavior.

Any dispute will be resolved by judges or organizers, and the decision will be final.

UI/UX Designing (Figma)

1. Format

Individual competition. Participants will design a complete UI/UX solution in Figma based on a problem statement announced at the venue.

2. Challenge Scope

Participants must produce:

1. User flow for key task journey
2. Wireframe or low-fidelity layout
3. High-fidelity UI screens for core flow
4. Basic clickable prototype in Figma

3. Time Limit

Total competition time: 2.5 hours.

4. Allowed Platform and Tools

Figma is the primary tool for this competition.

Use of plugins is allowed unless specifically restricted by organizers.

Pre-made templates and full UI kits are not allowed as final submissions.

AI assistance is allowed for ideation and microcopy support, but complete generated designs are not acceptable.

5. Rules

• Participants must bring their own laptop and have an active Figma account.
• All work must be created during competition time.
• At least one mobile app flow or one web flow must be completed end-to-end.
• Design must focus on usability, accessibility, and clarity.
• Copying existing products or templates will lead to disqualification.

6. Submission Requirements

Participants must submit:

1. Figma share link with view access enabled
2. Exported screens in PNG format
3. Brief design rationale including:

1. Target user
2. Main problem solved
3. Key UX decisions

7. Judging Criteria (100 Marks)

8. Tie-Break Policy

In case of equal marks, higher score in usability and interaction design will be preferred.

If still tied, judges may conduct a short Q and A round.

9. Code of Conduct

Respect judges, organizers, and fellow participants.

Any final decision regarding disputes will be made by the judging panel or organizers.