U.S. flag An official website of the United States government
Dot gov

The .gov means it's official.
Federal government websites always use a .gov or .mil domain. Before sharing sensitive information online, make sure you're on a .gov or .mil site by inspecting your browser's address (or "location") bar.

SSL

This site is also protected by an SSL (Secure Sockets Layer) certificate that's been signed by the U.S. government. The https:// means all transmitted data is encrypted - in other words, any information or browsing history that you provide is transmitted securely.

Develop Submission Requirements

Develop Submission Requirements

develop pencil and ruler icon

DEVELOP

In this phase you'll determine the challenge structure and implementation timeline. During this critical step, you'll work with internal groups to establish eligibility and submission requirements, terms and conditions, and judging criteria. You'll connect with your communications team to outline your announcement and ongoing outreach strategy to engage potential solvers.

Other Phases

discover books phase icondevelop pencil and ruler iconconduct wheel iconaward star medal icontransition hand and star icon

Develop Submission Requirements

Your target audience has to understand what you want. Develop appropriate requirements for challenge participants to follow in their submissions. Some challenges include detailed rules that apply to the submission and judging process to maintain fairness. For example, a prototyping or technology development challenge may have rules restricting the weight of a submission or how technologies interface to power sources.

Be clear. Participants and judges will thank you.

Key Takeaways

1. Be explicit.

Decide during the planning process what criteria are important for solutions to meet. Document these clearly and explicitly.

If you're asking participants to develop a website, specify which web browser versions, devices and operating systems it should support. Participants will have a better understanding of what's required of their solutions, and your team will have a legally justifiable method for disqualifying any that fail to meet these criteria.

Certain terms and expressions mean different things to different people. Your requirements should leave no room for interpretation.

For example, a submission deadline of 11/10/2025 would commonly be interpreted as November 10, 2025, in the United States. But if your challenge is open to those outside the country, some participants may think the deadline is October 11, 2025.

2. Don't be overly constraining.

It's good to be explicit, but artificial constraints can turn off potential solvers. Try to be as broad as possible in your submission requirements. For example, allow graphic designers to use a variety of file formats, and allow coders to use different programming languages.

Still have questions?

Contact the Team

Case Studies