Hosted byIIT (BHU) Varanasi
A 24-hour hackathon on e-scooters, e-rickshaws, e-cycles and e-cargo. There’s no problem statement: bring one you found, and the evidence that it’s real.
WithWMG, University of Warwick/IIT Kharagpur/SimLionics Funded byBritish Council Who does what ↓
Finding one is half the challenge. Tell us a real problem you have found in India's e-micromobility space, show us how you know it is real, and build something about it in a single day.
off an extension cord
eleven-hour delivery shift
dead pack, 14 months
Name a real person or organisation — a rider, a fleet, a lender, a workshop, a city.
You watched it happen, you asked someone, or you found data. One honest sentence beats a confident guess — talking to one real rider counts as evidence, and we score it as such.
Software, built at the hackathon. Explain how it addresses the problem you named.
You build from 12:00 on Saturday to 14:00 on Sunday. Tell us honestly how far you expect to get.
Two or three of you. Say who does what.
You arrive with a problem you found. At 12:00 you start building it, and on Sunday afternoon you pitch something that runs.
Illustrative, not a menu. Plenty of these vehicles already collect data — it just stays locked inside whoever built them, rarely shared and almost never standardised. If your idea sits outside these and you can argue for it, send it anyway.
Swap cabinet, 18:40
Four webinars from Sustainable e-Micromobility Futures, the Warwick–IIT research project behind SHIFT. They show where the hard questions are. They are not a problem statement: the problem is still yours to find.
University of Warwick · Connected Places Catapult · ICCT India · Curve Electric · moderated by IIT (BHU)
University of Birmingham · Innpact Solutions · Deloitte India · WRI India · moderated by WMG, Warwick
About:Energy · Amara Raja · IIT Madras · BatteryIQ · moderated by IIT Kharagpur
WMG, Warwick · Oorja · Envision Energy · moderated by SimLionics
Everything you build happens between 12:00 on Saturday and 14:00 on Sunday.
The one in your abstract, for the person or organisation you named. Your answer to question 04 is your plan, and your progress is measured against it.
Your solution is software, built at the hackathon in one public GitHub repo. Libraries, public datasets and your research notes are fine. Mentors score the progress they see at three check-ins, so work you arrive with earns nothing.
Two pages, in your repo by 14:00 on Sunday. It goes into the project's published report, with your names on it.
Build night
The problem you find and how you solve it count for half.
Is it real, and do you know who has it?
A named rider, fleet or workshop, and evidence you gathered.
Does it actually solve that problem?
A working demo that tackles the problem you named.
Would it work in India?
Costed in ₹. Runs on a cheap phone, a patchy network or weak power.
Did you keep moving forward across three check-ins?
Real steps between the mentors’ visits, against your own plan.
Is your pitch clear?
A live demo inside three minutes. Straight answers to questions.
Mentors score Progress at three check-ins — Saturday 17:00, Sunday 10:00 and Sunday 12:00 — and you can ask them anything. From 14:00 on Sunday a jury of five reads every repo, then hears three-minute pitches from 16:00 and scores the other four lines. Saying honestly what didn’t work counts in your favour.
Open to all, until 2:15 pm on Thursday 8 October 2026. Enter as a team of two or three. No hardware, no entry fee.
A laptop, its charger, a GitHub account and whatever you normally code on. Research and data, yes; project code, no. No hardware needed.
The E-Hall, opposite the Proctor’s Office at IIT (BHU) Varanasi, Saturday 09:30 to Sunday 17:50. You stay on campus on Saturday night, and we provide the accommodation. The ghats are a twenty-minute ride away.
A ₹1,00,000 prize pool, awarded at the results on Sunday. The jury also picks projects to carry on with a partner after the event. Your case study is published with your names on it.
No, and that is deliberate. The problem you find and your solution to it are half your score. The eight areas on this page are examples, not a list to pick from — and the four talks under them are a good place to start looking. You build for the problem in your abstract.
Please don’t. Mentors score the progress they see at three check-ins, so work you arrive with earns nothing. Libraries, public datasets and your own research notes are fine.
No. Teams are two or three people, so find a teammate before you register. A team of two is judged exactly the same way as a team of three — there is no allowance either way.
No. Your solution is software. Bring a laptop and your usual setup.
On campus. Everyone stays on Saturday night, and we arrange the accommodation for shortlisted teams. The E-Hall closes at 20:30 on Saturday, so you keep building from your hostel overnight.
Say so clearly, in your case study and your pitch. The jury scores an honest account of what did not work above a demo it cannot check.
On your abstract. We read for a real, evidenced problem first, and the build you propose second. We score it out of 100: the problem 30, your evidence 30, the build 20 and your 24-hour plan 20.
Yes — a ₹1 lakh prize pool, awarded at the results at 17:30 on Sunday 11 October. A jury of five decides the prizes, and also picks projects to carry on with a partner after the event.
You do. Case studies are published CC-BY-4.0 and code under MIT, so the work can go into the project's report with your names on it.
Write to Dr. Agnivesh Pani at agnivesh.civ@iitbhu.ac.in. If the same question comes up often enough, we will run an online session before the deadline and post the details here.
Trunk road, 21:10




Funded through the British Council Going Global Partnerships Industry–Academia TNE Grant 2025–26.