Photographs
Photographs you have taken yourself: the overflowing drain, the broken footpath, the crowded clinic, the unlit street at night. Original photographs are the strongest evidence.
Guideline 02
Go out, look closely, and come back with proof.
This competition is not about sitting in a classroom and inventing an idea. Follow these five steps in order and, by the time you sit down to build your PowerPoint, you will already have everything you need.
The five steps
Each stage builds on the previous one.
- 01ObserveLook around and notice a civic problem that affects people in your community.
- 02Gather evidenceGo deeper. Collect photographs, data and observations, or talk to the people affected.
- 03AnalyseUnderstand why the problem exists. What causes it? Why has it not been solved?
- 04Design a solutionPropose a practical, technology-enabled idea that could address the root cause.
- 05PresentPut everything together into a clear PowerPoint submission.
Step 1 — Observe
Before you pick a theme, spend time simply noticing. Walk through your neighbourhood, your school route, your local market, a government office, a hospital, a bus stop. Watch how things work, and watch where they break down.
- What frustrates people here? What takes longer than it should?
- What do people complain about but have accepted as normal?
- Who is affected the most — children, elderly people, women, farmers, daily wage workers?
- Has this problem been like this for a long time, or is it getting worse?
You do not need a solution at this stage — in fact it is better if you do not have one. Do not start with a solution and then look for a problem to fit it.
A helpful exercise
Each member spends one day observing their surroundings with a notebook. Write down every problem you notice — big or small. Then sit together and compare notes. The problems that several of you noticed independently are often the strongest ones to pursue.
What NOT to do
Do not Google “civic problems in India” and pick one from a list. The judges will know. Your observation should be personal — something you have seen, experienced, or heard about from people around you.
Step 2 — Gather evidence
Once you have identified a problem, prove that it exists. Evidence is what separates a strong submission from a guess.
Interviews or conversations
A conversation with a shopkeeper, a farmer, a bus driver or a neighbour counts. Write down what they said — you may paraphrase — and include it.
Data and numbers
Numbers that show the scale. Count the overflowing bins on your street, or use government reports, news articles and published data.
Personal observations
If your problem happens at a specific time — a road that floods only in monsoon, a market that becomes unsafe at night — describe it clearly.
Secondary sources
News reports, government data or published studies that support your claim. They should supplement your original evidence, never replace it.
How much is enough?
Typically at least 3–4 original photographs plus 1–2 other forms of evidence. One powerful photograph with context beats ten generic images.
What does NOT count as evidence
Stock images from the internet, generic statistics without a source, or vague statements like “everyone knows this is a problem.” If you did not take the photograph, observe it yourself, or find it from a credible source, it is not evidence.
Step 3 — Analyse
Most student projects identify a problem and jump straight to a solution. The best submissions pause here and think deeper about why the problem exists.
- Why does this problem exist? What is the root cause, not just the visible symptom?
- Has anyone tried to solve it before? If yes, why did it not work?
- Who is responsible — the government, a private company, the community, or nobody?
- What would need to change for this problem to go away?
Symptom vs root cause
Symptom: “There is garbage on the street.”
Root cause: “There are no dustbins within 200 metres, and the municipal collection truck comes only once a week.”
A symptom-level solution is “let us organise a cleanup drive.” A root-cause solution is “let us create a system where residents report full bins so the truck comes when needed.” The second solves the problem at its source.
Step 4 — Design a solution
Your idea should involve technology in some way — but technology does not mean building an app. It can be a mobile phone camera, an SMS alert, a sensor, a database or a digital platform.
It targets the root cause
Address the cause you identified in Step 3, not just the visible symptom.
It is realistic
A clear, practical idea that could be implemented in your town or district is exactly what we are looking for.
Technology has a clear role
Explain what role technology plays and why it is needed. If the solution works without it, ask whether it adds value.
It is simple to explain
You should be able to explain your idea in 2–3 sentences. If you cannot, it may be too complicated.
Questions to stress-test your idea
- Who would use this solution — citizens, government officials, students, farmers?
- What would be needed to make it work? Think about cost, resources, permissions and time.
- What could go wrong? Every idea has weaknesses; naming them shows maturity.
- Does something similar already exist? If yes, how is your approach different or better?
Remember: you are NOT building a prototype
This is an ideathon, not a hackathon. You are not expected to write code, build hardware or create a working model. The judges evaluate the quality of your thinking, not your technical skills.
Step 5 — Present
Your PowerPoint is the only thing the judges will see. Everything you have observed, gathered, analysed and designed must come through clearly in your slides.
- Introduction — who is your team, and what is your chosen topic?
- The problem — what is it, where does it occur, who is affected?
- Evidence — photographs, data, conversations and observations.
- Analysis — why does this problem exist? What is the root cause?
- Your solution — what is the idea, and how does technology help?
- Feasibility — is this realistic? What challenges would it face?
- Impact & vision — who benefits, and how does this connect to a better 2047?
Presentation tips
Write in your own words. The judges want to hear your voice, not a textbook.
Use visuals — your own photographs, simple diagrams or hand-drawn sketches are more convincing than clip art.
Keep slides uncluttered. Less text, more clarity. And proofread.
Common mistakes to avoid
Starting with the solution
Deciding on a solution first and then looking for a problem to fit leads to weak problem statements and forced evidence.
Using internet images as evidence
Downloading images instead of taking your own photographs. Judges can tell the difference immediately.
Being too vague
“We will solve the water crisis” is not a plan. A narrow, well-defined problem with a focused solution is always stronger.
Skipping the analysis
Jumping from Step 1 to Step 4. The middle steps are where the depth of your thinking shows.
Making technology the hero
Technology should serve the solution, not be the solution. If you cannot explain the idea without it, rethink it.