Partner School Agreement
Codeflow Research Collaboration
Study: From Coding to Co-Creating: Competency Frameworks for Human-AI Collaboration in Software Development Researcher: Davor Radic, IU International University of Applied Sciences Supervisor: Dr. Mark Menzel Contact: d.radic@roc-nijmegen.nl
1. Agreement Overview
This agreement is between the research team (Davor Radic, IU International University of Applied Sciences) and the partner school. It outlines the terms of collaboration for hosting an AI-integrated hackathon as part of an academic research study.
2. Researcher Responsibilities
The researcher agrees to:
- Provide all hackathon content, tutorials, and materials at no cost to the school
- Join remotely (via Microsoft Teams or Zoom) for the on-site coding sprint session
- Provide the Codeflow Recorder application and technical support for installation
- Ensure all data collection complies with EU GDPR / DSGVO regulations
- Pseudonymize all participant data (linked to participant IDs, not names) — no student names will appear in publications
- Provide consent form templates for students and parents/guardians
- Share the final research results and curriculum recommendations with the partner school
- Delete all raw research data within 2 years after the study concludes
3. Partner School Responsibilities
The partner school agrees to:
- Designate a faculty coordinator as the main contact person
- Provide a suitable classroom or lab with internet access and power outlets for the coding sprint day
- Schedule one on-site session (approximately 3 hours) within the agreed timeframe
- Distribute the tutorial link (codeflow.live/docs/tutorials) to students (1 week before the coding sprint)
- Distribute and collect signed consent forms from all participants (and parents/guardians for minors)
- Ensure participating students have laptops and required software installed (as specified in the Hackathon Playbook)
- Provide at least 1 supervising teacher/mentor present in the classroom during the coding sprint
- Complete a lightweight mentor observation checklist during the coding sprint (3 questions per team)
- Not share raw research data or student recordings with third parties
4. Hackathon Structure
The hackathon consists of two phases:
| Phase | Description | Duration |
|---|---|---|
| Preparation Phase | Students complete 6 tutorials at home (2 videos + 4 reading guides) covering AI tools, ethics, and Codeflow Recorder setup | ~60 min (self-paced, 1 week before) |
| Coding Sprint Day | On-site session: technical check-in, 1-hour recorded coding challenge, team presentations, surveys and peer evaluation | ~3 hours (1 morning) |
For the full detailed schedule, see the Hackathon Playbook.
5. Data Processing
| Item | Detail |
|---|---|
| Data controller | Davor Radic (IU International University of Applied Sciences) |
| Data collected | Screen recordings (1-hour coding sprint), keystroke frequency, paste events, window switches, survey responses, peer evaluation forms |
| Legal basis | Informed consent (GDPR Art. 6(1)(a)) |
| Storage | Encrypted Firebase servers, EU region |
| Access | Researcher and thesis supervisor only |
| Pseudonymization | All data linked to participant IDs, not names. Only the researcher holds the key linking IDs to identities. |
| Retention | Deleted within 2 years after study completion |
| Student rights | Access, rectification, deletion, restriction, objection, portability |
6. Publication & Acknowledgment
- The partner school will be acknowledged in the thesis (unless the school prefers anonymity)
- No individual students will be identifiable in any publication
- The partner school may reference participation in this research in its own communications
- Results may be published in the Master's thesis, academic conferences, and journals
7. Cost
There is no financial cost to the partner school. All materials, software, and support are provided free of charge.
8. Termination
Either party may withdraw from this agreement at any time. If the school withdraws before data collection, no data is retained. If withdrawal occurs after data collection, already-collected data will be deleted upon request.
Contact d.radic@roc-nijmegen.nl to receive the printable version of this agreement and discuss next steps.
Version 2.0 — March 2026