Terms and Conditions

1. General Information

2. Participation

3. Objective and Problem Submission

  1. Call for Submission of Topics and Teams:
    The competition will officially commence with a call for submission of topics and team registration issued by the Organizing Committee. This call invites participants to propose digitalization challenges from the judiciary or public administration that can be solved using digital technology.
  2. Problem Identification and Submission:
    • Interested Parties and also Participants may propose practical problems related to legal or administrative processes within the judiciary or public administration. These problems should not have any existing open-source solutions.
  3. Approval of Topics:
    • The Organizing Committee will review and approve all submitted topics. After consulting with the Programme Committee, the Organizer will publish the final approved topics, making them available for all teams to work on.
  4. Topic Selection:
    • Topics will be announced publicly. Once the topics are released, teams will have the opportunity to choose any approved topic and begin work. The same topic may be chosen by several teams.

4. Process of the Competition

  1. Research and Consultation Period:
    Following the publication of the topics and teams, participants will have at least 10 weeks to conduct research, begin working on an executable prototype and consult with relevant stakeholders, including judiciary or public administration officials, to refine their solutions.
  2. Hack Date:
    The date for the Hack will be set no earlier than 10 weeks after the publication of the topics and teams. On this date, participants must present their solutions publicly, including an executable prototype.
  3. Prototype Requirement:
    Each team must produce an executable prototype that demonstrates the functionality of their solution. Prototypes can be created using traditional coding methods, no-code platforms, or AI tools that support automated coding. To the extent solutions are based on software libraries or other tools, such libraries or tools need to be available open source.
  4. Documentation and Publication Material: Teams must submit documentation and publication materials on the Hack Date, including:
    • The problem definition and the chosen solution
    • A detailed report on the research conducted
    • The design and coding approach
    • The technology used and any code generated
    • Input and feedback from mentors, in particular from the judiciary or public administration received during the research phase
    • Open Licence Statement
    • Commitment for Publication
  5. Public Presentation and Feedback:
    Teams will present their solutions and engage in a public discussion with the jury and audience. They may refine their solutions based on feedback received at the Hack. The refined solution, documentation and publication materials can be submitted up to one week after the Hack Date.
  6. Judging and Winner Announcement: At the end of the Hack the Jury will deliberate and announce the winning teams based on the judging criteria.

5. Committees and Jury

  1. Organizing Committee and Programme Committee:
    • The Organizing Committee will oversee the administration and logistics of the Hackathon. The Organizing Committee is appointed by the Organizer.
    • The Programme Committee will provide strategic direction and review the proposed topics and teams. The Programme Committee is appointed by the Organizer.
  2. Jury Selection:
    • The Jury will be appointed by the Organizer based on recommendations from the Programme Committee, will consist of at least three members.
  3. Exclusion of Committee Members:
    • Members of the Organizing Committee and the Jury are excluded from participating as competitors in the Hackathon.

6. Technology and Tool Usage

7. Scientific Documentation and Publication

8. Intellectual Property and Licensing

9. Use of Data

10. Judging Criteria

Solutions will be judged on:

11. Prizes and Recognition

12. Disclaimers and Rights of Organizer

13. Privacy Policy for the “Law As Code” Hackathon

14. Choice of Law

15. Publications, Dates and Timeline