Run a one-hour hackathon around a tiny but familiar problem. A visitor at a school maker fair wants to find the right activity. Teams build a paper guide or a small program, hand it to someone who has never seen it, and use what happens to improve it.
Each team leaves with a prototype, a before-and-after test and a one-minute demo. A pencil and a sheet of paper are enough for both versions.
In pairs, draw a two-stop map using the practice schedule below. Put a picture and a written label at each stop. Make one card for each visitor question. One student follows the map while the other watches silently. Circle the first place the visitor gets stuck, change the map and swap jobs.
What to look for Can a new visitor use the guide to find the correct place and time, or find out that the schedule does not answer their question? Let students point, draw or dictate their reasons.
Grades 6–12 · Make a fair help desk that checks its answers
Teams of two or three turn the same schedule into a lookup table, a spreadsheet or a short program. It must answer a question, identify its source row, and hand questions it cannot answer to a person. Give another team a copy with no instructions. Older students can test a time boundary or a change in the published schedule.
Connect it to AI If school policy permits, the teacher can run one visitor question through an approved AI tool using only the fictional schedule. Compare the response with the source row. The paper version uses the sample unreliable answer below and leads to the same test.
The practice schedule
These three entries describe an imaginary maker fair. Copy them onto the board or cut them into cards. All the information students may use appears here.
Maker fair source cards
Card
Activity
Where and when
A
Paper bridges
Studio A, 10–11 a.m.
B
Drawing robots
Studio B, 10:30–11:30 a.m.
C
Fair information desk
Main entrance, 9:30 a.m.–noon
Before class
Print one team sheet per group and display the three schedule cards. Keep a large-print copy at a reachable desk. Provide a text description for every picture.
Set out paper and pencils or open a blank document on a shared device. Students can take turns building, testing and recording. A partner may read questions aloud.
For an outside competition, write down the current rules on age, team size, adult help, AI use and public sharing before choosing tools. A classroom rehearsal can stay entirely in the room.
Your hour, minute by minute
0–5 · Set the problem. Ask, “If you arrived at our fair at 10:45, how would you find the robots?” Give students the three source cards and define a successful answer together.
5–12 · Make predictions. Write one question the schedule answers and one it leaves open. Record the expected answers on the team sheet before building.
12–27 · Build the first version. Draw the map or write the lookup. Pick roles. The recorder saves this version even if the team spots a mistake.
27–39 · Trade and test. Hand the prototype to a different team. The builder stays silent. The tester tries both questions and writes exactly what happened.
39–50 · Revise and test again. Change one specific thing. Repeat the failed test and the test that originally passed. Add a new question if both passed the first time.
50–60 · Share the evidence. Pairs present to one another at the same time. Use one minute per team to show the first attempt, the revision and a result. Everyone finishes by naming one question the prototype still cannot answer.
Teacher rehearsal
Which response would you let the help desk give?
A visitor asks, “Can I join drawing robots without registering?” The practice schedule gives the room and time and lists an information desk.
One mistake worth showing the class
First attempt. The team made an activity list. Their first rule returned the first program that matched a keyword. When a visitor asked, “Can I drop in for drawing robots without signing up?” the help desk answered, “Yes, drop in at Studio B.” Card B gives the location and time. It says nothing about registration.
The change. The team added a registration column marked “unknown” and a route to the information desk. The revised answer was, “Drawing robots is in Studio B from 10:30 to 11:30. To check registration, ask at the main entrance.” The team cited cards B and C.
Example team test log
Visitor question
First test
After revision
Where are the paper bridges at 10:15?
Studio A. Passed against card A.
Studio A. Still passes.
Can I join drawing robots without registering?
“Yes.” No supporting source. Failed.
“Ask at the main entrance.” Supported by B and C. Passed.
Demo script. “We thought the activity name was enough to answer every question about it. Our tester asked about registration. We changed the guide to show what is known and where to ask. Both test questions now pass. We still need the organizer's answer about registration.”
Give every team a record of its work
The one-page handout has room for the visitor’s goal, a sketch or decision rule, two test questions, a revision and a short record of help received. Students can write on paper or type into the sheet and print their answers. Open the editable student worksheet · Get the one-page PDF for your class
Score what students can demonstrate
Use four criteria worth two points each. Ask each learner to explain one team decision by speaking, pointing or writing. This is a classroom rubric. Outside contests publish their own scoring criteria.
Classroom scorecard · 8 points possible
Criterion
0 points
1 point
2 points
Visitor and goal
No user or task identified.
Names a visitor or task.
Names both and describes a result a tester can observe.
Use of evidence
Answers lack support.
One answer matches a source card.
Points to the source for a known answer and handles a missing fact explicitly.
Testing and revision
No recorded test.
Records one result or a change.
Records two tests, makes a change and retests both questions.
Student explanation
Design choices are unclear.
Describes what the team built.
Explains a choice and identifies the sources, tools or people that helped.
Before this becomes a contest entry
Have students write their own project question. Use the fair example to rehearse a method. Give each team the rules for the competition they actually want to enter.
Technovation Challenge · Keep a record of AI assistance
For the 2027 season, teams identify AI tools in the written submission, explain which work each tool supported, and show how students checked or developed its output. Student teams create their own deliverables. The oldest teammate’s age on August 1, 2027 determines the division. The guide lists ages 8–12, 13–15 and 16–18. Each student profile includes a parental consent form. 2027 eligibility, honor code and submission requirements
Future Engineers · Keep the entry’s ideas and substantive work student-created
The general rules prohibit using AI to develop the substantive content or ideas of an entry. The sponsor may allow limited spelling or similar mechanical editing. Check the individual challenge for its additional requirements. A good coaching question here is “How could you test your idea?” Give students the space to develop the answer themselves. Future Engineers entry rules, section 4.4
Keep teaching the skill
For Computer Science Education Week, December 7–13, 2026. The Hour of AI collection includes free activities for grades 3–12. Pick one activity your class can finish, open its teacher notes and try the student experience before class. Choose an Hour of AI activity · Read the 2026 program announcement
For a middle-school follow-up. Experience AI, from the Raspberry Pi Foundation and Google DeepMind, offers lessons for ages 11–14. Use the learning materials to explore how a system learns from examples after your students have tested a hand-written rule. Explore Experience AI
For the next student lesson. Day of AI offers a free introductory unit with versions for ages 8–10, 11–13 and 14–18. Use the algorithm lesson to have students write and debug the sequence behind their fair guide. Educators register with email for the curriculum. Choose a Day of AI age band · Curriculum access
For your own preparation. The free, self-paced AI 101 for Educators course on Code.org includes a module on responsible AI. Use it to plan how you’ll teach students to recognize an unsupported answer. Start AI 101 for Educators
For student teams
Ready for a real audience?
Choose a local robotics session, an online teen hackathon or a creative coding contest with your students. Review the host’s age, team and AI rules before students begin an entry.