Online build sprint · 03 Sep 2026

BUILD WHAT
PEOPLE WILL
ACTUALLY USE.

One focused day. Eight meaningful problem spaces. A working prototype by 5 PM.

10:00–17:00 IST
100% online Build anywhere
Official poster / 2026
Vibeathon 2026 official event poster
ACCESSIBLE AI CLIMATE RESILIENCE TRUSTED CIVIC TOOLS SMARTER WORK
The brief

Eight problems.
One day to move.

Pick one direction, narrow it to a real user, and make the smallest version that proves the idea can work.

01Accessible AI

Plain Language Anywhere

Turn dense public or educational information into clear, accessible formats without losing the source.

Minimum credible demo
  • Accept text, a URL, or a document
  • Create at least two accessible outputs
  • Keep source passages traceable
  • Include a simple user-feedback loop
Guardrail: Do not present medical or legal summaries as professional advice.
02Climate resilience

Ready, Block by Block

Help one neighbourhood, campus, or community prepare for extreme heat or local flooding.

Minimum credible demo
  • Show a current risk snapshot
  • Map or list vulnerable points
  • Prioritise a practical action checklist
  • Make the plan shareable or usable offline
Guardrail: Clearly label simulated data, data gaps, and uncertainty.
03Trusted civic tools

Verify Before You Share

Help people inspect a public claim or document through evidence, provenance, and an honest “unknown” state.

Minimum credible demo
  • Accept a claim or document
  • Compare supporting and opposing evidence
  • Label every source and date
  • Share the reasoning—not only a verdict
Guardrail: Automated output must not be presented as an official fact-check.
04Smarter learning & work

Handoff Without the Meeting

Convert scattered notes and messages into a handoff people can understand and act on.

Minimum credible demo
  • Accept mixed, messy inputs
  • Extract decisions, owners, blockers, and deadlines
  • Allow review and correction
  • Export a clean, shareable handoff
Guardrail: Preserve traceability and never invent an owner or deadline.
05Public health

Care, Even on Low Signal

Design a low-bandwidth pathway that helps people find appropriate nearby care and prepare useful information before a visit.

Minimum credible demo
  • Work on a slow or intermittent connection
  • Offer clear next-step navigation
  • Create a concise visit-preparation summary
  • Support at least two languages or accessibility modes
Guardrail: Do not diagnose, prescribe, or replace emergency services.
06Digital safety

Scam Pattern Radar

Help a user recognise suspicious patterns in a message, listing, or payment request before they act.

Minimum credible demo
  • Accept text or an image
  • Highlight specific warning signals
  • Explain why each signal matters
  • Offer a safe verification checklist
Guardrail: Never claim certainty; protect submitted personal information.
07Community access

Find the Door In

Make one essential local service—scholarships, benefits, shelters, legal aid, or public facilities—easier to discover and understand.

Minimum credible demo
  • Use a structured, source-backed directory
  • Support plain-language filtering
  • Show eligibility or access steps
  • Display source freshness and ownership
Guardrail: Do not invent service availability or eligibility.
08Responsible automation

The Human Checkpoint

Redesign one repetitive workflow so automation does the busywork while a person keeps control of important decisions.

Minimum credible demo
  • Visualise the current and improved flow
  • Automate at least one real step
  • Add an explicit review checkpoint
  • Log changes and failure states
Guardrail: High-impact decisions must remain reviewable and reversible.
The run of show

Seven hours.
Keep it moving.

No pitch-deck theatre. Define, build, test, and show the thing.

  1. 10:00Opening & problem selection01
  2. 10:30Build sprint begins02
  3. 13:00Progress checkpoint03
  4. 16:15Final submissions04
  5. 16:30Rapid demos05
  6. 17:00Close06
How work is assessed

Useful beats flashy.

A clear, tested prototype with honest limitations will score better than an oversized promise.

30%Problem relevance
30%Working execution
25%Trust & usability
15%Demo clarity
Submission checklist

Make the work
easy to judge.

  1. 01Working prototype or clickable demo
  2. 02Two-minute demonstration video
  3. 03Repository or project link
  4. 04One-page note: user, decisions, limitations
03 September 2026 · Online

Bring a problem.
Leave with proof.

Registration is open. Choose your problem statement, tell us what you want to build, and submit your participant details through the official form.

Google Forms opens in a new tab. No payment is requested.