CityGov Hackathon 2026

Official Rules: 2026 CityGov Hackathon Challenge

 NO PURCHASE NECESSARY. VOID WHERE PROHIBITED.

 1. Hackathon Summary

1.1 Name. 2026 CityGov Hackathon Challenge

1.2 Organizer: CityGov

1.3 Challenge Question. How can colleges and universities help students turn education into meaningful careers?

1.4 Purpose. Many students graduate with talent, skills, and ambition but still lack clear pathways to internships, public-sector jobs, career guidance, professional networks, and long-term opportunity. The Hackathon invites participants to create practical, realistic solutions that make the move from education to employment easier and more equitable.

1.5 Format. The Hackathon is an online competition with three rounds. All updates and advancement results appear in the “Spotlights” section of CityGov.

1.6 Binding agreement.  By registering or submitting an entry, each participant accepts these Official Rules, the CityGov Terms of Use, and the CityGov Privacy Policy. If these Rules conflict with the Terms of Use on a Hackathon matter, these Rules control.

 2. Timeline

·       Official announcement and rules published  October 12, 2026

·       Registration opens October 12, 2026

·       Registration closes October 26, 2026

·       Submission deadline November 6, 2026

·       Round 1 results posted in Spotlights November 9, 2026

·       Round 2 results posted in Spotlights November 16, 2026

·       Winners announced in Spotlights November 20, 2026

·       Prize delivery November 27, 2026

2.1 All deadlines use Eastern Time. The time stamp on the CityGov platform is the official time.

2.2 The Organizer may extend or change any date. Changes will be posted in Spotlights, and the posted version controls.

3. Eligibility

3.1 Who may enter. Anyone who meets all of the following:

• Is at least 18 years old.

• Lives in the United States.

• Has created a CityGov account with a first name, last name, and completed their profile with a photo.

• Is not barred by Section 3.4.

3.2 Who we expect to participate. Students, recent graduates, job seekers, career changers, educators, career counselors, workforce professionals, civic technologists, designers, developers, researchers, and public-sector staff. No particular background is required. Winners may donate the proceeds to a charity, cause, or organization of their choosing with the CityGov endorsement!

3.3 Minors. Participants aged 17 may enter with written consent from a parent or guardian, and the adult must accept the prize on their behalf.

3.4 Ineligible persons.

• CityGov owners, employees, contractors, and interns, and their immediate family and household members.

• Judges, mentors, and anyone involved in designing or administering the Hackathon, as well as their immediate family and household members.

• Anyone on a U.S. government restricted-party or sanctions list, or located in an embargoed jurisdiction.

• Government employees whose agency or ethics rules prohibit accepting a prize. These participants are responsible for checking their own rules and may compete without receiving a prize.

3.5 Teams.

• Teams may have 1–4 members. A solo entry counts as a team of one.

• Every team member must have their own CityGov account with a completed profile.

• A person may belong to only one team.

• Each team names one Team Lead, who submits entries and receives communications for the team. Notice to the Team Lead counts as notice to all members.

• Members may be added or removed before the Round 1 deadline. After that, changes need written Organizer approval. Adding members after Round 1 to bring in outside work is not permitted.

3.6 Employer and school permissions. Participants who work for an employer, or who are enrolled at a school with IP or outside-activity policies, are responsible for confirming that their participation and submission are allowed. The Organizer is not liable for conflicts between a participant and their employer or school.

4. Registration

4.1 Registration requires four steps:

1. Create a CityGov account with accurate information.

2. Complete the profile. Define the minimum set of fields, including name, email, school or organization, role, and bio.

3. Register as an individual or create or join a team.

4. Accept these Official Rules.

4.2 Registration is free.

4.3 Participants must keep their profile information accurate through the end of the Hackathon. False or misleading information may lead to disqualification.

4.4 One account per person. Creating duplicate accounts is prohibited and will be checked by IP and other means.

5. What You May Build

5.1 Accepted solution types. App, platform, prototype, service model, public policy, campaign, tool, or other solution that improves career outcomes after education.

5.2 Focus areas (illustrative, not limiting).

• Pathways from classroom to internships and first jobs

• Public-sector and civic career access

• Career guidance, advising, and mentoring models

• Professional network building for students without existing connections

• Skills translation, credentials, and portfolios

• Employer, school, and city partnership models

• Equity and access, including first-generation students, rural and low-income students, adult learners, veterans, and career changers

• Measuring and improving post-graduation outcomes

5.3 Requirements for every project.

• It must answer the challenge question.

• It must be created for this Hackathon. Existing projects are eligible only if the submission clearly identifies what was built or substantially improved during the Hackathon period and must be disclosed.

• It must be lawful, ethical, and safe for its intended users.

• It must be explainable to a non-technical audience.

5.4 Not accepted.

• Projects unrelated to education-to-career outcomes

• Projects that promote discrimination, deception, or exploitation of job seekers (for example, pay-to-play job schemes or misleading placement claims)

• Projects that require collecting sensitive personal data without a clear consent and protection plan

• Content that is unlawful, defamatory, obscene, or infringing

6. Submission Requirements

6.1 Where to submit. Through the designated CityGov submission portal. Email, social media, and other channels will not be accepted unless announced in Spotlights.

6.2 Required elements.

• Project title

• Team information: Names, CityGov profile links, and the Team Lead

• Problem statement: The specific barrier between education and employment, and who experiences it

• Target users: Who benefits; students, graduates, job seekers, career changers, or others

• Solution description: Up to 500–750 words describing what it is and how it works

• Equity statement: Up to 400 words on how it helps people who lack access to networks and opportunity

• Pilot plan: How a school, college, workforce organization, employer, or city could test it. Include who runs it, timeline, resources, cost estimate, and risks

• Success metrics:  At least 2–3 measurable outcomes, such as internship placements, job interviews, or advising reach

• Demonstration: Link to a demo, prototype, mockup, slide deck, policy brief, or campaign samples.

• Optional Video (Round 2) | [2–3] minutes, in English or with English captions, hosted on YouTube/Vimeo/or simply recorded on your smartphone with viewing access set to link-accessible.

• AI-use disclosure: required if AI tools were used in a significant way (see Section 12)

• Sources and credits: Third-party tools, data, open-source components, and references

6.3 Format rules.

• Files must be [PDF, PPTX, PNG, JPG, MP4, or a public link].

• Links must remain active until winners are announced.

• Submissions must be in English.

• Judges are not required to download software, create accounts, or pay to view a project.

6.4 Late and incomplete entries:  Late or incomplete submissions may be disqualified at the Organizer's discretion. The Organizer may give a short [24-hour] cure window for minor technical problems but is not required to.

6.5 Resubmission* A team may update its submission until each round's deadline. Only the latest version at the deadline will be judged.

7. The Three Rounds

The Organizer will announce the specific format, deliverables, and number of advancing teams when each round launches. Advancement results will be posted in Spotlights.

7.1 Teams may be notified of advancement in Spotlights and through email or in-platform notification. Participants are responsible for checking both.

7.2 A team that does not advance will get ½ point towards the next Hackathon event.

7.3 The Organizer may adjust the number of advancing teams, add or merge rounds, or change round formats if needed.

7.4 Final presentation. Finalists may be asked to give a [5–7] minute presentation followed by [3–5] minutes of questions, live or by recorded video. A finalist who cannot present at the scheduled time must notify the Organizer in advance, and the Organizer will try to accommodate them without any guarantee. 

7.5 Winner(s) will be featured on the CityGov spotlights page, social media, and national television (if approved).

8. Judging

8.1 Panel. Judges may include CityGov leadership, higher-education professionals, workforce and public-sector experts, employers, and community representatives. Panel members will be disclosed in Spotlights / upon request. Judges must disclose conflicts of interest and recuse themselves from scoring any team with which they have a relationship.

8.2 Scoring. Each criterion is scored from 0 to 100.

Criterion: What judges look for

A. Barrier clarity: Does the project clearly identify and address a specific barrier between education and employment? Is the problem well defined and evidence-based?   Scored 0-10

B. Usefulness: Would it be useful to students, graduates, job seekers, or career changers? Is it easy to understand and use?   Scored 0-10

C. Creativity and originality: Is the approach new, inventive, or a fresh combination of existing ideas?   Scored 0-10

D. Pilot feasibility: Can a school, college, workforce organization, employer, or city realistically pilot it? Are resources, timeline, partners, and risks realistic?  Scored 0-10  

E. Career impact and equity: Could it create stronger career outcomes, especially for people who lack access to networks and opportunity? Scored 0-10

F. Public-sector and civic relevance: Does it connect education to public-sector jobs, public service, or civic workforce needs? Does it involve cities, agencies, or public institutions in a meaningful way? Scored 0-10  

G. Scalability and sustainability: Could it grow beyond a single pilot to more schools, regions, or users? Is there a realistic plan to fund, staff, and maintain it? Scored 0-10  

H. Measurable outcomes: Does it define clear success metrics, such as placements, interviews, retention, or advising reach? Is there a credible way to track results? Scored 0-10  

I. Accessibility and inclusive design: Is it usable by people with different abilities, devices, languages, backgrounds, and levels of experience? Does it address privacy and avoid bias? Scored 0-10  

J. Presentation and communication: Is the submission clear, organized, and persuasive? Does the demo, video, or pitch show the idea effectively to a non-technical audience? Scored 0-10  

8.3 Score interpretation guide.

Participants can polish their submissions after each round!

91-100 (Exemplary): Fully meets the criterion in an exceptional way, with specific, compelling evidence, clear originality, and little to no room for improvement. (Winners typically live here)

81-90 (Excellent): Fully meets the criterion with specific, convincing evidence. (This will get you into finals)

61-80 (Satisfactory): Meets the criterion with minor gaps. (This will get you into round 2)

41-60 (Adequate): Partially meets the criterion.

21-40 (Weak): Barely addresses the criterion.

0-20 (Not shown): Does not address the criterion.

8.4 Final ranking.  The total weighted score from the final round determines the winners. Scores from earlier rounds do not carry forward.

8.5 Tie-breakers, in order.

1. The higher score on Criterion E (career impact and equity)

2. The higher score on Criterion D (pilot feasibility)

3. A vote of the judging panel

8.6 Decisions. Judges' decisions are final and binding on all matters related to the Hackathon. The Organizer is not required to give individual scores or feedback, though it may choose to share summary feedback.

8.7 Judging independence.  Scores must be based only on the submission materials and presentation. Participants may not contact judges to influence results. Doing so will result in disqualification.

9. Prizes

9.1 Prize table.

-          1st place  $1,000

-          2nd place  $200

-          3rd place  $100

9.2 non-cash recognition.  Winners [and finalists] may receive recognition in Spotlights, on CityGov's website and social media, and in partner communications including television and radio. Winners may also be considered for opportunities to advance their idea, such as introductions, pilot conversations, or feature placement. These opportunities are discretionary and do not constitute a guarantee, a job offer, an investment, a contract, or a partnership.

9.3 One prize per team.  A team receives one prize per project, distributed among the team. A person may not win more than one prize, even if they appear on more than one team (which Section 3.5 does not allow).

9.4 Team prizes.  A team prize is divided equally among members unless the Team Lead gives the Organizer a written, all-member-signed allocation before payment. The Organizer will pay the Team Lead or each member individually and is not responsible for how the team divides funds.

9.5 Payment method.  Prizes will be paid by check, Venmo, PayPal, or similar within days after winner verification. Winners are responsible for any payment fees and taxes not associated with CityGov.

9.6 Taxes.  Winners are solely responsible for federal, state, and local taxes on prizes. The Organizer may require a W-9 (or W-8 for non-U.S. persons) and may issue a Form 1099 where required by law.

9.7 No substitution. Prizes are non-transferable and have no cash substitute, except that the Organizer may substitute a prize of equal or greater value if circumstances require.

9.8 Withholding prizes. The Organizer may decline to award a prize if no entry meets a reasonable quality standard or if the winners cannot be verified.

10. Winner Verification

10.1 Potential winners will be notified by email and Spotlights. They must respond within 5  days.

10.2 Verification may require:

• Proof of identity and eligibility

• A signed eligibility and publicity release

• Confirmation of team membership and allocation (for teams)

10.3 If a winner fails to respond or verify in time, is ineligible, or declines the prize, the Organizer may disqualify that team and award the prize to the next-highest-scoring team.

11. Intellectual Property

11.1 Ownership. Participants retain ownership of their projects and related intellectual property. The Organizer claims no ownership.

11.2 License to the Organizer. By submitting, each participant grants CityGov a non-exclusive, worldwide, royalty-free, perpetual license to use, reproduce, display, publish, and describe the submission's non-confidential materials (title, summary, images, video, and presentation) to operate, judge, and promote the Hackathon, CityGov, and future hackathons. This includes use in Spotlights, on the website, in social media, in investor and partner materials, and in reports. This license does not allow CityGov to build or sell the project itself.

11.3 No obligation to use ideas. The Organizer and its partners may independently develop products or programs that may resemble submissions. Participants should not submit trade secrets or patentable information they are not prepared to disclose. CityGov will not use a participant's submission to build a competing product without a separate agreement.

11.4 Participant warranties. By submitting, each participant represents that:

• The submission is original, or that they have the right to use all included material.

• It does not infringe any copyright, trademark, patent, privacy right, or other right.

• It contains no malware or harmful code. You will be liable

• All team members consent to the submission and these Rules.

11.5 Third-party and open-source materials.  These may be used if properly licensed and credited in the submission.

11.6 Confidential information. Do not include confidential, proprietary, classified, or non-public information of any employer, school, agency, or other party.

11.7 Pilots and commercialization. Any pilot, partnership, license, investment, or commercial relationship between CityGov (or any partner) and a participant requires a separate written agreement.

12. Use of AI and Other Tools

12.1 Participants may use AI tools, no-code platforms, templates, open-source libraries, and other tools.

12.2 Participants must disclose significant AI use in the submission, including what tools were used and for what purpose (for example, drafting text, generating code, creating images, or analyzing data).  Failure to do so will result in disqualification.

12.3 Participants are responsible for the accuracy, originality, legal compliance, and bias review of all AI-assisted work, and must verify any data or claims.

12.4 Participants must not enter confidential or personal data into AI tools in violation of those tools' terms or applicable law.

12.5 Projects made entirely of unreviewed AI output, with no human judgment, understanding, or contribution, may be scored significantly lower or disqualified.

13. Data, Privacy, and Responsible Design

13.1 Do not use or submit real personal data about students, job seekers, or other individuals unless you have their documented consent and a lawful basis. Use sample, synthetic, or anonymized data in demos.

13.2 Projects that handle student records must address applicable laws, such as FERPA, and projects that serve minors must address children's privacy requirements.

13.3 Projects should address algorithmic bias, accessibility (for example, WCAG alignment), and fairness. Judges may consider these in scoring.

13.4 Organizer data use. CityGov will collect registration and submission information to administer the Hackathon, communicate with participants, verify winners, and promote results. It will handle this information in accordance with the CityGov Privacy Policy and will not sell personal information related to Hackathon participation.

13.5 Platform security.  Participants must not probe, scan, or test the security of CityGov or any partner system without written permission.

14. Code of Conduct

14.1 Expected behavior. Be respectful, honest, collaborative, and inclusive. Give credit where it is due.

14.2 Prohibited conduct.

• Harassment, bullying, hate speech, discrimination, or threats

• Plagiarism, fabricated data, or misrepresenting your work, credentials, or results

• Hacking, tampering with, or abusing the CityGov platform, the submission process, or other participants' work

• Creating multiple accounts, manipulating scores or votes, or coordinating fake reviews or engagement

• Contacting judges to lobby for results

• Sharing others' submissions without permission

• Violating law or third-party rights

14.3 Reporting. Report concerns through the CityGov contact form. The Organizer will review reports and may act at its discretion, including removal from the Hackathon.

15. Disqualification and Appeals

15.1 The Organizer may disqualify any participant, team, or submission that violates these Rules, the Code of Conduct, or applicable law, that provides false information, or that threatens the integrity or safety of the Hackathon.

15.2 Disqualified participants forfeit all prizes and recognition. If a prize has been paid, the Organizer may require its return.

15.3 Appeals. A participant may submit a written appeal within 3 business days of notice of disqualification, explaining why the decision should be reconsidered. The Organizer will respond within 5 business days. Scores themselves may not be appealed, and the Organizer's decision on appeals is final.

16. Publicity

16.1 By participating, each participant allows CityGov to identify them by name, profile, school or organization, and project (but not other personal data) in connection with the Hackathon. This includes announcing finalists and winners.

16.2 By accepting a prize, winners additionally grant CityGov permission to use their name, likeness, voice, and project description in Hackathon and CityGov promotion, without further compensation or approval, unless prohibited by law.

16.3 A participant who has a safety or privacy concern may request anonymity through our contact form before the winners are announced. The Organizer will try to accommodate reasonable requests, which may affect prize eligibility.

17. Accessibility and Accommodations

CityGov wants everyone to be able to participate. Participants who need accommodation (for example, an alternative submission format or extra time to present) should contact the organizers at least 5 days before the relevant deadline.

18. Disclaimers and Limitation of Liability

18.1 The Hackathon is provided "as is." The Organizer makes no warranty about the availability of the platform, the submission system, or Hackathon content.

18.2 The Organizer is not responsible for lost, late, misdirected, or incomplete entries, technical failures, network or platform problems, or human error.

18.3 To the fullest extent allowed by law, participants release CityGov, its officers, employees, partners, sponsors, judges, and agents from any liability, claim, or loss arising from participation or from the acceptance, use, or misuse of any prize.

18.4 Nothing in these Rules limits liability that cannot legally be limited.

18.5 No endorsement. Participation, advancement, or winning does not imply endorsement by CityGov, a school, a government, or any partner, and participants may not claim otherwise.

18.6 Not an employment or investment offer. Nothing in the Hackathon creates an employment, agency, partnership, or investment relationship.

19. Changes, Cancellation, and Governing Law

19.1 The Organizer may modify these Rules, change dates, or suspend or cancel the Hackathon if fraud, technical failure, legal issues, or other circumstances beyond its control affect fairness or operation. Notice will be posted in Spotlights.

19.2 If a provision is found unenforceable, the others remain in effect.

19.3 These Rules are governed by the laws of the State of New York, without regard to conflict-of-law principles. Disputes will be resolved in the state or federal courts located in New York County, New York, and participants consent to that jurisdiction.

19.4 The Organizer's failure to enforce any provision is not a waiver of it.

 20. Contact and Updates

-          Questions and support: Hackathon@CityGov

-          Accommodation: Hackathon@CityGov.com

-          Code-of-conduct reports and appeals: Hackathon@CityGov.com

-          Official updates, advancement, and results: the Spotlights section of CityGov

Sponsor/administrator: Cambridge Management Insights, LLC. Rules version: 1.0, published October 12, 2026.

 Appendix A: Participant Checklist

 -          [ ] Created a CityGov account

-          [ ] Completed my profile

-          [ ] Registered as an individual or joined a team (and named a Team Lead)

-          [ ] Confirmed I'm eligible, and that my employer or school allows participation

-          [ ] Written a clear problem statement and identified my target users

-          [ ] Included an equity statement

-          [ ] Built a demo, prototype, mockup, brief, or campaign sample

-          [ ] Written a pilot plan with partners, timeline, cost, risks, and metrics

-          [ ] Disclosed AI use and credited third-party materials

-          [ ] Used only sample or anonymized data

-          [ ] Verified that all links work and are viewable

-          [ ] Submitted before the deadline

Appendix B: Pilot Plan Template

1.      Pilot host: which school, college, workforce organization, employer, or city?

2.      Participants: who and how many?

3.      Timeline: 30, 60, or 90 days, with milestones.

4.      Resources needed: staff, funding, technology, and partnerships.

5.      Estimated cost: one-time and ongoing.

6.      Success metrics: targets and how they'll be measured.

7.      Risks and mitigation: privacy, adoption, equity, and capacity.

8.      Scale-up path: how it could expand if the pilot works.

 Appendix C: Short Public Announcement (October 12)

The 2026 CityGov Hackathon Challenge is officially open!

How can colleges and universities help students turn education into meaningful careers? Create a CityGov account, complete your profile, and build an app, platform, prototype, service model, policy, campaign, or tool that makes the path from education to employment easier and fairer. Enter solo or with a team. Three rounds. Three prizes: $1,000, $200, and $100. Watch Spotlights to see if you've advanced. Full Official Rules are on CityGov.