Play around with Gavel

## Tasks for Gavel system this year

### Evaluate the Gavel System from Last Year:

- Review the issues faced last year with the Gavel system.
- Identify areas that need improvement based on the problems encountered.

### Separate Gavel System for Software and Hardware:

- Develop a strategy to efficiently separate the Gavel system for software and hardware projects.
- Ensure that judges are appropriately assigned to their respective categories.

### Section for AWS Projects:

- Create a dedicated section for AWS projects to meet AWS evaluation requirements.

### Subdivide Individual Software Category:

- Determine whether it's necessary to subdivide the individual software category into three sections.
- Assess whether this subdivision is beneficial or if it can be streamlined.

### Test Run of the System:

- Conduct a test run of the Gavel system to evaluate its effectiveness.
- Assess the impact of any changes made to the system based on the previous year's experience.

### Judging Completion Indicators:

- Establish clear indicators to determine when a group's judging process is complete.
- Enable students to leave once their section's judges have finished.

### Organizing Team Decision-Making:

- Consider bypassing the second round of judging and allow the organizing team to make final decisions.
- Use the Gavel system to shortlist projects but let the team decide the winners.

### Documentation and Communication:

- Document all decisions and changes made to the Gavel system.
- Communicate any updates or changes to judges, participants, and the organizing team.

### Continuous Improvement:

- Encourage ongoing feedback from judges, participants, and organizers to improve the system further.
- Be open to making adjustments based on feedback.

### Contingency Planning:

- Develop contingency plans for potential issues that may arise during the event.
- Prepare for unexpected situations to ensure a smoother event.

### Training for Judges:

- Provide training to judges, especially those evaluating AWS projects, to ensure they understand the criteria and process.

### Timelines and Deadlines:

- Establish clear timelines and deadlines for all phases of the event, from project submission to judging completion.

### Feedback Gathering:

- After the event, gather feedback from all stakeholders to identify areas for further improvement.

This list is based on the feedback from Eugene.

No files, tests, or entry points are named. Start by reviewing the Gavel issues and problems from last year, then turn the listed judging, AWS, training, timeline, and contingency concerns into a scoped plan. Done means the required decisions, test run, documentation, communication, and feedback process are defined.

Written by the indexing model from the issue text.