The Congressional App Challenge runs on a roughly 50–60 day sprint, and most of the adults who could help — parents, tutors, teachers, Scout leaders, mentors — assume they're not qualified to. HCAI Essentials trains non-technical adults to guide that process anyway. Start where you are.
The old assumption was that helping a kid build working software required a computer-science background — that you needed to already know how to code before you could stand next to a student and be useful.
We build from proximity instead. AI can carry most of the technical implementation now. What the student still needs is an adult nearby who protects their ownership of the thinking — who asks good questions, keeps momentum when things stall, and doesn't quietly take the decisions away from them. That's the job. It's a coaching job, not an engineering job.
Nine stages, in order. Each one is small enough to finish in a sitting.
Find a real problem worth the student's attention.
Get specific about who has the problem and why it matters.
Shrink the idea to something buildable in the time you have.
Pick the simplest tools that get the job done.
Let AI carry implementation while the student directs it.
Check the build against the original problem.
Put it in front of real users and watch closely.
Revise based on what testing actually showed.
Document the decisions so the story is earned, not assumed.
Practical materials, not theory. Everything is meant to be used the same week you get it.
Worksheets and planning documents you can adapt to your own student, your own timeline, your own group.
A structured framework for moving a student from a vague idea to a coherent, buildable plan.
Language for the moments coaches usually freeze in — when a student is stuck, discouraged, or moving too fast.
A "Need Help" pathway for the moments a build genuinely needs a hand you don't have.
A running, duet-style conversation between two hosts about AI, kids, and the adults trying to help them learn something real. No scripts pretending to have it all figured out — just two people working through what's actually happening as students build.
You don't need to feel fully ready to start. The Congressional App Challenge deadline is real, but it's a manageable runway — most coaches begin before they feel prepared and build the confidence along the way.
No. That's the reframe this whole program is built on. AI carries the technical implementation; your job is to protect the student's thinking, ask good questions, and keep the project moving.
You're not expected to improvise. The facilitation scripts and response cards exist specifically for coaches running this for the first time — they tell you what to say, not just what to do.
Plan on a short, regular block of time across the sprint rather than one long session. Most coaches find an hour or two a week is enough to keep a student moving through the stages.
The framework flexes across elementary through high school. The stages stay the same; what changes is how much scaffolding a given age needs from you.
You get immediate access to the full set of resources, the framework walkthrough, and the technical support pathway — so you can start planning your first session right away.