University hackathon: a student project submission pack
A template for university hackathon organizers covering project materials, individual contributions, submission deadlines and judge access checks.

A template for university hackathon organizers covering project materials, individual contributions, submission deadlines and judge access checks.

There is half an hour left before the final. One team is replacing its slides, another is trying to get repository access, and a third thought sending the project to the chat would be enough. There is little time to explain the task now. Submission requirements need to be clear to participants, instructors and judges before the hackathon starts.
At Stavleak, we suggest connecting the required materials to the learning objective and the review method. What work will the student submit? How will a judge open it? How will the instructor see what each participant learned? A small pack answering these three questions is enough. Adapt the template below to your university's rules.
The team project and a student's individual contribution are different things. One experienced participant may build a good prototype. Another student's research or testing may not appear on the final screen. Identify the shared competition materials separately from the individual reflection that shows learning.
If the hackathon counts toward a course grade, the responsible instructor sets the requirements under the university's procedures. Participants need to know in advance which materials are for the competition and which are for academic assessment. Do not automatically turn a team's place in the final into an individual course grade.
Add these fields at the top of the requirements document:
"Send the materials in the evening" is not enough. A record saved in a form may also differ from a submitted project. The organizer should show the actual acceptance indicator and ask participants to check it.
If the deadline changes, notify every team through the same channel. Permission given in a private chat does not replace the shared rules. State which materials the change applies to and when it takes effect.
The list below is for a student hackathon with software projects. If participants submit research, a device or a design, change the materials to suit that result. You do not need to make every item mandatory: do not request a file solely to increase the pack's size if judges will not use it.
Attach conditions covering file types, sizes, video length and presentation language to this list. The organizer chooses specific limits based on the submission system and the time available for judging. Do not copy them unchanged from another hackathon.
Do not require students to account for every activity minute by minute. Offer this template instead:
Evidence can be a link to a file, a change, a test result or research notes. Students should not describe themselves as the authors of the entire project when explaining their own contribution. If the work was shared, they should say it was done together.
Do not use commit counts as the sole measure of individual contribution. Investigating a bug, speaking to a user, preparing tests and pair programming leave different traces. An instructor needs to see the student's understanding of a decision as well as the amount of work.
Checking the pack from its author's account is not enough. The organizer should accept a test project and open it with the permissions assigned to a judge. Check the repository, slides, video and demo separately.
Do not require confidential materials to be made public. Agree on the judges' access method in advance. Do not include a student's personal password, a live access token or another person's data in the project description. Prepare safe data and restricted access for the demo.
If an external service fails, state in the rules which alternative will be accepted. Allowing a video does not by itself remove a requirement for a working prototype. The team needs to know which evidence the judge will use.
Identify the version of the accepted materials. If corrections are permitted, apply the same procedure to every team. Silently replacing the original work with a later file makes assessment harder to follow.
If a judge cannot open the materials, the organizer records the issue and follows the procedure published in advance. Keep the contact request, technical check and assessment decision together in one record. This helps explain to the team what happened.
Assessment of learning may continue after the final. Once the project has been reviewed, the instructor can return to the individual reflection and ask the student to explain one decision. Keep the competition score separate from the learning conclusion drawn from that conversation.
Want to host a university hackathon on Stavleak? We can organize the event for you, help with selected stages or provide the event workspace for you to organize it yourself. Start preparing with the organizer materials. Find more guides in the Stavleak resource centre.
Take it further
Open organizer materials in Kazakh