To make an educational game pitch video, build it around one moment of play and show that the learning happens inside that moment, not around it. Open with the player and the thing they will be able to do afterwards, show the core loop as a sequence of drawn screens, then prove the learning is built into the mechanic rather than added as a quiz between levels. Keep it to two or three minutes, which is about 300 to 450 spoken words. Finish with what exists now (a paper prototype, a playtest, a build) and what you are asking for. Judges forgive rough art. They do not forgive a pitch where the game and the lesson are two separate things.

The two questions every judge is asking

An ordinary game pitch only has to answer one question: would people want to play this. An educational one has to answer a second at the same time: would they learn the thing you say they will learn, by playing.

Most student pitches answer one and wave at the other. Either the video is all lore, characters and art, with "and it teaches history" in the last ten seconds, or it is a learning outcomes table with a game-shaped logo on top. Both lose marks for the same reason. The judge cannot see the connection.

Game designers have a rude name for the second failure: chocolate-covered broccoli. The learning is the broccoli, the game is the chocolate, and players can taste the difference immediately. The opposite, where succeeding at the game requires using the knowledge, is usually called intrinsic integration. You do not need the jargon in your pitch. You do need your video to show the integration, because that is what separates an educational game from a quiz with a soundtrack.

A structure that fits in three minutes

The core loop gets the most time because it is the game. A loop is the thing the player does over and over: look, choose, act, see the result, repeat. If you cannot draw one turn of it in four or five frames, the design is not ready to pitch, and the video will show that more clearly than any feedback form.

Worked example: Bharat Heritage Explorer

Here is how the structure fills out for an imagined student game about Indian heritage sites. The player is a traveller restoring a damaged map of India, site by site.

The player. "Riya is twelve. Her class covers medieval Indian history this term, and she has forty minutes of computer time on Thursdays."

The learning goal. "After five sessions, Riya can place six major heritage sites on a map, name who built them, and explain one thing each tells us about its period."

The core loop, as four drawn screens:

1. A torn corner of the map, with a faded silhouette of a temple shaped like a giant chariot with carved stone wheels.
2. Three clue cards: a coastline on the Bay of Bengal, a carved wheel that works as a sundial, a king of the Eastern Ganga dynasty.
3. The player drags the site to a spot on the map and chooses a builder.
4. The map heals around the Konark Sun Temple in Odisha, and a new region opens with the next silhouette, this time a ruined city of boulders and the clue cards for Hampi and the Vijayanagara Empire.

Where the learning sits. "You cannot open the next region by guessing. Each wrong placement darkens a clue, so the player has to read the clues to progress. The clues are the curriculum."

That last line is the whole pitch. Everything before it sets it up and everything after it supports it.

Evidence. "We ran a paper version with eleven classmates. Nine finished three regions in twenty minutes. Two got stuck on Hampi, so we added a river clue for the Tungabhadra."

The ask. "We are looking for one teacher willing to trial the browser version with a class this term."

Check every fact you put on a clue card. In this example, the Konark temple dates from the thirteenth century and is attributed to King Narasimhadeva I, and Hampi was the capital of the Vijayanagara Empire. If your pitch is about teaching facts, a wrong fact on screen loses the argument on its own.

Showing gameplay before you have a build

Most pitches happen before the game exists, and that is fine. Judges know. What you cannot do is fill the gap with mood art and hope.

Draw screens, not scenes. A drawn storyboard frame of the actual interface (the map, the cards, the cursor, the score) says more than a beautiful painting of the world. The judge is evaluating the interaction.

Show one complete turn. Not a montage of features. One turn, start to finish, including what happens when the player gets it wrong. The failure state is often where the learning design is cleverest, and it is the part most pitches skip.

Label the mechanic as it happens. A small caption that says "wrong answer darkens a clue" at the moment it happens does more than a minute of narration afterwards.

Do not fake footage. If the video looks like a working build and it is not, someone will ask to play it. Drawn frames make the stage of the project honest at a glance.

A whiteboard or cutout style suits interface storyboards well, because both read as plans rather than finished art. If your game has a mascot or guide character, keep that character the same in every scene; how to keep the same character across a video series covers how.

Writing the script for the ear

Three minutes of narration is short. Every sentence has to carry something.

• Use the player's name. "Riya drags the temple to the coast" is a picture. "The user interacts with the location mechanic" is not.
• Say the outcome before the feature. "So she has to read the clue" lands harder than describing the darkening effect first.
• Cut the lore. One sentence of setting is enough. Backstory belongs in the design document, not the pitch.
• Read it aloud with a timer. At roughly 150 words a minute, 400 words is two minutes forty. If you run over, cut from the setting, never from the loop.

Make it

1. 1

   Write the one-sentence learning goal

   After playing, the player can do something specific. If you cannot write it, the game does not have an educational design yet, and no video will hide that.

2. 2

   Storyboard one turn of the loop

   Four or five frames on paper, including a wrong answer. This is the core of the video and the core of the design, so do it before writing narration.

3. 3

   Write the script to the six-part structure

   Player, goal, loop, where the learning sits, evidence, ask. Aim for 300 to 450 words and read it aloud against a timer.

4. 4

   Paste it into openCanviz and keep your wording

   Choose Keep my wording so the narration is your timed script, set the target length to match, and pick whiteboard or cutout so the frames read as interface plans.

5. 5

   Fix every frame against your storyboard

   Edit any scene where the drawing does not match the turn you designed, and check every fact on every clue card against a real source.

6. 6

   Add the evidence and the ask as their own scenes

   Real numbers from a real playtest, even a small one, then one clear request. Replace the generated voice with your own recording if the brief rewards delivery.

Common questions

How long should an educational game pitch video be? If the competition or brief gives a limit, hit it exactly. Otherwise two to three minutes. Pitch videos are often watched in a batch by tired judges, and the ones that end early with a clear ask are remembered.

Should I show the team? A single scene near the end with names and roles is enough, unless the brief asks for more. A pitch is about the game and the player; the team becomes relevant when you make the ask.

What if we have not playtested? Run the smallest possible test before you record. Ten classmates and a paper prototype for twenty minutes will give you one honest sentence of evidence, which is worth more than any amount of projected impact.

Is this different from a hackathon demo? Yes. A demo proves the thing works; a pitch argues that the thing should exist. If you built a working prototype in a weekend, how to make a hackathon demo video in an hour is the better guide.

Can I make the pitch in Hindi or another language? Yes. Write or translate the script in the language you want and generate from that; the narration follows the script. For a heritage game aimed at Indian classrooms, a Hindi version of the pitch can be a strong extra. See how to make an explainer video in Hindi.