To make a project explainer video for Smart India Hackathon, first check where your team will use it, because the national idea submission is a short PDF presentation, not a video. Videos are most often asked for in college internal hackathons, linked from the idea PDF, or used in mentoring rounds and the finale pitch. Make a two minute video in five parts: the problem statement in the ministry's or company's own words, the user who has the problem, your solution in one sentence, how it works drawn as three to five boxes, and why it is feasible. Write about 280 words, draw the architecture rather than reading slides aloud, and keep the same structure as your six slide PDF so the two reinforce each other.

Where a video fits in SIH

Smart India Hackathon is run by the Ministry of Education's Innovation Cell with AICTE, and the format changes a little each year, so treat the official guidelines on sih.gov.in for the current edition as the final word. In the 2025 edition, the process worked like this:

A few rules from the 2025 guidelines worth knowing because they shape the video. Teams have six members from the same college, including at least one woman. A team can submit ideas against at most two problem statements. Each problem statement closes after 500 idea submissions, so popular ones fill early. Ideas were judged on novelty, complexity, clarity, feasibility, practicability, sustainability, scale of impact, user experience and potential for future work. In 2025, idea submission closed on 30 September and the finale was held offline in the second half of the year. Recent editions have kept a similar pattern, but confirm dates with your SPOC.

The practical conclusion: build your argument as the PDF first, because that is what national evaluators read. The video is the same argument, spoken and drawn, for the stages where people watch instead of read.

What evaluators are trying to find out

An evaluator reading hundreds of ideas for one problem statement is asking four questions, roughly in this order.

1. Did they understand the problem statement? Not the general area, the exact statement the organisation posted, with its constraints.
2. Who uses this, and what changes for them? A real user, a real situation.
3. Can six students actually build it? Named technologies, a sensible scope, a plan for the hard part.
4. Is it different from the other 499? One specific idea that is yours.

A video that answers those four in two minutes will beat a five minute video with better visuals. Most SIH explainers fail question 1: they describe a nice app without ever quoting the problem it was meant to solve.

The five part structure

Keep the same order as your PDF slides. An evaluator who watches the video after skimming the PDF should recognise every part.

Worked example: crop disease detection for small farmers

Agriculture problem statements appear in most SIH editions, so here is a full script for an invented but typical one: a problem statement asking for a way to help small farmers identify crop diseases early, usable on low-end phones in areas with poor connectivity. The team's idea is an offline image classifier inside a lightweight Android app, with advice in the farmer's language. About 230 words.

Problem statement (drawn). "Our problem statement asks for early detection of crop diseases for small and marginal farmers, on low-cost phones, in areas with weak or no internet. That last condition rules out most of what already exists, because most plant disease apps send the photo to a server."

The user (drawn). "Meet Ramesh. He grows tomatoes on two acres. He notices spots on the leaves. The nearest agriculture officer visits once a month, and by then the blight has spread."

The solution (drawn). "Our idea, PattiScan, lets him photograph a leaf and get a likely disease and the next step in under five seconds, with no internet."

How it works (drawn, one box at a time). "The app holds a small image model on the phone itself. Ramesh takes a photo. The model compares it against the diseases it was trained on for his crop, using public plant disease image datasets. It shows the top result with a confidence level, and a short spoken tip in Hindi or Marathi. If confidence is low, it says so and saves the photo. When the phone next finds a signal, saved photos are uploaded so an expert can review them and the model can improve."

Feasibility and impact (drawn). "We have a working prototype for three tomato diseases, built with TensorFlow Lite, running on a phone with 2 GB of RAM. In the finale we would extend it to the crops named in the problem statement and test it with farmers near our college."

Notice what the script does. It quotes the constraint (low-cost phones, no internet) in the first ten seconds, and then every later part answers it. The architecture is drawn because "the model runs on the phone, uploads happen later" is exactly the kind of idea that takes a paragraph to read and three seconds to see. Do not put an accuracy number on screen unless you measured it on data you can name.

Video for the finale pitch

If your team reaches the finale, judges will see the working prototype. A short drawn explainer still helps as the first sixty seconds of the pitch: problem, user, architecture, then switch to the live demo. Splitting the explanation from the demo is the same approach as in how to make a hackathon demo video in an hour, which covers the screen recording side in detail. For a hardware edition entry, how to make a robotics project explainer video covers drawing sensors, controllers and actuators.

Make it

1. 1

   Copy the problem statement word for word

   Paste the exact text and ID from the portal at the top of your script. Underline the one constraint your idea is built around.

2. 2

   Write the six slide PDF first

   Follow the official template for your edition. The video is the same argument spoken aloud, so the PDF is your outline.

3. 3

   Write a 280 word script in five parts

   Problem statement, the user, the solution in one sentence, how it works, feasibility and impact. One paragraph each.

4. 4

   Paste it into openCanviz

   Set a two minute target and choose Keep my wording. Whiteboard style draws the architecture box by box as you name each part. Narration can be in English or Hindi, and you can replace the generated voice with a team member's recording.

5. 5

   Check every name and number

   Pause on each scene. Check the problem statement ID, technology names, and any figure. Remove any number you cannot source, and fix scenes in the editor.

6. 6

   Get the file your college asked for

   Upload where your SPOC tells you, usually as an unlisted YouTube or Drive link. Free exports carry a watermark; a one-off payment unlocks a clean export of that project.

Common questions

Is a video compulsory for SIH idea submission? In the 2025 national guidelines, the team leader submitted the chosen problem statement, idea title, description and a PDF presentation; a video was not a listed field. Many colleges ask for one in the internal round. Check your edition's guidelines and ask your SPOC.

Should the video be in English or Hindi? The idea PDF is usually in English. A video for an internal round can be in whichever language your college accepts. If your user is a Hindi speaking farmer, a short Hindi clip of the app's spoken advice can strengthen the point. See Hindi me explainer video kaise banaye for making the whole video in Hindi.

How long should it be? Use your college's limit. Without one, two minutes. Evaluators and internal judges watch many, and a tight video reads as a team that understood its scope.

Can we show a prototype we have not finished? Show what exists and say clearly what does not. Drawn scenes are fine for the planned parts, as long as the narration says "planned". Presenting a drawing as a working feature is the fastest way to lose a judge's trust at the finale.

What if our idea is under Student Innovation, not a problem statement? Replace the first part with the problem in your own words and one sourced fact that shows it is real. The rest of the structure stays the same.