1. Hackathon Overview

1.1 Objective
The Rebuild Green Hackathon aims to foster collaboration and innovation in sustainable building practices, with a particular focus on utilizing straw panels provided by Modulina to reduce CO2 emissions and contribute to the green rebuilding of Ukrainian cities.
1.2 Significance
Projects must align with the hackathon’s transformative goals for municipal decision-making, incorporating circular construction methods and bio-materials, including but not limited to prefabricated straw panels.

2.Structure of the Hackathon
2.1 Three Stages
The event is divided into three key stages:

• Stage 1. Ideation and Planning

Teams are encouraged to listen to the lectorium part and, after reviewing the provided materials and recorded sessions from invited experts and mentors, develop innovative ideas related to the tasks set by the municipalities. These tasks are expected to be addressed through sustainable methods using biomaterials and eco-technologies.

• Stage 2. Development and Collaboration

Teams work on their projects, focusing on interdisciplinary collaboration online, starting from September 28.

• Stage 3. Presentation

On October 23, teams will present their comprehensive solutions to the jury on Demo Day, which should include architectural and engineering vision, construction solutions with biomaterials, and integrated eco-technologies. The Demo Day will be held in a hybrid format, both offline in Kyiv and online for those unable to attend in person.

3.Mentorship Program
3.1 Mentor Involvement During Proposal Development
Participants (teams) will have access to mentors from various fields such as bio-construction specialists, architects, marketers, and impact strategy experts, who will help develop the idea into a comprehensive project concept.
3.2 Mentor Support During the Crash Test
Mentors will guide teams in improving their solutions and preparing an impactful presentation, ensuring a professional and comprehensive approach to presenting the proposal for the municipal case before the jury.

4.Team Organization
4.1 Teams are expected to self-organize, bringing together participants with diverse skills. If a person registers without a team, the facilitator will ensure that this person joins a team with other registered participants. Teams are allowed to attract additional team members during the hackathon, but such participants must register under the general guidelines.
4.2 Teamwork and collaboration are essential, particularly during the development and presentation phases. The team that creates the project and wins the prize will be the team considered for implementing the proposed solution/vision/project.

5.Project Preparation
5.1 Teams must prepare their projects based on the presentation structure provided by the organizers. Projects may involve the use of straw panels as well as other technologies, but the main prize, Modulina straw panels, will be awarded to the best project designed using straw.
5.2 Teams must present their projects to the jury on October 23 in the order determined by the organizers. Video presentations and presentation materials (ppt) must be submitted to the organizers no later than 6:00 PM Kyiv time on October 21.

6.Eligibility and Requirements
6.1 Teams must consist of individuals with diverse knowledge and experience, including but not limited to construction, architecture, sustainability, and marketing. All team members agree that if they refuse to participate in project execution, they will be replaced by another team member as proposed by the remaining team members.
6.2 For future participation, teams are expected to have implemented or proven projects that demonstrate the practical application of their ideas.

7.Logistics and Communication
7.1 All participants must register their teams before or during the hackathon. Registration details will be provided via official channels.
7.2 A WhatsApp group will be used for communication throughout the event. Participants are expected to actively engage in these channels for updates and coordination.

8.Budgeting and Resources
8.1 Teams must carefully plan their budgets, including the use of Modulina straw panels, which are provided for 200 sqm of walls. If the winning project exceeds this capacity, additional material can be provided based on a prorated calculation and supply of the required additional square meters of straw wall panels on special terms for hackathon participants.
8.2 Teams may select construction partners, whether local or international, depending on the project’s goals.

9.Rules of Participation
9.1 Participants are encouraged to actively engage with mentors, collaborate with team members, and contribute to the success of the hackathon.
9.2 Teams must adhere to the hackathon schedule, including deadlines for project submission and presentations.
9.3 Participants must uphold ethical standards throughout the event, ensuring fair competition and respect for others’ ideas.

10.Support and Resources
10.1 Modulina provides mentorship support and prefabricated materials in amounts set forth in a memorandum of cooperation.
10.2 The organizers support participants throughout the hackathon.

11.Winning and Future Opportunities
11.1 Winning teams may receive prizes and potential funding opportunities for their projects, not only from Modulina Straw Panels but also from any other stakeholders or beneficiaries of the hackathon.
11.2 None of the organizers or sponsors of the hackathon are responsible for the actual construction or implementation of the project after the event. However, the organizers commit to supporting the winning team, making it more competitive, and helping secure the necessary resources for project implementation during the acceleration program in January-March 2025.
11.3 Teams with implemented projects will be considered for participation in future hackathons and related events.
11.4 Every team that did not receive the main prize but gained support from a municipality will also be eligible for support from the hackathon organizers during the acceleration phase, aimed at making the project more competitive and securing the necessary resources for project implementation.

12.Copyright and Scaling of Solutions
12.1 All project concepts created during the hackathon are the intellectual property of the team and belong equally to all team members who were designated as part of the specific hackathon team at the time of team formation and those who joined the team during the project development, up until the crash test on 19/10.
12.2 By participating in the hackathon, the team agrees to grant the hackathon organizers non-exclusive rights to distribute the created project concepts to municipalities that need similar solutions so that these municipalities can apply for necessary funding from financial and charitable organizations. It is mandatory to mention all team members who contributed to the concept as authors, and to ensure the involvement of those responsible for specific parts of the future project implementation—the team members. Participants designated by the team as potential future project contributors are not considered authors of the concept for the purposes of this hackathon. The selection of partners and suppliers remains the right of the municipal body in coordination with the team representative who has been designated as the leader/project manager.
12.3 This rule also applies to the scaling of project concepts (solutions) created by the teams in other regions of Ukraine by promoting these proposals to other municipalities by the hackathon organizers, provided that all team members are properly credited as authors in all public and non-public communications and/or are involved in the further implementation of these solutions on a priority basis.
12.4 If during the team’s work at any stage of joint solution creation, divergent ideas emerge, the team may submit more than one concept for the jury’s consideration, indicating in the team composition all members who worked on the task from the moment of its creation, while also identifying the leader/project manager according to who will execute the proposed solution. If one of these solutions wins the hackathon, the team indicated in the proposal is the winner and retains all rights mentioned in point 12.1. However, the executor of the solution will be the participant(s) specified in the presentation as directly responsible for the future implementation of the project. Those participants whose views diverged from the team are considered members of the team and co-authors of the solution only by virtue of their participation in the team at various stages of the solution’s creation but will not be directly involved in the implementation of that specific solution.
12.5 Each team member has the right to publish the project concept after the hackathon, provided they mention all team members who participated in the hackathon from the time of the team’s formation, regardless of whether that person will be a future participant in the execution of the solution or not.

13.Evaluation and Scoring System
13.1 Projects (ppt presentation and pre-recorded video) are evaluated by the jury based on a predefined set of criteria using a scale from 0 to 10. The total score for each project will be the sum of points awarded by all jury members after the first round of evaluation. This round is mandatory for all jury members, and scores must be submitted to the organizers before the start of Demo Day.
13.2 Jury members are encouraged to attend Demo Day to meet the teams, ask questions, and rank the projects from first to last place based on overall impressions. This ranking will affect the scores from the first round through a coefficient system:
Example:

• After the first round:
• Project 1: 58 points
• Project 2: 48 points
• Project 3: 48 points
• Project 4: 50 points
• Project 5: 55 points
• Project 6: 57 points
• After the second round (with coefficients applied):
• Project 6: 57 × 1.1 = 62.7 points
• Project 3: 48 × 1.05 = 50.4 points
• Project 5: 55 × 1.0 = 55 points
• Project 1: 58 × 0.95 = 55.1 points
• Project 4: 50 × 0.9 = 45 points
• Project 2: 48 × 0.85 = 40.8 points

13.3 In the event of a tie, the team with the highest score from the judge representing the municipality for which the project was designed will be declared the winner. If this also results in a tie, the team with the highest score from the general sponsor, Modulina, will be declared the winner.
13.4 If the highest-scoring project does not include Modulina panels, the victory will pass to the next highest-scoring project that uses Modulina panels.
13.5 If multiple teams remain tied for first place after all criteria have been applied, the jury may give the teams one minute to present additional arguments. After this, the judges will deliberate in a separate room and announce the final winner of the Rebuild Green Hackathon 2024.

14.Contact and Inquiries
14.1 For any questions or further information, participants can contact the organizers via the provided communication channels such as email at ceo@hub-synchro.space or the Rebuild Green Community WhatsApp group.
14.2 All confidential questions to mentors and municipalities should be addressed using special Google forms provided by the organizers.
14.3 To maintain confidentiality of solutions, organizers provide separate team groups within the WhatsApp community to facilitate communication and the working process.
14.4 All additional information and changes to these rules will be addressed through the WhatsApp Rebuild Green Community group to ensure that all relevant parties have access to the information.
14.5 The technical tasks from the municipalities provided at the beginning of the hackathon are considered relevant and sufficient for the program. Any specific requests from teams will be reviewed by the municipality, and if feasible within the timeframe, will be provided to the hackathon organizers. Any new information provided by the municipality in addition to what was initially provided will be made available in the shared Google Drive folder, accessible to all teams working on the task, not just the team that made the request.