Attendance, Mess, Hostel, Repeat: Campus Life, Debugged (Demo)

Name: Attendance, Mess, Hostel, Repeat: Campus Life, Debugged (Demo)
Start: 2026-09-21T18:29:00.000Z
End: 2026-09-21T18:29:00.000Z
Location: Bhubaneswar and Rourkela

Four apps, six notice boards, two WhatsApp groups and one register. Replace all of it.

Registration closed

21 Sept 2026

Team size

3–6 members

Mode

In person

Venue

Bhubaneswar and Rourkela, Each team reports to the city of the zone it chose at registration

Registration closed

Already registered? Sign in

Role: Full-Stack Developer / Product Engineer
Format: Evaluation only
Prize: ₹60,000
Deadline: Closed 21 Sept 2026

Evaluation only · Open

Design a technology solution that removes the daily friction of campus life — for the student trying to get something done, and for the administrator trying to keep track of two thousand of them. Not a new app for one problem. A working answer to the everyday operational mess that everyone has quietly accepted as normal.

Overview

Outcomes

Routine campus tasks completed in one place instead of five queues and a phone call
Administrators with real visibility into what is pending, where, and for whom
Faster resolution of complaints, requests and approvals, with an audit trail
Fewer notices lost to a WhatsApp group at 2 AM
A solution that works for a student on a low-end phone and a patchy hostel network

Overview Campus life runs on a strange mixture of registers, notice boards, WhatsApp forwards, printed forms and one person who knows how everything actually works. Attendance is tracked in one system, hostel complaints in a diary, mess feedback nowhere, gate passes on paper, fee queries in a queue outside an office that opens at 11. Students lose hours to it. Administrators lose visibility to it. Both sides assume this is simply how college works. The Story It is Tuesday. A student needs a bonafide certificate, wants to report that the hostel tap has been leaking for nine days, would like to know whether tomorrow's class is cancelled, and has been told the mess menu changed. This requires: one office, one warden, one notice board, and one senior who "usually knows." Total time: most of the afternoon. Total number of these tasks that genuinely needed a human being: roughly zero.

Problem statement

Student-side daily operations — attendance visibility, timetable and class updates, leave and gate-pass requests, document and certificate requests, fee and dues status, notices and announcements
Hostel and facility operations — complaint and maintenance ticketing with status tracking, room and asset records, mess menu and feedback, visitor and gate logs
Communication — targeted notifications by batch, branch, hostel or year, replacing broadcast WhatsApp chaos, with read and action tracking
Administrator side — a single view of pending requests, complaint ageing, repeat issues, resolution times and workload distribution across staff
Accessibility and reality checks — low-bandwidth operation, low-end device support, regional language support, and a path for students who genuinely have no smartphone
Optional intelligence — routing complaints to the right department automatically, detecting recurring issues, predicting demand on facilities, or a chatbot that answers the twenty questions the office is asked every single day

For the Grand Finale, your build should include:

A working prototype covering at least three distinct everyday campus workflows, end to end, from student request to administrator resolution
An administrator dashboard showing pending items, ageing, resolution time and recurring issue patterns
A notification and communication layer with targeting and delivery/action tracking
An accessibility demonstration — the flow working on a low-end device or a poor connection, plus the fallback for students without smartphones
An adoption note: how a college with existing systems and existing habits would actually roll this out, and what data it would need to migrate

The Grand Finale is judged on:

Real reduction in everyday friction for students and administrators — 30%
Breadth and completeness of the workflows implemented — 20%
Administrator visibility, tracking and actionable insight — 20%
Accessibility, low-bandwidth and low-end device readiness — 15%
Usability, adoption realism and demo quality — 15%

How it runs

1.Mid evaluationThe top 5 go on to the Grand Finale.In person · Bhubaneswar and Rourkela, Each team reports to the city of the zone it chose at registrationHand-in closes 15 Oct, 11:59 pm IST
2.Grand FinaleThe final round: results are decided here.In person · BPUT, Rourkela

Deliverables: Mid evaluation

Your idea in one line
One or two sentences a judge can read in ten seconds: what you are building and who it is for.
What will be working by the finale?
The parts you commit to having running at the Grand Finale, most important first.
Tech stack and hardware you plan to use
Languages, frameworks, models, boards and sensors, and anything you still need to get hold of.
A diagram, sketch or mock-up of your idea
One image that shows how it works: an architecture diagram, a wireframe, or a photo of a sketch. Put anything more in your deck.
What have you built or tested so far?
Optional. Anything already running, measured or prototyped, even if it is rough.
Pitch deck (PDF)
Optional. Export your slides as a PDF. Judges read it on the page, next to your answers.

Deliverables: Grand Finale

A working prototype covering at least three distinct everyday campus workflows, end to end, from student request to administrator resolution
An administrator dashboard showing pending items, ageing, resolution time and recurring issue patterns
A notification and communication layer with targeting and delivery/action tracking
An accessibility demonstration — the flow working on a low-end device or a poor connection, plus the fallback for students without smartphones
An adoption note: how a college with existing systems and existing habits would actually roll this out, and what data it would need to migrate

Evaluation criteria

15% Problem Understanding & Relevance
20% Innovation & Creativity
20% Solution Approach & Technical Depth
25% Prototype / Implementation & Feasibility
10% Impact, Usability & Sustainability
10% Presentation & Demonstration

Questions & answers

No questions yet — be the first to ask.

More challenges to enter

Prizes are offered and awarded by Wooble Software Private Limited, not by Wooble. Amounts shown are as stated by the host and may include the host’s own valuation of non-cash items. Who places, how and when a prize is paid, and any tax or deduction, are between the winner and the host. A challenge may close, change or be withdrawn before results are declared.