Go Code Colorado is committed to an open and transparent process. All Go Code Colorado rules and judging criteria are publicly available throughout the competition.
If you have questions about any of the rules, regulations, or requirements email us anytime.
You must provide a completed and signed Go Code Colorado Terms of Participation and Release Form to
participate in the challenge.
Read the following Go Code Colorado rules:
Go Code Colorado CHALLENGE: Official Participant Rules 2019
NO PURCHASE NECESSARY TO ENTER OR WIN. A PURCHASE WILL NOT IMPROVE YOUR CHANCES OF WINNING. VOID WHERE PROHIBITED OR RESTRICTED.
- To enter the Go Code Colorado Challenge, log on to gocode.colorado.gov, and register to attend one of the Challenge Day events.
- Participants must submit an entry that uses public data to assist with a business decision-making process.
- In creating their entry, participants must use at least one dataset that is publicly available on the Colorado Information Marketplace (CIM), which can be found at data.colorado.gov. In addition to at least one public dataset from CIM, participants may also use private data (with appropriate use license), public data that does not come from CIM, and open data.
- Teams are encouraged (but not required) to work on their idea leading up to Challenge Day, and show up to Challenge Day prepared to work on their idea. A minimum of one person from each team must attend Challenge Day and register their team name, GitHub repository and Semi-Final Competition location with the Go Code Colorado organizers.
- All teams must complete the “Virtual Checkpoint” form after Challenge Day and before Semi-Final submission.
- Western Slope (Grand Junction) participants must submit their Semi-Final entry by Monday April 15, 2019 by 5:00 PM MDT, and Front Range (Denver) participants must submit their Semi-Final entry by Monday April 22, 2019 by 5:00 PM MDT. Semi-Final submissions include all materials in the team GitHub repository in addition to “Virtual Presentation” of recorded screencast of presentation slides with narrated audio.
- A panel of judges (“Judges”), will be selected by Go Code Colorado organizers. Judges, in their sole discretion, will select the winners of the Semi-Final Competition based on the judging criteria, technical evaluation and data evaluation as published on gocode.colorado.gov/judging-criteria.
- On Friday May 3, 2019 the Judges will choose twelve (12) finalist teams (“Finalist Teams”), three (3) Semi-Final lists from each track (2) from each region (2). Semi-Final submissions are judged against other teams who submitted from the same region and same competition track. Competition location is defined on Challenge Day, competition track is defined at Semi-Final submission by following submission instructions for each track.
- The 12 Finalist Teams will move on to the next round of competition (the “Final Competition”) and be judged irrespective of initial competition region.
- The 12 Finalist Teams are eligible to receive personalized mentor support as coordinated by Go Code Colorado organizers.
- All Finalist Teams must submit their entries for the Final Competition by 4:00 PM MST Monday, May 20, 2019.
- The Finalist Teams in the Product track must develop a market-relevant web or mobile application, and provide associated code in their designated repository. For Finalist Teams to be eligible to win an award at the Final Competition in the “Product Track”, the submission must be a minimum viable product (MVP). This means a product that is available for use by public users (or login/testflight information be provided with the final submission). Full submission requirements are found in the Rules and detailed in the “Product Track” Judging Criteria https://gocode.colorado.gov/rules/judging-criteria/
- The Finalist Teams in the “Analytics Track” must produce an analysis that tells a data story, and provide associated code or other documentation to their designated repository. For Finalist Teams to be eligible to win an award at the Final Competition in the “Analytics Track”, the submission must be digital and publicly accessible. This means a product that is usable by public consumers. Full submission requirements are found in below in the Rules and detailed in “Analytics Track” Judging Criteria https://gocode.colorado.gov/rules/judging-criteria/
- To be eligible to win, the Finalist Teams must attend and present at the Final Competition in Denver, Colorado on Thursday May 30, 2019. Teams must arrive no later than 4:00 PM MST and stay until the winning teams (“Winners”) are announced.
- The Finalist Teams in the “Product Track” must present their work to a group audience in a 5 minute pitch presentation and answer questions from Judges for up to 5 minutes.
- The Finalist Teams in the “Analytics Track” must present their work through a tabletop demo with 5 minute data story and answer questions from Judges for up to 5 minutes.
- Judges, in their sole discretion, will select the winners of the Final Competition based on the judging criteria as published on gocode.colorado.gov/judging-criteria.
- Winners will be announced at the Final Competition on May 30, 2019.
YOU MAY ONLY COMPETE IF:
- You are an individual legally residing in one of the fifty United States or the District of Columbia or you are a corporation, LLC, or other organization that is domiciled in the United States and properly formed at the time of entry.
- You are fourteen years old or older. If you are under eighteen years old, you must identify yourself as a minor and provide proof of parental consent (NOTE this link is for 2018 — update to 2019 coming soon).
- If you are a team, corporation, or nonprofit organization, all individual members must meet the eligibility requirements.
- If you have participated in the Go Code Colorado Challenge previously, you may participate again if you meet all of the other eligibility requirements.
- An individual may join more than one team, and in more than one track. Teams entering both tracks with two clearly distinct separate entries (as defined by different topic areas) is acceptable. Teams entering the same entry in both tracks is not permitted.
- A team must consist of at least two people.
- You must disclose any actual or potential conflicts of interest you have with: (a) an employee of a sponsor; (b) employees or contractors of Go Code Colorado; (c) the Colorado Department of State; (d) the State of Colorado; (e) competition Judges, their immediate families (spouse, parents and step-parents, siblings and step-siblings, and children and step-children), and household members (people who share the same residence at least three months out of the year); (f) competition mentors, their immediate families, and household members.
- All programs associated with Go Code Colorado are subject to all applicable United States federal, state, and local laws and regulations.
- By participating in Go Code Colorado, you agree to any and all Go Code Colorado rules and procedures and understand and agree that the Judges’ decisions are final and binding on all matters related to the Go Code Colorado Challenge.
- You have no right, power, or authority to bind Go Code Colorado, the Colorado Department of State, and the State of Colorado to the fulfillment of any condition, contract, or obligation or to create any liability binding on Go Code Colorado, the Colorado Department of State, and the State of Colorado.
- You may not be an employee or independent contractor of Go Code Colorado, the Colorado Department of State, the Business Intelligence Center, or the Offices of the Governor (including, but not limited to, the Office of Economic Development and International Trade and the Office of Information Technology).
- All entries created for the Go Code Colorado Challenge should be written for the competition or specifically improved from an existing idea to compete in the competition. This means that for the “Product Track” the web or mobile application was not commercially available before February 20, 2019. This means for the “Analytics Track” the analysis or research had not been completed and published prior to February 20, 2019.
- Each Semi-Finalist team must submit the code and/or related documentation for their entry to a repository on GitHub, within the Go Code Colorado organization, by 5:00 PM MDT on April 15, 2019 (GJ) and April 22, 2019 (Den), for the Semi-Final Review. The submission must include all source code and related documentation of the entry, and a recorded video of the powerpoint slides with narrated audio.
- Semi-final video presentation must follow a template and technology established for each track for submission as outlined in GoCodeColorado GitHub Knowledge Base Semi-Final Submission Guidelines. These guidelines outline the tools to record audio and slides using specified recording software intended to create standardization in the format of submissions. These videos may be used by Go Code Colorado for promotional material if deemed appropriate by the Go Code Colorado organization.
- Each Finalist Team must submit the code and/or related documentation for their entry to a repository on GitHub, within the Go Code Colorado organization, by 3:00 PM MDT on May 20, 2019, for the Final Competition. The submission must include all source code and a README file with documentation, and where relevant the submission should also include a data architecture diagram. Details for submission are outlined in GoCodeColorado GitHub Knowledge Base Final Submission Guidelines.
- Each Finalist Team must submit a completed, accurate Final Competition Acknowledgement and Disclosure of Team Members form (NOTE this link is for 2018 — update to 2019 coming soon) by 5:00 PM MDT on May 20, 2019, for the Final Competition.
- The submission will be reviewed for technical merit as part of the final judging criteria.
- All materials submitted to Go Code Colorado must be in English.
- Go Code Colorado reserves the right to disqualify any entry that is offensive, as determined by Go Code Colorado, in our sole discretion. Please ensure your entry is appropriate for all viewing audiences.
- Each of the winners of the Final Competition will receive a cash award of ,000. The odds of winning depend on the number of registered participants.
- Go Code Colorado reserves the right to assess your eligibility and compliance with these Official Participant Rules at any point during the event series. If Go Code Colorado requires any assistance in order to assess your compliance, you must promptly provide that assistance. If you do not provide the requested assistance in a timely manner, or if Go Code Colorado has reason to believe that you are not complying with the Official Participant Rules, you may be disqualified, in Go Code Colorado’s sole discretion.
- Go Code Colorado reserves the right to modify the terms of these Official Participant Rules at any time in its sole and exclusive discretion. All notifications and changes to these Official Participant Rules will be posted on gocode.colorado.gov.
REVISED AS OF FEBRUARY 18, 2019
GO CODE COLORADO JUDGING CRITERIA
This Go Code Colorado judging criteria is to be used by Go Code Colorado Judges (“Judges”) in choosing winners of the challenge. 2019 marks the first year of two different competition tracks, and this criteria and guidelines, along with the related technical and data evaluation sheets, detail the requirements for submission.
Semi-Final and Final Competition judging will be based on material provided in each team’s GitHub repository in the Go Code Colorado GitHub Organization. Scoring will be a weighted composite of the 5 factors shown in tables below, detailed scoring from the technical evaluation and data evaluation, and material covered during team presentations.
Business Decision Makers
A Business Decision Maker (BDM) is someone within a business responsible for strategic and/or tactical decisions. The competition is funded by the Colorado Secretary of State’s Business and Licensing Division, and therefore the focus of this competition is on businesses. Non-Profit entities can be considered businesses for the purpose of the competition, so long as the solution still tracks toward the BDM of that entity. Creating a solution for a Government Entity is entirely outside of the scope of the competition.
Judging Criteria Category Weights
Judging Criteria Tracks – Side by Side
2019 Challenge Statement
Use public data to deliver solutions to or insights for a business decision-maker.
BUSINESS PRODUCT TRACK – In the Product Track, teams compete to create market-relevant applications or tools – using public data – that provide solutions for business decision makers in Colorado.
BUSINESS ANALYTICS TRACK – In the Analytics Track, teams compete to analyze Colorado’s public data to provide useful insights that benefit business decision makers in Colorado.
The Difference Between the Analytics and Product Tracks
- Allows market-relevant web/mobile application user (BDM) to come to their own decision from the data and information as presented in the product.
- The BDM interprets the data story based on their individual needs and use cases guiding their use of the application.
- Product tech score is a composite of (1) user experience, (2) sustainability, (3) functionality, (4) logical structure.
- Product data score value scale: (1) increasing accessibility (2) combination (3) analysis.
- Deliver 5 minute pitch presentation with 5 minutes for questions at the Final Event.
- Results are presented as code and related documentation for market-relevant web/mobile application, and must be understandable and rebuildable from the repo.
- Must be automated, and any manual work is only proof of concept for future functioning additions.
- Has concrete findings, and concrete insights (data, information, knowledge) that are pertinent to a BDM.
- Results are conveyed through the telling of the data story by the analyst and presenting as a question and answer for the BDM.
- Analytics tech score is a composite of (1) accuracy (2) confidence (3) repeatability.
- Analytics data score is a composite of (1) data storytelling, (2) data combinations, (3)data analysis type
- Presentation of data story at Final Event consists of a 5 minute tabletop widescreen demo, with 5 minutes of questions.
- Results are presented as code and related documentation for digital interactive or static outcomes.
- Can be automated, but does not need to be. Can be entirely manual.
1.) INNOVATION/RELEVANCE – 20% OF SCORE
Product – Identify a new and different way to provide BDMs with resources through a tool that helps them solve a real problem.
Analytics – Design a data analysis that seeks to address a problem or answers a question relevant to a real problem for BDMs.
2.) IMPLEMENTATION/DATA STORY – 10% OF SCORE
Product – Design and develop a tool based on the BDM as the primary user. All entries should assist the user in easily navigating the tool to find relevant info pertinent to them. The tool must be functional and publicly accessible by Semi-Final submission, with a clear roadmap of how all proposed components would be completed by the Final Event.
Analytics – Cleary define the issue and identify the specific question being analyzed. All entries should be easily digested with a clear and simple story that can be communicated effectively. The final analysis must be digital and publicly accessible by Semi-Final submission, with a clear roadmap of how any additional insights would be completed by the Final Event.
3.) QUALITY/TECHNICAL EVALUATION – 20% OF SCORE
Product – Ensure the product is well-built, has useful functionality that will be easily adopted by BDMs, and is based on the technology or code structure that are sustainable and scaleable. The final output must be a minimum viable product (MVP). This means a product that is available for use by public users. It should also allow for insights to be easily drawn from the experience. Both Semi-Final and Final submissions will be investigated for technical completeness. Product Track Technical Evaluation.
Analytics – Ensure the analytical method is valid and appropriate to the question being answered, and the design is Innovative, comprehensive, and efficient. Also that the model has an acceptable margin of error, a repeatable methodology, and the goals and conclusion of the analysis are clearly defined. The final output is easily digestible by the target audience and conveys the message with minimal to no additional interpretation. Both Semi-Final and Final submissions will be investigated for technical completeness. Analytics Track Technical Evaluation.
4.) PRESENTATION – 10% OF SCORE
Presentation scores for both the Semi-Final and Final rounds will be based on the materials provided in the team’s GitHub repository as they relate to what is presented. The Judges goal is to understand the team’s concept and/or analysis and results.
Semi-Final Presentation scores will be based on a recorded screencast of presentation slides with narrated audio as a “Virtual Presentation” and submitted in accordance with instructions found at GoCodeColorado GitHub Knowledge Base Semi-Final Submission Guidelines.
Finalist Presentation scores will be based on in-person delivery of presentation or demo and questions at the Final Event. Judges will have been given access to the competition repo prior to the event. GoCodeColorado GitHub Knowledge Base Final Submission Guidelines.
Product – Successfully explain how the idea facilitates the discovery of insights by the BDM using public data. The Finalist Teams in the Product Track deliver a 5 minute pitch presentation with 5 minutes for questions at the Final Event
Analytics – Successfully explain how the data analysis delivers insights to the BDM using public data. The Finalist Teams in the Analytics Track will present their data story at the final event as a 5 minute tabletop widescreen demo with 5 minutes for questions at the Final Event.
5.) USE OF DATA SOURCES – 40% OF SCORE
Product – Add value to public data and cogently deliver it to a BDM to help them with their decision-making process. Teams must provide descriptions of the data used, data sources and show how they have combined or analyzed the data to create new insights that help a BDM. Product Track Data Evaluation.
Analytics – Add value to the public data and cogently use it as part of an analysis to draw conclusions that answer a question asked by a BDM. Teams must provide descriptions of the data used, data sources, methods for obtaining and preparing the data for analysis and how their methods provide reliable and useful information to a BDM. Analytics Track Data Evaluation.