How to create a challenge on buidlbox

Creating a challenge on buidlbox is simple. To start, navigate to the "Challenges" section under the "Manage hackathon" tab in the hackathon dashboard. Click "Create a Challenge" and fill out the all the fields of the challenge form. Remember to be as thorough and descriptive as possible! 

Challenge Details 

Complete the Challenge Details by filling out all the fields in the form. Be sure to give your challenge a descriptive Title to attract participants to the challenge. 

1. Challenge Owner (visible to hackathon Admin only)

• If you are completing the process of creating a challenge on behalf of a hackathon sponsor, select their respective Guidl name under the drop down menu of the "Challenge Owner" field. 

      2. Title

• Be sure to give your challenge a descriptive title to attract participants to the challenge.

      2. Challenge Description

•  Be as descriptive as possible about what you want to see built. Challenges should be useful for your Guidl, but open-ended enough to allow for creativity from hackers. What do they need to create, and what framework is required?
  Ex: Build a [project] using [X tool/ API] that [theme statement].
  Ex: Build an application using React that helps make education accessible.

      3. Acceptance Criteria

• Acceptance criteria is a crucial section to be able to maintain integrity in case you decide to pay out a project partially, or pay out no projects at all in the respective challenge. You should be able to point at these acceptance criteria and state which one(s) were not met in case of a partial or no-pay scenario.
•  Consider what participants need to submit with their project and what constitutes a valid submission to win the prize. Share clear, concise, and detailed criteria for what you would consider a successful project.
• What will help you determine whether a submission passed a threshold of acceptable quality?      Please include any relevant contribution guidelines & standards.
• Would you like a demo/presentation included in the submission? (Recommended!). Be sure to    specify.
  
  💡 Tip: Have the judging criteria reflect some of the stated acceptance criteria. E.g: if you have an Acceptance Criteria of "Must include documentation" you might want to include "Documentation quality" as a judging criteria.

          Here are some reasonable asks: 

• Link to the working project 
• Link & access to the GitHub repository (public or private)
• 3-5 minute demonstration video
• Must be built using X tooling

       4. Tags 

Adding tags to hackathon challenges can help organize and categorize them, making it easier for participants to understand the specific themes or areas of focus and participate in challenges that align with their interests and skills 

To add a Tag, select one from the drop-down menu under "Tag". You can select as many tags as are relevant to that specific challenge, but keep it focused. We suggest no more than 3 tags per challenge.

Judging

Most commonly, hackathons set up one panel of judges made up of subject matter professionals asked to judge all of the eligible projects based on the same judging criteria. You may attach however many judges you want to be able to judge the challenge and then how many of those in total would need to judge each project for the project to be considered judged.

Adding Judges to each challenge

Note: Before inviting a judge to evaluate a challenge, ensure you first send them a judging invitation. The judge must accept this invitation before they can officially be added as a judge for the challenge. For detailed instructions, refer to the guide titled "How to Add a Judge."

To add a Judge, select the name of the Judge from the drop-down menu. You can add more than one judge per challenge.

The number of judges you can select to judge a challenge can vary depending on several factors, including the size of the event, the number of submissions expected, and the complexity of the evaluation criteria. However, as a general rule of thumb, having at least two to three judges for each challenge is recommended.

The advantage of having multiple judges is that it helps ensure the evaluation is fair and impartial. With two or more judges, you can reduce the risk of one person's biases or opinions influencing the evaluation outcome. Additionally, having multiple judges can provide different perspectives and insights into the submissions, leading to a more thorough and accurate evaluation.

Judging Criteria

Before you launch your hackathon, you should define the judging criteria and their weight. Both are important for participants to know how their projects will be judged.

• What are the criteria you want your judges to care about? Be sure to clearly describe what each criteria are measuring for participants and judges to be on the same page. 

Judging criteria should mirror what you would like the projects to focus on. Judging criteria may include:

• Innovation - Creativity, originality, novelty
• Implementation - Does the end result demonstrate quality software development and design?
• Impact - How big of an impact could the project have?
• Usability

Adding Judging Criteria 

Add the criteria in the field under "Judging Criteria" and select the score from 1 to X that the judges can award during the judging process. 

Continue adding additional criteria by selecting the "Add Criteria".

Note: There is no limit to the number of judging criteria you can add. 

Resources

Resources are a means to help your participants and your hackathon’s success. Adding resources is optional, however we highly recommend including any necessary resource to help participants build a fantastic project. Resources might include:

• Links to documentation 
• Example Data - This may include sample code, datasets, or APIs.

Adding Resources in buidlbox.io

To add a Resource, you can navigate to the resource section to add the resource URL and resource title. 

Click on the "Add Resource" sign to continue adding resources.

Note: There is no restriction on the number of resources you may incorporate.

 

Payout Information

To add the Prize amount and categorization of a specific bounty, complete the "Payout Information" modal in the "Create a Challenge" section. 

The payout information includes the following:

• Payout Chain 
• Payout Token
• Reward Type (Ranked Prize, Prize Pool or Other)
• Prize Details (Optional)

Note: "Ranked Prize" is a fixed reward for specific winning positions (ex. 1st Place, 2nd Place, 3rd Place). "Pool Prize" is a collective sum that is distributed among multiple winners based on their positions or performance."Other" may be selected for rewards that are not cash prizes (eg. merchandise, gift cards, tickets, internship opportunities, tech gadgets, etc.) We recommend specifying in detail what "Other" prize entails in the "Prize details" field. 

Once you have filled in all the fields to create your challenge, take a moment to review all the details closely. Ensure there are no errors and that everything is clear for participants to start working on their projects seamlessly. If everything looks good, proceed to click on the "Create Challenge" button. Congratulations! Your challenge has been successfully created.

Note: Please bear in mind that all challenges are subject to approval by the hackathon organizer (Admin) before they can be published on the landing page for participants to see and join.

Creating a Challenge as the Co-sponsor of a hackathon!

If you are co-sponsoring a hackathon, you will be able to create challenges by following the same steps listed in this article. Once the challenge has been created, it will be under "Pending"status and the organizing Guidl of the hackathon will have to review the challenge and "Accept Challenge". The challenges will be published to the hackathon landing page only by the organizing Guidl.