Gebruiker
4 min
The L&T Masterpiece serves as the core integration point for the Law & Technology master program at Erasmus School of Law. It is designed to bridge the gap between theoretical legal knowledge and practical application by requiring students to engage in two primary tracks: conducting an individual doctrinal legal research paper and developing a collaborative legal service innovation tool. The course emphasizes the development of interdisciplinary skills, specifically focusing on how lawyers can effectively communicate and collaborate with technical experts.
The course architecture is built upon four distinct tracks:
The course utilizes a diverse assessment structure where the final grade is a weighted combination of the research paper (40%), tool specifications (35%), jury presentations (15%), and Course Connectors (10%). Additional components, such as technology terminology exercises and group-work reflections, are graded on a pass/fail basis. The design process is iterative, requiring groups to move through stages of empathy, definition, ideation, prototyping, and testing, while maintaining a "group charter" to manage collaboration.
This course is critical because it forces students to move beyond abstract legal analysis. By requiring students to translate legal, ethical, and technical requirements into a functional design specification, the program prepares graduates to navigate the modern legal profession, where the ability to manage technology-driven change and collaborate with non-legal stakeholders is increasingly essential.
Sam: That's a smart design. It forces accountability at every decision point, not just at submission.
Alex: And it's reinforced by the "Tech Terms" assignments, assessed pass/fail. The goal is cross-domain fluency — ensuring students can communicate with developers without needing to be coders themselves. The syllabus frames this explicitly as minimizing translation loss between legal requirements and technical specifications.
Sam: Which is actually the core failure mode in most legal tech projects. The legal team and the engineering team end up talking past each other, and the gap opens at the requirements stage.
Alex: Exactly — and the program is designed to close that gap before students enter practice. There's also a clear generative AI policy worth noting: full disclosure is mandatory, every AI-generated citation must be verified against OSCOLA standards, and fabricated sources are an automatic fail. That's not a minor procedural note. It reflects the program's underlying argument — that the process of legal engineering matters more than the existence of a finished artifact.
Sam: So the deeper claim is that "legal engineer" should be a core professional competency, not a specialist niche.
Alex: That's the bet the program is making. Whether the market validates it is genuinely open — but as a curriculum design, it's a coherent response to a real structural gap between how law is taught and how legal technology is actually built and deployed. Thanks for listening to ResearchPod.