Congressional App Challenge 2026: Build a Demo You Can Explain

A club equipment tracker can have a login screen, an animated dashboard, and no reliable way to check out an item. For a student planning a Congressional App Challenge entry, that is a useful distinction: an interface is not yet evidence that the core task works.

HAEA's recommended starting point is one interaction you can demonstrate and explain. The plan below is an editorial working method, not an extra set of competition rules.

Check the district before committing to a team

The organizer's eligibility rules require middle or high school students to reside in the US when submitting; citizenship is not required. Living in Canada does not generally qualify a student for this competition.

Enter a participating congressional district where you live or attend school. Individuals and teams of up to four can enter; at least half the team must live or attend school in that district. For a three‑person team, that means at least two qualifying members, not one.

Treat this as an initial screen, not a complete eligibility decision. Confirm district participation and every teammate's eligibility with the organizer before dividing the work.

Define one task and one failure case

Consider a hypothetical club equipment tracker using made‑up inventory and no real student records. Its first task is narrow: enter an item ID, check that the item is available, and change its status to checked out.

Write a test before adding another feature:

• Starting state: the sample item exists and is available.
• Action: enter its ID and select Check out.
• Expected result: the status changes once and a confirmation appears.
• Failure case: an unknown ID produces an explanation without changing another item.

This gives a teammate something specific to verify. If the failure case still changes the wrong item, fix that behavior before spending the next work session on dashboard animations.

A feature list describes intentions. A repeatable test shows what the current build actually does.

Use tools you can understand well enough to debug. A new framework is worth learning when it solves a specific project need, not simply because it makes the stack sound more advanced.

Keep a record of decisions, not just finished files

The 2026 rulebook assigns coding and technical development to the student or team. It requires documentation of external tools and full AI disclosure; AI may support parts of the work, not replace the technical development or the student's understanding.

A contribution log can make those distinctions easier to explain. Record the date, component, student‑made change, outside assistance, and test result while the details are still fresh.

For the hypothetical tracker, a useful entry might read: "Added an unknown‑ID check; used the language documentation to understand lookup behavior; tested a missing ID and confirmed that inventory stayed unchanged." That records a decision and its verification, rather than only saying "worked on the app."

Keep AI assistance and reused code visible in the same log. Disclosure does not make otherwise prohibited help acceptable; the competition's full rules still control.

Rehearse the proof inside a 150-second plan

The rulebook calls for a public YouTube or Vimeo demo lasting one to three minutes. It must identify the participants and app, explain purpose and audience, name the tools and languages, and show working functionality.

Here is one HAEA rehearsal budget, not an organizer‑required format:

HAEA

Segment	Time	What the viewer should understand
Context	30 seconds	Who built it, who it serves, and what task it performs
Working behavior	75 seconds	The successful interaction and one handled failure
Technical decision	30 seconds	Tools used and a specific choice you can explain
Limitation	15 seconds	What the current version does not yet do

The calculation is 30 + 75 + 30 + 15 = 150 seconds, or two minutes and 30 seconds. Half that example, 75 of 150 seconds, is reserved for showing behavior rather than describing plans.

If the explanation will not fit, identify which step is essential to proving your central task. Cut unrelated material before speeding up narration.

The rehearsal is also a scope test: can another person see what works, understand your contribution, and name the remaining limitation?

Finish the entry, not just the recording

The current registration page lists October 26, 2026, at noon Eastern Time as the deadline. Account setup is not evidence that the complete application has been submitted.

Before the deadline, use the organizer's full checklist and complete the required written responses. The rulebook also allows judges to request app and source‑code access; retain a runnable copy and your contribution records.

• Check that the submitted demo link opens while signed out.
• Keep home addresses, phone numbers, and private student records out of the public demonstration; use synthetic test data.
• Review required personal information with a parent or guardian in the organizer's application, not in a public project post.
• Retain the organizer's submission confirmation privately and verify that the entry is complete.

The next useful milestone is a build that passes your written test. Compare other options in HAEA's opportunity explorer, or begin this entry through the organizer's registration page.