Congressional App Challenge 2026: What Middle and High School Coders Need to Know Before the October Deadline

Published August 26, 2026 · Contest profile · Computer science · Grades 6–12

Two students working together on laptop code at a school desk

The Congressional App Challenge is the rare student competition where the field you are competing against is decided by geography rather than by talent pool. Entries are judged within a single congressional district, not nationally — which means a strong submission in a district where six students entered has a materially better chance than the same submission in a district where sixty did. The 2026 cycle closes on October 26, 2026 at 12:00 p.m. ET, and there is no entry fee. The rules are short. The part that eliminates students is not the rules.

The deadline that is not yours

There are two deadlines in this competition and students only ever hear about one of them. October 26 is the student submission deadline. September 15, 2026 is the deadline for a Member of Congress to register their district for the 2026 cycle.

Participation is decided by each Member’s office. If your representative does not register the district, there is no challenge in your district to enter — and no amount of preparation changes that. The official site maintains a list of participating districts, and it is the first thing to check, before you write a line of code. If your district is not on it in early September, the productive move is a short, polite email to the district office asking whether they intend to participate. Offices do respond to this, and students asking is a recognised part of how districts end up registered.

Who is eligible

Grade level: you must be enrolled in middle or high school as of October 26, 2026 — the submission date, not the date you start building. Middle school generally means grades 6–8, with regional variation.
Residency: U.S. residents at the time of submission.
District: you may compete in the district where you live or the district where you attend school — but only one. Submitting in multiple districts is not permitted.
Teams: individuals or teams of up to four students. At least half the team must be eligible to compete in the district you are entering.
App creation window: the app must have been created after October 30, 2025. A project from a previous cycle does not carry forward.

The team-composition rule is the one that catches groups formed across school boundaries. A team of four with only one member eligible in the chosen district does not satisfy “at least half.” Work out which district you are entering before you finalise the team, not after.

What you are allowed to build

Unusually little is constrained. Any programming language, any platform, no limits on the application’s theme or topic. Web app, native mobile, desktop, game, hardware-adjacent project — all in scope. Block-based languages are not excluded, which matters for younger middle school entrants who have not moved to text-based code yet.

That openness shifts the difficulty from technical gatekeeping to judgment. When nothing is prescribed, the submissions that stand out are the ones that solve a problem the judges can recognise as real — frequently something specific to the student’s own school, neighbourhood, or community. A competent app addressing a concrete local problem consistently reads better in district judging than a technically ambitious app with no evident user.

Before you start building

Confirm your district is registered. Check the participating-districts list on the official site. This is the only step with a hard external dependency.
Read the current rulebook yourself. The organisers publish a full PDF rulebook for each cycle covering submission components — code, demonstration video, and written responses — and the specifics of format and length are set there rather than on the summary pages. Third-party guides go stale between cycles; the rulebook does not.
Register early, submit early. Registration and submission both run through the same student portal, and the deadline is a midday cutoff rather than end of day. A noon deadline reliably catches students who planned to finish the night before.
Build the demo material as you go. The video and written explanation are graded work, not paperwork. Recording a walkthrough while the app is fresh in your head is faster and better than reconstructing it in the last week.
Check your school’s and the contest’s position on AI-assisted code against the current rulebook before relying on generated code in a submission. Policies across student competitions have been tightening, and this is a judged, attributed piece of work.

Why it is worth entering

District-level judging is the structural advantage. Most national STEM competitions put a student against a self-selected field of tens of thousands. This one puts them against the other students in their district who both knew about it and finished — and the finishing rate is the real filter. Winning entries are recognised by the Member of Congress and have historically been displayed in the U.S. Capitol, which is a distinctive line on a college application and a genuinely unusual thing to have done in ninth grade.

Rules and dates change between cycles. Verify every date above against the official Congressional App Challenge site and its current rulebook before you plan around them — particularly the district-registration status, which is the only item on this list that is not in your control.