Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Day 1: Build the Foundation — Ingest, Search, Retrieve
Module 1: The Legal Engineer’s Landscape
- Learning objectives — understand the role, AI’s place in legal work, and the two critical risks that permeate every aspect.
- Topics
-
- The legal-engineer role and current market demand.
- AI applications: eDiscovery, review, contracts, research, investigations; plain-language explanation of the EDRM model.
- Build vs. Buy considerations.
- The two pervasive risks: confidentiality/privilege and defensibility.
Module 2: Legal Data Is Messy — Ingestion and Extraction
- Learning objectives — manage the reality of legal data at scale.
- Topics
- Handling 1,400+ file types, emails, PST files, scanned paper, load files (.dat/.opt); understanding critical embedded metadata.
- Text extraction (Tika), OCR, and deduplication strategies.
- Lab: FreeEed Ingestion — build an ingestion pipeline using a deliberately messy document set (emails/PSTs, scans, load files).
Module 3: Search and Retrieval — The Foundation
- Learning objectives — construct the core eDiscovery primitive: finding any information within any dataset.
- Topics — full-text search and indexing (Solr/Lucene); relevance, metadata, and date filtering; searching across OCR’d content.
- Lab: eDiscovery Search — index a corpus and perform real eDiscovery-style searches, including within OCR’d scans.
Module 4: RAG for Legal Documents — with Citations
- Learning objectives — implement RAG over legal documents that provides source citations.
- Topics
- Why retrieval, not fine-tuning, is preferred for sensitive material — ensuring the model never stores the documents.
- Chunking, embeddings, and critically, citations/provenance.
- Multi-document and thread summarization.
- Lab: Legal RAG with Citations — build a RAG Q&A system over a document set that answers questions using source citations.
Day 2: Make It Private, Defensible, and Shippable
Module 5: Privacy, Privilege, and Local Serving — The Privilege Trap
- Learning objectives — keep legal data local and certify its security.
- Topics
- Data flow when using cloud-based AI services.
- Privilege waiver, duty of competence, and the "private" spectrum (contractual vs. physical).
- Morgan v. V2X case study: why local deployment is court-defensible.
- Serving local models (Ollama/vLLM) and monitoring outbound traffic.
- Lab: Local Model + Egress Proof — run a local model end-to-end and use monitoring tools to prove no data egressed.
Module 6: Defensible AI Review
- Learning objectives — measure and document an AI review to ensure legal validity.
- Topics
- Court-acceptable metrics: recall, elusion, precision, ground-truth validation; TAR/active learning.
- Transparency (rationale for coding) and reproducibility — pinning the model version, fixing settings, and logging all actions.
- Creating a "defensible case snapshot" allowing others to re-run your review later with identical results.
- Lab: Defensible Review — evaluate an AI review against blind ground truth and produce a reproducibility bundle.
Module 7: Ship It — Workflow, Private Deployment, and Governance
- Learning objectives — assemble components into a workflow, deploy privately, and score the system.
- Topics
- Multi-step legal workflows (ingest → search → summarize → review → produce) with human-in-the-loop processes.
- Private/on-premises deployment essentials (containerization; keeping data in-house).
- AI governance for legal contexts and scoring systems using SAIS-100 (the Elephant Scale Secure AI Score).
- Lab: Score and Package — wire a multi-step workflow, score it via SAIS-100, and package it for private deployment.
Capstone (integrated across Day 2)
- Construct a private, defensible legal-AI application end-to-end — ingest a messy corpus, search it, answer questions with citations using a local model, measure review defensibility, and package for private deployment.
- Participants leave with a portfolio project that mirrors the responsibilities of a legal engineer.
Optional Day 3 / Advanced Modules (deliverable as a 3rd day or a modular series)
- Investigations: Entities, Relationships, and Timelines — extract people/orgs/dates, reconstruct email threads, build chronologies, map near-duplicates and document lineage. Lab: build a timeline and entity/relationship view.
- Agentic and Multi-Step Legal Workflows (deep dive) — advanced orchestration, contract analysis, multi-doc synthesis, tool use, and guardrails as design principles. Lab: build a multi-step workflow with a human checkpoint.
- Deployment at Scale — on-premises and appliance deployment, distributed processing for large volumes, regulated environments (CJIS, government, higher-ed), hardware sizing. Lab: containerize and scale a processing job across workers.
- Governance and Compliance Deep-Dive — the AI-regulation landscape (100+ US state AI laws, the EU AI Act), audit requirements, and a full SAIS-100 governance audit. Lab: audit a legal-AI system against a governance/defensibility checklist.
Requirements
- Proficiency in Python and basic API usage.
- Helpful but not required: Familiarity with LLMs at a user level (no ML background needed — we develop the conceptual framework).
- No legal background required — essential legal concepts are taught within practical contexts.
Target Audience
- Software and AI engineers transitioning into legal technology.
- Engineers at legal-tech companies requiring deeper domain-specific knowledge.
- Tech-savvy legal, eDiscovery, or information-governance professionals who wish to build solutions rather than just purchase them.
- Individuals aiming for "legal engineer" or "AI legal engineer" roles.
14 Hours
Testimonials (1)
That i gained a knowledge regarding streamlit library from python and for sure i'll try to use it to improve applications in my team which are made in R shiny
